Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I currently use Clonezilla to copy an image of a computer that I've worked on to many computers (a job of formatting and reinstalling Windows on a large amount of computers). I can't remember the blue screen of death notice I always get but it has something to do with hardware and/or drivers. The way I fix this when moving it to a VM is VMWare's vCenter Converter and removing all drivers. How can I do this without VMWare if I'm trying to copy the image to another computer? I can also see this being if I need to move a hard drive to another computer. This can be a solution that I work with clonezilla's file before transferring it to the computer or after I transfer it to the other computer.

UPDATE: I guess I don't mean all drivers but any driver that would cause a BSOD.

UPDATE: The error code I normal get is STOP 0x0000007B

share|improve this question
up vote 7 down vote accepted

Run the sysprep tool. Let it shutdown the computer. Now you can clone the drive.

share|improve this answer
I will give it a try. – Gabriel Graves Feb 28 '13 at 4:06

The stop code (0x7B) means that Windows can't find the boot device. It's not a crash, the loaded drivers aren't causing a BSOD. Windows remembers what device driver it booted from previously and tries it on subsequent boots. If the driver loads, but doesn't find a device, you end up with 0x7B. Removing the driver simply fails the normal boot process, after which Windows tries any driver.

Running sysprep is the recommended way of preparing Windows to be imaged. It fixes a lot of other potential issues all at once. If you don't want to use sysprep you can edit the registry manually to kickstart the driver search process. Microsoft has directions for this process.

share|improve this answer

Use your target system as the template. Take an inventory of the required drivers used by your cloned systems (VM's or not) such as with loadord.exe from SysInternals.

As a measure of prudence, just DISABLE those unnecessary drivers and services. Remember you can start and stop drivers with the same familiar methods of controlling services even if you use, for example, net stop beep.

sc config beep start= disabled (sc.exe relies on those leading spaces, weird) will turn off the pc speaker that annoyingly plays during some functions such as when executing a pause timer command.

hope you're already aware of the necessity of properly configuring your hal.sys when replicating/cloning systems especially when converting to VM's.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .