Windows 10 Anniversary Update BSOD 0xC1900101-0x4000D and More!

Hi, this is my first post so I apologize in advance for any naivete.

Right, so I've been using Windows 10 home without (much) issue for months now, and I decided to do the anniversary upgrade. All is well until it gets to ~75% at which point I blue screen with error

0xC1900101-0x4000D - The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation

This started me off on a long and frustrating journey over the last three days desperately trying everything I could find online to fix the issue, but I'm at the point of giving up, so I figured maybe some kind soul would aid me online.

Thing's I've tried thus far (that I can remember - it's been a lot):

• Doing the anniversary upgrade from windows update
• Doing the anniversary upgrade via the windows upgrade assistant
• Doing the anniversary upgrade via ISO
• Doing the anniversary upgrade via ISO from bootable USB
• Reinstalling (not fresh) Windows 10, which yields bsod
  0xC1900101-0x2000C - The installation failed in the SAFE_OS phase with an error during APPLY_IMAGE operation
• Ran chkdsk, which fixed a couple corrupt files, but didn't solve the problem
• Ran sfc, which reported no errors
• Updating every driver I could (using DriverMax to identify out of date drivers, but not to install them)
• Ran driver verifier with all options but low resources simulation on all non-microsoft drivers, which causes a bsod before it gets to login
  DRIVER_VERIFIER_DETECTION_VIOLATION
  . I have the minidumps of this (attached the latest), but have been unable to identify the culprit
• all these things multiple times, plus probably a whole load of other stuff i'm too fried to remember atm

Other information that may be useful:

• Desktop I built ~5 years ago
• Windows 10 Home 1511
• ASUS P8P67-M Pro Motherboard
• Intel i5 2500K
• Zotac Nvidia GeForce 560 ti
• 2 x 4 GB DDR3 1333 mhz RAM
• 128 GB SSD which holds primarily the OS (has ~40 GB free atm)
• 500 GB HDD which holds everything else (notably my user folder)
• This computer has had stability issues for years now which has caused me boundless frustration, both application crashes and BSODs, however they happen infrequently enough to live with and seem to be utterly and completely unpredictable. This is a whole other can of worms that I don't think is related to the issue at hand.
• Although I've been trying tons of things these past few days, as far as I know I've not "cluttered" my OS in the process. I think it's in a relatively stable, clean state as it stands.

If anyone's willing to take a crack at this headache of mine I'd be infinitely appreciative!

Ran the DM Log Collector - attached is the result.

Edit:
I forgot to mention, I've also tried uninstalling my antivirus as well as disconnecting everything from my computer during installation (internet, mouse, keyboard, printer, etc.), to no avail.

I'm having the exact same problem. Have tried 3 times on 2 different computers with the same 0xC1900101-0x4000D error each time. Both computers are basically same hardware but different AV (one is Bitdefender and other is Trend) so I don't think it is the AV. In searching, I have seen mention of the system or recovery partition being too small. I have a 'Windows RE tools' partition of 1023 MB, a 'SYSTEM' partition (FAT32) of 360 MB and a 'Recovery Image' partition of 15.56 GB in addition to the regular 'Windows' partition. I'm not sure which one might be the problem - I think I have seen reference to the size of the SYSTEM partition but I can't find again where I read this. Have you looked into this aspect?

jesser said:

I'm having the exact same problem. Have tried 3 times on 2 different computers with the same 0xC1900101-0x4000D error each time. Both computers are basically same hardware but different AV (one is Bitdefender and other is Trend) so I don't think it is the AV. In searching, I have seen mention of the system or recovery partition being too small. I have a 'Windows RE tools' partition of 1023 MB, a 'SYSTEM' partition (FAT32) of 360 MB and a 'Recovery Image' partition of 15.56 GB in addition to the regular 'Windows' partition. I'm not sure which one might be the problem - I think I have seen reference to the size of the SYSTEM partition but I can't find again where I read this. Have you looked into this aspect?

This has not come up in anything I've read thus far concerning the issue. My partitions are even smaller than yours (100mb for system, 450mb for recovery), so I suppose it's possible.
Apparently Windows 7 uses 100mb for the system partition, whereas Windows 8/10 are supposed to use 350mb, which explains the size of mine as my hard drive was never reformatted during the upgrade process from 7. This is something I will look into.
As far as the recovery partition, according to google 450mb is normal for Windows 10, so yours seems excessively large.

Okay, so I expanded my system reserved partition from 100mb to 500mb, and tried again. I ran the iso installer from USB, disconnected everything else, made it to 86%, and then BSOD'd with

PAGE_FAULT_IN_NONPAGED_AREA

and then I got the same

0xC1900101-0x4000D - The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation

Man, I give you credit for keep at it. Right now I don't have the time to wait around for it to go through the whole thing and fail again. Is this any help? I found it here:

Solved SFC and SFCFix Logs (Windows 10 corruptions) - Windows 10 Forums

"After doing some more research, it was confirmed by other people that in-place upgrade leaves the installed applications untouched.
So, I went ahead and carried the in-place upgrade and also was going well until the very last stage and then again PC decided to restart at 93% and then the same extremely frustrating Restoring Your Previous Version of Windows and was back to where started.

But this time, the Windows Media Creation Tool showed the below error code!

0xc1900101-0x4000d the installation failed in the second_boot phase with an error during migrate_data operation

So, it was time for a new researching session. After some researching, I came across some suggestions as below from different websites/forums.


"Ok, I finally got it working. I don't know what did it, but it must have been one the following.
What I did:
- Deinstalled Avira Antivirus
- Enabled Windows Defender instead
- Deleted Items in Prefetch-Folder (C:\Windows\Prefetch)
- Deleted Items in Temp-Folder (%USER%\AppData\Local\Temp)
- There was one driver update pending for my WiFi adapter which always failedonupdate. I updated it manually
- I also updated my Intel-Graphics-Driver
- Uninstalled Windows Phone 8.1 Emulator
- Disabled all Services, except Microsoft Servicesinmsconfig
- Disabled all Startup Items in Task Manager
- Downloaded Update again
- Installed successfully
I hope this helps someone, glad it finally worked.
See you at #10049 :)"

Source1: Eror Error 0xC1900101 - 0x4000d When I instal Windows 10 technical - Microsoft Community


Source 2: Fix: We Couldn 0x400D) Error

The above two I can remember I followed and then ran the in-place upgrade and it worked and completed the in-place upgrade installation. Finally worked!!:):):)

After that, I ran SFC /scannow and that also completed with no violation found. Another great thing!

I am yet to check how things goes with the Auto Wake Up from Sleep Mode and freezes and also Driver Verifier related BSODs.

Right, so I followed the suggestions by jesser, disabled all non-microsoft services, disabled all startup apps, and cleared out the pre-fetch and temp folders.

To reiterate, my anti-virus has been disabled from the start, I've updated all my drivers to the best of my ability, and am disconnecting everything from my computer when doing the install, once it's finished downloading.

Did the install this time via Windows Upgrade assistant, got to something like ~85% no problem, then the same BSOD once again

PAGE_FAULT_IN_NONPAGED_AREA

Attached is a fresh zip provided by dm log collector.