Deployed Windows 7 Image failing to start -SCCM 2012 SP1
Hello, I am deploying windows 7 image using SCCM 2012 SP1, the installation goes thru fine but when it is in the process of restart, a blue screen is displayed for a split second and then it tries to reboot again with same results. Are there any logs on
the SCCM server I can check to see where the problem may be?
January 10th, 2014 7:38pm
Are you applying a driver package in your task sequence for that particular PC make and model?
January 10th, 2014 7:48pm
No driver package is being applied. All the drivers are under Drivers.
January 10th, 2014 7:52pm
Could possibly be a driver issue. Does this happen on all devices or just one model? If it's just one model perhaps you could consider testing with a driver package only.
January 10th, 2014 7:58pm
with all models. That's why I was trying to see if there are any logs I can check off the SCCM server.
January 10th, 2014 8:02pm
Tried safe mode with command prompt but same results. It won't let me get to the logs...
January 10th, 2014 8:07pm
Does it fail during the TS or just reboot and BS. What OS are you deploying? Are you PXE imaging? Can you find the report "History of a task sequence deployment on a computer" and see if the error is in there for an unknown system?
January 10th, 2014 8:10pm
It's failing at reboot, the windows logo comes up and then a quick blue screen ant it tries to reboot again. I am deploying Windows 7. I cannot access the imaged computer at all, even safe mode with command prompt does not work.
January 10th, 2014 8:14pm
Can you boot back up to WinPE and access c:\?
January 10th, 2014 8:15pm
You need to get the blue screen error code. When it reboots, hit F8 like you are going into safe-mode but instead of doing so, choose the option that says something like proceed but do not automatically restart on error -- it's near the bottom, next to last
if I remember correctly. Then, the blue screen won't go way and you can troubleshoot based on the error code (and post it here).
January 10th, 2014 8:29pm
January 10th, 2014 9:05pm
Gerry is correct that this means inaccessible boot device (not usually though, always). And, it is always the result of a missing or bad storage driver. You need to add the appropriate storage driver for deployment during the TS.
January 10th, 2014 9:13pm
Remember to update driver packages, boot and dp..
January 10th, 2014 9:26pm
Still failing!!!Here are the boot and OS settings
January 11th, 2014 1:32am
January 11th, 2014 1:32am
January 11th, 2014 1:33am
Any idea on what's wrong with the settings above and why it's unable to boot up?
January 13th, 2014 11:47am
Sorry, but what you've posted above has nothing to do with adding the proper storage drivers to the deployed OS image so I'm not sure why you're expecting different results. As Mentioned, a 7B blue screen code is always related to storage drivers and the
accessibility of the storage.
January 13th, 2014 1:33pm