TechOnTip Weblog

Run book for Technocrats

P2V Migration Gotcha 1: x00007B Blue Screen Error while migrating Windows 2003 x64bit Server

Posted by Brajesh Panda on April 9, 2012

Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware converter. After multiple attempts realised converter is failing at a certain stage; not completing the task. Even if we start the converted virtual machine, it shows blue screen error with x00007B error. This error refers to disk driver issues. Here are my findings about this issue!

  • Mostly all Windows 2003 x64bit servers do not come with LSI logic SCSI drivers in their driver folder. So if you migrate a Win2003x64 server, your migration may fail at VM reconfiguration phase of migration. And if you start the same VM, it will end up with x00007B Blue Screen of Death error!
  • Here are 3 possible reason for this kind of failure (mostly the 1st one)
    • Missing driver file
    • Missing registry keys for these drivers/devices (Registry Entry)
    • Missing start up services entry to load the driver & registy at the boot. (Registry Entry)
  • Missing Driver File
    • Copy symmpi.sys file to C:\Windows\system32\drivers folder of x64bit server.

       

  1. Missing registry keys for these drivers/devices (Registry Entry)

To edit/change registry keys you have to connect system drive VMDK to another live x64bit server & mount the registry hive to perform necessary action.

  • Shutdown broken VM & take copy backup of system drive (C Drive)
  • Connect the system drive to another x64bit working VM & make sure it is detected with a drive letter
  • In the work VM, Open registry, Click on HKLM, Select File & Load Hive, browse to the above drive letter\Windows\system32\Config, Double Click Syste, it will ask you a name, type BrokenSystem
  • Now you can browse HKLM hive of broken system
  • Expand BrokenSystem -> ControlSet001 -> Control -> CriticalDeviceDatatabase
  • Look for a key called pci#ven_1000&dev_0030,
  • If you have a key called pci#ven_1000&dev_0030, Select the same;
  • There should be two strings in pci#ven_1000&dev_0030
  • ClassGUID which has a value of {4D36E97B-E325-11CE-BFC1-08002BE10318}
  • Service which has a value of symmpi
  • If these two strings are either not present in pci#ven_1000&dev_0030 or contain different information, change them.
  • If you do not have a key called pci#ven_1000&dev_0030
  • RIGHT-CLICK on the LEFT PANE and click new -> key
  • key name is pci#ven_1000&dev_0030
  • RIGHT-CLICK in the RIGHT PANE and click new -> string value the name of this value is ClassGUID the value is {4D36E97B-E325-11CE-BFC1-08002BE10318}
  • RIGHT-CLICK in the RIGHT-PANE and click new -> string value the name of this value is Service the value is symmpi

     

  1. Configure “Missing start up services entry to load the driver & registy at the boot” following below process
    1. Shutdown broken VM & take copy backup of system drive (C Drive)
    2. Connect the system drive to another x64bit working VM & make sure it is detected with a drive letter
    3. In the work VM, Open registry, Click on HKLM, Select File & Load Hive, browse to the above drive letter\Windows\system32\Config, Double Click Syste, it will ask you a name, type BrokenSystem
    4. Now you can browse HKLM hive of broken system
    5. Expand BorkenSystem -> ControlSet001 -> Services; if you have a service called symmpi left-click on it Or if you do not have a service called symmpi RIGHT-CLICK on the LEFT-PANE and click new -> key
      1. Key name is symmpi
      2. f the symmpi key is setup properly you should have 7 keys in the right pane.
      3. (Default) (value not set) STRING
      4. ErrorControl (DECIMAL) 1 DWORD
      5. Group SCSI miniport STRING
      6. ImagePath system32\DRIVERS\symmpi.sys STRING
      7. Start 0 (DECIMAL) DWORD
      8. Tag 33 (DECIMAL) DWORD
      9. Type 1 (DECIMAL) DWORD
      10. If you have all of the keys in the right pane, most likely you will notice that the ImagePath key is missing and Start is set to 4 instead of 0.
      11. RIGHT-CLICK on the RIGHT PANE and select new -> String Value name = ImagePath value = system32\DRIVERS\symmpi.sys
      12. Double-Click on Start in the RIGHT-PANE, make sure DECIMAL is selected and change it to 0 if it is not 0 already.
      13. if you do not have all of the keys listed above create them using the method listed below.
      14. RIGHT-CLICK on the RIGHT PANE and select new -> type is either String Value or DWORD (see table above for types, names a values)
      15. Note: when entering DWORD values it helps to ensure that you have DECMIAL selected.

         

Make sure after you have added, adjusted or just verified the configuration of the symmpi service configuration take back the registry hive until you reach to SYSTEM2 and then unload it.

About these ads

9 Responses to “P2V Migration Gotcha 1: x00007B Blue Screen Error while migrating Windows 2003 x64bit Server”

  1. […] to run a standard driver in place of the custom one, things decide to stop working. In my case I followed these steps and got things […]

  2. […] P2V Migration Gotcha 1: x00007B Blue Screen Error while … – Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware … Even if we start the converted virtual machine, it shows blue screen error with x00007B error. … P2V Migration Gotcha 1: x00007B Blue Screen Error while migrating Windows 2003 x64bit … […]

  3. […] P2V Migration Gotcha 1: x00007B Blue Screen Error … – Apr 09, 2012 · Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware converter. After multiple attempts realised converter is failing …… […]

  4. […] P2V Migration Gotcha 1: x00007B Blue Screen Error … – Apr 09, 2012 · Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware converter. After multiple attempts realised converter is failing …… […]

  5. […] P2V Migration Gotcha 1: x00007B Blue Screen Error … – Apr 09, 2012 · Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware converter. After multiple attempts realised converter is failing …… […]

  6. […] P2V Migration Gotcha 1: x00007B Blue Screen Error while … – Fix P2v Blue Screen Windows 2003 Errors – Windows XP, Vista & Windows 7, 8 said. October 12, … Fix Mrxsmb.sys Blue Screen Windows Server 2003 Errors – Windows XP, Vista & Windows 7, 8 said. October 24, … […]

  7. […] P2V Migration Gotcha 1: x00007B Blue Screen Error while … – Fix P2v Blue Screen Windows 2003 Errors – Windows XP, Vista & Windows 7, 8 said. October 12, … Fix Mrxsmb.sys Blue Screen Windows Server 2003 Errors – Windows XP, Vista & Windows 7, 8 said. October 24, … […]

  8. […] P2V Migration Gotcha 1: x00007B Blue Screen Error while … – Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware converter. After multiple attempts realised converter is failing at a certain stage; … Fix Mrxsmb.sys Blue Screen Windows Server 2003 Errors – Windows XP, Vista & Windows 7, 8 said. […]

  9. […] P2V Migration Gotcha 1: x00007B Blue Screen Error … – Apr 09, 2012 · Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware converter. After multiple attempts realised converter is failing …… […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
Follow

Get every new post delivered to your Inbox.

Join 76 other followers

%d bloggers like this: