BSOD with atikmpag.sys error - still occurs with updated driver

Arc · 09 Jul 2015

After completing the re-pasting the thermal paste etc, post another Speccy screenshot too, for comparison.

moomin · 02 Sep 2015

Hello again Arc. Apologies for the long delay in getting back to you.

As recommended, I've had my computer cleaned/pasted by a professional. You'll see from the attached Speccy screenshot that temperatures are much lower now.
Attachment 370529

Unfortunately, not long afterwards I started to experience the same BSODs again. At first the BSOD occurred after playing video for 10-20 minutes but now it happens immediately on rebooting, so I can only use my computer with the AMD driver disabled. I have tried different versions of the AMD driver but to no avail. Recent minidumps are included in the attached zip file.
Attachment 370530

I've also run Disk Check and Memtest86+ (8 passes) and neither found any problems. I would like to re-run Furmark but that's presently not possible due to the BSODs.

Any further advice you can provide would be gratefully received. Many thanks.

Arc · 02 Sep 2015

Unfortunately both the attachments are showing to be invalid, so I cannot check them. Can you please re-upload those?

moomin · 02 Sep 2015

Sorry about that. Let's try again...

Attachment 370551

Attachment 370552

Arc · 02 Sep 2015

Code:

BugCheck 116, {fffffa8008254010, fffff88004e31cac, 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+ccac )

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

Code:

    Image name: atikmpag.sys
    Timestamp:        Tue Aug 04 07:12:28 2015 (55C01884)

Uninstall the installed display driver using Display Driver Uninstaller. Then install the CCC 15.7 WHQL only.

https://www.sevenforums.com/graphic-c...ndows-7-a.html

Let us know for any further BSOD after doing it.

moomin · 03 Sep 2015

Did what you suggested, Arc. Same BSOD appeared as soon as I rebooted. Dumps attached.
Attachment 370576

Arc · 03 Sep 2015

The latest crash dump included in the folder shows the same version of display driver that was installed there previously, and not the suggest one.

Code:

fffff880`0549c000 fffff880`05544000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Aug 04 07:12:28 2015 (55C01884)
    CheckSum:         000AF3B6
    ImageSize:        000A8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So the same BSOD is supposed to continue.

moomin · 03 Sep 2015

I could only find version 15.7.1 via the link you provided so I reinstalled this version. If you could give me a direct link for the earlier version 15.7 I'll try with that instead. Thank you.

moomin · 03 Sep 2015

Since my previous message I finally found and installed version 15.7. My computer rebooted successfully and I've managed to play video for 1 hour without any problems. Fingers crossed that my BSOD issues are now resolved, I'll obviously let you know otherwise.

Many thanks for all your help and patience, Arc. Out of curiosity, are you able to explain why version 15.7 works for me when several earlier/later versions of AMD generate these BSOD issues?

Arc · 05 Sep 2015

moomin said:

Many thanks for all your help and patience, Arc. Out of curiosity, are you able to explain why version 15.7 works for me when several earlier/later versions of AMD generate these BSOD issues?

It depends on many a things. But, try to use a WHQL driver always .... coz those are the stable releases.

Sometimes, some WHQL drivers turn out to be buggy, they cause BSODs. Then it is better to shift to the earlier WHQL which provided stability there.

Sometimes, some games cause instabilities on their own, then the driver itself has nothing to do there.

There are some other environmental factors including hardware which often play in .... we try to find out and minimize them depending on the situation.

Overall, it is too hard to explain in a short span, when we are discussing about gaming related BSODs.