Ocassional BSOD usually with YouTube videos

[sonomaman]

Well, here's still another BSOD tale of woe

First, I'm NOT a gamer and NOT an over-clocker.

My BSOD's only happen randomly but ALWAYS when viewing a you tube video. The BSODs always points to my atikmpag.sys file. It is version 8.14.1.6099, 184kb, 2/11/2010. I have been unable to determine the 'latest' version because this file is embedded in AMDs Catalyst package where the atikmpag.sys version is hidden. I have loaded the current Catalyst version for my W7 64-bit custom PC about 2-months ago.

I use the on-board ASUS M5A88-V evo mobo video.

I hope I have uploaded the correct DM log collector file, which did not allow me to name the file per the forum instructions. I'm assuming the file has all the pertinent info about the BSODs together with info about my PC.

Any ideas?

 

[Arc]

Hi sonomaman.

It is a stop 0x116, which is a display/graphics related issue. And your display driver is too old. It appears to be an onboard graphics? And ASUS does not have any feasible update for it.
View attachment 320024

You may try AMD Driver Autodetect .... if it gives any update to the display driver.

Let us know the result.
___________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80064ea160, fffff88002cbe0a4, 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+60a4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80064ea160, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002cbe0a4, 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+60a4
fffff880`02cbe0a4 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.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`06622888 fffff880`04efe140 : 00000000`00000116 fffffa80`064ea160 fffff880`02cbe0a4 00000000`00000000 : nt!KeBugCheckEx
fffff880`06622890 fffff880`04efde4a : fffff880`02cbe0a4 fffffa80`064ea160 fffffa80`03756270 fffffa80`036bf410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`066228d0 fffff880`04fa4f13 : fffffa80`064ea160 00000000`00000000 fffffa80`03756270 fffffa80`036bf410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06622900 fffff880`04fcecf1 : 00000000`ffffffff 00000000`034437ff 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`066229e0 fffff880`04fcd437 : 00000000`00000102 00000000`00000000 00000000`034437ff 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06622a10 fffff880`04fa02d2 : ffffffff`ff676980 fffffa80`036bf410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06622ab0 fffff880`04fccff6 : 00000000`00000000 fffffa80`076a28b0 00000000`00000080 fffffa80`036bf410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06622bc0 fffff800`02f6a73a : 00000000`fffffc32 fffffa80`076ab060 fffffa80`03641b30 fffffa80`076ab060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06622c00 fffff800`02cbf8e6 : fffff800`02e49e80 fffffa80`076ab060 fffff800`02e57cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06622c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+60a4
fffff880`02cbe0a4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+60a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b736741

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
---------

3: kd> lmvm atikmpag
start             end                 module name
fffff880`02cb8000 fffff880`02cec000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Feb 11 07:41:13 2010 (4B736741)
    CheckSum:         00038565
    ImageSize:        00034000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[sonomaman]

I ran the AMD AutoDriver Detect. It reports I have the latest driver. Yes, I'm using the on-board graphics on my ASUS M5A88 -V evo motherboard.

Strange this atikmpag.sys related BSOD problem is so widespread and apparently so difficult to solve.

 

[Arc]

Actually it is not very difficult to solve.

Uninstall the installed display driver. Then run windows update to get an appropriate driver. That one that will be installed will work stable for you.