Sign in with
Sign up | Sign in
Your question

BSOD When Gaming

Last response: in Graphics & Displays
Share
January 27, 2013 2:41:42 AM

Whenever I'm in a gpu intensive game, my computer restarts and my gpu stops outputing a signal. When I restart my computer, all is fixed, until... well... until the circle comes again. I tried looking for a solution, then I noticed how personal BSODs tend to be so I got some information from my dump file.

Now whenever i test it, it shuts down when the gpu reaches about 78 Celsius...

PC Specs:
Spoiler

CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.8GHz
Ram: 8192MB
Video Card: NVIDIA GTX 660 TI
Power Supply: Thermaltake 750 watt
OS: Windows 7 64 bit


Mini Dump:
Spoiler
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a7670
Debug session time: Fri Jan 25 23:29:14.711 2013 (UTC - 5:00)
System Uptime: 0 days 0:34:09.929
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006a2a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb8c630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
nvlddmkm+ade630
fffff880`0fb8c630 4055 push rbp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`03fdba48 fffff880`06b43000 : 00000000`00000116 fffffa80`06a2a010 fffff880`0fb8c630 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03fdba50 fffff880`06b16867 : fffff880`0fb8c630 fffffa80`08f07000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03fdba90 fffff880`06b42e0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`06a2a010 fffff880`06a37dc0 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03fdbb40 fffff880`06a37ec1 : fffffa80`06754d50 00000000`00000080 00000000`00000000 fffffa80`08ed3010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03fdbbc0 fffff800`03178e5a : 00000000`02738f4c fffffa80`08ef7060 fffffa80`066ee040 fffffa80`08ef7060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03fdbc00 fffff800`02ed2d26 : fffff800`03054e80 fffffa80`08ef7060 fffff800`03062cc0 fffff800`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`03fdbc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+ade630
fffff880`0fb8c630 4055 push rbp

SYMBOL_NAME: nvlddmkm+ade630

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 506b3099

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

More about : bsod gaming

January 27, 2013 2:48:30 AM

Video Driver failure,

reinstall the drivers, uninstall the drivers through Nvidia control panel or Windows control panel, then use a utility like Driver Sweeper to clean out the remnants, then reinstall the latest drivers from the Nvidia site.

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006a2a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb8c630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

That basically means the driver crashed and Windows couldn't recover it so the system stopped displaying.
m
0
l
January 27, 2013 3:56:27 AM

darkspartenwarrior said:
Video Driver failure,

reinstall the drivers, uninstall the drivers through Nvidia control panel or Windows control panel, then use a utility like Driver Sweeper to clean out the remnants, then reinstall the latest drivers from the Nvidia site.

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006a2a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb8c630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

That basically means the driver crashed and Windows couldn't recover it so the system stopped displaying.


I just tried this, I no longer get a BSOD message upon crashing, but they still persist during high intensity games.
m
0
l
Related resources
January 27, 2013 3:58:39 AM

Are you sure you totally cleaned out the old driver?

If yes, then I have no idea, sorry >.>
m
0
l
a c 203 U Graphics card
January 27, 2013 4:11:29 AM

downlaod msi afterburner and make sure you make a fan profile that turns the gpu fan to 100 percent at 50 or 60c. could be the card is over heating. also download gpu-z make sure the card and the pci slot running at the right speed. could be a dirty card or pci slot and the card not running at it full speed.
m
0
l
January 27, 2013 2:49:39 PM

@smorizio: I checked everything with the tempetures, it seems normal (45 C when not gaming, about 79~80 C at the highest intensity moments). It seems the blue screen errors only pop up sometiems, but not everytime. I recentley got this one (a little bit different then the rest)

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff80003025290, the pool entry being checked.
Arg3: 0000000000ffffff, the read back flink freelist value (should be the same as 2).
Arg4: 0000000000ffffff, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x19_3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: WifiSvc.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002fc74b3 to fffff80002e9cfc0

STACK_TEXT:
fffff880`0850c3c8 fffff800`02fc74b3 : 00000000`00000019 00000000`00000003 fffff800`03025290 00000000`00ffffff : nt!KeBugCheckEx
fffff880`0850c3d0 fffff800`02eb02f6 : ffffffff`00000000 00000000`00000008 fffffa80`07237a10 fffff880`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`0850c4c0 fffff880`02c81a1b : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`091f2138 : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`0850c510 fffff880`02c82d8a : fffff880`0850c7d0 fffff8a0`00000070 fffffa80`08e61880 fffff880`0850c7d0 : nsiproxy!NsippProbeAndAllocateParameters+0x447
fffff880`0850c670 fffff880`02c848e8 : fffffa80`08e61880 fffffa80`08e617b0 00000000`00000000 fffffa80`08e617e8 : nsiproxy!NsippEnumerateObjectsAllParameters+0x266
fffff880`0850c860 fffff880`02c849db : fffffa80`08219b80 00000000`00000000 00000000`00000001 00000000`00000003 : nsiproxy!NsippDispatchDeviceControl+0x70
fffff880`0850c8a0 fffff800`031b3687 : fffffa80`094c8b30 fffffa80`094c8b30 fffffa80`08e618c8 fffffa80`08e617b0 : nsiproxy!NsippDispatch+0x4b
fffff880`0850c8d0 fffff800`031b3ee6 : 00000000`032de848 00000000`00000b64 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0850ca00 fffff800`02e9c253 : fffffa80`0a387060 00000000`032de7e8 fffff880`0850ca88 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0850ca70 00000000`74dc2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`032df0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74dc2e09


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+a53
fffff800`02fc74b3 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+a53

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a53

BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a53

Followup: Pool_corruption
---------
m
0
l
a c 203 U Graphics card
January 28, 2013 3:50:10 AM

video card bsod are heat...overclock to far or a power issue. start with making sure the gpou fan is maxing out to keep the card cool. check your power supply not the max output but the 12v leg for it wattage and amp and see if your near the max voltage/amps of it. some ps lie about there power supply output. you can try using hardware monitor to watch the power supply voltage output.
m
0
l
!