KERNEL_SECURITY_CHECK_FAILURE (0x139) | Microsoft Community [Unofficial] | Page 1

gray bane Feb 22, 2026, 3:34 AM

#

I have been getting GSOD issues on Release Preview Ring for the past few months after much troubleshooting I'm convinced this is a Windows Update issue as I am struggling to nail it down after running DISM and SFC repairs, bios updates, driver updates, resetting network stack, disabling and re-enabling Hyper-V, removing possible problematic drivers and apps.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffff8688bcf0eec0, 0xffff8688bcf0ee18, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7f5d9d0b-fd9f-44b2-b6e0-865ca65866d4.

In addition to this I have found excessive warnings on the Hyper-V VM switch logs in event viewer:

V-Switch operation OID_GEN_STATISTICS (131334) took too long to complete. Operation Type: OID HOST VNIC. Execution time 0 ms. Queued time 0 ms. Expected execution time less than 0 ms. NicName: C08CB7B8-9B3C-408E-8E30-5E16A3AEB445. NicFriendlyName: Default Switch.

https://aka.ms/AAzvatv

gray bane Apr 1, 2026, 7:22 AM

#

This issue is ongoing an a Deeper dive on this is pointing to Focusrite USB audio drivers

dusk cave Apr 8, 2026, 9:51 PM

#

gray bane I have been getting GSOD issues on Release Preview Ring for the past few months ...

An bug check is an result from the kernel having a invalid memory table causing patch guard to initialize a BSOD,
Likewise messed up from hyper-V being installed incorrectly,
best option is to reinstall windows

#

or could be an bad driver for network for Hyper-V

#

Fixing a kernel that has bad memory is hard, best to reinstall windows anyways

#KERNEL_SECURITY_CHECK_FAILURE (0x139)