windows11 insider update restart bluescreen

[shippo1982]

Windows OS: windows11

windows11 insider update restart bluescreen

help

[Support]

Could you try the following steps to see if it works?
1) When Windows 11 get bluescreen 3 times during boot-up, it will try the automatic repair and shows the "Automatic Repair" screen when it cannot repair the computer. Click the "Advanced options" button, then "Troubleshoot" > "Advanced options" > "Startup Settings" > "Restart",
2) After your PC restarts, it will show the Startup Settings screen. Type "F7" to activate the "Disable driver signature enforcement" options.
3) If Windows still get bluescreen, try "F4" to activate the safe mode at the Startup Settings screen.

[shippo1982]

I tried all of them, but I couldn't boot with a boot error.

[shippo1982]

I can't help it, so I'm repairing it with repair software, uninstalling Primocache, updating Windows, and installing Primocache again

[Support]

Thank you for the information. We will check further.

[anbu]

Unfortunately, I can understand that.

After upgrading to Windows 24H2, I got an error message after starting. Windows recognized it on startup and tried to repair it on its own. However, this failed (as I had expected). A reboot was performed. After that it got horrible. Immediately after booting, my PC went into an endless loop with reboot and BSOD. Over and over again.
Further repairs using various tools (via USB start) failed, so I ended up having to reinstall my PC's operating system from a boot drive via USB.

I have therefore no longer installed PrimoCache. More out of safety. I want to rule everything out now. I actually had a problem with another Windows update some time ago, which I was able to solve in the end by deactivating PrimoCache. Presumably the Windows update process had problems with the active PrimoCache cache.

However, I can neither confirm nor deny whether PrimoCache was really the cause of the 24H2 upgrade.
Microsoft itself is currently only reporting various problems with hardware (e.g. SSD), drivers, programs, etc.. They probably don't know for sure themselves.

I therefore see Microsoft as being more to blame. Their software is real banana software. It matures with customers who are unwitting testers. In my opinion, this upgrade was not tested correctly if even their own repair fails.

No wonder Microsoft has now withdrawn the upgrade to 24H2 for many devices.

[anbu]

According to new reports, some SSDs are causing problems.
Could it be? Is PrimoCache not the cause here? My SSD from Kingston has now also received a firmware upgrade.
The information from the manufacturer is rather sparse.

[secured2k]

I have had constant crashes due to data corruption with PrimoCache installed with L2 caching/persistence during Windows 11 24H2 updates. There does appear to be some compatibility change with this newer build of Windows as L1/L2 caching is not working over the built-in Windows caching (based on statistics monitoring).

What appears to be happening is Windows is doing some updates on the normal storage and during those updates, the L2 cache is not updated. This is probably because the Windows setup is not loading third-party drivers like PrimoCache (booting into a WinPE environment to install the base system update). When the system boots up to the normal upgraded environment, PrimoCache loads again and starts serving non-matching file system data from the L2 cache, and this causes Windows to see NTFS file system corruption (mismatched data from cache vs newly upgraded files). When/If Windows tries to repair these inconsistencies, data files are lost/corrupted.

To solve this, any major Windows updates (Major build changes such as 10.0.226## to 10.0.261##) required me to turn off PrimoCache's features such as Prefetch Last cache (Read from L2, Start at Windows Boot) and enable "Volatile Cache Contents" on the L2 cache.

[Support]

What appears to be happening is Windows is doing some updates on the normal storage and during those updates, the L2 cache is not updated. This is probably because the Windows setup is not loading third-party drivers like PrimoCache (booting into a WinPE environment to install the base system update). When the system boots up to the normal upgraded environment, PrimoCache loads again and starts serving non-matching file system data from the L2 cache, and this causes Windows to see NTFS file system corruption (mismatched data from cache vs newly upgraded files). When/If Windows tries to repair these inconsistencies, data files are lost/corrupted.

To solve this, any major Windows updates (Major build changes such as 10.0.226## to 10.0.261##) required me to turn off PrimoCache's features such as Prefetch Last cache (Read from L2, Start at Windows Boot) and enable "Volatile Cache Contents" on the L2 cache.

PrimoCache does have a mechanism to disable L2 cache after a major Windows upgrade reboot, unless the "Ignore Sync Check and Preserve Cache Anyway" option is checked. So this problem usually shouldn't happen. I'm not sure if Windows changed something in recent updates, but we will recheck the issue.

[shippo1982]

Happy New Year. Thanks for the update. It's been a long time, but have you solved the problem? I hope to hear from you better.