Windows 10: BSOD during update from Windows 10 TP

In first, sorry for any English mistakes, I'm Dutch.

I'm experiencing a BSOD during the update from Windows 10 TP build 10074 to 10122 or the newer 100130. When the install is at 32% it crashes with the error CRITICAL_PROCESS_DIED or DRIVER_POWER_STATE_FAILURE. It then restores the previous build (10074) and gives me the error "The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation" and 0xc1900101 - 0x30018. I've tried all of the common fixes for this error but none fixed the problem.

It's driving me nuts, could someone please help.



:)

 

Windows 10 notification on windows 10 Insider Preview

Navneet, from your reply, I understand.that it will not be possible to update from the TP version to the release version of Windows 10. Is this correct?

Having upgraded my windows 7 to the TP, how do I remove the TP to restore windows 7?

 

Get rid of defender !

I agree you shouldn't install any third-party Anti-Malware for Windows 10 TP. The reason is other Anti-Malware products are not officially supported on Windows 10 TP, which means even though, you might be able to install them and run them, they haven't tested
properly with Windows 10 TP and they might not work well and cause error and problems.

You may only install them , if the manufacturer indicate their products is working and supported on Windows 10 TP. Of course during final release of Windows 10 TP , there would be many compatible version of Anti-Malware products but for now, it is better
you don't install any other Anti-Malware products.

 

Here's the 0x9F
Code: DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe001723146f0, Physical Device Object of the stack Arg3: fffff8039ae73990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe0017a8473f0, The blocked IRP[/quote]
Looking at the blocked IRP it's pointing to the nVidia driver causing the POWER_STATE_FAILURE.

Code: 0: kd> !irp ffffe0017a8473f0 Irp is active with 6 stacks 5 is current (= 0xffffe0017a8475e0) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [ 0, 0] 0 2 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 ffffffffc000000e [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 16, 0] 0 2 ffffe001723146f0 00000000 fffff8008b9a0d08-ffffe0017aadb610 \Driver\pci nvlddmkm Args: 00000000 00000000 00000000 00000000 >[ 16, 2] 0 e1 ffffe0017a845040 00000000 fffff803993a9e7c-ffffe0017ad6cea8 Success Error Cancel pending \Driver\nvlddmkm nt!PopRequestCompletion Args: 00000000 00000001 00000001 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-ffffe0017ad6cea8[/quote]
It may be worth trying to install an earlier driver, or alternatively uninstalling the card through Device Manager and rebooting to let Windows install the generic driver it applies by default. Then try updating the build.

Code: 0: kd> lmvm nvlddmkm start end module name fffff800`8b840000 fffff800`8c311000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Sun May 10 19:38:11 2015 (554FA593) CheckSum: 00A95F35 ImageSize: 00AD1000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
I'll have to look more into the other dumps you're getting but though I'd post that info up for you in the meantime.

 

Thanks!! I'm going to try this, will let you know if I succeed!

Edit:
Too bad, still the same error.. Any other suggestions?

 

This was the first Google result. I'm on build 10122 with Nvidia graphics. 3 days in a row it has forced a mandatory update but bsod during the update and restores back to 10122. Same each time. Tried clearing the update directory but didn't help. Probably a fix coming soon. Imagine going live next month with an unsafe updater *Shock

 

Ha cool! *Smile
My laptop does also have a Nvidia (Gt745m). I'm on build 10074 (still) and I never updated. I also tried to clear the update directory but also no good.
I reaaaaallyyy hope Microsoft has everything fixed before the launch.. so I don't need a fresh install *Smile

 

The new install won't know about hardware changes made in the previous install *Wink
The only way to do that is to pull the card, if that can be done.

See if installing when NOT connected gets you past the BSOD.

How would you do that you might ask.
First, get the install media for your wireless adapter if you use one. Store it on a USB thumb drive.

Then fire up Windows Update (WU) and let it begin the 10.0.130 download / install process
When it goes into the Preparing stage, copy the ESD file to a new location (see tutorial)
Then follow this tutorial: ESD to ISO - Create Bootable ISO from Windows 10 ESD File - Windows 10 Forums

You only have a short time to copy the ESD before Windows is done with it (about 10% of the preparation stage) and deletes it. There is enough time to copy it though.

Then put the ISO to a DVD or USB flash drive, boot from that to install
Remove the Ethernet cable if you have a wired conneciton
If you also have a wireless connection, the install asks for you to tell it which SSID to use
- press the Skip this step so you do not connect.

If this works, don't install anything or do much personalization.
The first thing you should do is connect again and run Windows Update (WU) - this should get all of your drivers.

I should caution you in that when I installed the first time, I went through the procedure above. Windows behaved as a caged beast, 99% disk activity and too many Autoruns (almost every conceivable driver was installed and set to run automatically). I'm on my third iteration of 10.0.130 and things are running well enough for development code, but I almost gave up on 10.0.130. The good news is that once you have the ESD, ISO and install media created, you can dispense with the download part.