Bugcheck 10d during upgrade to Windows 11 from Windows 10

Anonymous
2025-02-22T03:44:50+00:00

So I've been trying to upgrade my system to Windows 11. I've upgraded my processor, motherboard and RAM to something that is Windows 11 compatible. The PC Health Check app says that my system is now fully ready for Windows 11. I download the Windows 11 package from Windows Update, and then schedule the upgrade at night. When I come back to check it, it seems that during the upgrade process it undergoes a Bugcheck 10d (0000000000000006, 0000000000000003). This has happened consistently 3 times in a row. It then reverts to Windows 10.

Windows for home | Windows 10 | Install and upgrade

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.

0 comments
Answer accepted by question author
Anonymous
2025-02-26T06:57:26+00:00

Windows has a tool to find misbehaving drivers: Windows Driver Verifier (WDV)

https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Driver Verifier - Windows drivers | Microsoft Learn

  1. Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

  1. Create a new restore point Create System Restore Point in Windows 10

https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

  1. Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

https://www.tenforums.com/tutorials/2294-boot-advanced-startup-options-windows-10-a.html

  1. Plan to run the tool with various customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial

  1. Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

Customized tests will then be posted for the next run of WDV.

WDV can run continuously during the testing.

For any BSOD post a new V2 share link into the newest post.

Was this answer helpful?

1 person found this answer helpful.
0 comments

71 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-03-14T15:41:44+00:00

    Another day, and another new BSOD, this time it's called "DPC Watchdog Violation", in about the same place as the previous failure. This installation seems to be cursed, what could be going on?

    Image

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-13T20:30:41+00:00

    Okay, so here's the latest development. Seeing as the previous times that I was running the Windows 11 upgrade resulted in a blank screen and a frozen computer, I decided that perhaps the installer doesn't like the built-in IGPU on this computer. So I decided to install a DGPU that I was planning on installing after the Windows 11 upgrade, earlier than expected. So after installing the DGPU, I ran the Win 11 upgrade again, and I watched it throughout the 4 hour installation. So what I noticed is that it had gotten pretty far into the installation process, almost 50% when a new type of BSOD happened. This time I caught what was shown on screen, this BSOD said, "hypervisor error"! This might have been what's been happening even under the IGPU, but it didn't get shown on screen, for whatever reason.

    Another issue is that this BSOD dump file didn't get saved. It said it was 100% complete, but it didn't get saved to the standard BSOD area. I assume maybe it got saved to the Windows 11 BSOD area, which then gets deleted after the install fails. So there's no new BSOD's in the log package. Here's the latest V2 Log, DESKTOP-YJK-(2025-03-13_15-54-18), for what it's worth since it doesn't include the Hypervisor BSOD inside it.

    I read that the solution to the Hypervisor error is to simply turn it off in the BIOS and attempt it again with it off. I'm going to go do that now, come back to you guys and report later.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-12T22:14:54+00:00

    Multiple times I've requested that you run the two groups and post querysettings or V2.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-12T21:36:33+00:00

    Okay, this seems to have worked, IOMAP has disappeared as a service (the file still seems to exist on drive but unused), and I've been running with WDV activated in the background for 10 minutes and still no BSOD. I will now reset the Verifier settings to normal and attempt the Win 11 upgrade again now.

    Update: Looks like the Windows 11 upgrade failed again with a 0xC1900101 - 0x30018 error message again. This time I watched it go through the steps of installation, I saw it reboot a couple of times, it got upto 30% I think, and then rebooted, and then the next reboot was blank, no images on screen, and no power to the mouse or keyboard, though you could see that the system was on, because you could hear the fans running. I think we've probably done all that we can do to fix any driver issues, and now it's time to look at the Windows 11 install process itself?

    Was this answer helpful?

    0 comments