📎 AI Summary:
The thread discusses a Windows 7 user experiencing frequent blue screens caused by the atikmpag.sys graphics driver, with troubleshooting suggestions focused on updating or reinstalling AMD GPU drivers. The user confirms running the latest Catalyst version and has tested the video memory without issues, though blue screens continue. The forum members recommend trying beta driver versions and thorough driver removal. Overall, the conversation is helpful and ongoing, aiming to resolve the driver-related BSOD problem.
I

ijun

Member
Joined
May 13, 2015
Messages
35
Thread Author #1
Running on Windows 7 Home Premium, been keep getting blue screen that are caused by atikmpag.sys for a few months already. Need some help on this problems as I've no clue about it. Please.
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cf3f4e0, fffff88004e27970, 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+b970 )

Followup: MachineOwner
Hi Ijun...
Sort by date Sort by votes
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#21
Thanks.. I see these are made in two flavors 520W and 620W. Please post which one you have and am I correct in saying you have an AMD R9 290X?
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#23
ok bud just see how you go with changing the drivers as suggested.
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#25
Hi,
no dump file included:
An image from 'Windows 7 BSOD Cause by atikmpag.sys'. Screenshot of a Windows 7 forum thread on BSOD atikmpag.sys with file explorer open.


Are you definitely sure it was a bsod? If it was make sure your pagefile is at least 200mb. This post in the sysnative forums shows what has to ne enabled for a dump file to be created:
BSODs but no Dump Files?
 

Last edited by a moderator:
Upvote 0 Downvote
I

ijun

Member
Joined
May 13, 2015
Messages
35
Thread Author #26
kemical said:
Hi,
no dump file included:
View attachment 30017

Are you definitely sure it was a bsod? If it was make sure your pagefile is at least 200mb. This post in the sysnative forums shows what has to ne enabled for a dump file to be created:
BSODs but no Dump Files?
Click to expand...
Yes i'm sure it's a BSOD, stated same as previous caused by atikmpag.sys
 

Last edited by a moderator:
Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#27
Have you removed the Pagefile? Or reduced it to below 200mb?

Open the run box and type services .msc and click ok. Look down the list in the revealed box for Windows error reporting service and make sure it's set to manual.

Open an admin command prompt, type:
sfc /scannow
Press enter and await results.
 

Upvote 0 Downvote
I

ijun

Member
Joined
May 13, 2015
Messages
35
Thread Author #28
kemical said:
Have you removed the Pagefile? Or reduced it to below 200mb?

Open the run box and type services .msc and click ok. Look down the list in the revealed box for Windows error reporting service and make sure it's set to manual.

Open an admin command prompt, type:
sfc /scannow
Press enter and await results.
Click to expand...

It's already on manual.
And the sfc/scannow is verification 100% completed, Windows resouce protection did not find any integrity violations.
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#29
Sometimes no dump file can mean that there is an issue with the hard drive. Now I'm not saying for a second this is the case here but it might be prudent to perform a chkdsk?
Link Removed
Whichever method you choose please ensure you look for and repair broken sectors.
 

Upvote 0 Downvote
I

ijun

Member
Joined
May 13, 2015
Messages
35
Thread Author #30
kemical said:
Sometimes no dump file can mean that there is an issue with the hard drive. Now I'm not saying for a second this is the case here but it might be prudent to perform a chkdsk?
Link Removed
Whichever method you choose please ensure you look for and repair broken sectors.
Click to expand...
i've done it already, i will see how it goes, if BSOD persist i'll inform you again? :)
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#31
Another thing you could try if you haven't already is re-seating the GPU and just making sure the connections are tight. TDR errors can be notoriously difficult to track down and having no dump file means it's even harder I guess. Have you actually checked the mindump folder yourself to see if it contains any dump files?
 

Upvote 0 Downvote
I

ijun

Member
Joined
May 13, 2015
Messages
35
Thread Author #32
kemical said:
Another thing you could try if you haven't already is re-seating the GPU and just making sure the connections are tight. TDR errors can be notoriously difficult to track down and having no dump file means it's even harder I guess. Have you actually checked the mindump folder yourself to see if it contains any dump files?
Click to expand...
May i know where to locate the folder? :/
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#33
Sure it's in the main windows folder. Please post the dump file if you find it.
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#35
Hmm and you sure your settings are set like this:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

Check your pagefile and make sure the top checkbox is ticked so it's automatically sorted.
 

Upvote 0 Downvote
I

ijun

Member
Joined
May 13, 2015
Messages
35
Thread Author #36
kemical said:
Hmm and you sure your settings are set like this:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

Check your pagefile and make sure the top checkbox is ticked so it's automatically sorted.
Click to expand...
Yes just changed the settings to the one that you've mentioned :)
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,163
#37
Ahh ok cool... That's probably why you weren't seeing any then... Ok as soon as you get a dump file please post (which i know you will anyway but just thought I'd say.. :) )
 

Upvote 0 Downvote
I

ijun

Member
Joined
May 13, 2015
Messages
35
Thread Author #38
kemical said:
Ahh ok cool... That's probably why you weren't seeing any then... Ok as soon as you get a dump file please post (which i know you will anyway but just thought I'd say.. :) )
Click to expand...
So i will get a dump file after each BSOD? o_O
 

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