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-12T13:15:50+00:00
    1. Open administrative command prompt and copy and paste:

    sc delete iomap64

    scdelete iomap

    Post a share link.

    There is no service named IOMAP64 installed on the system.

    C:\WINDOWS\system32>sc query iomap

SERVICE_NAME: iomap
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\WINDOWS\system32>sc query iomap64
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

    And how come you can't see the IOMAP service when you list services in the standard way? Is it a hidden service? Also it says IOMAP is a kernel driver, is this safe to delete?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-12T07:32:49+00:00
    1. Open administrative command prompt and copy and paste:

    sc delete iomap64

    scdelete iomap

    Post a share link.

    1. Launch everything search > type: iomap > post a share link

    voidtools

    1. Create a new restore point.
    2. Restart WDV with the two groups of customized tests in the prior post.

    Event[196]:

    Log Name: System

    Source: Service Control Manager

    Date: 2025-02-28T01:13:45.1630000Z

    Event ID: 7045

    Task: N/A

    Level: Information

    Opcode: N/A

    Keyword: Classic

    User: S-1-5-18

    User Name: NT AUTHORITY\SYSTEM

    Computer: desktop-yjk

    Description:

    A service was installed in the system.

    Service Name: IOMap

    Service File Name: C:\WINDOWS\system32\drivers\IOMap64.sys

    Service Type: kernel mode driver

    Service Start Type: demand start

    Service Account:

    Event[10975]:

    Log Name: System

    Source: Service Control Manager

    Date: 2025-03-12T01:46:13.0770000Z

    Event ID: 7045

    Task: N/A

    Level: Information

    Opcode: N/A

    Keyword: Classic

    User: S-1-5-18

    User Name: NT AUTHORITY\SYSTEM

    Computer: desktop-yjk

    Description:

    A service was installed in the system.

    Service Name: IOMap

    Service File Name: C:\WINDOWS\system32\drivers\IOMap64.sys

    Service Type: kernel mode driver

    Service Start Type: demand start

    Service Account:

    iomap IOMap ??\c:\windows\system32\drivers\iomap64.sys

    IOMap64.sys Mon Dec 2 02:42:15 2024 (674D72E7)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-12T06:24:39+00:00

    Okay so just ran the WDV and it created a new minidump file. It should be in the latest V2 Log:

    DESKTOP-YJK-(2025-03-12_02-17-34)

    It looks like the new minidump points to the IOMap64.sys file again, but neither Driver Explorer nor Autoruns sees it in their startup lists. Not sure why it should be even seen, it's not being loaded.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-12T05:29:15+00:00

    The OS disk has already been checked during a reboot, and it's error free now.

    Was this answer helpful?

    0 comments