Try running this registry fix on the XP system before you run sysprep. It might also be the SATA mode setting in the bios that is causing theBSOD, might try setting it to compatibility mode and see if it will boot.
Mergeide.reg 6.8 K
as cgodden said, it is most likely your SATA controller driver not properly loaded.
You can disable the automatic reboots by hitting F8 during your boot and choose "Disable Automatic Restart on errors" That should at least give you the BSOD error code and further investigate.
Also here is documentation on the mergeide.reg - http://community.landesk.com/support/docs/DOC-8455
Does the BSOD give a 0x0000007b error? If so that's the hard drive controller. If it's a non-standard controller then you would need to inject the correct driver. If it is a controller that XP has default drivers for then you will want to follow the steps in this article:
It outlines a problem with the different standard hard drive controller drivers in XP and how they are handled, as well as a workaround to resolve it.
Let me know if this helps!
Looks like I should read all the posts before I make my own. This information is already listed. Sorry guys!
From reading that one document, I think doing the mergeide.reg before I sysprep could resolve my problem. The BSOD error is about the harddrive controller and it's safe to assume that's part of the problem. I DO have the correct sata drivers injected, but since I built the image on an IDE harddrive I'm going to need to run that reg patch. I will try it in a little bit and post back with my results.
I dont know if creating your master image on a machine with IDE would be the problem. I built my master on the oldest machine I could find with IDE hard drive and have deployed the image using HII to many different models with primarily SATA hard drives. Its worth a shot but dont see how that would cause it. The only issues I ever had with a machine looping was and incorrect SATA driver.
Yea I mean what I tried to do to "test" HII was build an image on the oldest machine we have and deploy it to my machine, which is one of the newest. I'm fairly certain the sata driver is correct but I will try to find the driver from a different source and see if that works too.
alternatively you can take a look at Jan Buelen's MSD utilities: CaptureMSD and InjectMSD
Summary of the utilities:
CaptureMSD: you run this on the working machine and it captures the hard disk controller drivers and registry entries
InjectMSD: you run this in your OSD script or Provisioning template after the image is layed down to inject the drivers and registry entries.
I still use this way and it hasn't let me down. but this is not the LANDesk way so (disclaimer)
I had a simliar issue and changing the SATA from AHCI to compatibility fixed the issue for me. No BSOD after boot! Thanks!