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: Most helpful
  1. Ramesh 181.6K Reputation points Volunteer Moderator
    2025-03-01T04:23:00+00:00

    It could be the ASUS Aura service (Reference: https://rog-forum.asus.com/t5/asus-software/iomap64-sys-fault-in-non-paged-area/td-p/640010)

    Regarding the incompatible drivers, please run the Farbar Scanner and share your logs.

     1. Download Farbar Recovery Scan Tool 64-bit (FRST64.exe)

    https://www.bleepingcomputer.com/download/farbar-recovery-scan-tool/

    Note: If Microsoft Edge or Chrome mislabels the Farbar Scanner executable as PUA/malware, choose to keep it by tapping … in the bottom bar, choosing Keep, and then choosing Keep anyway in the dialog that appears.

    See this screenshot: https://learn.microsoft.com/en-us/deployedge/media/microsoft-edge-security-download-interruptions/dowload-was-blocked.png. It's a safe tool used in most antimalware forums.

    1. If the OS language is non-English, rename FRST64.exe to FRST64English.exe.
    2. Run the program. Don't check or uncheck any options. Click "Scan".
    3. Add the two logs, FRST.txt and Addition.txt, to a Zip archive, upload them to your OneDrive and share the link here.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-03-01T04:05:10+00:00

    Memory integrity shows the following incompatible drivers:

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-03-01T03:52:48+00:00

    Try it again: https://drive.google.com/file/d/1GvqDOauymnTcZ2_8KF63NWL0UgF5yqwy/view?usp=sharing

    IOMap64.sys is shown as the faulting driver. It might be related to some ASUS app. ASUS PC Probe, maybe.

    According to Bing, it belongs to a package called:

    The iomap64.sys file is associated with the Asus GameFirst technology, which is found on Asus motherboards. This system file helps optimize network traffic for gaming applications, providing a smoother gaming experience. However, it can sometimes cause issues, such as triggering a blue screen of death (BSOD) in Windows.

    I don't see any programs installed called Asus Gamefirst, these are the only things installed Asus related:

    Was this answer helpful?

    0 comments No comments
  4. Ramesh 181.6K Reputation points Volunteer Moderator
    2025-03-01T03:32:45+00:00

    Try it again: https://drive.google.com/file/d/1GvqDOauymnTcZ2_8KF63NWL0UgF5yqwy/view?usp=sharing

    IOMap64.sys is shown as the faulting driver. It might be related to some ASUS app. ASUS PC Probe, maybe.

    * * * * *
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the
    IRP's IoStatus.Status field.
    Arg2: fffff804c55b25a0, The address in the driver's code where the error was detected.
    Arg3: ffff910a7314f720, IRP address.
    Arg4: 0000000000000000, Expected status code.
    
    Debugging Details:
    ------------------
    
    Unable to load image IOMap64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for IOMap64.sys
    * * * * *
    

    I'd suggest enabling Memory Integrity to identify incompatible drivers. After identifying the incompatible drivers, they can be removed using Autoruns or Drivers Store Explorer.

    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