Getting Constant BSOD KERNEL_SECURITY_CHECK_FAILURE Errors

Question

Hello,

I've been struggling with unpredictable BSODs always with the same KERNEL_SECURITY_CHECK_FAILURE.

The minidump file indicated the file is the Kernel ntoskrnl.exe and the address is ntoskrnl.exe+6be5e9.

Searching online indicates the issue is likely a driver issue, so I have tried the following, all with no success:

• Updating Windows
• Updating ALL Drivers
• Fully removing GPU Drivers and reinstalling them
• chkdsk
• sfc /scannow
• Updating BIOS
• Checking RAM with Windows Memory Diagnostic
• Removing additional SSDs temporarily
• Resetting Windows (Keeping Files)
• Fully reinstalling Windows from network, full wipe of data

The worst part of this error is that it is wholly unpredictable.

Sometimes my computer will work fine for hours before crashing, sometimes twenty minutes.

But it always inevitably has the exact same crash and error code.

Any advice would be greatly appreciated. I'd rather not have to send the computer in for expensive repairs if I can avoid it.

Here is a GDrive link to the .dmp file. After applying a Windows Repair Update (also did not fix the issue), the Minidump folder was wiped, so there is only the most recent crash.

https://drive.google.com/file/d/15wSJOl7DmGNJ58CALAOQx7xr3Zylo6FP/view?usp=drive_link

Edit: Another crash! This one only took five minutes to appear. New record!
https://drive.google.com/file/d/1vyh5ejf6oGy9sQilFr-MMiN_8raqcCv6/view?usp=sharing

Answer 1

Hi. I'm David, and I'm happy to help you.

---

The minidump does not mention any third-party driver, only a generic system file.

---

I suggest you use the Driver Verifier utility. This utility is used to force the system to show the driver causing the problem.

Before turning on Driver Verifier, I like to create a restore point just in case. I suggest doing the same.

https://support.microsoft.com/windows/system-protection-e9126e6e-fa64-4f5f-874d-9db90e57645a

---

Turn on Driver Verifier, let the system crash 3 times, then turn off Driver Verifier. Share the minidumps that the crashes created.

1. Press Win + R, type verifier, and press Enter;
2. Select Create custom settings (for code developers) and click Next;
3. Check these options:

• Pool Tracking
• I/O Verification
• Deadlock Detection
• DMA Checking
• Security Checks
• Force pending I/O requests
• IRP Logging
• Miscellaneous Checks
• DDI compliance checking

4. Select Select driver names from a list;
5. Sort by Provider and choose all non-Microsoft drivers;
6. Click Finish and restart your computer. Driver Verifier will now monitor the selected drivers.

(Pay attention to the blue screen that is displayed. Sometimes, it may contain useful information.)

---

After the system crashes at least 3 times, follow the procedure below to disable the Driver Verifier.

1. Open Start and type cmd, right-click on Command Prompt and select Run as administrator.
2. Run the following commands at the Command Prompt one at a time:

verifier /reset
verifier /bootmode resetonbootfail

3. Then, restart the PC.

---

If the system no longer starts due to BSOD caused by the Driver Verifier, start it in Safe Mode and perform the above procedure to disable Driver Verifier.

https://support.microsoft.com/en-us/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f

---

I await your reply.

Feel free to ask any questions you may have.

Answer 2

The KERNEL_SECURITY_CHECK_FAILURE BSOD can be frustrating, especially when it occurs unpredictably. Since you've already taken several troubleshooting steps, here are some additional suggestions that might help:

1. Driver Verifier: Use the Driver Verifier tool to identify problematic drivers. This tool can help catch driver issues that may not be apparent during normal operation. You can enable it by running verifier in the command prompt and following the prompts to select drivers to verify.
2. Check for Hardware Issues: Since you've already checked RAM, consider testing other hardware components. This includes running diagnostics on your hard drive or SSD to ensure there are no underlying issues.
3. Remove Third-Party Software: Sometimes, third-party software, especially security software, can interfere with system operations. Try uninstalling any third-party antivirus or system utilities to see if that resolves the issue.
4. System Restore: If the problem started recently, consider using System Restore to revert your system to a previous state before the issue began.
5. Event Viewer: Check the Event Viewer for any critical errors that coincide with the times of the BSOD. This might provide more insight into what is causing the crashes.
6. Revisit BIOS Settings: Sometimes, settings in the BIOS can lead to instability. Ensure that your BIOS settings are optimized for your hardware configuration, and consider resetting to default settings if necessary.

If none of these steps resolve the issue, it may be worth considering professional diagnostics to check for deeper hardware issues or potential motherboard problems.

---

References:

• Troubleshoot bug checks (stop code errors)
• Advanced troubleshooting for stop code errors