Can you get into the recovery tools and do a Refresh?
How do you fix Surface Pro 3 BSOD after Sysprep?
I am trying to create a reference image for our company, but I haven't had any success. Machine keeps on blue screening after I ran sysprep. When I ran sysprep, it goes to the normal process then the Shutting Down with spinning dots show up, and then bluescreen. Just wondering if someone out there had similar issue and was able to fix it.
Thanks!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
7 answers
Sort by: Most helpful
-
Anonymous
2015-01-15T01:18:03+00:00 -
Anonymous
2015-01-15T16:46:43+00:00 After it blue screens, it restarts normally, but then when I try to Sysprep again, I get a different error saying "Sysprep 3.14: A fatal error occurred". So I had to start installing the OS from scratch again. And when I try to sysprep, same pattern, bluescreen then automatically restarts and when trying to sysprep again, fatal error occurred.
-
Anonymous
2015-02-05T13:38:07+00:00 We're trying to sysprep a Surface Pro 3 here as well and also getting a blue screen when the machine tries to shut down.
After 3 attempts (restoring to a pre-sysprep state each time) we decided to run Windows Update before sysprepping which applied a firmware update and whatever hotfixes were missing but that made no difference either. The Panther\setuperr.log file shows a big list of:
"Failed to secure driver file C:\Program Files\Intel\OpenCL\bin\x64<filename> Err=0x3"
All of these lines look to be Intel related. And then:
0x0f0073 RunExternalDlls: Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet=0x1f
WinMain: Hit Failure while processing sysprep re-specialize internal providers; hr=0x8007001f
The blue screen info:
The bugcheck was 0x0000009f
DRIVER_POWER_STATE_FAILURE
We can get the machine to load back into Windows, that's not a problem, the problem is we need to be able to sysprep the device in order to create an image we can use to deploy to more Surfaces.
edit: I should mention that the Win 8.1 Update 1 install that we're trying to capture has obviously been done using the latest 8.1 Update 1 MSDN iso, not the OEM install that came pre-installed on the surface.
edit2: It's probably also worth mentioning that we used the January 2015 driver pack so have the latest drivers available installed. I did just try grabbing the latest Intel HD4600 drivers however they refuse to install on account of the device being a Surface and refer me to the manufacturer. So, manufacturer?
edit3: Using the exact same install media (MSDN Win 8.1 Pro x64 Update), sysprep works fine on a Lenovo W540 so the issue is specific to the Surface Pro 3. This really isn't helping with corporate take-up of Surface devices and even mean we end up not going with the Surface, this needs addressing asap.
-
Anonymous
2015-02-05T17:31:20+00:00 -
Anonymous
2015-05-19T14:24:34+00:00 did you get a solution for this?