BSOD atikmpag.sys/display driver error upon login - need help

Hello,

I've recently started getting bsod on my four year old Acer 7750g-6645. The first happened randomly while browsing in chrome. The laptop froze then went to a blue screen and rebooted before I could catch the information. Upon restart/logging into my user account, moments later while idling, the computer again blue screened. This time showing unresponsive display driver error. Another time atikmpag.sys error. At the moment, using the computer in safe mode is the only way stop the bsod from happening. I would really appreciate some advice on a fix.

Acer Aspire 7750G-6645
Intel Core i5-2450M 2.5GHz
AMD Radeon HD 7670M 1GB VRAM
4GB DDR3
500GB HDD
Windows 7 Home Premium x64

ETA: DM Log Collector's zip file wasn't showing up on my desktop or anywhere else, so I used the SF Diagnostic Tool instead.

Hello and welcome Rax mate that one serious lot of BSOD's and searching through a few I can see a few areas to be looked at and I have only had a cursory look.
One that I came across has me curious

Code:

*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys

Now without being sure this is probably caused by a security program Eset-NOD32 if you are running it best disable it and see if that makes any difference in the meantime we shall work through the other dumps.

No worries Rax mate it is a while since I was last on line so just how did you get rid of that Eset stuff because most AV's have dedicated removers and one should never rely on the Windows Control Panel method of uninstalling AV's for doing so.

So did you use the Est site to get the removal tool. Sorry I would link it if it came up for me maybe you can Google it yourself. If you did use it then you might try as I always do and that is check in the registry
HKEY's LOCAL_MACHINE & CURRENT_USER > Software > scroll down each list and check for Eset entries > if you find some let me know.

Now Avast also has it's idiosyncrasies so good idea disabling it temporarily.

I think I used the removal tool...but it's been a while and i'm not 100% sure. Anyhow, I checked the registry and I do see entries for Eset.

HKEY_LOCAL_MACHINE\SOFTWARE\ESET
HKEY_LOCAL_MACHINE\SOFTWARE\ESET\Setup
HKEY_LOCAL_MACHINE\SOFTWARE\ESET\Setup\CurrentSession
HKEY_LOCAL_MACHINE\SOFTWARE\ESET\Setup\Drivers

I installed and ran Eset's removal tool as suggested but only Avast (my current antivirus) is showing up for removal. Should I delete these Eset registry entries?


ETA: I have HitmanPro as an on-demand scanner. Could that be a reason for the Eset entries???

I also use SuperAntiSpyware and MalwareBytes as on-demand scanners too, in case that's important.

Ok Rax mate best read this first Registry - Backup and Restore

Personally what I do is to Export the whole registry (see my pic) doing individual HKEY's is up to you because if you slip then you can Merge back in those entries. Either method is what you need to get rid of the Eset totally.

When you get to the large full entry right click it and then delete.

Ok now that is done and before we go any further I am just wondering if you can try doing whatever you normally do and see if there are any more issues with the blue screens.

In the meantime I'll run through the dump files and see if anything sticks out and get back to you.

Right now lets start with some simple stuff I have seen a few Googles and RAM has been mentioned with the dump here and I really do feel sorry that you have been plagued with so many blue screens. But I am sure we can get to the bottom of the problem.

Code:

FAILURE_BUCKET_ID:  X64_0x5C_HAL_FAILED_TO_RESTART_PROCESSOR_AFTER_SLEEP_nt!PopHandleNextState+12a

BUCKET_ID:  X64_0x5C_HAL_FAILED_TO_RESTART_PROCESSOR_AFTER_SLEEP_nt!PopHandleNextState+12a

Now I suggest you reseat the RAM sticks first see if there is any difference witht the machine running and then run a memtest as per this tutorial RAM - Test with Memtest86+ and unless errors come up fairly quickly then let it run for at least 8 passes any less and you may as well not bother (a lot of people give up quickly) It is tedious and very time consuming and I find best left until towards the end of the day and most work is done on the machine and then if necessary left to run overnight.

In my pic the memtest version is not the same but the readout looks very much like it. I have a few explanatory things in the pic so you can see what I mean.