Bugcheck 10d during upgrade to Windows 11 from Windows 10

Anonymous

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.

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

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

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

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

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

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

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.

0 comments

71 additional answers

Ramesh 181.6K Reputation points Volunteer Moderator

2025-02-26T05:18:34+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.
1. Please share the latest dumps from "C:\windows\minidump". Let's check whether the Logitech driver is still loading.
2. The following batch file collects the setup logs and saves the zip file to your desktop.
Download setuplogscollect.bat and run it as administrator.

https://winhelponline.com/files/setuplogscollect.bat

Right-click on the downloaded file and click Properties. Click "Unblock" and click OK.

Right-click on the file and choose "Run as administrator"

It outputs a SetupLogs.zip file on your desktop.

Share the file on OneDrive and post the download link here.
Was this answer helpful?

0 comments No comments
Anonymous

2025-02-26T15:36:19+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.

Please share the latest dumps from "C:\windows\minidump". Let's check whether the Logitech driver is still loading.
As mentioned, no new dump files have been created since the ones I already sent you. I'm seeing that the BSOD itself hangs at 0% without saving anything new.
Was this answer helpful?

0 comments No comments
Ramesh 181.6K Reputation points Volunteer Moderator

2025-02-26T15:52:13+00:00

As mentioned, no new dump files have been created since the ones I already sent you. I'm seeing that the BSOD itself hangs at 0% without saving anything new.

Sorry, I missed it. Please share the latest setup logs.

Enable Memory Integrity. To enable memory integrity in Windows, go to Windows Security > Device security > Core isolation details > Memory integrity. If it shows any incompatible drivers, post the screenshot here.
Was this answer helpful?

0 comments No comments

Anonymous

So far, no BSOD, I'm only testing the LEQDUSB.SYS driver that was the subject of the previous Windows 11 upgrade failure, according to people on here.

PS C:\WINDOWS\system32> verifier /querysettings

Verifier Flags: 0x00100610

Standard Flags:

[ ] 0x00000001 Special pool.  
[ ] 0x00000002 Force IRQL checking.  
[ ] 0x00000008 Pool tracking.  
[X] 0x00000010 I/O verification.  
[ ] 0x00000020 Deadlock detection.  
[ ] 0x00000080 DMA checking.  
[ ] 0x00000100 Security checks.  
[ ] 0x00000800 Miscellaneous checks.  
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.  
[X] 0x00000200 Force pending I/O requests.  
[X] 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.  
[ ] 0x00080000 DDI compliance checking (additional).  
[ ] 0x00200000 NDIS/WIFI verification.  
[ ] 0x00800000 Kernel synchronization delay fuzzing.  
[ ] 0x01000000 VM switch verification.  
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).  

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

leqdusb.sys

0 comments