At work we use SCCM to image computers that we deploy. Once in a while a computer won't image. I have taken a screen shot of the error that sccm throws, but the SCCM guys tell me that it is too generic to determine the problem.
These are HP elite 8200 pc's and the part numbers are the exact same. So on a 8200 that took the image, in msconfig I enable boot logging, then I swapped the hard drive for one that didn't accept the image. When the computer that didn't take the image has the hard drive in it from the computer that did take the image, it won't boot. So I take the hard drive out of the bad 8200, and look for the ntbtlog.txt, but it doesn't have it. If I put it back in the 8200 that imaged correctly, then it creates a ntbtlog.txt file.
My theory is that there is a driver that SCCM or Windows doesn't like. But the boot logging file isn't created, so I'm guessing Windows dies before it can create the log.
So is there a way in Windows 7 to boot so that each driver is loaded interactively?