Win 11 Version 24H2 Install Failed

Hi sms1295,

1. I'm unsure if reinstalling 23H2 and upgrading to 24H2 will help because 0xC1900101 is mostly a driver-related (and sometimes hardware-related) issue. But you could try that, considering that the repair installation shouldn't take much time on SSDs.

By the way, I noticed that some drivers were automatically added every time you reverted from clean boot mode after the failed setup attempt. The first one was added by the Intel Driver utility and the gdrv3.sys driver was installed by a Gigabyte service.

semav6msr64.sys

gdrv3.sys

2. I prefer installing programs on the C drive and moving the data files (Documents, Desktop, Music, Videos, Downloads) to the other partition or drive. Separating the data reduces the size of the image when backing up the OS partition. I backup the OS partition using Macrium. Data files will be backed up using a robocopy batch file to an external drive and NAS.
3. Unused and superseded driver store packages can be removed using the Pnpclean command we used earlier. Altenatively the Windows Assessment Toolkit from Microsoft can do the job. However, there is no tool to identify invalid drivers (vs driver store packages). It has to be done manually using a tool like FRST.

Ramesh,

I run a multiple internal drive computer (FYI..Drive 5, which had the controller issue,e was the USB I was using to run the ios file). Opening the case to disconnect and the possibility of the upgrade failing again isn't worth disconnecting the drives. I'm going to move on to a clean install, which I think has become the best option with the number of issues I have with my computer. Thank you for all your help. You have introduced me to a few new tools, so this has not wasted my time. I have several questions, I hope you will have time to answer them for me:

1. Would using the Windows tool "Reinstall Now" to reinstall 23H2, and then do the 24H2 upgrade, be an option?
2. I have the OS on the C drive and my programs on the D drive. I read back when I built my PC several years ago that having the OS on a separate drive from the programs was an ideal setup. Is it? Since I'm about to do a clean install, should I just have the OS and programs on the same drive? Some programs will only install on the C drive, like VirtualBox. BTW..I'm not a gamer.
3. Is there a tool that will identify invalid drivers and give the option to remove them?

Thanks again,

sms1295

There were BSODs on:

05/07: 1

05/14: 1

05/15: 2

The logs reported the use of WDV.

There were no BSODs with the 3 customized tests in the TF tutorial.

However there were a limited number of tested non-Microsoft drivers.

ctiio64.sys 

igdkmdn64.sys 

netwtw14.sys 

ialpss2\_i2c\_adl.sys 

teedriverw10x64.sys 

iccwdt.sys 

ialpss2\_gpio2\_adl.sys 

hideventfilter.sys 

corsairvbusdriver.sys 

corsairvhiddriver.sys 

iocbios2.sys 

ibtusb.sys 

leqdusb.sys 

lhideqd.sys 

dump\_dumpstorport.sys 

dump\_stornvme.sys 

dump\_dumpfve.sys 

corsairllaccess64.sys

These are some non-Microsoft drivers that were not tested yet:

Nvidia

Realtek

etc.

Click on the Provider column to sort > scroll up and down > select all drivers that are non-Microsoft drivers

1. Please attempt to make a new restore point.

Create System Restore Point in Windows 11 | Windows 11 Forum

Post any error message.

2. Create a bootable Windows 11 Media Creation Tool (MCT) (Windows 11 iso):

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

Download Windows 11

3. See this link to turn off WDV via Windows Recovery Environment (RE):

Boot to Advanced Startup (WinRE) in Windows 11 | Windows 11 Forum

(option nine and seven)

4. Restart WDV with these groups of customized tests:

Group A

[ ] 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. 

Group B

[ ] 0x00020000 DDI compliance checking. 

[ ] 0x00080000 DDI compliance checking (additional). 

[ ] 0x02000000 Code integrity checks.

[ ] 0x00000002 Force IRQL checking. 

[ ] 0x00000008 Pool tracking. 

Group C

[ ] 0x00008000 Power framework delay fuzzing. 

[ ] 0x00010000 Port/miniport interface checking. 

[ ] 0x00040000 Systematic low resources simulation. 

[ ] 0x00000020 Deadlock detection. 

[ ] 0x00000080 DMA checking. 

Group D

[ ] 0x00000100 Security checks. 

[ ] 0x00000800 Miscellaneous checks. 

[ ] 0x00200000 NDIS/WIFI verification. 

[ ] 0x00800000 Kernel synchronization delay fuzzing. 

[ ] 0x01000000 VM switch verification. 

For each group 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.

Hi sms1295,

There was another crash, but it didn't occur during the setup; it happened a few minutes after the rollback began. The VSS error 0x80070006 (handle is invalid) is still there.

The rollback occurred before the Pre OOBE phase.

Unfortunately, some drivers are automatically added every time you revert from clean boot mode. Do not revert from clean boot mode until troubleshooting is complete.

These two drivers are repeatedly getting added because you switched to normal mode.

semav6msr64.sys

gdrv3.sys

Here is something you can try before attempting the Setup.

• Uninstall the two drivers using Farbar.
• Disconnect all other disks.
• Uninstall all Gigabyte apps. One of the apps is readding the gdrv3.sys driver.
• Uninstall Intel Driver Update Utility
• Turn off WinRE by running "reagentc /disable". You can reenable it after the upgrade.
• Run Memory Diagnostics since there are a lot of 0xC0000005 errors. https://www.techrepublic.com/article/how-to-detect-bad-ram-with-the-windows-memory-diagnostic-tool/ You can check the results of the Memory Diagnostics in the event log.
• If nothing helps, you may do the BSOD troubleshooting or clean install Windows 11 24H2 using USB after backing up the data with the other drives disconnected.

Ramesh,

I decided to run the update, and it failed again with error code 0xC1900101 - 0x40017. I've uploaded the following results:

drivers.txt

New Admin Log.evtx

Addition.txt

FRST.txt

Upgrade_failure_logs_2025-05-15_20-03-43.zip

Also ran the V2 collector and that file is XPS-720-(2025-05-15_20-18-16).zip.

Share drive is below:

https://drive.google.com/drive/folders/1pAkm8Z6XBzIzfItGsqtEctSxFMpbP4UR?usp=sharing

On a related topic..How do I know that the VSS and Cryptographic Services are fixed?

Thanks for your help,

sms1295