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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2025-02-23T15:26:05+00:00

    The Logitech SetPoint Unifying KMDF USB Filter - LEqdUsb.sys caused the crash.

    Can you uninstall that software?

    It will be a little difficult as all of the mice I have are Logitech wireless mice. I'll see if can't get myself a simple wired mouse somewhere.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-02-23T15:28:07+00:00

    So I'll go check into the corruption on drive O, it's not really involved in the bootup process, it's used entirely for holding daily system backups. Also drive E, which is just a storage area for games. But it's good to know about that.

    Update: I ran the chkdsk on drives E & O, it found no problems on either of them.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-02-23T22:00:20+00:00

    When you've completed the Sea Tools Long generic and HD Tune Full error tests please post images or share links.

    The reported bad block may not appear if chkdsk was ran before the error or surface scan.

    Run HD Sentinel last and please post images or share links.

    When all of the chkdsk /b /v have completed please run the V2 log collector and post a share link into the newest post.

    The upgrade can be performed after uninstalling the Logitech drivers.

    (Make sure that the non-Windows drives are detached)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-02-26T05:10:20+00:00

    I uninstalled the Logitech Unifying software, but the problem still occurred again. I even tried updating the Unifying software. Also I'm finding that during this upgrade, whenever the Bug check 10d occurs, the machine freezes, and the BSOD doesn't complete saving the dump file. A few early ones got saved, but it looks like the newer ones don't.

    Was this answer helpful?

    0 comments