BSOD randomly x116 atikmpag.sys

blackstrike · 20 Dec 2013

this is amazingly bsod. when playing game, watching movie, even browsing
i have HD 4650 DDR 2 sometimes keep bsod in 1 day.
magically not bsod in 4-5 days. and bsod again.
once bsod appear it will likely bsod in next 2-3 hours
the problem is AMD driver .

today , i got bsod at 4 pm. i uninstall complete the driver (12.4)
and i install 13.9 the latest in web AMD. done installing
restart.. and boot up to desktop. 4 sec later bsod.
so i think this is must driver faulty. i uninstall again.
and installing (12.4b) its ok.. not bsod... until the last. it bsod again when browsing (-+ 8pm)

please help me, i dunno what to do now.. i planned for format computer next sunday if still not solve

PS: ignore the first bsod, IRQL not less equal. because my old c2d E7500 is broke. i changed to pentium E2160 now. but not formatting. so i guess maybe the win 7 fault too

Arc · 20 Dec 2013

Hi blackstrike. Stop 0x116 BSODs are display/graphics related.

It seems to be an old computer.

Code:

BiosVersion = 080012 
BiosReleaseDate = 05/14/2008

If there is any possible BIOS update, apply it. PCCHIPS Web Site

How old the ATI Radeon HD 4600 Series GPU is? Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

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 .

The display driver is old, too.

Code:

    Image name: atikmpag.sys
    Timestamp:        Fri May 25 01:24:11 2012 (4FBE91E3)

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.

Let us know the results.
______________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {867d6228, 9623420e, c00000b5, a}

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+720e )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 867d6228, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9623420e, The pointer into responsible device driver module (e.g. owner tag).
Arg3: c00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000a, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+720e
9623420e 8bff            mov     edi,edi

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
94e64ba4 9b5da0ff 00000116 867d6228 9623420e nt!KeBugCheckEx+0x1e
94e64bc8 9b5ceae6 9623420e c00000b5 0000000a dxgkrnl!TdrBugcheckOnTimeout+0x8d
94e64bec 9b60b92c c00000b5 00000000 94e64cb0 dxgkrnl!TdrIsRecoveryRequired+0xb8
94e64c64 9b632d55 fffffcfb 0002c5fd 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
94e64c90 9b612993 87ae73c8 94e64cb0 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
94e64d28 9b637501 00000000 83872fa5 87ae73c8 dxgmms1!VidSchiScheduleCommandToRun+0x14d
94e64d3c 9b6375bd 87ae73c8 00000000 87ac2a48 dxgmms1!VidSchiRun_PriorityTable+0xf
94e64d50 83a2c53a 87ae73c8 b0b53661 00000000 dxgmms1!VidSchiWorkerThread+0x7f
94e64d90 838cd899 9b63753e 87ae73c8 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+720e
9623420e 8bff            mov     edi,edi

SYMBOL_NAME:  atikmpag+720e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fbe91e3

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys

BUCKET_ID:  0x116_IMAGE_atikmpag.sys

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

1: kd> lmvm atikmpag
start    end        module name
9622d000 96274000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri May 25 01:24:11 2012 (4FBE91E3)
    CheckSum:         0004FBBA
    ImageSize:        00047000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4