Intel Core i7 970 Processor 3.20GHz (6 core)
6 Gigabytes of RAM
Win7 (64-bit) Home Premium
GeForce GTX 560 Ti (1.5GB VRAM)
Last night, the machine kept having the audio fade in and out and I would randomly hear the sound effect of a USB device being connected/disconnect when I wasn't do so. So, I ran CCleaner and rebooted. It the dumped me to the Start Up Repair menu and said it could not be repaired. If I hit "Finished," the machine powered down.
So I booted up the DVD for Windows 7, ran the Start Up Repair from there. It said it worked and if I run it again from the DVD, it says no errors are found. I also ran the memory checker (came up fine), ran chkdsk (came up fine), ran the Seagate Harddrive Utility for DOS (came up fine) and finally an AVG virus scan from boot media (came up fine). I attempted System Restore on every available restore point and each one failed with a hex error code.
Still, when I boot up normally, it throws me to the Start Up Repair screen, doesn't fix the issue, and produces the following output:
Problem Event Name: StartUpRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200512
Problem Signature 05: AutoFailover
Problem Signature 06: 21
Problem Signature 07: NotRootCause
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
I live in a remote area and we only have one PC repair place in town and the gentleman who runs it is gone until the 15th. I'm typing this message on an ancient Mac Book, but it won't do for the work I must complete. I'd also like to avoid having to format the HD for the obvious reason. If I absolutely have to, I will, but I'm not convinced its HD related since everything comes up clean on the HD health.
Anyone have any ideas? Thank you so much for your time.
EDIT: One other thing I that I tried just now was running the Windows Defender Offline tool and it came up with no malware.
EDIT #2: I ran sfc (sfc /scannow /offbootdir=d:\ /offwindir=d:\windows) from the install disc > Repair > Command prompt window. The result was simply:
Windows Resource Protection did not find any integrity violations.
Edited by Rivet, 07 January 2013 - 09:32 PM.