Blue screen because of AHCI drivers when running sysprep to prepare OS
Question
Answers
All replies
-
Also here is a screenshot of my push task sequence.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com -
I also went as far as to recreate my task sequence to "apply data image" as opposed to "apply operating system". I'm assuming this just straight applies the image and leaves the unrolling to you so I figured it would have less of an imact on the image. Keep in mind the image file that I'm referencing when I created it and rebooted the PC unrolled perfectly fine with BSOD.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com -
So I've gone to the next step. I did the manual sysprep and it worked perfectly fine. So I copied the sysprep folder back to the hard drive. I then used the capture media CD to capture my image to WIM format. Once the capture is complete I reboot the machine and unroll it. Everything works perfectly fine. So then I create a task sequence to deploy the WIM file to the machine. It deploys the image. Then when you reboot it goes through the sysprep mini setup. On the next reboot I get below. I'm completely at a loss at this point as to why the image would unroll from the capture sequence but when redeploying it fails. It should be the same exact image. Makes no sense.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com -
I decided to make the following change to my task sequence below. Same thing, boot to Windows
XP sysprep mini setup perfectly fine. Then when it reboots BSOD.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com -
The reason I separated the build & capture was so that I could load custom software/settings etc. before capturing the image. Below is a screenshot of my Build portion. You can see I had to add a custom step "Apply Driver Package" Without this step I would get the same exact BSOD.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com -
I've already tried this in the past but you give me an idea from your post. I'm going to try to put the "Apply Driver Package" step into my deploy task sequence.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com -
Ok here is what I have.
1. Deployed XP. Downloaded all my drivers, software, updates, etc.
2. Manually ran sysprep using these lines below.
[Sysprep]
BuildMassStorageSection=No[SysprepMassStorage]
PCI\VEN_8086&DEV_2929&CC_0106=C:\Drivers\MSD\IMv89\iaAHCI.inf ; Intel(R) ICH9M-E/M SATA AHCI Controller
3. Manually sysprep'd the system so that I could test it out. It worked unrolled everything was fine.
4. Copied the Sysprep back since it was deleted.
5. Used the capture media CD. Ran the wizard selected where to save the .WIM file. Everything worked good.
6. After the WIM file was created reboot the client machine. It unrolls perfectly fine. NO BSOD.
7. However, once deploying this image back to the same exact machine it BSOD.
8. Mounted the WIM image to extract the sysprep and c:\drivers directory. This way I could verify the integrity. Looks fine.
9. I then tried to use an "Apply Data Image" in my task sequence as opposed to "Apply Operating System Image". This did not work.
10. Here are the task sequences that I've tried.
Here is what the most baffling part to me is. If I captured the WIM file and then rebooted the source machine. How could it be when I redploy the same exact WIM file to the same exact machine that it would fail? The data should be identical. Any feedback would be great as I'm at a total loss at this point.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com -
One thing I did not add in the steps above is that if I did a scratch load of Windows XP SP3 I would get the same BSOD. I had to add the following to my task sequence in order to just do a plain deployment from the XP SP3 CD.
This is a screen shot of what I had to do but do not look at the other steps in the task sequence just the "Apply Driver Package" step that is the relevant one.
Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com
