KB5132061 (26200.9974) causes repeated BSOD 0x3B in Registry process ~8-11 min after boot

Question

KB5132061 (26200.9974) causes repeated BSOD 0x3B in Registry process ~8-11 min after boot

HM 0

After installing 2026-11 security update KB5132061 (OS build 26200.9974), the PC crashed

8 times in one day with SYSTEM_SERVICE_EXCEPTION (0x3B, c0000005).

Process context: Registry (every time)
Faulting address: ntoskrnl.exe+0xbd2753 / +0xbd2734 (hive cell map lookup), and ntoskrnl.exe+0x8689e4 / +0x868a53 (caller using the returned cell)
Stack: ntoskrnl, Ntfs.sys, storport.sys only (no third-party driver)
Timing: 7 of 8 crashes occurred 8 to 11 minutes after boot
Uninstalling KB5132061 fixed the issue (stable since).

Hardware: MSI MAG Z890 TOMAHAWK WIFI (BIOS 1.AD0), Intel Core Ultra 9 285k, NVIDIA GeForce RTX 4070 Ti SUPER, NVMe storage.
I can provide minidumps if needed.
I had to pause Windows Update because of this.

Do you know if a fix will be published or if there's another solution ?
Thank you

0 comments

2 answers

Your answer

Answer 1

HM 0

Yeah I don't have any crash since I uninstalled this update, so it's obviously linked to it in some way.
Here's some of the minidumps:
https://1drv.ms/u/c/ef302d5b23a9772c/IQBWk-oZ0Oy6Sa95z4CfbTtYAdtRS-YXd4Nh2Gg_9v8uQ6w?e=LR0Lhb

https://1drv.ms/u/c/ef302d5b23a9772c/IQAL5ZzFBrp-SLKTXbcbpI3AAdRnRp8mwEfyjFGD8DHsGqw?e=t0gLph

https://1drv.ms/u/c/ef302d5b23a9772c/IQBA2hfU4BKfS6Lltq8SX8PoAcfFd7SYnmtEqVNAvRZRE0Y?e=DulBdr

I notified the issue on the Feedback Hub.

TaoLi 120.6K Reputation points Independent Advisor

2026-11-13T01:32:11.04+00:00

Thanks, the dump confirms the same Registry crash, about 8 minutes 42 seconds after startup. It shows an invalid memory access, but doesn’t pinpoint the cause.

Since uninstalling KB5132061 stopped the crashes, keep updates paused temporarily.

Thank you also for reporting this issue to Microsoft so that they can investigate and fix it.
HM 0 Reputation points

2026-11-13T05:23:18.6066667+00:00

@TaoLi Is there any way to further pinpoint the cause? I can reinstall the update to help find the inner issue if there's a good way to do it.
TaoLi 120.6K Reputation points Independent Advisor

2026-11-13T09:37:00.2766667+00:00

Yes—a more detailed dump may help. First check whether C:\Windows\MEMORY.DMP already exists from an affected crash.

If not: Win + R >> sysdm.cpl >> Advanced >> Startup and Recovery Settings >> Write debugging information >> Automatic memory dump. Keep the paging file system-managed and restart.

After one crash, save C:\Windows\MEMORY.DMP

Answer 2

Since uninstalling KB5132061 stopped the crashes, that strongly suggests an update-related issue. I’d keep it uninstalled and updates paused temporarily while investigating.

Yes, please share 2–3 minidumps from the affected boots. Copy them from C:\Windows\Minidump to your Desktop >> ZIP them >> upload to OneDrive and share the link here. That is the default small-dump location. Seeing only Microsoft drivers in the stack doesn’t conclusively identify the cause.

Please also submit your findings through Feedback Hub using Win + F, including that uninstalling the update restored stability. Share the dumps here and I’ll follow up.