A couple of months ago, my Win7 PC unexpectedly became unable to boot normally. I'm able to boot into the various Safe Modes, but everything else fails (including what is sometimes called a "clean boot," in which msconfig.exe is used to disable non-essential drivers, services, and programs).
The last time I used my PC normally, I played Skyrim for a few hours and then shut down normally. I use my PC for gaming only, and hadn't really installed any new software in 4 or 5 months.
When I attempt to boot, I get the "Starting Windows" screen with the pulsing logo, and then after a couple of seconds the screen goes black and the mobo BIOS screen reappears -- the computer has just rebooted. Just before the screen goes dark, there is a quiet but distinct "click" sound from inside the tower. It is not an unusual sound -- there are several large fans and 4 or 5 HDDs in there, and the machine has always made a lot of interesting noises while booting -- but its proximity to the failure is suggestive.
I've been fixing my own Win machines for a long time, but after 2 months of experimenting every weekend, I'm out of ideas. I've got a CBS.log file that purports to describe the problems that couldn't be fixed by the System File Checker, but nothing inside looks serious. And while the log suggests that repair completed successfully, stdout says otherwise:
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
I've read that sfc
needs to be run several times to accomplish its work. I've run it literally dozens of times, and every time it says it was unable to fix some of the problems it found. I've examined a lot of these logs, and it's not actually clear that anything is being accomplished -- the number of work items appears to be roughly constant over time (I have not counted carefully). At this point, the only reason I run sfc
at all is that it's the only tool that finds problems, and it's the most verbose of the system recovery tools available without booting normally.
I have already run chkdsk
, but it found no errors.
I have attempted to repair my boot sector and MBR, based on a cryptic, once-only error code seen during System Recovery (I don't recall the error code). It did not fix the problem, but for several hours I was forced to boot from the Win7 install disc, until I successfully repaired the damage I had done (I think). I think this suggests that the boot sector & MBR are fine.
I have uninstalled my graphics drivers (nVidia).
Automatic Windows Update is disabled. I personally inspect every available update before downloading and installing it. I stay on top of it, and generally only refuse updates that are about Win8 readiness.
I tried to do a "repair installation" of Win7 from the DVD, but it refuses to do that from Safe Mode (which really makes me wonder WTF the point is -- medicine that only healthy people can take?).
At this point, I really feel like I need someone to hold my hand; I've done an extensive amount of research and experimentation with the various recovery strategies that are mentioned online, and none of them has made a difference.
I'm attempting to boot Win7 Home Premium (64-bit) SP1 from a 60GB SSD (7.5 GB free).
Any help is appreciated.
-- UPDATE --
I tested booting the PC with all drives disconnected except the primary, and it still failed.
I booted the machine using an Ubuntu Live USB, and used Disk Utility to inspect the boot disk. It reports the disk is healthy, and shows three partitions:
- 105 MB FAT "EFI System Partition"
- 134 MB "Microsoft Reserved Partition"
- 64 GB NTFS "Linux Basic Data Partition"
When I run "Check Filesystem" on each parition, both 1 & 2 are described as "clean," but 3 is described as "not clean."
More about partition 3:
- Overall assessment: Disk is healthy
- Power Cycles: 2819
- Bad Sectors: None
- All but one of the various error metrics are at 0; there are 31 "Data Address Mark Errors"
I ran the extended SMART Self-test, and none of these values changed, and the disk is still reported as "healthy."
Based on this SE thread, I ran sudo ntfsfix /dev/sda
, but it failed with really interesting information:
ubuntu@ubuntu:~$ sudo ntfsfix /dev/sda
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing
Trying the alternate boot sector
Unrecoverable error
Volume is corrupt. You should run chkdsk.
I've already run chkdsk on the drive about 15 times, and each time it completes successfully with no errors.
What do I do next?
-- UPDATE --
From my Ubuntu Live USB stick, I am able to mount and explore both the EFI partition and the large main one. The Disk Utility GUI doesn't present an option to mount the other one, and I assume that a "Microsoft Reserved Partition" probably won't play well with *nix.
Days spent researching "NTFS signature" have not proved helpful.
-- UPDATE --
The "NTFS signature" issue appears to be unrelated. I was specifying the wrong device (/dev/sda
instead of /dev/sda3
). When I corrected the command, ntfsfix
ran successfully. The boot problem is not fixed, however.
I've since removed my video cards, and now I see a BSOD where the screen used to be blank. The message is:
STOP: c000007b {Bad Image}
Exception Processing Message c000007b Parameters 19b6aa0 0 0 0
ntfsfix
against/dev/sda
! That's the whole disk - you'll corrupt your drive. Only run it against your NTFS partition, which sounds like issda3
.