Question about the Kernel Security Check Failure at line 139.
Question about the Kernel Security Check Failure at line 139.
Hi,
My PC specifications:
CPU: Intel I9-13900K
RAM: Corsair Dominator Platinum 32GB DDR5 6000
Motherboard: Asus Rog Maximus Z790 Hero WiFi
SSD: WD Black SN850X 1GB NVMe
GPU: Geforce RTX 4090 Phantom
I had no issues before, but about three months ago it began with about one byte per day, and it worsened until the PC reached ten bytes daily.
I chose to upgrade to a fresh Windows 11 Pro install and updated all firmware and drivers to the latest versions.
I ran several mem tests, including a USB stick test, and everything passed.
Now it’s much better, but when I play racing (my only game), I still encounter the kernel 139 message after 2-3 hours.
I installed WINdng and checked my dumpfile, but I’m unsure what’s causing the problem.
Could someone help me identify the issue?
Thanks already
(sorry for my bad English, I’m from the Netherlands)
What power supply unit are you employing?
Using Kernel_Security_Check_Failure, attempt to disable secure boot and observe if the issue improves with fewer BSODs.
In any case, given these symptoms, I’d begin considering an Intel 13th/14th deterioration problem. The CPU could be compromised.
Along with the previous suggestions, I am curious about whether your motherboard includes built-in hard drive or RAM monitoring systems. Since if the PSU is faulty, it might be a SATA Controller, hard drive, or RAM issue. I believe Memtest86+ would be a suitable next step if your PSU and its voltage/amps are within specifications.
Do you want to check if your Asus ROG Thor 1200w Platinum II PSU is working properly?
Usually, a stack buffer overflow in a video driver suggests updating the video driver and deleting any over GPU overclock settings.
First fix would be to install the latest stable video driver.
Second fix involves removing overclock drivers and updating the BIOS to the latest release.
If you're going to post dumps then PLEASE post the actual dump files, not just the output from analyze -v. Dump analysis is way more involved that just analyze -v. Upload the dump files please.
There are numerous power supply testing guides available, and I believe this forum under the power supply section has at least one or two of them.
BUT if you're not sure, then don't take any chances, particularly if you're not familiar with handling electricity or circuits.
You can simply purchase a new, reliable unit and try it out to see if it resolves the problem, as you would need to do anyway if the current one doesn't meet specifications.
Did you resolve this matter or identify the issue? I’ve also encountered similar problems before, never experiencing BSODs prior. It now occurs consistently during every race in iRacing. RAM was tested extensively, CPU remains unchanged, and no overclocking was applied. Windows was reinstalled alongside the latest BIOS, firmware, and drivers. All USB devices were unplugged, yet the problem persists. I’m really puzzled.
Summary: The system failed due to a KERNEL_SECURITY_CHECK_FAILURE (139) error, pointing to corruption in a vital kernel data structure. Likely cause points to a memory management or graphics component failure resulting in data corruption.
I’m starting to believe the problem might lie with the anti-cheat system, given that it seems to have a malfunction. It could be a bad interaction with one of the drivers, though I’d expect more users to encounter this issue. Have you attempted switching back to an Nvidia driver from around September, which is something I haven’t tried yet?
This error appears in the event log during the BSOD:
Faulting application name: start_protected_game.exe, version: 1.9.3.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000001591ad19b3d
Faulting process id: 0x1C4C
Faulting application start time: 0x1DC8E3E7BB3141C
Faulting application path: C:\Program Files (x86)\iRacing\start_protected_game.exe
Faulting module path: unknown
Report Id: 83e0f76f-f082-4f84-8a1c-53182b1f303e