0x0000007B – Ramblings of an IT Admin

STOP 0x0000007B Resolved on P2V’d Windows SBS 2011

***The following was on a Hyper-V vm, but this also applies to VMware.***

****This should work on most versions of Windows (doesn’t have to be SBS)****

The other week we picked up a new client with an emergency issue. They had an SBS 2011 Server on failing hardware. The hardware was so bad that we didn’t think it would last until the replacement server would arrive. We had an older Server that had enough power to handle their server virtualized until their new hardware arrived. So I started the virtualization process. This is where the fun began. (There were several issues minor issues, but I’ll stick to the major problem here.)

After creating the vm without any disk drives, I attached the newly created drives and powered up the vm and was greeted by the BSOD: STOP 0x0000007B.

Luckily there is an easy fix for this and you don’t need restart the p2v.

Boot the vm off any Windows CD/DVD (Windows 7 & up. Doesn’t have to be the same OS as vm. You could also mount the drive on the host or another vm. If you mount the drive, just run regedit)
After booting off OS cd, when you encounter the language selection, hit Shift-F10 for a command prompt
At the command prompt, run regedit
In regedit, highlight Hkey_Local_Machine
With Hkey_Local_Machine highlighted, goto File, and Load Hive
In Load Hive, select the drive letter where Windows OS was installed (C: in this case), then go to: Windows\System32\config\system
Name the Hive whatever you want (IE: recovery)
Expand HKEY_LOCAL_MACHINE\recovery\ControlSet1\Services\intelide
Change the data for value “Start” from “3” to “0”
Now goto File and “Unload Hive” (If you run into issues make sure Hkey_Local_Machine is highlighted)
Exit regedit and reboot the machine and you’re good to go

If you still have issues after reboot, check the following keys and set them to:

Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

Resolving issues after migrating Windows 7 to new hardware (BSOD Stop 7B 0x0000007B)

Awhile ago, I had a client that had purchased several of the same laptops for training purposes. Since all of the laptops were the same make and model, I setup 1 of the 10 as a master image that I had locked down so the trainees had limited access to the pc. Any changes made are automatically wiped after logout/reboot. For faster deployment of the laptops, I had created an image of the first laptop via Clonezilla (I am a big fan of Open Source).

A few years had gone by and there was an issue with one of the laptops. We checked the warranty status and found it was out of warranty. Rather than pay for repairs, it was cheaper to find a replacement on Amazon. Unfortunately, the one on Amazon had a different processor (not that big of a deal).

The new laptop arrived and I pushed out the image to the replacement laptop and when it booted we were greeted with the BSOD Stop 7B 0x0000007B. Rather than reload and reconfigure Windows from scratch I used a tool I had used in the past to help with this exact issue: fix_7hdc.vbs. To resolve this:

Download fix_7hdc.vbs and copy the .vbs to a USB drive
restart the pc.
When the pc is restarting keep tapping the F8 key.
When the Advanced Startup Options Menu appears, Select “Repair My Computer”
In that window, select “Command Prompt”

Insert your USB drive
To find the drive letter of your USB drive via DOS prompt type: wmic logicaldisk get name,description
Once you have the drive letter, goto that drive: e:
Run the script via: cscript fix_7hdc.vbs /enable /search
When the script is done, you are safe to reboot.
Windows made it quite a bit further after reboot, but it still had issues so I rebooted into safe mode and logged in as the administrator and let Windows Find and install the drivers it was able to on its own. When completed I rebooted to Windows and downloaded the rest of the needed drivers and installed the latest Windows updates.