BSOD - probably because of old drivers that I am unable to remove

gss175 · 12 Apr 2014

I am running win 7 x64 on a E6750 Core2Duo on Asus P5E VM HDMI motherboard, 4 GB OCZ memory. I am getting random and increasingly more frequent BSODs. I replaced the memory, tried 2 new video cards as well as the built-in graphics, but still get BSODs. Re-installed Windows, remains stable for some days and then BSODs started again.

In the past few months, I do not get a BSOD but the display flickers and the computer crashes. Sometimes I get a message "Display driver igfx stopped responding and has successfully recovered." but of course it does not recover. I have to re-start by turning it off and on again. No mini-dumps are generated because there are no BSODs.

Steps taken so far:

1. Installed new video cards and new drivers.
2. Updated all drivers.
3. Tried to remove ASACPI - the Asus MB utility. But looks like I cannot seem to remove it from the Registry.
4. Ran multiple virus and malware scans.
5. SFC/scannow shows no problems. Disk drives are defragmented.

I had another computer exactly like this with the exact same problem- when I upgraded to Windows 8 on that machine, the BSODs stopped and it has NEVER crashed. From this I assume that the problem is not hardware related but is probably related to a Windows 7 driver.

I am attaching SF_Diagnostic_Tool file as well as DM Log Collector. For 3 of mini dmp files, I get access denied and cannot add them to the archive. But as can see, all of the mini dmps are from 2013. The computer crashes almost everyday but no mini dmps are generated nowadays.

I would prefer not to upgrade this machine to Windows 8 if I can find a solution to the crashes.

Very much appreciate your assistance !

Many thanks.

Arc · 13 Apr 2014

Hi gss175.

The crash dumps are too old to infer the present situation.

Attachment 313636

Run disc cleanup to remove the old ones. Then follow it:
Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

gss175 · 13 Apr 2014

Thanks, Arc. The problem is that there are no BSODs now - the computer just freezes and becomes unresponsive. I have to restart it by turning off the power. Will your suggestion still create a dump file ?

Arc · 13 Apr 2014

You may try a way, by enabling Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

gss175 · 14 Apr 2014

Thanks a lot. Will do and get back to you.

gss175 · 14 Apr 2014

I got a BSOD and minidump today (see attached).

Here is what I did. On 4/12, I looked at Device Manager and found a ! mark in a yellow triangle in front of ATK0110 ACPI Utility. On looking at the properties tab, it said "A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)". I removed the driver and the next time I tried to start the computer, it would not boot. I had to let it rollback to the last time it started before I made the change in ATK0110 ACPI Utility. It starts now, but the ! sign is back. Somehow, I think this is the culprit driver for all my troubles ?

On another note, there is another minidmp file from a month ago that I am unable to do anything with because it says I do not have permission, no matter what I try (I have tried the solutions posted on this forum to get permission but none of them work).

Suggestions ?

Arc · 15 Apr 2014

Can you provide some more information?

Click on the button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

gss175 · 22 Apr 2014

Here it is. Please let me know what else you need.

Many thanks for all your help.

gss175 · 24 Apr 2014

I did the Driver Verifier today - and the computer would not start at all. Rolled it back with system restore. A new mini dump was generated. I am attaching it to this message.

I read the minidump and figured out that it was pointing to Trusteer software. I uninstalled it, and re-ran driver verifier. Another BSOD and minidump. Now it pointed to another software, Daemon. I uninstalled that as well, and am now running the verifier again. So far so good. No BSOD as yet. Will keep you updated.

Would greatly appreciate your help in how to fix this situation.

What do I do next ?

Thanks.

Golden · 25 Apr 2014

Did you remove The Trusteer software after the latest BSOD? The latest .dmp still shows that as a problem.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e4, fffff8800665d9e3, fffff880061e07b0, 0}

*** WARNING: Unable to verify timestamp for RapportCerberus64_43926.sys
*** ERROR: Module load completed but symbols could not be loaded for RapportCerberus64_43926.sys
Probably caused by : RapportCerberus64_43926.sys ( RapportCerberus64_43926+539e3 )

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

If you did remove it after the BSOD happened, then thats OK...just monitor your system for BSOD's.