Blue screen crash error, help!

  raiton12 15:23 11 Aug 2014
Locked

My computer (built a couple months ago) has been crashing recently. It happens mostly when I play games, but it does occur randomly outside of games. I have run some tests with WhoCrashed which I will attach, I will also attach a list of parts used in the building of my computer and the after-crash report message from windows.

----------------------------Parts list------------------------------------------

Case: ENERMAX HOPLITE Mid-Tower ATX Case click here

CPU: AMD Phenom II X4 970 Quad-Core @ 3.5GhZ stock click here Fan: Cooler Master Hyper TX3 click here Asrock 970 Extreme3 click here

Memory/RAM: G.SKiLL Sniper 8GB (2x4gb) DDR3-1333 click here Supply: Raidmax Hybrid 2 530W click here Card: Sapphire Radeon HD 6870 click here Drive: Seagate Barracuda 500G 7200RPM click here pop up message on restart-----------------------------**

"windows has recovered from an unexpected shutdown"

Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033

Additional information about the problem: BCCode: 1000007e BCP1: FFFFFFFFC0000005 BCP2: FFFFF88004943EC8 BCP3: FFFFF880059A06A8 BCP4: FFFFF8800599FF00 OS Version: 617601 Service Pack: 1_0 Product: 256_1

Files that help describe the problem: C:\Windows\Minidump\081114-22074-01.dmp C:\Users\Powerhouse\AppData\Local\Temp\WER-47939-0.sysdata.xml

----------------Reports on crashes from WhoCrashed (multiple days)------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 8/11/2014 2:12:29 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081114-22074-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20EC8) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004943EC8, 0xFFFFF880059A06A8, 0xFFFFF8800599FF00) Error: SYSTEMTHREADEXCEPTIONNOTHANDLED_M file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 8/11/2014 2:12:29 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20EC8) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88004943EC8, 0xFFFFF880059A06A8, 0xFFFFF8800599FF00) Error: SYSTEMTHREADEXCEPTIONNOTHANDLED file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sun 8/10/2014 9:53:24 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081014-20295-01.dmp This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800495940C) Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFA0, 0x0, 0xFFFFF8800495940C, 0x0) Error: PAGEFAULTINNONPAGEDAREA file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sat 8/9/2014 11:35:04 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080914-84209-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x145744) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF96000165744, 0xFFFFF880069225F0, 0x0) Error: SYSTEMSERVICEEXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sat 8/9/2014 9:01:27 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080914-15568-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033BDC61, 0xFFFFF880098A7FC0, 0x0) Error: SYSTEMSERVICEEXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 8/9/2014 3:09:55 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080814-18033-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x3B (0xC0000005, 0x6D, 0xFFFFF88007ECEA40, 0x0) Error: SYSTEMSERVICEEXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 8/4/2014 2:26:18 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080314-19546-01.dmp This was probably caused by the following module: dxgmms1.sys (0xFFFFF88004421133) Bugcheck code: 0x50 (0xFFFFF8AAFFA1A5D8, 0x0, 0xFFFFF88004421133, 0x5) Error: PAGEFAULTINNONPAGEDAREA file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sun 8/3/2014 4:40:50 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080314-19110-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x46D8A) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF96000086D8A, 0xFFFFF880098E7000, 0x0) Error: SYSTEMSERVICEEXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sat 8/2/2014 7:20:10 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080214-16957-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA8007231060, 0x0) Error: DRIVERVERIFIERDETECTED_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 8/2/2014 4:55:57 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080214-23758-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x231AB3) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000291AB3, 0xFFFFF880099B55D0, 0x0) Error: SYSTEMSERVICEEXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Conclusion

39 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

CPU MoBo: Power Graphics Hard **------------------Windows

  raiton12 15:31 11 Aug 2014

ah, sorry. I couldnt find the original

  pravin007techno 09:50 28 Aug 2014

raiton12, hope you find the solution to your blue screen issue, if not just go with these one, i too totally confused with these, but hope you would get of it, i too had same problem with my windows system, later i followed some steps to skip from the problem, now I'm not getting the problem with blue screen any more!

  Fruit Bat /\0/\ 09:59 28 Aug 2014

You have problems with drivers all the shown reports indicate a driver problem.

Go into device manager click view - show hidden devices - they will show in light grey uninstall them all (its slow as you will have to do them one at a time)

reboot and see what happens then if still crashing you will need to uninstall and reinstall / update all your drivers one at a time until the problem stops

start with the graphics drivers.

This thread is now locked and can not be replied to.

Elsewhere on IDG sites

OnePlus 5 review

See the work of famous artists playing with toys

iPad Pro 10.5in (2017) review

Comment faire une capture d’écran sur un Mac ?