Home / server / Questions

Questions[stoperror](server)

Martin Hope
NickG
Asked: 2017-01-13 02:01:51 +0800 CST
  • 2

I'm trying to create a Windows Server 2016 instance on Hyper-V 2008 and it fails to boot from the ISO because of a stop error "MACHINE CHECK EXCEPTION". Is installing 2016 not possible on an OS as old as 2008 R2?

I've tried installing the same ISO on Windows 10 HyperV and that works OK.

Is the only solution to upgrade the host OS to a later version?

hyper-v stoperror windows-server-2016 hyper-v-server-2008-r2
Martin Hope
Andy Arismendi
Asked: 2012-02-09 00:45:09 +0800 CST
  • 2

When Windows is installed it searches it's driver database and installs the appropriate HBA driver so the boot loader can access the drive and boot the system. When an image is taken and cloned to a machine of an incompatible HBA type, Windows will fail to boot with a 7B (inaccessible boot device) error because it doesn't rescan for HBAs every boot.

What are ways of getting a Windows image that was created on a machine with one HBA type to clone onto another with an incompatible HBA type? For example non AHCI to AHCI, RAID to non-RAID, IDE to SCSI, etc...

Contraints:

  1. Free methods are preferable.
  2. The image can't be pre-syspreped and loaded with drivers for a bunch of different HBA types.
  3. I also may not have the system type the image was taken from in the first place.
  4. I'd like to stay away from the Windows repair approach because I think that makes other changes other than just fixing the HBA driver (if it even does fix the HBA driver).

The only way I've been able to get this to work is to:

  1. Install a fresh copy of Windows onto the machine I'm cloning to. F6 driver additions added if required.
  2. Extract the CriticalDeviceDatabase registry information and driver sys files with a script I wrote.
  3. Image over the machine with the incompatible image.
  4. Boot up into ERD commander and attach to the Windows install and import the registry data and driver files I previously extracted.

This typically works however it's not particularly easy and ERD commander is aging. It's not even based on WinPE.

The reason I use ERD commander is that it can attach to the registry hive with read/write access and has read/write access to the disk. I use both of these capabilities to import registry data and driver files.

So far this approach has generally worked for me however I want to see what other ways people have to solve this problem considering the constraints I've listed.

windows imaging stoperror hba sysprep
Martin Hope
palehorse
Asked: 2009-05-12 07:55:06 +0800 CST
  • 3

We have a Dell PowerEdge 2950 running Windows Server 2003 R2, Enterprise x64 with Service Pack 2 installed.

Recently, we've been experiencing multiple STOP errors occurring with that server. Fortunately it is in place as a fail over machine so it is not currently affecting our production environment. The error that shows up in the server log is this:

Event Type: Error
Event Source:   System Error
Event Category: (102)
Event ID:   1003
Description:
Error code 000000000000009c, parameter1 0000000000000004, 
parameter2 fffffadf90881240, parameter3 00000000f2000000, 
parameter4 0000000000060151.

So far the best I've been able to track down is that the 9C error is some sort of generic hardware problem. The other parameters have been no use in narrowing this one down.

There have been no hardware changes since the machine was brought into service last year. It has a twin box that is identical (the primary that this one acts as a fail over for) that is not experiencing the behavior. The last software change was on 4/16/2009 when several security updates were applied. The blue screens started happening on 5/9/2009.

Are there any diagnostics that may help with tis problem?

windows-server-2003 bsod server-crashes stoperror