New
#1
BSOD playing any game.
Hi, my computer keeps getting BSOD when i play games, and sometimes when im in windows.
Would really like some help, it's recently reinstalled (The computer)
- Windows 7 Ultimate x64.
Thank you!
Hi, my computer keeps getting BSOD when i play games, and sometimes when im in windows.
Would really like some help, it's recently reinstalled (The computer)
- Windows 7 Ultimate x64.
Thank you!
Hi BlackNinjah.
A stop 0x116 is a display related BSOD.
Are you overclocking?
As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.
Uninstall the existing version of the display driver using Display Driver Uninstaller and try 340.52 WHQL.
When done, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
Let us know the results.
______________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800db0a420, fffff8800f9d151c, ffffffffc000009a, 4} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+91951c ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800db0a420, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f9d151c, 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: ------------------ FAULTING_IP: nvlddmkm+91951c fffff880`0f9d151c 48ff255dc9ecff jmp qword ptr [nvlddmkm+0x7e5e80 (fffff880`0f89de80)] DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre STACK_TEXT: fffff880`0803ea48 fffff880`06ecc134 : 00000000`00000116 fffffa80`0db0a420 fffff880`0f9d151c ffffffff`c000009a : nt!KeBugCheckEx fffff880`0803ea50 fffff880`06e9f867 : fffff880`0f9d151c fffffa80`0bf1b000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0803ea90 fffff880`06ecbf43 : fffffa80`ffffd846 00000000`00000000 fffffa80`0db0a420 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3 fffff880`0803eb40 fffff880`06f9c03d : fffffa80`0d5ac760 00000000`00000080 00000000`00000000 fffffa80`0bd4a010 : dxgkrnl!TdrResetFromTimeout+0x23 fffff880`0803ebc0 fffff800`02d1f73a : 00000000`0407c15b fffffa80`0bf36060 fffffa80`096ae9e0 fffffa80`0bf36060 : dxgmms1!VidSchiWorkerThread+0x101 fffff880`0803ec00 fffff800`02a748e6 : fffff800`02bfee80 fffffa80`0bf36060 fffff800`02c0ccc0 fffffa80`0b70a8b0 : nt!PspSystemThreadStartup+0x5a fffff880`0803ec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+91951c fffff880`0f9d151c 48ff255dc9ecff jmp qword ptr [nvlddmkm+0x7e5e80 (fffff880`0f89de80)] SYMBOL_NAME: nvlddmkm+91951c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5414a236 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x116_image_nvlddmkm.sys FAILURE_ID_HASH: {1f9e0448-3238-5868-3678-c8e526bb1edc} Followup: MachineOwner --------- 3: kd> lmvm nvlddmkm start end module name fffff880`0f0b8000 fffff880`0fd8c000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Sun Sep 14 01:29:50 2014 (5414A236) CheckSum: 00C8E3A6 ImageSize: 00CD4000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4