F5F Stay Refreshed Hardware Desktop Windows 11 24h2 continues to experience BSODs with minor variations after upgrading from Windows 10.

Windows 11 24h2 continues to experience BSODs with minor variations after upgrading from Windows 10.

Windows 11 24h2 continues to experience BSODs with minor variations after upgrading from Windows 10.

I
ItzDutchFTW
Junior Member
33
03-25-2021, 01:48 AM
#1
Hello, My PC has been experiencing frequent BSODs since upgrading from Windows 10 to 11. I’m currently using version 24H2 with the latest patch. Even after reinstalling Windows multiple times and updating drivers, the crashes persist. I’ve attached the most recent BSOD analysis report from WinDGB. The error details are as follows:

- KERNEL_SECURITY_CHECK_FAILURE (139) – A kernel component has corrupted a critical data structure, potentially allowing unauthorized control.
- Key values: CPU, memory, and performance metrics show abnormal readings.
- Analysis results include detailed logs and timestamps.
- The system is attempting to recover, but the issue remains unresolved.

Please let me know if you need further assistance or clarification.
I
ItzDutchFTW
03-25-2021, 01:48 AM #1

Hello, My PC has been experiencing frequent BSODs since upgrading from Windows 10 to 11. I’m currently using version 24H2 with the latest patch. Even after reinstalling Windows multiple times and updating drivers, the crashes persist. I’ve attached the most recent BSOD analysis report from WinDGB. The error details are as follows:

- KERNEL_SECURITY_CHECK_FAILURE (139) – A kernel component has corrupted a critical data structure, potentially allowing unauthorized control.
- Key values: CPU, memory, and performance metrics show abnormal readings.
- Analysis results include detailed logs and timestamps.
- The system is attempting to recover, but the issue remains unresolved.

Please let me know if you need further assistance or clarification.

T
TehStratosHD
Senior Member
492
03-25-2021, 07:47 AM
#2
The two crashes indicate unrelated causes, often linked to memory problems. Memory isn't always RAM, but it's typically the main concern. Windows moves low-priority RAM data into the page file and retrieves it when needed, making storage appear as memory. The controller inside the CPU can cause this effect; failure here makes storage seem like memory. If storage components are affected, try testing RAM individually—use one stick at a time. If only one stick triggers crashes, the issue is likely in the CPU. Memory testers often miss faulty RAM, especially with DDR4 and newer models, so I’m skeptical of them. Your system has a 14th-gen CPU, and Intel previously misconfigured voltage settings for 13th and 14th gen chips, leading to premature failures. Around half of the 13900K and 14900K CPUs have experienced such issues at that voltage, suggesting memory-related problems. If the CPU ran without a BIOS update and still failed, it points to memory rather than hardware damage. Updating the BIOS can resolve the bug, but it won’t help if the CPU is already damaged.
T
TehStratosHD
03-25-2021, 07:47 AM #2

The two crashes indicate unrelated causes, often linked to memory problems. Memory isn't always RAM, but it's typically the main concern. Windows moves low-priority RAM data into the page file and retrieves it when needed, making storage appear as memory. The controller inside the CPU can cause this effect; failure here makes storage seem like memory. If storage components are affected, try testing RAM individually—use one stick at a time. If only one stick triggers crashes, the issue is likely in the CPU. Memory testers often miss faulty RAM, especially with DDR4 and newer models, so I’m skeptical of them. Your system has a 14th-gen CPU, and Intel previously misconfigured voltage settings for 13th and 14th gen chips, leading to premature failures. Around half of the 13900K and 14900K CPUs have experienced such issues at that voltage, suggesting memory-related problems. If the CPU ran without a BIOS update and still failed, it points to memory rather than hardware damage. Updating the BIOS can resolve the bug, but it won’t help if the CPU is already damaged.

S
Superwolf888
Junior Member
43
04-01-2021, 02:39 PM
#3
I haven't made any recent changes to your bios. The issue you're experiencing with frequent blue screens after upgrading from Windows 10 to 11 seems unrelated to a new bio update. Consider checking system stability or hardware health.
S
Superwolf888
04-01-2021, 02:39 PM #3

I haven't made any recent changes to your bios. The issue you're experiencing with frequent blue screens after upgrading from Windows 10 to 11 seems unrelated to a new bio update. Consider checking system stability or hardware health.

B
brainothon
Member
187
04-01-2021, 10:07 PM
#4
Certainly, keep in mind that addressing the problem with the updated BIOS is still important even if the fix applies to your CPU.
B
brainothon
04-01-2021, 10:07 PM #4

Certainly, keep in mind that addressing the problem with the updated BIOS is still important even if the fix applies to your CPU.

T
Taybaybay
Posting Freak
850
04-03-2021, 03:11 AM
#5
It seems the CPU is likely the issue, based on the crash you described where the Microsoft Store simply shut down.
T
Taybaybay
04-03-2021, 03:11 AM #5

It seems the CPU is likely the issue, based on the crash you described where the Microsoft Store simply shut down.

M
MollyM00
Member
197
04-05-2021, 10:55 AM
#6
Verify the RAM functionality first.
M
MollyM00
04-05-2021, 10:55 AM #6

Verify the RAM functionality first.

V
209
04-12-2021, 07:20 AM
#7
I checked both RAM sticks individually and confirmed that both functioned properly.
V
VeraquinGaming
04-12-2021, 07:20 AM #7

I checked both RAM sticks individually and confirmed that both functioned properly.

A
Altijd_Scoepi
Member
183
04-12-2021, 10:34 AM
#8
Unless it has crashed often before, you need to check each stick for longer than usual. Even if a single stick works fine by itself, it might point to a speed problem, though the 5600 should handle it well. The issue could be with the timing, the memory controller, or the CPU not being compatible with that setup. Running the test with one stick at a time makes things harder; it would be easier if it didn’t require multiple switches.
A
Altijd_Scoepi
04-12-2021, 10:34 AM #8

Unless it has crashed often before, you need to check each stick for longer than usual. Even if a single stick works fine by itself, it might point to a speed problem, though the 5600 should handle it well. The issue could be with the timing, the memory controller, or the CPU not being compatible with that setup. Running the test with one stick at a time makes things harder; it would be easier if it didn’t require multiple switches.