Win 11 Version 24H2 Install Failed

Ramesh,

driver.txt added to the shared drive.

Link below:

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

There was another BSOD today.

WDV is used multiple times per day in threads.

When possible start the tool with the 3 customized tests in this link:

Enable and Disable Driver Verifier in Windows 10 | Tutorials

Boot to Advanced Startup Options in Windows 10 | Tutorials

(Option six or five)

For each test:

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.

BSOD - Posting Instructions - Windows 10 Forums

questions,

Thanks for the info, but doing these steps is out of my comfort zone. I need to take a step back and consider a clean install.

Thanks again,

sms1295

Hi sms1295#,

Thanks. There are many issues, starting from Cryptographic services not starting, and hence the VSS service is crashing with error 0x80070006. There are remnants of VirtualBox and VMware in network bindings. Microsoft Defender is crashing with the errors 0x80070006 and 0xc0000005.

Harddisk5 is going bad ("The driver detected a controller error on \Device\Harddisk5\DR5."), But that may not be related to the original issue.

System Restore Point can't be created unless the VSS and Cryptographic Services are fixed.

If you're willing to attempt the setup one more time, please try the following:

1. Reset the network using the "Network Reset" feature in Settings. This removes all network adapters, adapter settings, and re-installs them. Your Wi-Fi profiles may be deleted and need to be configured again. Restart Windows.
2. Uninstall Intel(R) Extreme Tuning Utility.
3. Certain 3rd party driver packages can be deleted using these commands:

(All the driver packages have been backed up to C:\Drivers already.)

• pnputil /delete-driver oem134.inf /uninstall /force
• pnputil /delete-driver oem2.inf /uninstall /force
• pnputil /delete-driver oem51.inf /uninstall /force
• pnputil /delete-driver oem61.inf /uninstall /force
• pnputil /delete-driver oem68.inf /uninstall /force
• pnputil /delete-driver oem75.inf /uninstall /force
• pnputil /delete-driver oem77.inf /uninstall /force
• pnputil /delete-driver oem80.inf /uninstall /force
• pnputil /delete-driver oem83.inf /uninstall /force
• pnputil /delete-driver oem88.inf /uninstall /force
• pnputil /delete-driver oem89.inf /uninstall /force
• rundll32.exe c:\windows\system32\pnpclean.dll,RunDLL_PnpClean /DEVICES /MAXCLEAN
• pnputil /enum-devices /problem /ids

4. Share the contents of "C:\Windows\Minidump". The last minidump was probably created on May 10.
5. You may retry the setup using the ISO with dynamic updates turned off and internet connection enabled.

If you're considering a clean install then it's a test drive opportunity.

If there is no misbehaving driver then WDV does not typically cause BSOD crashes.

If there is a misbehaving driver then WDV typically cause BSOD crashes.

To recover from a WDV BSOD > hard reboot > safe mode > type verifier /reset and / or verifier /bootmode resetonbootfail

Once you hard reboot and recover to the desktop > logs are collected > a misbehaving driver may be uninstalled.

Then it's a "rinse and repeat" process for other customized tests.

If a dump file is created it can be debugged.

WDV is designed to cause repetitive crashes until the tool is turned off.

The tool cannot cause crashes while in safe mode.

So it's learning how to hard boot (the power switch) to boot into safe mode.

Boot to Advanced Startup Options in Windows 10 | Tutorials

(Option six or five)

If you want me to be available then let's schedule a time.