Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Don't know what caused this BSOD

06 Sep 2012   #1

Win 7 Ultimate, x64-bit
 
 
Don't know what caused this BSOD

I don't know whats this BSOD about plz analyze and then tell me what to do....

My System SpecsSystem Spec
.

06 Sep 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

BSOD Analyze

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005de64e0, fffff880119a4654, 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+14a654 )

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: fffffa8005de64e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880119a4654, 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+14a654
fffff880`119a4654 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04426888 fffff880`07708000 : 00000000`00000116 fffffa80`05de64e0 fffff880`119a4654 00000000`00000000 : nt!KeBugCheckEx
fffff880`04426890 fffff880`07707d0a : fffff880`119a4654 fffffa80`05de64e0 fffffa80`05fadc00 fffffa80`05e5b1a0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`044268d0 fffff880`077aef07 : fffffa80`05de64e0 00000000`00000000 fffffa80`05fadc00 fffffa80`05e5b1a0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`04426900 fffff880`077d8b75 : 00000000`ffffffff 00000000`0006cdde 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`044269e0 fffff880`077d72bb : 00000000`00000102 00000000`00000000 00000000`0006cdde 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04426a10 fffff880`077aa2c6 : ffffffff`ff676980 fffffa80`05e5b1a0 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04426ab0 fffff880`077d6e7a : 00000000`00000000 fffffa80`05fa9d50 00000000`00000080 fffffa80`05e5b1a0 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04426bc0 fffff800`0356fe6a : 00000000`fffffc32 fffffa80`05f85b50 fffffa80`03c469e0 fffffa80`05f85b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04426c00 fffff800`032c9ec6 : fffff880`037d7180 fffffa80`05f85b50 fffff880`037e1fc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`04426c40 00000000`00000000 : fffff880`04427000 fffff880`04421000 fffff880`0d2aed70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+14a654
fffff880`119a4654 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+14a654

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  502297bb

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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: fffffa8005de64e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880119a4654, 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+14a654
fffff880`119a4654 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04426888 fffff880`07708000 : 00000000`00000116 fffffa80`05de64e0 fffff880`119a4654 00000000`00000000 : nt!KeBugCheckEx
fffff880`04426890 fffff880`07707d0a : fffff880`119a4654 fffffa80`05de64e0 fffffa80`05fadc00 fffffa80`05e5b1a0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`044268d0 fffff880`077aef07 : fffffa80`05de64e0 00000000`00000000 fffffa80`05fadc00 fffffa80`05e5b1a0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`04426900 fffff880`077d8b75 : 00000000`ffffffff 00000000`0006cdde 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`044269e0 fffff880`077d72bb : 00000000`00000102 00000000`00000000 00000000`0006cdde 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04426a10 fffff880`077aa2c6 : ffffffff`ff676980 fffffa80`05e5b1a0 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04426ab0 fffff880`077d6e7a : 00000000`00000000 fffffa80`05fa9d50 00000000`00000080 fffffa80`05e5b1a0 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04426bc0 fffff800`0356fe6a : 00000000`fffffc32 fffffa80`05f85b50 fffffa80`03c469e0 fffffa80`05f85b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04426c00 fffff800`032c9ec6 : fffff880`037d7180 fffffa80`05f85b50 fffff880`037e1fc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`04426c40 00000000`00000000 : fffff880`04427000 fffff880`04421000 fffff880`0d2aed70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+14a654
fffff880`119a4654 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+14a654

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  502297bb

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`1185a000 fffff880`1253f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Aug 08 22:45:47 2012 (502297BB)
    CheckSum:         00CC797E
    ImageSize:        00CE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Go through the link below:
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
My System SpecsSystem Spec
Reply

 Don't know what caused this BSOD





Thread Tools



Similar help and support threads for2: Don't know what caused this BSOD
Thread Forum
BSOD caused by sdd.dll BSOD Help and Support
What caused this BSOD? BSOD Help and Support
Don't know what caused this BSOD BSOD Help and Support
BSOD when playing games. BlueScreenView says ntoskrnl.exe caused BSOD BSOD Help and Support
Don' know what caused BSOD BSOD Help and Support
Just got a bsod, would like to know what caused it BSOD Help and Support
BSOD was caused by ? BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:01 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33