New
#1
BSOD playing Dota 2, error 0x000000116
thanks in advance for your help!
thanks in advance for your help!
Avast! is a frequent cause of BSOD's. Please uninstall it and use Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
- Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
- Help protect your PC with Microsoft Security Essentials
- Malwarebytes Free
You may also take a look at:NoteDo not start the trial version of MalwareBytes
------------------------
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
- Click on the
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow - read here
Run Disk Check on your Hard Drive for file system errors and bad sectors on it - read here
Monitor hardware temperature with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:
Follow this-
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800c1b1010, fffff880061c5700, 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+8ed700 ) Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800c1b1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff880061c5700, 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+8ed700 fffff880`061c5700 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`02b10a48 fffff880`04741054 : 00000000`00000116 fffffa80`0c1b1010 fffff880`061c5700 ffffffff`c000009a : nt!KeBugCheckEx fffff880`02b10a50 fffff880`04714867 : fffff880`061c5700 fffffa80`09cab000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`02b10a90 fffff880`04740e63 : fffffa80`ffffd84d 00000000`00000000 fffffa80`0c1b1010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3 fffff880`02b10b40 fffff880`0583803d : fffffa80`09fa8250 00000000`00000080 00000000`00000000 fffffa80`09c9f410 : dxgkrnl!TdrResetFromTimeout+0x23 fffff880`02b10bc0 fffff800`03318bae : 00000000`01c38480 fffffa80`09cc5060 fffffa80`05a8b840 fffffa80`09cc5060 : dxgmms1!VidSchiWorkerThread+0x101 fffff880`02b10c00 fffff800`0306b8c6 : fffff800`031f5e80 fffffa80`09cc5060 fffff800`03203cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`02b10c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+8ed700 fffff880`061c5700 4055 push rbp SYMBOL_NAME: nvlddmkm+8ed700 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 51c41788 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner --------- 7: kd> lmvm nvlddmkm start end module name fffff880`058d8000 fffff880`063bd000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Fri Jun 21 15:06:16 2013 (51C41788) CheckSum: 00AB87FF ImageSize: 00AE5000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4Test your Hardware for Stability and Heat Problems with Prime95:
How to Stress Test a Video Card with Furmark:
Test your CPU Stability with IntelBurnTest:
When Furmark fails - there are still several possibilities.
- The most common ones -
- - Faulty Graphics Card
- - Underpowered/Faulty PSU (what is your PSU? Brand? Model?)
- - Faulty RAM (this is unlikely as you say the Prime95 Blend test and Memtest didn't show errors?)
- - Faulty Motherboard (unlikely - as it's been replaced)
- - Faulty CPU (very unlikely - anyway, Prime95 passed)