BSOD: Getting Error 0x0000000A - Please Halp

Well it turns out I'm getting another shot at it, the shop wants to format it. So I'll try the above steps again tonight and let you know how it goes.

Okay. Take your time.

Let me know these:

1. The age of the hardware
2. Its warranty status
3. What is the date of installation of the OS
4. Was the OS ever re installed

1) It's a newer HP desktop, maybe a year old, loaded 1TB, 8GB memory, etc
2) It may be under warranty, but were in a time crunch, so if I can't fix it this weekend I'll just format and start over
3) The OS came installed on the PC (I can get the exact date when I get home)
4) No the OS was never reinstalled, in fact I don't even have the disks (of course)

Thanks :)
Carry out the tests from my post #6 and let me know the results

koolkat77 said:

Suggestions:

Please uninstall and remote control programs. Also uninstall Bit Defender.

* System file checker for repairing any damaged files within windows
SFC /SCANNOW Command - System File Checker

* Run Memory test for 8 passes preferably overnight.
RAM - Test with Memtest86+

* To make sure your hard drive is good run
Disk Check

* Hard drive test both short and long with
SeaTools for Windows

SeaTools for DOS

* Look for an update on your BIOS version from the manufacturers website.

Code:

BIOS Version/Date    American Megatrends Inc. 5.02, 4/17/2009

Let us know the results

Okay I'm on the first step, I ran the test and got the result: "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log". I've attached the CBS Log for inspection. Please let me know how to proceed. Thanks!

How many times have you run the SFC? Sometimes needs to be run more than 3 times

There is only a single error in the log

Code:

Line 8577: 2012-09-23 15:09:44, Info                  CSI    000002de [SR] Cannot repair member file [l:18{9}]"vcomp.dll" of Microsoft.VC80.OpenMP, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, hash mismatch

Running SFC again will do nothing to fix it.

The problem appears to be with vcomp.dll - which in my main machine only actually exists in the WinSxS folders and is from Visual Studio 2005.
I doubt very much that it is the cause of your problem - but here's a way to fix it.

You'll see a zipfile attached - extract it to C:\SFCrepair

Then use the following method to put the files where they need to be
1) reboot, and use F8 to access the advanced boot menu - pick Repair your Computer.
Once you've logged in open the option for a Command Prompt.
at the prompt type DIR C:\sfcrepair - if it finds the files, then great, if, not then try DIR D:\sfcrepair (and so on until you find it).
Now use the following commands

XCOPY <drive>:\sfcrepair <drive>:\Windows\winsxs /S /Y

Change the <drive> to the proper drive letter you found above.

note that you MUST get those commands exactly right, or they simply will not work.

Once you have the in place, reboot to Windows normally

Run another SFC /SCANNOW and post the results

@Noel
While I was waiting on a reply from the community, I dropped down to the next troubleshooting step I could do, and I ran Disk Check. It was a 1TB drive, and the scan took a couple hours, not sure if that's normal. However I tried booting back up just for grins, and SHAZZAM!! It's all working?!?! I surfed the net, created some Word docs, ran a full AV check and then let it run all night. I shut it down and then booted up, let it run an hour, rinsed and repeated three times. I think we're good, however I don't know if it's safe to give the all clear, or if I should continue to run repair tools on the system.

Which version of CHKDSK did you run? - by preference, it should have been the /R - which on a 1TB drive could easily take 4-5 hours.
Please run another SFC /SCANNOW anyhow - it may show more events now.

I found the culprit! I let a Security Essentials run all day doing a deep scan and it detected the Alureon.A virus. I read the Wikipedia entry and that sounds like all the symptoms, the BSOD masquarading as a hardware issue when it's a virus. While the scan revealed the threat it couldn't remove it. I had to use the Kaspersky TDSSKiller to actually remove that sucker. Effing viruses! When I was a kid they were funny, but now as an adult their just petty.

As promised I wanted to post the result so others can hopefully catch their issues. However I also was wondering if I need to run any repair progs, or with the virus removed I should be good? Thanks for all the support!