Blue Screen of Death while hibernating

#1
Every week or so I get a Blue Screen of Death. It happens when I open my computer after it has been hibernating. I have a Toshiba Satellite A505 running Windows 7 Home Edition.

I am attaching a zip file of the .dmp files from C:\Windows\Minidump

I look forward to a solution. Thank you.
 


Attachments

Captain Jack

Extraordinary Member
#2
Every week or so I get a Blue Screen of Death. It happens when I open my computer after it has been hibernating. I have a Toshiba Satellite A505 running Windows 7 Home Edition.

I am attaching a zip file of the .dmp files from C:\Windows\Minidump

I look forward to a solution. Thank you.
Hello and Welcome !!

Seems like the crashed has caused by igdkmd64.sys which belongs to your Intel Display Driver. I would recommend to uninstall the Drivers and download a fresh copy from Intel's website and install it and see if that fixes the problem.

Once of the best advice i seen about this VIDEO_TDR_FAILURE (116) crash is :

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling." - H2SO4
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit


Update the Following Drivers

Code:
FwLnk.sys    Sun Nov 19 19:41:04 2006
TVALZ_O.SYS  Fri Nov 09 08:38:41 2007
Thpevm.SYS   Tue Sep 04 06:43:06 2007
tdcmdpst.sys Tue Dec 11 07:59:00 2007
IntcHdmi.sys Mon Sep 22 19:19:56 2008
agrsm64.sys  Mon Nov 10 20:31:35 2008
Stacks & Bugchecks

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

=======================================================================

fffff880`02e30110 fffff880`044fbb74 dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02e30150 fffff880`045a2f07 dxgkrnl!TdrIsRecoveryRequired+0x114
fffff880`02e30180 fffff880`045d0d7e dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02e30260 fffff880`045b6bb1 dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02e302a0 fffff880`045c391c dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`02e303a0 fffff800`032ebd38 dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback+0xe0
fffff880`02e30410 fffff880`045c894c nt!MmRotatePhysicalView+0x6e8
fffff880`02e30650 fffff880`045c2eb8 dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0x148
fffff880`02e306e0 fffff880`045b8cf2 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x6f8
fffff880`02e30850 fffff880`045c5ebb dxgmms1!VIDMM_GLOBAL::PurgeAllocation+0x3a
fffff880`02e308a0 fffff880`045b260b dxgmms1!VIDMM_SEGMENT::PurgeContent+0x133
fffff880`02e30900 fffff880`045b23b3 dxgmms1!VIDMM_GLOBAL::ProcessSystemCommand+0xc7
fffff880`02e30990 fffff880`045cc231 dxgmms1!VidMmiProcessSystemCommand+0x47
fffff880`02e309c0 fffff880`045cb3bc dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`02e309f0 fffff880`0459d77a dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`02e30a20 fffff880`045cd927 dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
fffff880`02e30ab0 fffff880`045b24b9 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
fffff880`02e30b20 fffff880`045945c6 dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
fffff880`02e30b90 fffff880`044d07a1 dxgmms1!VidMmPurgeAllSegments+0xe2

====================================================================


fffff880`02e30108 fffff880`044fbef8 nt!KeBugCheckEx
fffff880`02e30110 fffff880`044fbb74 dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02e30150 fffff880`045a2f07 dxgkrnl!TdrIsRecoveryRequired+0x114
fffff880`02e30180 fffff880`045d0d7e dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02e30260 fffff880`045b6bb1 dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02e302a0 fffff880`045c391c dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`02e303a0 fffff800`032ebd38 dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback+0xe0
fffff880`02e30410 fffff880`045c894c nt!MmRotatePhysicalView+0x6e8
fffff880`02e30650 fffff880`045c2eb8 dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0x148
fffff880`02e306e0 fffff880`045b8cf2 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x6f8
fffff880`02e30850 fffff880`045c5ebb dxgmms1!VIDMM_GLOBAL::PurgeAllocation+0x3a
fffff880`02e308a0 fffff880`045b260b dxgmms1!VIDMM_SEGMENT::PurgeContent+0x133
fffff880`02e30900 fffff880`045b23b3 dxgmms1!VIDMM_GLOBAL::ProcessSystemCommand+0xc7
fffff880`02e30990 fffff880`045cc231 dxgmms1!VidMmiProcessSystemCommand+0x47
fffff880`02e309c0 fffff880`045cb3bc dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`02e309f0 fffff880`0459d77a dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`02e30a20 fffff880`045cd927 dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
fffff880`02e30ab0 fffff880`045b24b9 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
fffff880`02e30b20 fffff880`045945c6 dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
fffff880`02e30b90 fffff880`044d07a1 dxgmms1!VidMmPurgeAllSegments+0xe2
Hope this helps,
Captain
 


#3
Thank you!
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.