Main Forum > Tweaking.com Support & Help

Can I boot from a USB and fix a non bootable install

(1/4) > >>

Docfxit:
I have a PC that I get a BSOD 0x7b when I boot into normal or safe mode.

Can I use Windows Repair AIO to repair it?

It has Win7 on it.  It started giving me the 0x7b when I enabled Driver Verifier. I created a USB bootable Win7 so I can run Windows Repair AIO from the USB.  It would be great if it could load the registry of the D: drive and repair what ever is wrong with it.

I saw this in a different post:
- Also make sure to untick those external drives in the main repair GUI.  A USB HDD today can easily contain 500 GB or more in data/info. Because USB disk I/O is (much) slower than disk I/O for an internal drive. (think: serial data transfer versus parallel data transfer).

Thank you,

Docfxit

Boggin:
Are you able to boot up into the advanced boot options to try Last Known Good Config or select Repair your computer and either try Startup Repair or the restore points from the Recovery Environment ?

Docfxit:

--- Quote from: Boggin on February 12, 2017, 12:53:48 am ---Are you able to boot up into the advanced boot options to try Last Known Good Config or select Repair your computer and either try Startup Repair or the restore points from the Recovery Environment ?

--- End quote ---

Yes.  I can get to Advanced boot options.  When I select Last Known Good Config I still get 0x7b. When I select cmd prompt I still get 0x7b.  When I select safe mode with or without networking I still get 0x7b. When I boot to a Win7 CD I can get to Repair.  I have run through Repair /Reboot  three times.  Then I boot into normal mode.  I still get 0x7b.  When I run rstrui.exe from the repair console I get "No restore points have been created on your computer's system drive"

I'd like to know when I look at the boot options with bcdedit /enum  from the repair console is Boot Loader, Identifier supposed to be default like it is or should it be current?

Thank you,

Docfxit

Boggin:
default is your identifier.

Which bcd cmd were you thinking of running ?

Enter bcdedit |find "osdevice" then enter chkdsk x: /f where x is your partition letter to see what that reports.

Ignore the error 50 as it is unable to write a wininit log in this mode.

Docfxit:
I have done that a few times.

Thanks,

Docfxit

Navigation

[0] Message Index

[#] Next page