Windows 11 Pro at 23H2 will not upgrade to either 24H2 or 25H2, ends in BSOD

Question

Windows 11 Pro at 23H2 will not upgrade to either 24H2 or 25H2, BSOD after install "PAGE_FAULT_IN_NONEPAGED_AREA (0x50)" and reboot prompt "Attempting to Recover Installation" followed by "Undoing changes made to your computer"

System successfully passes hardware testing prior to trying 8 different times from Settings/Update page, ISO Boot, Rufus, USB, etc.

Last 2 attempts (w/follow-on BSODs) were using the Microsoft Installation Assistant

I have tried so many suggestions in the last few years and NOT willing to perform a clean upgrade.

If I knew EXACTLY which installation log files to package for problem resolution I would gladly send the package in for review. My last attempt @25H2, reverted back and then auto attempted to install 24H2 with same error + prompts and subsequent BSOD (Green on a scrambled monitor display).

Answer 1

Unfortunately, file is not accessible. Please check sharing settings.

Answer 2

Please create restore point before files deleting. If you'll see some problem (thou I do not believe this), you'll be able to roll back to previous state.

I suppose files remained after some incorrect software uninstallation.

Answer 3

Corsair drivers cause the problem. Please uninstall them or update.

Note, it is not recommended to share a full memory dump, some personal data may be extracted, thou this is not an easy task. Minidumps are enough in most cases.

Answer 4

Hi,

Please share several memory minidumps to OneDrive for analysis.

https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/how-to-post-crash-dumps-after-blue-screen-of-death/5b11c5c7-5903-45b8-8348-0fbee6b2ba6e

Answer 5

The issue you are experiencing with the BSOD error "PAGE_FAULT_IN_NONPAGED_AREA (0x50)" during the upgrade from Windows 11 Pro 23H2 to either 24H2 or 25H2 can be quite complex. Here are some potential resolutions based on common troubleshooting steps:

1. Check for Corrupted System Files: Run the System File Checker (SFC) and Deployment Imaging Service and Management Tool (DISM) to check for and repair corrupted files. You can do this by running the following commands in an elevated Command Prompt:
   • sfc /scannow
   • DISM /Online /Cleanup-Image /RestoreHealth
2. Update Drivers: Ensure that all drivers, especially for your graphics card and storage controllers, are up to date. Outdated drivers can often cause BSOD errors during upgrades.
3. Disable Overclocking: If your system is overclocked, revert to default settings in the BIOS/UEFI. Overclocking can lead to instability during upgrades.
4. Check for Disk Errors: Use the Check Disk utility to scan for and fix disk errors. Run the command chkdsk /f /r in an elevated Command Prompt.
5. Registry Key Modification: If you are encountering issues related to the Secure Boot feature, you might want to consider modifying the DisableCapiOverrideForRSA registry key as a temporary workaround. However, be cautious when editing the registry, and ensure you back it up first.
6. Use Windows Update Troubleshooter: Run the built-in Windows Update troubleshooter to identify and fix problems with Windows Update.
7. Review Installation Logs: If you are looking for specific installation log files to analyze, you can check the following logs located in the C:\$WINDOWS.~BT\Sources\Panther directory:
   • setupact.log
   • setuperr.log
   • setupapi.dev.log

These logs can provide insights into what went wrong during the installation process.

If these steps do not resolve the issue, consider reaching out to Microsoft Support for further assistance, as they can provide more tailored help based on the logs you can gather.

---

References:

• Error 0x000000c1 or 0x80092003 CRYPT_E_FILE_ERROR stops in-place upgrade from Windows 10 to Windows 11
• Resolved issues in Windows 11, version 23H2