BSOD after booting into Windows 7

mrgh · 17 May 2013

Problems started about a week ago with a random shutdown. PC will boot almost all the way into windows 7, then screen turns lines of colors followed by BSOD. Programs randomly lock up. Even had BSOD from Safe Mode when I couldn't boot into Windows. Yesterday I installed a new Corsair power supply and a new CPU cooler and heatsink. Process Lasso shows CPU usage randomly going up to 100% on the AMD Athlon II 640, (4 core). MemTest 86+ v4.20 showed all 12 gigs of ram with no errors. During the first night of problems I restored to an earlier date. When I booted up the problems were the same, but Symantec was not active. I ran Malwarebytes. It found 15 viruses and removed them. I ran Spybot and it found 4 more and removed them. Symantec locks up when I try to install, so I'm running Avast in the mean time. I'm at my wits end. If anyone can help, it's certainly appreciated. Info on a couple of the crashes are in the mrgh zip attached.

Specs:

koolkat77 · 17 May 2013

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

Security App
Crashes indicate Avast! being a possible cause. Remove Avast! and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective. Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

Information

DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.

Tip

Make full scans with both separately.

AMD OverDrive

Code:

AODDriver2.sys      Wed Jun 15 14:38:35 2011 (4DF86F8B)

(AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems. Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program. Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page) Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item. Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section. Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect. Sometimes the driver remains and continues to cause BSOD's.

Also perform a clean install of your ATI drivers:

Tip

How to clean left over drivers
Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper

Click on the Start

► Control Panel
► Programs
► Uninstall a program
► Uninstall everything related to the software.

Delete remnants of its drivers/older drivers using Driver Sweeper

Code:

atikmdag.sys        Thu Jun 30 09:59:27 2011 (4E0BF49F)
atikmpag.sys        Thu Jun 30 09:00:51 2011 (4E0BE6E3)

AMD Catalyst Drivers 13.1 Win 7 & Vista 64
AMD Inc - 146.47MB (Freeware)

Virus check
Scan your system with the following:

Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

ESET online scanner - One-time virus scanner free with ESET online scanner

Basic checks: Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

BSOD BUGCHECK SUMMARY

Code:

Debug session time: Fri May 17 08:33:09.276 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051613-57065-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:04:07.868
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )
BugCheck 1E, {ffffffffc0000005, fffffa800a6f93ef, 0, 7efa003c}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa800a6f93ef, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa003c, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  armsvc.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+487ed
BiosVersion = 6.07
BiosReleaseDate = 05/04/2011
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 17 01:22:03.488 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051613-30981-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:04:30.095
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )
BugCheck 1E, {ffffffffc0000005, fffffa800a7083ef, 0, 7fffffa003c}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa800a7083ef, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000007fffffa003c, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+487ed
BiosVersion = 6.07
BiosReleaseDate = 05/04/2011
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 17 00:31:59.161 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051613-63710-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:03:32.753
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )
BugCheck 1E, {ffffffffc0000005, fffffa800a7073ef, 0, 7fffffa003c}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa800a7073ef, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000007fffffa003c, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+487ed
BiosVersion = 6.07
BiosReleaseDate = 05/04/2011
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

mrgh · 18 May 2013

First, I want to thank you, Koolkat, for your assistance in troubleshooting these problems.

I removed Avast and replaced with MSE. The MSE scan said one infection, but I couldn't find out what it was. I then did the extensive ESET scan. It found 8 problems which I'll attempt to upload here.

Malwarebytes scan showed no problems.

Disk check showed no errors.

Seagate Seatools was run in DOS from boot. It passed the short test. On the long test it froze at 29%. I rebooted and ran the long test again. This time it froze at about 46%. Both times it froze, as soon as I moved the mouse, a constant beep started, sinilar to a bios beep.

SFC will not run from a command prompt in Windows. I attempted to then use a System Repair Disc I made when the PC was new so I could run SFC. It would not boot from the disc, even though I had no problem booting from the Seagate Seatools disc.

Memtest 86+ v4.20 also ran from boot and showed no errors. I haven't yet removed ATI and replaced it with the driver only.

Instead of BSODs, at least at present, I get constant random lockups in Windows, causing me to manually shut down. Sometimes it will shut down and restart before fully booting into windows. I am including the uploads of msinfo32 and systeminfo32.

Here is some extra information: When all these problems first started I had a sudden shutdown while in Windows. It wanted to boot into safe mode, but I booted it back into Windows. It fully boot, but I could hear the power supply fan fluctuating unnaturally. At this point, I tried to restore the system to an earlier date. Now there were BSODs, automatic reboots, lock ups, etc. I then undid the restore, but it made no difference. Erratic operation started before the initial restore anyway.

Because of the fluctuating power supply issue, I removed the 275watt power supply that came in this HP PC and put in a 500watt PC Power and Cooling I had on hand from an older Dell. Of course, it didn't correct any of the problems, but there was no erratic power supply operation. Since it was already a used power supply, I ordered a 500watt Corsair CX500 and an Artic Cooler fan and heat sink for the CPU, and installed both. With the computer problems, the Corsair sometimes races like crazy for 60 seconds or so at a time, then quiets down. So I don't know if temperatures are getting too hot at times, or what. I'm stumped!

I hope you can give me some input. And thanks for what you've attempted so far!

koolkat77 · 18 May 2013

I have requested a friend to take a look at your thread please wait for a reply from him.

I just noticed that you have Norton:

Code:

Start Menu\Programs\Norton	GH-HP\GH:Start Menu\Programs\Norton	GH-HP\GH

which is a frequent cause of BSOD's, please uninstall it with its removal tool as well. Uninstallers (removal tools) for common antivirus software

Windows Defender Offline: How to Use Windows Defender Offline

Britton30 · 18 May 2013

From all indications, freezes, sfc not running and Seatools failing to do a long test I think your hard drive (HDD) has failed. SpyBot can cause BSODs so I recommend it be uninstalled and when you reinstall the AMD (ATI) drivers don't install the Catalyst Control Center (CCC), also a cause of BSODs as well.

download and install Crystal Disk Info, run it and posr a screen shot so we can get an idea about your HDD.

Download Center - Crystal Dew World

This is the preferred, best way to upload an image to a post.
Screenshots and Files - Upload and Post in Seven Forums
You may also upload a photo or image as you would a file, without using the Snipping tool.

BSOD after booting into Windows 7

BSOD after booting into Windows 7

I have been trying with no success