BSOD atikmpag.sys appear sometimes after turn on laptop

Hi Nobodies.

Update your ATI/AMD display driver to the latest WHQL.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

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.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Let us know the results.
_________________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80053ce4e0, fffff88004030cf0, 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+acf0 )

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: fffffa80053ce4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004030cf0, 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+acf0
fffff880`04030cf0 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`036e59c8 fffff880`04323140 : 00000000`00000116 fffffa80`053ce4e0 fffff880`04030cf0 00000000`00000000 : nt!KeBugCheckEx
fffff880`036e59d0 fffff880`04322e4a : fffff880`04030cf0 fffffa80`053ce4e0 fffffa80`05a9daa0 fffffa80`05c80010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`036e5a10 fffff880`043c9f13 : fffffa80`053ce4e0 00000000`00000000 fffffa80`05a9daa0 fffffa80`05c80010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`036e5a40 fffff880`043f3cf1 : 00000000`ffffffff 00000000`001bd7e7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`036e5b20 fffff880`043f2437 : 00000000`00000102 00000000`00000000 00000000`001bd7e7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`036e5b50 fffff880`043c52d2 : ffffffff`ff676980 fffffa80`05c80010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`036e5bf0 fffff880`043f1ff6 : 00000000`00000000 fffffa80`05a9daa0 00000000`00000080 fffffa80`05c80010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`036e5d00 fffff800`031732ea : 00000000`fffffc32 fffffa80`0595db50 fffffa80`03c9d890 fffffa80`0595db50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`036e5d40 fffff800`02ec78e6 : fffff880`009eb180 fffffa80`0595db50 fffff880`009f5f40 00000006`156f0000 : nt!PspSystemThreadStartup+0x5a
fffff880`036e5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+acf0
fffff880`04030cf0 4055            push    rbp

SYMBOL_NAME:  atikmpag+acf0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5154e9d9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

0: kd> lmvm atikmpag
start             end                 module name
fffff880`04026000 fffff880`040ba000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Mar 29 06:39:45 2013 (5154E9D9)
    CheckSum:         00091A60
    ImageSize:        00094000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The system is overheating. Send it for servicing, ask for clean the inside and re-apply the thermal paste.

Whatever, the 62 degrees for a motherboard is high.