un-repairable STOP: 7B error following using a faulty USB drive

redfive · 03 Jun 2012

I recently plugged in a Corsair Voyager USB stick which turned out to be faulty. As part of confirming this (after not being able to access it in Windows) I checked if it was visible in the BIOS which it was but seems to be dead. I removed the Voyager drive but upon the restart Windows failed to load, it gets to the load screen and just as the animation starts it BSODs for 0.5 of a second and then restarts. It does this without fail in safe mode and does the same with the HDD plugged into another PC.

Nothing in the Recovery Console fixes the problem, CHKDSK says there are no issues, for some reason Sys Restore isn't functioning in the RC etc etc. I managed to get the stop code:

stop: 0x0000007B (0xFFFFF880009A98E8, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

This suggests to me that there is probably an issue with the SATA / chipset drivers and I can only assume that they have somehow been corrupted when Windows was trying to detect the faulty USB stick.

I know that SATA drivers can be installed separately on a Win install but surely you can also re-load them or load default drivers in the Recovery Console from either the Win7 disk or chipset drivers from another location.

If anyone has a link or instructions to how to carry out the above or any other information it would be greatly appreciated.

EDIT - meant to say that after chkdsk completes is comments "Failed to transfer logged messages to the event log with status 50" - unsure what this suggests.

usasma · 03 Jun 2012

Start with these free, bootable diagnostics: Initial Hardware Diagnostics
Post the results and we'll move on from there.

redfive · 04 Jun 2012

Thanks for the reply, the HDD is clean and there are no hardware issues with it or the PC itself.

usasma · 04 Jun 2012

I presume that you mean the hard drive passed the long/extended/thorough test using the appropriate manufacturer's diagnostic program?

If so, then it's time to try using Startup Repair: Startup Repair
Run Startup Repair a minimum of 3 times. If it still doesn't fix it, then go into the Command Prompt (in Startup Repair) and run these 3 commands (pressing Enter after each one):
bootrec /fixboot
bootrec /fixmbr
bootrec /rebuildbcd

If that doesn't work, then a repair install is next: Repair Install

redfive · 05 Jun 2012

Yup, all hardware diags came back clean before I posted here so have definitely ruled out a HW problem.

I mentioned in my first post that I tried everything in the Revovery Console including Startup Repair, Sys Restore to no avail, should have expanded that this included the standard /fix & /rebuild procedure but with no success.

It seems that a repair install will only work if you have access to Windows which I do not, not even in safe mode.

writhziden · 05 Jun 2012

Did you run Startup Repair three times? Startup Repair - Run 3 Separate Times

Troubleshooting Windows 7 Failure to Boot may also be of interest to you.

redfive · 05 Jun 2012

Yup, have done everything possible in recovery console including the 3 times startup repair trick.

Out of the "troubleshooting windows 7 boot failure" I have already tried everything there apart from point 8 (as I can see all the data on the drive when plugged into another PC as a slave) and obviously also not tried 9 or 10 due to this.

I am almost resigned to taking the data off the drive and starting from scratch, it's more the programs and their relavent settings and profiles which I don't want to loose or have to recreate from scratch.

usasma · 06 Jun 2012

Here's a suggested sequence for a "clean" install of Windows:

Backup, Wipe, and "Clean Install" of Windows

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7 and Vista.

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

NOTE: If this is due to an infection, remember to scan the data with another system's current antivirus in order to locate and remove any malware.
NOTE: Disconnect any additional hard drives (internal and external) that you may have installed. This may break any multi-boot setups that you have, so be prepared to conduct recovery operations on them once you're done. Don't forget that, if this is due to an infection, the additional hard drives may be infected also.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).

3. Use one of these free utilities to wipe the hard drive clean:
KillDisk ( Freeware Download Active@ KillDisk ).
DBAN ( DBAN Download | Darik's Boot And Nuke )
This will also delete any recovery partitions on the system - so the installation/recovery DVD's are essential!!!

4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!

5. Visit Windows Update and get all updates

6. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)

7. Visit Windows Update and get the Service Packs for your system. (usually under Important Updates).
Read these notes for installing Windows 7 SP1: Learn how to install Windows 7 Service Pack 1 (SP1) and Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
Read these notes for installing Vista SP1: Learn how to install Windows Vista Service Pack 1 (SP1)
Read these notes for installing Vista SP2: Learn how to install Windows Vista Service Pack 2 (SP2)
Search Google/Bing for installing other OS's Service Packs.

8. Visit Windows Update and get any other available updates

9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

10. Test to see if the problem remains.
If the problems persist, then the problem is most likely with your hardware.
If the problems are gone, then proceed with installing the latest version of your favorite programs, testing after each one for errors.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009/2010 is OK. Updates are available at the Asus support website.

CAVEAT: If you have a Sony system, make sure that you DO NOT have the 2007 (or earlier) version of the Sony Firmware Extension Parser (SFEP.sys). Update this driver immediately!!!

redfive · 06 Jun 2012

Looks like a helpful guide but, as I mentioned above, though I may soon be resigned to a clean install it is my last resort. I have definitley ruled out a hardware issue and the instillation is definitely not infected, I also have tools like KillDisk but as above I am trying to explore all possibilities before having to re-install. My general IT knowledge, especially hardware, is good enough - it's simply that I have reached the limits of my Windows knowledge. I can't believe that there's no way to repair an install when running as a slave drive or why Windows only seems to be capable of diagnosing itself in what is almost an abstract manner.

writhziden · 06 Jun 2012

The boot troubleshooting guide I gave you was made by one of the best, if not the best, of our boot and install experts. If going through that guide did not resolve the problem short of the clean install, then in my opinion, you are going to be hard pressed to resolve the problem otherwise.

The only thing that guide does not include that I have seen resolve such problems before is the following:

You will need a Windows 7 repair disc or you can use the Advanced Boot Options to get to the System Recovery Options.

Then try the steps in Startup Repair Infinite Loop Recovery. Note the warning:

Warning

The instructions presented withing this tutorial must be followed correctly, or you can damage your Windows 7 installation even further. This tutorial is designed to help recover from a bad registry that is causing the startup repair loop. You should note that there may still be some issues remaining that cannot be fixed by manually restoring the registry.