BSOD - Still Unresolved Probably Because of Old Drivers

[gss175]

I apologize for starting a new thread but I am not getting any responses in my old thread describes the problem and the steps that I have taken. I have new information, and am attaching new files to this thread. Old thread is here:

http://www.sevenforums.com/bsod-hel...because-old-drivers-i-am-unable-remove-2.html

Brief summary:

I am running win 7 x64 on a E6750 Core2Duo on Asus P5E VM HDMI motherboard, 4 GB OCZ (later Corsair and Crucial also) 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.
6. Run Driver Verifier.
7. Removed Trusteer.
8. There was a ! mark in a yellow triangle in front of ATK0110 ACPI Utility in Device Manager. 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, and it booted.
9. Disabled ATK0110 ACPI in Device manager.
10. Ran Memtest twice overnight.
11. Replaced memory twice.

No effect of any of the above.

Important HINT:

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 recent files. Old files can be found in the old thread.

Please help !

 

[HarriePateman]

I have had a look for you, very sorry your last problem did not get solved.

The BSOD reports a memory corruption.

BugCheck 4E, {c000001d, fffff88000d7cc00, fffff88009e32bc0, 0}

[COLOR=Red]Probably caused by : memory_corruption  ( nt!MiBadShareCount+4c )
[/COLOR]

Followup: memory_corruption
---------

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+

If there is no error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

   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.

 

[gss175]

Thanks a lot.

I have changed the memory three times, with there different brands: OCZ, Corsair and Crucial. I have run Memtest and Driver Verifier with all three sets of memories. No issues - yet the BSOD still persists.

I am completely foxed.

 

[HarriePateman]

Okay so it could possibly be HDD related.

Run a diagnostic tool for your HDD from the manufactures website please.

 

[gss175]

Good Idea on the hard drive. I have not done this yet. Will do today.

Here is another NEW information. Yesterday morning, when it crashed, I did not shut it off and reboot but left it alone for several hours. The screen would flicker, go black, come back (but unresponsive), go black again. I left the house but did not turn it off. When I came back, it was working again, with several windows that had the message: "Desktop Window Manager stopped working and was closed."

Last night, I also did not shut it down, and this morning, it was fine. One window, with the same message: Desktop Window Manager stopped working and was closed.

(Both times, it crashed again and I had to shut it.)

This is the first time that this has happened. So something has changed. I am going to research this message. Any ideas please?

Also, my wife says that anytime she opens multiple pictures the computer crashes.

 

[HarriePateman]

Try an SFC Scan.

   Information

:info:The sfc /scannow command (System File Checker) scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html