Windows 7 boot BSoD - Corrupt Registry?

Cormy1

Active member
Joined
Sep 10, 2024
Posts
29
Some context leading up to BSoD:

BSoD:
https://www.sysnative.com/forums/attachments/img_20241121_163159435-webp.111968/

Startup repair result:
https://www.sysnative.com/forums/attachments/img_20241121_163848273-webp.111967/
 
I don't normally help out with Windows 7, it's an unsupported OS now, but that 0x7B bugcheck in the blue screen you posted is an INACCESSIBLE_BOOT_DEVICE. That would seem to be related to this...
#3 the installation I am currently working with was recovered from a dying hard drive that was over 10 years old and so has LOTS of little issues here built up here and there.
If you're working with a known suspect HDD then, well, why?
 
I don't normally help out with Windows 7, it's an unsupported OS now, but that 0x7B bugcheck in the blue screen you posted is an INACCESSIBLE_BOOT_DEVICE. That would seem to be related to this...

If you're working with a known suspect HDD then, well, why?
I'm not working with a suspect HDD, I said the installation was RECOVERED from the dying hard drive.
As in contents of the drive were imaged/backed up and cloned/burned to another drive.
The system cannot be booted into, therefore no changes can be made to the dump settings, nor can the program be run from the system that is impacted.
Unless you're telling me the program will work on offline systems, that's not an option.
 
Load the system hive.
Then launch the following command from an elevated command prompt, zip the file you'll find on your desktop and upload it here.
Code:
reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services /s /t reg_dword /v start > "%userprofile%\desktop\services-start-values.txt"

NB: In the reg query command, you have to change "SYSTEM" with the name you gave to your loaded system hive.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top