BSOD Issues. atimpag.sys Stop 0x0...116 Error


  1. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
       #1

    BSOD Issues. atimpag.sys Stop 0x0...116 Error


    Dear 7 Masters
    I salute you and am hoping your vast wisdom can help out a novice.

    I have been experiencing BSOD's usually with the error STOP 0x00000116 at atimpag.sys.
    On reading the forums I was informed this was an error with the graphics card.
    So I uploaded the ATI AMD Catalyst Install Manager and I'm pretty sure it updated the driver from one from 2011 to one from 2013.

    However, the BSOD's have continued, about one every 2-3 weeks and often when I'm using a program with a lot of processes eg. Chrome or Spotify. (Latest-bsod.jpeg is attached)

    I ran a sfc /scannow this morning and got a message “Windows Resource Protection found corrupt files but was unable to fix some of them.” (scannow-result.jpeg)
    I attach the scannow results (CBS – copy.zip)

    I have updated my system details as required by sevenforums and attach the HARRY…zip file from dm-log-collector program.

    Any advice would be very much appreciated.
    Kind regards
    Harley Storey
      My Computer


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

    A stop 0x116 is a display/graphics related issue.

    Your graphics card is running with the latest supported driver, 13.9 WHQL. So we have least scope there to do with the drivers.

    Stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    Also let us know the wattage of the installed PSU.

    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 .
    _________________________________________________________
    Code:
    BugCheck 116, {fffffa800fcbd010, fffff88004154efc, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\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+8efc )
    
    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: fffffa800fcbd010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004154efc, 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+8efc
    fffff880`04154efc 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.17336 (debuggers(dbg).150226-1500) amd64fre
    
    STACK_TEXT:  
    fffff880`05fac9c8 fffff880`044bb134 : 00000000`00000116 fffffa80`0fcbd010 fffff880`04154efc 00000000`00000000 : nt!KeBugCheckEx
    fffff880`05fac9d0 fffff880`044bae3e : fffff880`04154efc fffffa80`0fcbd010 fffffa80`0fbea170 fffffa80`0f4c4010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`05faca10 fffff880`04562f13 : fffffa80`0fcbd010 00000000`00000000 fffffa80`0fbea170 fffffa80`0f4c4010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`05faca40 fffff880`0458ccf1 : 00000000`ffffffff 00000000`001b3bb6 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`05facb20 fffff880`0458b437 : 00000000`00000102 00000000`00000000 00000000`001b3bb6 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`05facb50 fffff880`0455e2d2 : ffffffff`ffb3b4c0 fffffa80`0f4c4010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`05facbf0 fffff880`0458aff6 : 00000000`00000000 fffffa80`0fe77d50 00000000`00000080 fffffa80`0f4c4010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`05facd00 fffff800`0310f456 : 00000000`fffffc32 fffffa80`0f8edb50 fffffa80`0ca78360 fffffa80`0f8edb50 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`05facd40 fffff800`02e672c6 : fffff880`009e9180 fffffa80`0f8edb50 fffff880`009f40c0 fffffa80`0db55ac0 : nt!PspSystemThreadStartup+0x5a
    fffff880`05facd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+8efc
    fffff880`04154efc 4055            push    rbp
    
    SYMBOL_NAME:  atikmpag+8efc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  517f30ef
    
    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
    ---------
    
    0: kd> lmvm atikmpag
    start             end                 module name
    fffff880`0414c000 fffff880`041ab000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Tue Apr 30 08:18:15 2013 (517F30EF)
        CheckSum:         000613E7
        ImageSize:        0005F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #3

    Thanks for your help Arc.

    I ran a Furmark test and attach a screenshot, didn't know if it would stop by itself but it ran for about 15 minutes before I stopped it.
    There were no crashes, BSOD's or artifacts (which I assume to be obvious video errors?) during the test.
    The interface has changed a little since the post instructions - under Settings I selected Burn-in, Xtreme burn-in, Post FX,Log GPU temperature and then "GPU stress test."

    I used the power supply calculator and it recommended a supply of at least 310W, my PSU is Antec Earthwatts EA 650W.

    I attach a Speccy screenshot and the snapshot URL is http://speccy.piriform.com/results/V...djLySJH5Vx7P7z

    Thanks for your kind help and assistance,

    cheers
    Harley
      My Computer


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

    Furmark ran fine. Temps are in control. Power supply is adequate. Driver is the latest one for your card.

    So apparently there is nothing to blame for the BSOD, provided you are not overclocking.

    I would prefer to wait for another BSOD before taking any more step.
      My Computer


  5. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #5

    Ok, thanks.
    I'll post again if there is another issue.
    kind regards
    Harley
      My Computer


  6. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #6

    BSODs on startup


    Hi Experts
    I am getting BSOD's again, this time on boot up.

    STOP: 0x000000116
    atikmpag.sys

    I am trying to access the Startup Repair but, F8 doesnt seem to do work.
    Not sure if I should run the DM Log Collector exe file again to create the error log, or if its already installed?
    The zipped minidumps are attached.

    Any help would be appreciated.
    Thank you,
    Harley
      My Computer


  7. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #7

    Trying another card


    Hi
    I am going to try purchasing an NVIDIA card which should bypass atikmpag.sys completely.
    I will post my results in case this can help anyone else.
    Harley
      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:56.
Find Us