locked
Blue Screen RRS feed

  • Question

  • Hello There, I got a Blue Screen Problem, i Got The Dumb Files and Reported Files

    Can you check them and tell me, What caused this Problem ?


    • Edited by Mr-Exlans Wednesday, April 9, 2014 11:22 AM
    Wednesday, April 9, 2014 11:20 AM

Answers

  • Thanks very much for the dump files!

    Both of the attached crash dumps are 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.
     
    Article here.

    0: kd> kv
    ChildEBP RetAddr  Args to Child              
    88c90b74 8c98e92c 00000116 8481a008 8c4169b0 nt!KeBugCheckEx+0x1e
    88c90b98 8c98f74b 8c4169b0 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d (FPO: [Non-Fpo])
    88c90bbc 8c9bf92c 00000000 00000102 855fe008 dxgkrnl!TdrIsRecoveryRequired+0xb8 (FPO: [Non-Fpo])
    88c90c34 8c9e9a32 fffffcfb 000c441c 00000000 dxgmms1!VidSchiReportHwHang+0x3c0 (FPO: [Non-Fpo])
    88c90c5c 8c9ea153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68 (FPO: [Non-Fpo])
    88c90c98 8c9c68f0 88c90c90 8597b9e8 8559fdd0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1 (FPO: [Non-Fpo])
    88c90d28 8c9eb4b7 855fe008 8287b3f1 855fe008 dxgmms1!VidSchiScheduleCommandToRun+0xaa (FPO: [Non-Fpo])
    88c90d3c 8c9eb573 855fe008 00000000 85048538 dxgmms1!VidSchiRun_PriorityTable+0xf (FPO: [Non-Fpo])
    88c90d50 82a4d66d 855fe008 a83dbe35 00000000 dxgmms1!VidSchiWorkerThread+0x7f (FPO: [Non-Fpo])
    88c90d90 828ff0d9 8c9eb4f4 855fe008 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    ^^ We can see from the call stack that the DirectX Kernel (dxgrknl) noted that recovery of the display driver was required due to a hang of the display driver as reported by DirectX's MMS (dxgmms1). However, since we got the 0x116 bug check, we can see that DirectX Kernel called the bugcheck as it did not recover the display driver successfully within the timeout period.

    ------------------

    1. Ensure you have the latest graphics/video card drivers via Lenovo's website. If you are already on the latest graphics/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 graphics/video card driver and many previous versions, please give the beta driver for your card a try if available.

    2. Update to Service Pack 1 ASAP: http://windows.microsoft.com/en-us/windows7/install-windows-7-service-pack-1

    3. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing conflicts:


    Avira removal - http://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/88

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    Regards,

    Patrick


    • Edited by Patrick Barker Wednesday, April 9, 2014 12:01 PM
    • Proposed as answer by ZigZag3143x Wednesday, April 9, 2014 12:11 PM
    • Marked as answer by 暁北 Wednesday, April 23, 2014 2:17 AM
    Wednesday, April 9, 2014 12:00 PM

All replies

  • Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick
    Wednesday, April 9, 2014 11:23 AM
  • http://multiupload.biz/93kxk0xarfkz/Blue Screen_MultiUpload.biz.rar.html

    Here Is the Dump Files


    • Edited by Mr-Exlans Wednesday, April 9, 2014 11:34 AM
    Wednesday, April 9, 2014 11:34 AM
  • Thanks very much for the dump files!

    Both of the attached crash dumps are 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.
     
    Article here.

    0: kd> kv
    ChildEBP RetAddr  Args to Child              
    88c90b74 8c98e92c 00000116 8481a008 8c4169b0 nt!KeBugCheckEx+0x1e
    88c90b98 8c98f74b 8c4169b0 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d (FPO: [Non-Fpo])
    88c90bbc 8c9bf92c 00000000 00000102 855fe008 dxgkrnl!TdrIsRecoveryRequired+0xb8 (FPO: [Non-Fpo])
    88c90c34 8c9e9a32 fffffcfb 000c441c 00000000 dxgmms1!VidSchiReportHwHang+0x3c0 (FPO: [Non-Fpo])
    88c90c5c 8c9ea153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68 (FPO: [Non-Fpo])
    88c90c98 8c9c68f0 88c90c90 8597b9e8 8559fdd0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1 (FPO: [Non-Fpo])
    88c90d28 8c9eb4b7 855fe008 8287b3f1 855fe008 dxgmms1!VidSchiScheduleCommandToRun+0xaa (FPO: [Non-Fpo])
    88c90d3c 8c9eb573 855fe008 00000000 85048538 dxgmms1!VidSchiRun_PriorityTable+0xf (FPO: [Non-Fpo])
    88c90d50 82a4d66d 855fe008 a83dbe35 00000000 dxgmms1!VidSchiWorkerThread+0x7f (FPO: [Non-Fpo])
    88c90d90 828ff0d9 8c9eb4f4 855fe008 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    ^^ We can see from the call stack that the DirectX Kernel (dxgrknl) noted that recovery of the display driver was required due to a hang of the display driver as reported by DirectX's MMS (dxgmms1). However, since we got the 0x116 bug check, we can see that DirectX Kernel called the bugcheck as it did not recover the display driver successfully within the timeout period.

    ------------------

    1. Ensure you have the latest graphics/video card drivers via Lenovo's website. If you are already on the latest graphics/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 graphics/video card driver and many previous versions, please give the beta driver for your card a try if available.

    2. Update to Service Pack 1 ASAP: http://windows.microsoft.com/en-us/windows7/install-windows-7-service-pack-1

    3. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing conflicts:


    Avira removal - http://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/88

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    Regards,

    Patrick


    • Edited by Patrick Barker Wednesday, April 9, 2014 12:01 PM
    • Proposed as answer by ZigZag3143x Wednesday, April 9, 2014 12:11 PM
    • Marked as answer by 暁北 Wednesday, April 23, 2014 2:17 AM
    Wednesday, April 9, 2014 12:00 PM