BSOD atikmpag.sys


  1. Posts : 2
    Windows 7 Home premium
       #1

    BSOD atikmpag.sys


    Hi, kindly help BSOD keeps me from working. I have uploaded a zip file from DM Log Collector.

    Thanks in advance.

    Manolet
      My Computer


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

    Update the display driver at first. It is too old to work stably there. Download Drivers

    Report us for any further BSOD after doing it.
    ________________________________________
    Code:
    BugCheck 116, {fffffa800c340010, fffff880070fcb78, 0, 2}
    
    *** 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+7b78 )
    
    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: fffffa800c340010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880070fcb78, 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+7b78
    fffff880`070fcb78 4883ec28        sub     rsp,28h
    
    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.17237 (debuggers(dbg).140716-0327) amd64fre
    
    STACK_TEXT:  
    fffff880`0b7ef888 fffff880`0705d144 : 00000000`00000116 fffffa80`0c340010 fffff880`070fcb78 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0b7ef890 fffff880`0705ce4e : fffff880`070fcb78 fffffa80`0c340010 fffffa80`0bf0aab0 fffffa80`0beee010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`0b7ef8d0 fffff880`0718bfbf : fffffa80`0c340010 00000000`00000000 fffffa80`0bf0aab0 fffffa80`0beee010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`0b7ef900 fffff880`071b5d09 : 00000000`ffffffff 00000000`00000e6d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`0b7ef9e0 fffff880`071b444f : 00000000`00000102 00000000`00000008 00000000`00000e6d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`0b7efa10 fffff880`071872e6 : ffffffff`ff676980 fffffa80`0beee010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`0b7efab0 fffff880`071b400e : 00000000`00000000 fffffa80`0bef6d50 00000000`00000080 fffffa80`0beee010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`0b7efbc0 fffff800`03577b8a : 00000000`fffffc32 fffffa80`0bf0d060 fffffa80`073069e0 fffffa80`0bf0d060 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`0b7efc00 fffff800`032ca8e6 : fffff880`03365180 fffffa80`0bf0d060 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0b7efc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+7b78
    fffff880`070fcb78 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+7b78
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e4c6c36
    
    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`070f5000 fffff880`07146000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Thu Aug 18 07:04:46 2011 (4E4C6C36)
        CheckSum:         0005396D
        ImageSize:        00051000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2
    Windows 7 Home premium
    Thread Starter
       #3

    Hi, Ive downloaded these and said that the install package is corrupt and cannot continue. Ive downloaded from HP. HPs drivers are installed. BSOD is gone, but my drivers still in standard VGA and the Catalyst is gone. Its very frustrating at this point as I cant work on regular graphics.

    Thank you very much!
      My Computer


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

    HP usually has old drivers listed. What is the driver version that you got from them?

    If the download came corrupted, better to have another try to download it.

    If any driver version cannot bring the regular graphics back, better to attempt to replace the graphics chip (or the computer itself, if it is within warranty).
      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 03:16.
Find Us