New
#1
Random BDOD. Restoring did not help.
Hello there. I haven't had a BSOD for months but lately they are back again. No idea where to start. Attaching the reports. Would appreciate any help
Hello there. I haven't had a BSOD for months but lately they are back again. No idea where to start. Attaching the reports. Would appreciate any help
Hello,
Could you take a look at this thread for your error code.
Let us know your findings.
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
Code:Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Usra\Downloads\PCNAME-20_05_2014_231749_83\051314-29858-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`032936d0 Debug session time: Tue May 13 20:10:45.982 2014 (UTC + 6:00) System Uptime: 0 days 0:00:31.950 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800b664010, fffff880049b72b0, 0, 2} Unable to load image 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+1392b0 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800b664010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff880049b72b0, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1392b0 fffff880`049b72b0 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`0238e9c8 fffff880`042ff140 : 00000000`00000116 fffffa80`0b664010 fffff880`049b72b0 00000000`00000000 : nt!KeBugCheckEx fffff880`0238e9d0 fffff880`042fee4a : fffff880`049b72b0 fffffa80`0b664010 fffffa80`0abb0d50 fffffa80`0abb6410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0238ea10 fffff880`043a5f13 : fffffa80`0b664010 00000000`00000000 fffffa80`0abb0d50 fffffa80`0abb6410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0238ea40 fffff880`043cfcf1 : 00000000`ffffffff 00000000`0000077a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0238eb20 fffff880`043ce437 : 00000000`00000102 00000000`00000006 00000000`0000077a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0238eb50 fffff880`043a12d2 : ffffffff`ff676980 fffffa80`0abb6410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0238ebf0 fffff880`043cdff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0ac55168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0238ed00 fffff800`033622ea : 00000000`04f8c888 fffffa80`0abafb50 fffffa80`06707b30 fffffa80`0abafb50 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0238ed40 fffff800`030b68e6 : fffff880`03088180 fffffa80`0abafb50 fffff880`030930c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0238ed80 00000000`00000000 : fffff880`0238f000 fffff880`02389000 fffff880`07302d40 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1392b0 fffff880`049b72b0 4055 push rbp SYMBOL_NAME: nvlddmkm+1392b0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 51427b3c FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner --------- 0: kd> lmvm nvlddmkm start end module name fffff880`0487e000 fffff880`05329000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Fri Mar 15 07:37:00 2013 (51427B3C) CheckSum: 00A8D47C ImageSize: 00AAB000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4