Win11 26H2 (KB5121794) -> boot BSODs on cold start, 25H2 stable | MSI GF63 12VF, dual boot

Hi,

Recurring BSODs on first boot of the day since mid Oct. Reproducible with
26H2 enablement package (KB5121794), gone on 25H2. Summary of what I've
already ruled out below.

ENV
MSI Thin GF63 12VF (MS-16R8)
i7-12650H / 16GB / RTX 4060 Laptop + Intel UHD
SSD: Kingston OM8PGP4512Q-AI 512GB NVMe
BIOS: E16R8IMS.117 (flashed 21 Oct, was 10E from 2023)
Win11 Home 25H2 26200.9711 (current). Issue on 26H2 / KB5121794.
Dual boot Linux Mint 22.3, UEFI + GRUB, Secure Boot on
Disk 0: EFI 300M | C: 406.5G NTFS | Linux 47.85G | Recovery 1.03G | Recovery 21.13G

CONFIG (partly changed during dual boot setup)
BitLocker: fully decrypted, protection off
Hibernation: off (-> no Fast Startup)
Pagefile: was 0 MB until 16 Oct, now system managed
System Restore: was off until 16 Oct, now on
BIOS: VMD off, Fast Boot on, UEFI, SB on
WU: paused until 04 Dec, "get latest updates" off

TIMELINE
pre dual boot no issues, updates fine
post setup Windows Hello PIN lost (TPM related), re-enrolled
16 Oct 26H2 + Rainbow Six Siege -> 0x13A KERNEL_MODE_HEAP_CORRUPTION,
reproducible. Removing KB5121794 fixed it (matches Ubisoft advisory)
18 Oct cold boot, 25H2 -> 0xc0000218, hangs at 0%. 2nd boot OK.
chkdsk /scan clean (0 bad sectors), sfc repaired files,
DISM RestoreHealth OK, sfc rerun clean
19 Oct cold boot -> 0xc0000218 again (twice that day). 2nd boot OK
21 Oct cold boot -> 0x74 BAD_SYSTEM_CONFIG_INFO. 2nd boot OK.
Get-PhysicalDisk: Healthy/OK, wear 0, 25C
mdsched: no errors, sfc clean. PIN lost again after mdsched.
BIOS 10E -> 117 via USB (UEFI BIOS Update)
22-29 Oct 25H2 + new BIOS: clean cold boots every day
29 Oct KB5121794 reinstalled by WU
30 Oct cold boot, 26H2 -> 0x7A KERNEL_DATA_INPAGE_ERROR, hangs at 0%,
then Automatic Repair failed (SrtTrail.txt).
Booted on next try, removed KB5121794, back on 25H2

NOTES
- only on first boot after several hours powered off, warm reboots never crash
- all codes = disk read / registry hive load failing during boot
- BSOD hangs at 0%, volmgr 161 "Dump file creation failed" logged after each one
- clean shutdown logged before every crashed boot
- no disk/stornvme errors for the internal SSD in the System log
- Linux booted once in that period, didn't touch NTFS
- also seen on 26H2: UplayWebCore crashes, one Metro crash
- older minidump from 29 Sep (before dual boot) points to BEDaisy.sys (BattlEye)
- no overclocking/undervolting, stock settings
- laptop is 2+ years old, out of warranty

QUESTIONS
1. known issue with 26H2 / KB5121794 + NVMe on cold boot or dual boot setups?
2. can hibernation off / BitLocker decrypted / pagefile history conflict with 26H2?
3. how to get a dump when the BSOD hangs at 0%?
4. worth testing/replacing the SSD despite clean diagnostics?
5. cleanest way to block KB5121794 on Home until fixed?

Logs (V2 log collector, network/license files removed):

Thanks,
Arshia Ahmadisartakhti

1) Please run admin PS > post share links displaying each command with results





2) Run tuneup1-bat > post a share link







3) Create a new restore point:




4) For any new BSOD post a new V2 share link into the newest post

Thanks for the help. Done:

1) PS commands done, results:
AutoReboot now False, DebugInfoType 7, pagefile auto (8 GB), no RAM defects listed.

2) tuneup1 done, results:
DISM scanhealth: component store repairable -> restorehealth successful,
SFC clean before and after, chkdsk /scan no problems, 0 KB bad sectors.

3) New restore point created.

4) Will post a new V2 share link if another BSOD happens.

Note: currently on 25H2 (26200.9711), KB5121794 removed again, updates paused until 04 Dec.
Should I reinstall 26H2 to reproduce the crash with the new dump settings, or stay on 25H2?

ArshiaDCT said:

Note: currently on 25H2 (26200.9711), KB5121794 removed again, updates paused until 04 Dec.
Should I reinstall 26H2 to reproduce the crash with the new dump settings, or stay on 25H2?

Click to expand...

1) Please run administrative command prompt: > post share links

wevtutil epl Application "%userprofile%\Desktop\application.evtx"

wevtutil epl System "%userprofile%\Desktop\system.evtx"



2) Uninstall Battleye



3) Reboot



4) Update Windows



5) For any update failure indicate whether there is an error code / message and/or rollback.



6) For any new BSOD post a new V2 share link into the newest post









I no longer want to have BattlEye on my system. How can I completely uninstall it?

Note that BE only installs into your system on Windows (as a system service), so you don’t need to uninstall it on any other OS.

Also, BE is only ever active when you are playing a BE-protected game with BE enabled, any other time it will never run in any way.

If you would still like to uninstall it, please go to the “BattlEye” folder in your game directory and check if there is a file called “Uninstall_BattlEye.bat”, which is present in many games.

If it exists, simply run it to completely uninstall the BE Service.

Otherwise or if you have already removed all game files from your system, you can start a command prompt as administator and simply enter “sc delete BEService” to do so.

Note that some games automatically uninstall BE when they are being uninstalled as well.