How to fix KERNEL_SECURITY_CHECK_FAILURE on Windows 11

Question

How to fix KERNEL_SECURITY_CHECK_FAILURE on Windows 11

Kingston Lu 0

2026-02-12 Update: Additional data can be found here: https://drive.google.com/drive/folders/1IsyTqPLYP8Hb5okdkee4NjCE0EHrMQRG?usp=drive_link

My computer experienced the KERNEL_SECURITY_CHECK_FAILURE blue screen today and last week. I have tried multiple solutions suggested online and they haven't seemed to work. The computer specifications are below: issue2 Since parameter 1 is set to 3, this means it's a LIST_ENTRY corruption, which has been said to be "difficult to track down" on learn.microsoft.com.

LIST_ENTRY corruption can be difficult to track down. This bug check indicates that an inconsistency was introduced into a doubly linked list (detected when an individual list entry element is added to or removed from the list). Unfortunately, the inconsistency is not necessarily detected at the time when the corruption occured, so some detective work may be necessary to identify the root cause.

Note that different programs were active at the time of both the bluescreen on January 18th and the one today.

I have unsuccessfully tried the following things:

DISM and sfc /scannow
Windows Memory Diagnostic
Full scan for malware
Updating device drivers
chkdsk

Does anyone have any other suggestions?

Tom Grand 5 Reputation points

2026-04-24T10:27:25.5933333+00:00

The specific detail worth paying attention to is parameter 1 = 3. That means LIST_ENTRY corruption, which is a particular type of kernel data structure getting corrupted rather than a straightforward driver crash. The reason it's tricky is that the corruption usually happens before the crash, so whatever caused it has often already finished running by the time Windows throws the error.

Your crash date of January 26 is worth noting. KB5074109 launched around that time and was confirmed to cause instability on certain systems. Ivan B was on the right track asking about it. Check if it's installed by going to Settings > Windows Update > Update history and searching for KB5074109. If it's there, try uninstalling it from there or from Control Panel > Programs > View installed updates.

If the update isn't the cause, the next most common trigger for LIST_ENTRY corruption specifically is third-party security software. Antivirus tools hook deeply into the kernel and are the number one culprit for this type of corruption even with well known brands. If you have anything other than Windows Defender running, try uninstalling it completely rather than just disabling it, since disabling still leaves kernel hooks in place.

If neither of those pan out, running Driver Verifier with all non-Microsoft drivers selected would be the next step. Let it crash a few times and share the new minidumps. Those would be much more targeted than the ones you already uploaded since Verifier is specifically designed to catch this type of corruption.

1 answer

Your answer

Tom Grand 5 Reputation points

2026-04-24T10:27:25.5933333+00:00

The specific detail worth paying attention to is parameter 1 = 3. That means LIST_ENTRY corruption, which is a particular type of kernel data structure getting corrupted rather than a straightforward driver crash. The reason it's tricky is that the corruption usually happens before the crash, so whatever caused it has often already finished running by the time Windows throws the error.

Your crash date of January 26 is worth noting. KB5074109 launched around that time and was confirmed to cause instability on certain systems. Ivan B was on the right track asking about it. Check if it's installed by going to Settings > Windows Update > Update history and searching for KB5074109. If it's there, try uninstalling it from there or from Control Panel > Programs > View installed updates.

If the update isn't the cause, the next most common trigger for LIST_ENTRY corruption specifically is third-party security software. Antivirus tools hook deeply into the kernel and are the number one culprit for this type of corruption even with well known brands. If you have anything other than Windows Defender running, try uninstalling it completely rather than just disabling it, since disabling still leaves kernel hooks in place.

If neither of those pan out, running Driver Verifier with all non-Microsoft drivers selected would be the next step. Let it crash a few times and share the new minidumps. Those would be much more targeted than the ones you already uploaded since Verifier is specifically designed to catch this type of corruption.

Answer 1

Ivan B 122.3K Independent Advisor

Hi ,

If it is a laptop or desktop, if possible, could you provide the laptop model or your desktop configuration?

Access the c:\windows\minidump folder, copy the files to your desktop, then upload them to OneDrive or Google Drive and post the link here for analysis.

Thanks

Ivan B 122.3K Reputation points Independent Advisor

2026-01-28T11:24:04.74+00:00

Hi,

Do you have the KB5074109 update installed?

Thanks
TNick-1472 0 Reputation points

2026-02-27T14:31:56.4966667+00:00

Hi, I have been having this error periodically for weeks now.

It's on a Dell precision 7680.

I think it might be a hardware issue as it only happens when I'm moving the laptop around.

Also, don't know if this is related, but at one point it wouldn't charge and I reseated the battery, which fixed that problem.Thanks for your help on this!
Tom Grand 5 Reputation points

2026-04-24T10:28:14.39+00:00

Crashing specifically when the laptop moves is almost always a physical connection issue rather than a software problem. Since you've already reseated the battery it sounds like you're comfortable opening it up. Worth reseating the RAM sticks as well, a slightly loose stick can cause intermittent corruption that produces exactly this error. Press them down firmly until both clips click into place on each side.
TNick-1472 0 Reputation points

2026-04-24T17:40:16.0266667+00:00

Thanks Tom.

This was indeed the issue.

After awhile, IT finally had me reseat the memory and that fixed it.

Notably, I have the 128GB model (I know, worth a fortune in 2026), so the reseating looked different than anything else.

But anyway, thanks again! It's people like you doing Microsoft's job for them that makes lives of people like me a lot easier