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-01T03:22:02+00:00

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-01T01:26:06+00:00

    It was not able to be viewed:

    Sign in to continue to Google Drive

    For share links please use drop box or google drive.

    Make sure that links are available without sign in.

    https://support.google.com/drive/answer/2424384?hl=en&co=GENIE.Platform%3DDesktop

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-01T00:20:31+00:00

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-02-28T23:44:29+00:00

    The V2 that was posted was dated 02/22/25.

    Please post a new V2 after each new BSOD.

    1. Please run Tuneup plus > post a share link

    https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

    Batch files for use in BSOD debugging - Page 2 - Windows 10 Forums

    Batch files for use in BSOD debugging - Windows 10 Forums

    2) 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. Run WDV multiple times to create new dump files
    2. Always turn off WDV by booting into safe mode with command prompt and using one or both of these commands:

    verifier /reset

    verifier /bootmode resetonbootfail

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

    1. Only use system restore if the two commands fail to turn off the tool
    2. Please test the drivers with each group of customized tests and for each run post querysettings or V2.

    Was this answer helpful?

    0 comments