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 No 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 No comments

71 additional answers

Sort by: Oldest
  1. Anonymous
    2025-02-22T04:03:56+00:00

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-02-23T00:04:32+00:00

    Here's the link to the files:

    https://drive.google.com/file/d/18dAIS0wKZpQ7vx4WDphkQnjMK0zRxUPA/view?usp=sharing

    Some of the stuff in TenForum were restricted, so I couldn't obtain those files, but this was the only one (v2 log collector) that was allowed.

    Was this answer helpful?

    0 comments No comments
  3. Ramesh 181.6K Reputation points Volunteer Moderator
    2025-02-23T03:10:08+00:00

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

    Can you uninstall that software?

    Crash dump analysis:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WDF_VIOLATION (10d)
    The Kernel-Mode Driver Framework was notified that Windows detected an error
    in a framework-based driver. In general, the dump file will yield additional
    information about the driver that caused this BugCheck.
    Arguments:
    Arg1: 0000000000000006, A fatal error was made in handling a WDF request. In this case,
    Parameter 2 further specifies the type of fatal error that has
    been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.
    Arg2: 0000000000000003, The driver attempted to send a framework request that has
    already been sent to an I/O target.
    Arg3: 0000307c81c6e7d8, The WDF request handle value.
    Arg4: ffffcf8380dc7de0, Reserved.
    
    Debugging Details:
    ------------------
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 1093
    
        Key  : Analysis.Elapsed.mSec
        Value: 7402
    
        Key  : Analysis.IO.Other.Mb
        Value: 0
    
        Key  : Analysis.IO.Read.Mb
        Value: 1
    
        Key  : Analysis.IO.Write.Mb
        Value: 0
    
        Key  : Analysis.Init.CPU.mSec
        Value: 312
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 5933
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 110
    
        Key  : Analysis.Version.DbgEng
        Value: 10.0.27725.1000
    
        Key  : Analysis.Version.Description
        Value: 10.2408.27.01 amd64fre
    
        Key  : Analysis.Version.Ext
        Value: 1.2408.27.1
    
        Key  : Bugcheck.Code.LegacyAPI
        Value: 0x10d
    
        Key  : Bugcheck.Code.TargetModel
        Value: 0x10d
    
        Key  : Dump.Attributes.AsUlong
        Value: 8
    
        Key  : Dump.Attributes.KernelGeneratedTriageDump
        Value: 1
    
        Key  : Failure.Bucket
        Value: 0x10D_6_LEqdUsb!unknown_function
    
        Key  : Failure.Hash
        Value: {3ed655a0-a16a-88d4-1ae3-af07a49c8674}
    
        Key  : Hypervisor.Enlightenments.Value
        Value: 77057948
    
        Key  : Hypervisor.Enlightenments.ValueHex
        Value: 497cf9c
    
        Key  : Hypervisor.Flags.AnyHypervisorPresent
        Value: 1
    
        Key  : Hypervisor.Flags.ApicEnlightened
        Value: 1
    
        Key  : Hypervisor.Flags.ApicVirtualizationAvailable
        Value: 0
    
        Key  : Hypervisor.Flags.AsyncMemoryHint
        Value: 0
    
        Key  : Hypervisor.Flags.CoreSchedulerRequested
        Value: 0
    
        Key  : Hypervisor.Flags.CpuManager
        Value: 1
    
        Key  : Hypervisor.Flags.DeprecateAutoEoi
        Value: 0
    
        Key  : Hypervisor.Flags.DynamicCpuDisabled
        Value: 1
    
        Key  : Hypervisor.Flags.Epf
        Value: 0
    
        Key  : Hypervisor.Flags.ExtendedProcessorMasks
        Value: 1
    
        Key  : Hypervisor.Flags.HardwareMbecAvailable
        Value: 0
    
        Key  : Hypervisor.Flags.MaxBankNumber
        Value: 0
    
        Key  : Hypervisor.Flags.MemoryZeroingControl
        Value: 0
    
        Key  : Hypervisor.Flags.NoExtendedRangeFlush
        Value: 0
    
        Key  : Hypervisor.Flags.NoNonArchCoreSharing
        Value: 1
    
        Key  : Hypervisor.Flags.Phase0InitDone
        Value: 1
    
        Key  : Hypervisor.Flags.PowerSchedulerQos
        Value: 0
    
        Key  : Hypervisor.Flags.RootScheduler
        Value: 0
    
        Key  : Hypervisor.Flags.SynicAvailable
        Value: 1
    
        Key  : Hypervisor.Flags.UseQpcBias
        Value: 0
    
        Key  : Hypervisor.Flags.Value
        Value: 4722927
    
        Key  : Hypervisor.Flags.ValueHex
        Value: 4810ef
    
        Key  : Hypervisor.Flags.VpAssistPage
        Value: 1
    
        Key  : Hypervisor.Flags.VsmAvailable
        Value: 1
    
        Key  : Hypervisor.RootFlags.AccessStats
        Value: 1
    
        Key  : Hypervisor.RootFlags.CrashdumpEnlightened
        Value: 1
    
        Key  : Hypervisor.RootFlags.CreateVirtualProcessor
        Value: 1
    
        Key  : Hypervisor.RootFlags.DisableHyperthreading
        Value: 0
    
        Key  : Hypervisor.RootFlags.HostTimelineSync
        Value: 1
    
        Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
        Value: 0
    
        Key  : Hypervisor.RootFlags.IsHyperV
        Value: 1
    
        Key  : Hypervisor.RootFlags.LivedumpEnlightened
        Value: 1
    
        Key  : Hypervisor.RootFlags.MapDeviceInterrupt
        Value: 1
    
        Key  : Hypervisor.RootFlags.MceEnlightened
        Value: 1
    
        Key  : Hypervisor.RootFlags.Nested
        Value: 0
    
        Key  : Hypervisor.RootFlags.StartLogicalProcessor
        Value: 1
    
        Key  : Hypervisor.RootFlags.Value
        Value: 1015
    
        Key  : Hypervisor.RootFlags.ValueHex
        Value: 3f7
    
    BUGCHECK_CODE:  10d
    
    BUGCHECK_P1: 6
    
    BUGCHECK_P2: 3
    
    BUGCHECK_P3: 307c81c6e7d8
    
    BUGCHECK_P4: ffffcf8380dc7de0
    
    FILE_IN_CAB:  010225-19218-01.dmp
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    FAULTING_THREAD:  ffffcf839a57e040
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    STACK_TEXT:  
    ffffb980`aa8e6408 fffff807`04008a44     : 00000000`0000010d 00000000`00000006 00000000`00000003 0000307c`81c6e7d8 : nt!KeBugCheckEx
    ffffb980`aa8e6410 fffff807`03fcd941     : 0000307c`81c6e7d8 00000000`00000000 0000307c`81c6e7d8 ffffcf83`80aea720 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68] 
    ffffb980`aa8e6450 fffff807`03fb1c4a     : ffffcf83`80aea700 ffffcf83`7e391820 00000000`00000000 fffff807`03fbc018 : Wdf01000!FxIoTarget::SubmitLocked+0x1b9b1 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 1318] 
    ffffb980`aa8e64e0 fffff807`31ce5265     : ffffcf83`80dc7f00 ffffcf83`7e391820 ffffcf83`80aea720 00000000`00000092 : Wdf01000!imp_WdfRequestSend+0x17a [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 2055] 
    ffffb980`aa8e6560 ffffcf83`80dc7f00     : ffffcf83`7e391820 ffffcf83`80aea720 00000000`00000092 0000307c`7f903188 : LEqdUsb+0x5265
    ffffb980`aa8e6568 ffffcf83`7e391820     : ffffcf83`80aea720 00000000`00000092 0000307c`7f903188 00000000`00000000 : 0xffffcf83`80dc7f00
    ffffb980`aa8e6570 ffffcf83`80aea720     : 00000000`00000092 0000307c`7f903188 00000000`00000000 00000000`00000000 : 0xffffcf83`7e391820
    ffffb980`aa8e6578 00000000`00000092     : 0000307c`7f903188 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffcf83`80aea720
    ffffb980`aa8e6580 0000307c`7f903188     : 00000000`00000000 00000000`00000000 00000000`00000000 0000307c`810c7578 : 0x92
    ffffb980`aa8e6588 00000000`00000000     : 00000000`00000000 00000000`00000000 0000307c`810c7578 ffffcf83`7ef38a80 : 0x0000307c`7f903188
    
    SYMBOL_NAME:  LEqdUsb+5265
    
    MODULE_NAME: LEqdUsb
    
    IMAGE_NAME:  LEqdUsb.Sys
    
    STACK_COMMAND:  .process /r /p 0xffffcf8375e86040; .thread 0xffffcf839a57e040 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  5265
    
    FAILURE_BUCKET_ID:  0x10D_6_LEqdUsb!unknown_function
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {3ed655a0-a16a-88d4-1ae3-af07a49c8674}
    
    Followup:     MachineOwner
    ---------
    

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-02-23T04:17:26+00:00

    Hi BlackJacques,

    These were some of the problems identified in the V2 collected log files:

    a) Drive problems including corruption, paging, retried, delayed write, bad block, etc.

    b) Failed Windows fast startup

    c) Many live kernel events

    d) Driver causing one hang / freeze

    e) Upgrade failure code 0xC1900101

    f) Collected BSOD dump files starting Sept 2024

    g) Misbehaving driver identified

    Fri Oct 18 07:57:05.714 2024 (UTC - 6:00)

    Fri Dec 27 23:24:03.760 2024 (UTC - 6:00)

    Thu Jan 2 10:00:50.645 2025 (UTC - 6:00)

    Please perform the following steps:

    1. Run Tuneup plus > post a share link (this script does not require logon)

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

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

    Batch files for use in BSOD debugging - Windows 10 Forums

    1. Turn off Windows fast startup:

    Turn On or Off Fast Startup in Windows 10 | Tutorials

    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. If possible detach all Logitech hardware and uninstall all Logitech drivers

    Make sure that this driver is uninstalled for the next upgrade attempt:

    leqdusb Logitech SetPoint Unifying KMDF USB Filter c:\windows\system32\drivers\leqdusb.sys

    1. Uninstall CPUZ
    2. Uninstall and reinstall: AMD GPU drivers

    amdwddmg amdwddmg c:\windows\system32\driverstore\filerepository\u0407052.inf_amd64_84d15514ad17ffa0\b406619\amdkmdag.sys

    Display Driver Uninstaller: How to use | Tutorials

    Display Driver Uninstaller (DDU) download latest version 18.0.9.3 | Wagnardsoft

    1. Place the computer into clean boot:

    Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts | Tutorials

    1. Temporarily detach all non-Windows drives
    2. Download to a new desktop folder:

    Download Official Windows 11 ISO file from Microsoft | Windows 11 Forum

    Download Windows 11

    1. Upgrade to Windows 11 using the desktop iso:

    a) while in clean boot

    b) after detaching all non-essential hardware

    c) without Internet access (detach Ethernet and Wifi off)

    1. For any upgrade failure search for: (hidden folder)

    C:$WINDOWS.~BT\Sources\Panther\setupact.log

    Post a share link.

    After a successful upgrade:

    a) perform Windows updates

    b) reinstall software as needed

    c) reattach hardware as needed

    d) make a new restore point as needed

    e) create a new Macrium backup image as needed

    1. All of the drives need to be tested (before or after the upgrade)
    2. Run Sea Tools Long generic test (all drives) > post images or share links

    SeaTools | Seagate US

    1. Run HD Tune (all drives) (run an old version so that it produces results for the whole drive)

    HD Tune website

    a) Health

    b) Full error scan

    1. Open administrative command prompt and copy and paste: chkdsk /b /v

    Run these chkdsk switches on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.

    Make sure that the windows drive runs overnight while sleeping.

    C:\WINDOWS\system32>chkdsk /b /v

    The type of the file system is NTFS.

    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another

    process. Would you like to schedule this volume to be

    checked the next time the system restarts? (Y/N)

    Chkdsk cannot run because the volume is in use by another

    process. Would you like to schedule this volume to be

    checked the next time the system restarts? (Y/N)

    Type: y

    Reboot as needed.

    1. Run HD Sentinel (all drives) > post images or share links (do not run until posting results for each steps 13, 14, and15)

    Hard Disk Sentinel - HDD health and temperature monitoring

    a) Overview

    b) Temperature

    c) SMART

    1. Please make sure that the above drive tests/steps are performed in sequence
    2. These steps / tests can be performed overnight while sleeping:

    a) Sea Tools Long generic test

    b) HD Tune Full error scan

    c) Chkdsk /b /v

    leqdusb Logitech SetPoint Unifying KMDF USB Filter c:\windows\system32\drivers\leqdusb.sys

    Installation Failure: Windows failed to install the following update with error 0xC1900101: Windows 11, version 23H2.

    An error was detected on device \Device\Harddisk6\DR6 during a paging operation.

    An error was detected on device \Device\Harddisk7\DR8 during a paging operation.

    An error was detected on device \Device\Harddisk7\DR7 during a paging operation.

    An error was detected on device \Device\Harddisk6\DR7 during a paging operation.

    An error was detected on device \Device\Harddisk4\DR6 during a paging operation.

    An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

    The device, \Device\Harddisk7\DR7, has a bad block.

    The cpuz135 service failed to start due to the following error:

    This driver has been blocked from loading

    The cpuz132 service failed to start due to the following error:

    This driver has been blocked from loading

    Dump file creation failed due to error during dump creation.

    Crash dump initialization failed!

    {Delayed Write Failed} Windows was unable to save all the data for the file E:$Extend$UsnJrnl:$J. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    {Delayed Write Failed} Windows was unable to save all the data for the file E:. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    {Delayed Write Failed} Windows was unable to save all the data for the file E:$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    {Delayed Write Failed} Windows was unable to save all the data for the file O:. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

    Windows failed fast startup with error status 0xC00000D4.

    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: O:, DeviceName: \Device\HarddiskVolume7.

           Failure status: The I/O device reported an I/O error. 
    
           Device GUID: {3cf3f733-a69c-4072-53f0-4fe2cd7c6dc1} 
    
           Device manufacturer:  
    
           Device model: WDC WD40EZAZ-00SF3B0 
    
           Device revision: 80.00A80 
    
           Device serial number:      WD-WX42AC2EYFTE 
    
           Bus type: SATA 
    
           Adapter serial number:  
    

    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume10.

           Failure status: The request failed due to a fatal device hardware error. 
    
           Device GUID: {ae4d8920-1ebc-e381-4a89-dc88607c563a} 
    
           Device manufacturer:  
    
           Device model: WDC  WDBNCE0010PNC 
    
           Device revision: 415020RL 
    
           Device serial number: 214263800037 
    
           Bus type: SATA 
    

    Display driver amdwddmg stopped responding and has successfully recovered.

    The IO operation at logical block address 0x161d98540 for Disk 5 (PDO name: \Device\0000004f) was retried.

    The IO operation at logical block address 0x10b40ff88 for Disk 5 (PDO name: \Device\0000004e) was retried.

    The IO operation at logical block address 0x5adc78 for Disk 4 (PDO name: \Device\0000004e) was retried.

    The IO operation at logical block address 0x5adc70 for Disk 4 (PDO name: \Device\0000004e) was retried.

    The IO operation at logical block address 0x5cdc68 for Disk 4 (PDO name: \Device\0000004e) was retried.

    A corruption was discovered in the file system structure on volume O:.

    The exact nature of the corruption is unknown. The file system structures need to be scanned online.

    Was this answer helpful?

    0 comments No comments