BSOD Unsure of Error Code but says Display Driver Error


  1. Posts : 3
    Windows 7 Home Premium 64 bit
       #1

    BSOD Unsure of Error Code but says Display Driver Error


    I keep getting a display driver error and then the computer crashes with the BSOD. It happens quite often but I can't get the error message.

    I checked my display drivers and according to the device manager, the drivers are up to date. I believe I have a AMD Radeon HD 7570

    I don't know what information to give someone, but please help.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi hmedina62.
    hmedina62 said:
    I keep getting a display driver error
    Can you be a bit more specific? Do you get any popup balloon from system trey like this one?



    Anyway, the issue is definitely display related. A stop 0x116 is display/graphics failure. And the display driver is not up to date. It is on June 2012.

    Update it, but not to the latest. Uninstall your installed latest version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    When the update is done, stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    As it is a branded desktop, one info is very important, The PSU. Let us know the wattage of the PSU.

    Also, is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Let us know the results.
    _____________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800f2d14e0, fffff880047a9738, 0, 2}
    
    Unable to load image atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+8738 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800f2d14e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880047a9738, 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: 
    atikmpag+8738
    fffff880`047a9738 4055            push    rbp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`04a8e928 fffff880`054dc140 : 00000000`00000116 fffffa80`0f2d14e0 fffff880`047a9738 00000000`00000000 : nt!KeBugCheckEx
    fffff880`04a8e930 fffff880`054dbe4a : fffff880`047a9738 fffffa80`0f2d14e0 fffffa80`0f1da010 fffffa80`0a6aa410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`04a8e970 fffff880`05582f13 : fffffa80`0f2d14e0 00000000`00000000 fffffa80`0f1da010 fffffa80`0a6aa410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`04a8e9a0 fffff880`055accf1 : fffffa80`ffffffff 00000000`00461c24 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`04a8ea80 fffff880`0557e2e1 : fffffa80`0a6aa410 fffffa80`00000002 00000000`00461c24 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`04a8eab0 fffff880`055aaff6 : 00000000`00000000 fffffa80`0a6bbd50 00000000`00000080 fffffa80`0a6aa410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
    fffff880`04a8ebc0 fffff800`0312473a : 00000000`fffffc32 fffffa80`066ecb50 fffffa80`066dcb30 fffffa80`066ecb50 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`04a8ec00 fffff800`02e798e6 : fffff880`009c0180 fffffa80`066ecb50 fffff880`009cb0c0 4f2b7a52`676a6161 : nt!PspSystemThreadStartup+0x5a
    fffff880`04a8ec40 00000000`00000000 : fffff880`04a8f000 fffff880`04a89000 fffff880`0a043d40 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+8738
    fffff880`047a9738 4055            push    rbp
    
    SYMBOL_NAME:  atikmpag+8738
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4fd0c0e2
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
    
    FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm atikmpag
    start             end                 module name
    fffff880`047a1000 fffff880`047f9000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Thu Jun 07 20:25:30 2012 (4FD0C0E2)
        CheckSum:         0005AB65
        ImageSize:        00058000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 3
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

    Display Error


    That is the popup I see. I'll try your solution and let you know if it works. I had tried to uninstall and reinstall awhile back but couldn't get the driver to install. I did a system restore.

    Arc said:
    Hi hmedina62.
    hmedina62 said:
    I keep getting a display driver error
    Can you be a bit more specific? Do you get any popup balloon from system trey like this one?



    Anyway, the issue is definitely display related. A stop 0x116 is display/graphics failure. And the display driver is not up to date. It is on June 2012.

    Update it, but not to the latest. Uninstall your installed latest version of the display driver.

    Then clean up any possible leftover.

    Then install version 13.9 WHQL only.

    When the update is done, stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    As it is a branded desktop, one info is very important, The PSU. Let us know the wattage of the PSU.

    Also, is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Let us know the results.
    _____________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck 116, {fffffa800f2d14e0, fffff880047a9738, 0, 2}
     
    Unable to load image atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+8738 )
     
    Followup: MachineOwner
    ---------
     
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800f2d14e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880047a9738, 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: 
    atikmpag+8738
    fffff880`047a9738 4055            push    rbp
     
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
     
    CUSTOMER_CRASH_COUNT:  1
     
    BUGCHECK_STR:  0x116
     
    PROCESS_NAME:  System
     
    CURRENT_IRQL:  0
     
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
     
    STACK_TEXT:  
    fffff880`04a8e928 fffff880`054dc140 : 00000000`00000116 fffffa80`0f2d14e0 fffff880`047a9738 00000000`00000000 : nt!KeBugCheckEx
    fffff880`04a8e930 fffff880`054dbe4a : fffff880`047a9738 fffffa80`0f2d14e0 fffffa80`0f1da010 fffffa80`0a6aa410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`04a8e970 fffff880`05582f13 : fffffa80`0f2d14e0 00000000`00000000 fffffa80`0f1da010 fffffa80`0a6aa410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`04a8e9a0 fffff880`055accf1 : fffffa80`ffffffff 00000000`00461c24 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`04a8ea80 fffff880`0557e2e1 : fffffa80`0a6aa410 fffffa80`00000002 00000000`00461c24 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`04a8eab0 fffff880`055aaff6 : 00000000`00000000 fffffa80`0a6bbd50 00000000`00000080 fffffa80`0a6aa410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
    fffff880`04a8ebc0 fffff800`0312473a : 00000000`fffffc32 fffffa80`066ecb50 fffffa80`066dcb30 fffffa80`066ecb50 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`04a8ec00 fffff800`02e798e6 : fffff880`009c0180 fffffa80`066ecb50 fffff880`009cb0c0 4f2b7a52`676a6161 : nt!PspSystemThreadStartup+0x5a
    fffff880`04a8ec40 00000000`00000000 : fffff880`04a8f000 fffff880`04a89000 fffff880`0a043d40 00000000`00000000 : nt!KxStartSystemThread+0x16
     
     
    STACK_COMMAND:  .bugcheck ; kb
     
    FOLLOWUP_IP: 
    atikmpag+8738
    fffff880`047a9738 4055            push    rbp
     
    SYMBOL_NAME:  atikmpag+8738
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: atikmpag
     
    IMAGE_NAME:  atikmpag.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4fd0c0e2
     
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
     
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
     
    ANALYSIS_SOURCE:  KM
     
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
     
    FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
     
    Followup: MachineOwner
    ---------
     
    2: kd> lmvm atikmpag
    start             end                 module name
    fffff880`047a1000 fffff880`047f9000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Thu Jun 07 20:25:30 2012 (4FD0C0E2)
        CheckSum:         0005AB65
        ImageSize:        00058000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  4. Posts : 3
    Windows 7 Home Premium 64 bit
    Thread Starter
       #4

    Not working


    I have tried the directions below twice. I keep getting a failure error when trying to install the new driver. What is going on? I am attaching a screen shot of the error notices.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Well, try to install any other driver version.

    Because, though this popup is caused for a bad GPU, but it is better to see the behavior with multiple versions of the driver before deciding a failing GPU.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 00:54.
Find Us