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

Exchange 2010: All db’s unmounted error -1032 file locked

A client had issues with their exchange server tonight…. All the mail DB’s were unmounted.

When I tried mounting the db’s exchange immediately shot back errors. I then tried running a soft recovery (http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/)of the exchange dbs as the logs were all ok, but I received a strange error from eseutil when I tried recovering: operation terminated with error -1032 file locked

I then stopped all exchange services to ensure exchange didn’t have a lock and retried still getting the same error. I then tried to write to the drive holding the logs and I was unable to write to it…. I then verified free space which was good, SAN for issues…it was OK. I then rebooted and retried thinking it was a fluke…no go. I rebooted into safe mode and ran:

diskpart

list volume

select volume 2

Ran the command:

attributes volume clear readonly

I did this on all volumes, made sure I could write to them all then rebooted and tested exchange satisfactory.