I have my Windows DVD, but trying recovery from that just makes my PC lose the boot drive, so after fixing that a couple of times
I went with trying what tools I could find. OTLPR gets as far as bringing up the M/S logo but then it blue screens.
I have a FRST scan attached.
Any help on where to go from here would be appreciated.
From the recovery disc select command prompt and run the following
chkdsk c: /r
On completion try a normal boot
No dice. Windows gets part way through the restart flashes blue and restarts as usual.
chkdsk returned:
The type of the file system is NTFS.
CHKDSK is verifying files (stage 1 of 5)…
175616 file records processed.
File verification completed.
605 large file records processed.
0 bad file records processed.
0 EA records processed.
60 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)…
245488 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)…
175616 file SDs/SIDs processed.
Security descriptor verification completed.
34937 data files processed.
CHKDSK is verifying Usn Journal…
35460784 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)…
175600 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)…
3355752 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
62417919 KB total disk space.
48635984 KB in 134642 files.
79596 KB in 34938 indexes.
0 KB in bad sectors.
279331 KB in use by the system.
65536 KB occupied by the log file.
13423008 KB available on disk.
4096 bytes in each allocation unit.
15604479 total allocation units on disk.
3355752 allocation units available on disk.
Failed to transfer logged messages to the event log with status 50.
X:\sources>
I’m not sure whether that error has any significance. I booted from USB and the x: drive appears to be writable if those matter.
No that error is to be expected
The problem is that the software hive (registry ) is not loading hence the boot failure, are you still getting the safe mode lock at aswvrt ?
Yes. No change there.
Hmm, The PC pauses for a long time at aswvrt but then the CD spins up before the PC crashes.
I hadn’t noticed this because I didn’t have a CD in the drive previously so the whirring wasn’t evident. So it must be doing something after/associated with
loading that driver, but it still doesn’t print up the next one.
OK lets see if we can restore the registry hives
Choose command prompt.
Once on the command prompt window, type c: and hit enter.
Type the following commands into the DOS command prompt. Each one of these statements copy the original registry files to the current registry directory.
[b]copy C:\windows\system32\config\regback\system c:\windows\system32\config\system
copy C:\windows\system32\config\regback\software c:\windows\system32\config\software
copy C:\windows\system32\config\regback\security c:\windows\system32\config\security
copy C:\windows\system32\config\regback\sam c:\windows\system32\config\sam
copy C:\windows\system32\config\regback\default c:\windows\system32\config\default
[/b]
Press the “Y” key after each copied file. This confirms that you want to overwrite the existing registry files.
Remove the Windows 7 installation disc from the drive and reboot the machine.
The registry is now restored with original settings.
You did it ! Thank you. I can’t believe it was something so simple.
Now to see if Windows patching breaks it again.
How can I buy you a remote beer ?
Glad that worked as it usually has a failure rate of 50%
How is the computer behaving now ?
So far so good. I haven’t put it on the network yet but I’m going to try that and get everything updated.
I think everything is pretty much OK. Lots of my Windows updates have failed but scheduled for retry and some are working so I’ll see if that sorts itself out.
Maybe rolling the registry back has caused a mismatch between applied patches and matching registry entries. (guessing)
Anyway, thanks again.
That is the probable cause, it may be worthwhile resetting windows updates to stop the confusion. Use the aggressive mode for this fixit
I’ll try that when I get home. All but two updates have sorted themselves out but those two are definitely borked.
Thanks. The big hammer approach seems to have worked. Reapplied over 30 updates. I’m a happy camper.
Glad to hear 
Enjoy