Sign in with
Sign up | Sign in
Your question
Solved

Multiple blue screen crashes while gaming.

Last response: in Windows 7
Share
November 18, 2013 10:40:15 AM

Hey there!

Since a couple of days I've been getting blue screen crashes during my gaming sessions. The games I've been playing are Xcom: Enemy Within and Path of Exile. Crashes occur anywhere from 10 minutes to 45 minutes into the game. Using the computer for anything else doesn't result in crashes. The error code seems to be different every time I get a blue screen, i've managed to note down several instances:

*** STOP: 0x0000008E (0xC0000005, 0X9317dd3c, 0Xa63EE7A9, 0x00000000)

*** STOP: 0x0000008E (0xC0000005, 0x83027D67, 0x981E1C73, 0x00000000)

*** STOP: 0X000001E (0xC00001D, 0X80789db0, 0x00000000, 0x00000000)

I haven't made any hardware changes in years. I have recently cleaned out my cpu cooler which was clotted with dust.

My setup:
OS: Windows 7 32bit.
CPU: Intel Core2Duo E6850 3.00 GHz
GPU: Nvideo Geforce GTX 460
RAM: 4Gb OCZ DDR2 SDRAM
PSu: Cooler Master Realpower Pro 620W
MOBO: Asus P5N32-E SLI Plus nForce 650i SLI

Most of the parts in my pc (with the exception of the GPU) are well over 5 years old.

Any idea what the cause of this problem could be?
a b 4 Gaming
a b $ Windows 7
November 18, 2013 11:10:27 AM

we will do some test first the memory stick one at the time with memtest or the win 7 module ,after the driver and the os does the are up to date then the 3 one use this to read the minidump iles in plain text and report the result http://www.resplendence.com /whocrashed also use this on the sensor parts for the system temp and details http://www.hwinfo.com/download.php

Best solution

a b $ Windows 7
November 18, 2013 11:52:12 AM
Share

A mis-behaving power supply will do that.
Related resources
November 18, 2013 12:06:44 PM

Running whocrashed provided the following report:

Spoiler
System Information (local)
computer name: RIK-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P5N32-E SLI PLUS
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488145408 total
VM: 2147352576, free: 1940844544



Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 17-11-2013 12:36:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-20404-01.dmp
This was probably caused by the following module: unknown_module_5f5e5d5c.sys (nt+0xDEBFC)
Bugcheck code: 0xFE (0x6, 0xFFFFFFFF86F400DC, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_5f5e5d5c.sys .
Google query: unknown_module_5f5e5d5c.sys BUGCODE_USB_DRIVER



On Wed 11-9-2013 11:44:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091113-19032-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07F)
Bugcheck code: 0x116 (0xFFFFFFFF8625C008, 0xFFFFFFFF9230DAF2, 0xFFFFFFFFC00000B5, 0xA)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 Wed 4-9-2013 11:27:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090413-23805-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
Bugcheck code: 0x116 (0xFFFFFFFF86A48008, 0xFFFFFFFF92323AF2, 0xFFFFFFFFC00000B5, 0xA)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 1-2-2013 14:35:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFC000001D)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFFFFF80789DB0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED



Conclusion
4 crash dumps have been found and analyzed. 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:

unknown_module_5f5e5d5c.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

It only reports on four crashes some of which are from some time ago. I am guessing most my recent crashes did not result in a minidump file? Since I've had crashes every day for the past 5 days which aren't in the raport.
a b 4 Gaming
a b $ Windows 7
November 18, 2013 12:28:09 PM

check all your driver if they are ut to date .
November 18, 2013 2:24:53 PM

All my drivers are up to date. I tried running the Windows Memory Diagnostics tool, it freezes at 21% mark. Guessing that isn't a good sign either.
a b 4 Gaming
a b $ Windows 7
November 18, 2013 8:41:42 PM

do you have 1 or 2 stick of memory ,sometimes this happening let it go to the end it does the same in my system .
November 19, 2013 2:53:22 AM

I have 4 memory sticks (each 1gb). I tried leaving the Memory Diagnostics tool on overnight, it was still at the same percentage in the morning after running for 7 hours.
a b 4 Gaming
a b $ Windows 7
November 19, 2013 9:32:25 AM

test one at the time or use memetest in the same way use the 5.01 for windows at the bottom ofr the link http://www.memtest.org/
November 25, 2013 5:03:58 AM

Finally managed to find the solution. Turns out it was the PSU, I've replaced it and the blue screens haven't returned :D .
a b $ Windows 7
November 25, 2013 9:41:00 AM

You can thank me upthread. :) 
!