I would like an opinion for a system that has intel board (Intel Stone Desktop). I have installed windows 7 with 2 GB RAM. System randomly after 1 or 3 hours ( no standar time) goes to auto sleep and then blue screen. I have changed the memory but it stills do the same thing.. I will post dumb file and info.. If anyone knows something i would like to hear his opinion..
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
[SOLVED] System goes to Sleep Mode automatically and then Blue Screen..
- Thread starter csinner
- Start date
Hi,
The attached DMP file is of the VIDEO_TDR_FAILURE (116) bug check.
So, let me now explain what VIDEO_TDR_ERROR means. First off, TDR is an acronym for 'Timeout Detection and Recovery'. Timeout Detection and Recovery was introduced in Vista and carried over to Windows 7. Rather than putting exactly what Timeout Detection and Recovery does exactly, I'll just directly quote the MSDN article!
With this being said, if Timeout Detection and Recovery fails to recover the display driver, it will then shoot the 0x116 bugcheck. There are many different things that can cause a 0x116, which I will explain below:
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
FAILURE_BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
^^ Intel Graphics Driver.
Dated from 2009.
Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
Regards,
Patrick
The attached DMP file is of the VIDEO_TDR_FAILURE (116) bug check.
This indicates that an attempt to reset the display driver and recover from a timeout failed.
So, let me now explain what VIDEO_TDR_ERROR means. First off, TDR is an acronym for 'Timeout Detection and Recovery'. Timeout Detection and Recovery was introduced in Vista and carried over to Windows 7. Rather than putting exactly what Timeout Detection and Recovery does exactly, I'll just directly quote the MSDN article!
Timeout detection:
The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen.
To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play.
Preparation for recovery:
The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the driver collect hardware and other state information that could be useful for post-mortem diagnosis.
Desktop recovery:
The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.
With this being said, if Timeout Detection and Recovery fails to recover the display driver, it will then shoot the 0x116 bugcheck. There are many different things that can cause a 0x116, which I will explain below:
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
FAILURE_BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
^^ Intel Graphics Driver.
Code:
0: kd> lmvm igdkmd32
start end module name
8ea1e000 8ef1b000 igdkmd32 T (no symbols)
Loaded symbol image file: igdkmd32.sys
Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
Image name: igdkmd32.sys
Timestamp: Wed May 06 14:13:40 [COLOR=#ff0000][I][B]2009 [/B][/I][/COLOR](4A01D354)Dated from 2009.
Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
Regards,
Patrick
Has Sysnative Forums helped you? Please consider donating to help us support the site!