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-03-11T20:00:38+00:00
    1. Please run Tuneup plus > post a share link

    This script includes modifications of Windows default settings.

    The new settings make it less likely that the computer user will miss BSOD.

    https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

    1. Create a new restore point

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

    1. Review the WDV instructions:

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

    1. Review 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. Run the tool with various customized test settings:

    a) Test all non-Microsoft drivers

    b) Test no Microsoft drivers

    First group:

    [ ] 0x00000001 Special pool.

    [ ] 0x00000002 Force IRQL checking.

    [ ] 0x00000008 Pool tracking.

    [ ] 0x00000020 Deadlock detection.

    [ ] 0x00000080 DMA checking.

    [ ] 0x00000100 Security checks.

    [ ] 0x00000800 Miscellaneous checks.

    [ ] 0x00020000 DDI compliance checking.

    [ ] 0x00080000 DDI compliance checking (additional).

    [ ] 0x00200000 NDIS/WIFI verification.

    [ ] 0x00800000 Kernel synchronization delay fuzzing.

    Second group:

    [ ] 0x00000010 I/O verification.

    [ ] 0x00000200 Force pending I/O requests.

    [ ] 0x00000400 IRP logging.

    [ ] 0x00002000 Invariant MDL checking for stack.

    [ ] 0x00004000 Invariant MDL checking for driver.

    [ ] 0x00008000 Power framework delay fuzzing.

    [ ] 0x00010000 Port/miniport interface checking.

    [ ] 0x00040000 Systematic low resources simulation.

    [ ] 0x01000000 VM switch verification.

    [ ] 0x02000000 Code integrity checks.

    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.

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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-12T01:29:11+00:00
    1. Please run Tuneup plus > post a share link

    This script includes modifications of Windows default settings.

    The new settings make it less likely that the computer user will miss BSOD.

    https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

    Here's the logs for Tuneup Plus: Tuneup_log 2025-03-11 at 21-14-50

    1. Create a new restore point

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

    1. Review the WDV instructions:

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

    Should I run the Verifier while Core Isolation is still on, or should I disable Core Isolation now?

    I'll get to the rest of these steps once I get your answer about Core Isolation.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-12T01:56:03+00:00

    Core isolation and memory integrity can be turned off.

    Was this answer helpful?

    0 comments
  4. Ramesh 181.6K Reputation points Volunteer Moderator
    2025-03-12T02:34:33+00:00

    See if you can delete these two drivers using Autoruns.

    https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

    C:\Windows\system32\drivers\cpuz135_x64.sys

    C:\WINDOWS\system32\drivers\RtHDMIVX.sys

    RtHDMIVX.sys is the Realtek HD Audio driver.

    Hi,

    Were you able to enable Memory Integrity?

    Share the latest setup logs please.

    I'll check the memory integrity again.

    Update: yes, Memory Integrity Core Isolation has been enabled and it is working after a reboot!

    Notifications won't be sent for posts edited after some time.

    Can you share the latest setup logs?

    Was this answer helpful?

    0 comments