How to Fix Kernel Security Check Failure on Windows 11?

0
5
Asked By CoolGiraffe17 On

I'm dealing with a frustrating issue on my Windows 11 computer where I keep getting a BSOD (Blue Screen of Death) error that says 'Kernel Security Check Failure.' It usually happens a few minutes after I start using my PC, and then it restarts all on its own. I've run some commands in Windows to check for problems and they didn't find any issues. These include running `dism /online /cleanup-image /restorehealth`, `mdsched.exe`, and `sfc /scannow` which did repair some corrupted files but didn't solve the BSOD issue. I've also shared my DMP file for further analysis. Here are my specs:
- GPU: PowerColor Radeon RX 6500 XT
- Motherboard: Gigabyte B660 DS3H AC DDR4-Y1
- SSD: WD Blue SN550 500 GB
- CPU: Intel Core i3 12100f
- RAM: 16 GB T-FORCE Vulcan Z

3 Answers

Answered By UserFriendly42 On

It sounds like you've already done quite a bit of troubleshooting! Since many users have reported similar BSOD errors following the 24H2 update for Windows 11, it might be worth checking if your Realtek network driver is the issue. I recommend updating it from your motherboard manufacturer’s website. If that doesn’t work, try the latest version directly from Realtek's site, specifically the NetAdapterCx version. Make sure to disconnect from the network if you need to switch drivers and only rely on WiFi for the installation.

Answered By CleverCactus83 On

I can relate to your struggle! BSODs can be really annoying. Before trying anything too involved, ensure your data is backed up. If you're still experiencing issues after updating the Realtek driver and BIOS, try booting into Safe Mode to see if the BSOD still occurs. Also, check the Minidump folder for any crash logs and share those for deeper analysis.

Answered By TechSavvyDude On

Have you considered updating your motherboard's BIOS? If you're using an iBUYPOWER system, your BIOS version might be outdated compared to the latest available on Gigabyte's support page. Regarding the BSOD itself, it looks like WinDbg pointed to a driver called HpReadHWData.sys. If you have any HP software or hardware connected, that could be causing conflicts. Check if you can update or uninstall that driver and see if it helps.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.