📎 AI Summary:
The thread discusses a series of Windows Blue Screen of Death (BSOD) errors on a user's son's computer, with the initial post providing a dump file for troubleshooting. A responder suggests a possible video driver issue, specifically related to atikmpag.sys, and recommends updating the display driver first. After the user updates to AMD 13.9 drivers without success, trying an alternative ATK0110 driver appears to have resolved the problem, with the original poster confirming a successful fix.
Jimbo22

Jimbo22

Essential Member
Joined
Aug 27, 2008
Messages
5,036
Thread Author #1
On my sons computer, he keeps getting these BSOD's, randomly. Here is the dmp file using the diagnostic tool from the BSOD thread how to ask for BSOD help.
 

Attachments

Solution
Trouble
It looks like a video card issue, possibly a corrupt driver.
Code: 
BugCheck 116, {fffffa800480b4e0, fffff88003f45efc, 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 )
Code: 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800480b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f45efc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code...
Sort by date Sort by votes
Trouble

Trouble

Noob Whisperer
Joined
Nov 30, 2009
Messages
13,723
#3
It looks like a video card issue, possibly a corrupt driver.
Code: 
BugCheck 116, {fffffa800480b4e0, fffff88003f45efc, 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 )
Code: 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800480b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f45efc, 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.
Code: 
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
But try updating this driver first and see if it improves stability at all
ASACPI.sys Sun Mar 27 21:30:36 2005
Link Removed
expand "Utilities", second one down ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit
See if that helps at all.
 

Upvote 1 Downvote
Solution
Jimbo22

Jimbo22

Essential Member
Joined
Aug 27, 2008
Messages
5,036
Thread Author #4
Damn...I just updated the driver to the latest.....it's now on AMD 13.9, it was running 13.1 and doing the same thing.

I'll try that ATK0110 driver a shot and report back.
 

Last edited:
Upvote 0 Downvote
Jimbo22

Jimbo22

Essential Member
Joined
Aug 27, 2008
Messages
5,036
Thread Author #5
Well that seems to have fixed it....so far, no BSODs.

Thanks Trouble!
 

Upvote 0 Downvote
You must log in or register to reply here.