i9 14900KF random crashes and BSOD with different stop codes

[eanastasov]

Hello, so i have this issue with my i9 14900KF processor. I bought it December 2023 in a pre-build system. 

My configuration:

MSI PRO Z790-P WIFI (MS-7E06) - BIOS A.G0 2025/04/11
Intel Core i9-14900KF
A-Data 4x16GB DDR5 6000 SDRAM PC5-38400
Asus GeForce RTX 4090 OG 
WD Black SN850X HS 2TB

1000W 80 Platinum PSU

So, I was struggling with my processor since day 1. I tried different fixes to make my system stable. After many Windows updates and re-installations I finally found out what the problem is. And before that I tried any possible fixes, believe me. Here some of my stop codes:

1. 0x0000003B – SYSTEM_SERVICE_EXCEPTION

• Module: ntdll.dll

• Description: This error usually occurs when there is an exception in kernel-mode, typically due to driver issues, memory corruption, or incompatible software.

• When: During face recognition in PortraitPro Studio 23 and 24 (95–99% progress).

• Frequency: Frequent and repeatable.

• Tried Fixes: Lowering overclocks, updating BIOS/drivers, changing antivirus, relocating install to E: drive, reinstalling Windows, swapping SSD, etc.

2. 0x0000001A – MEMORY_MANAGEMENT

• Description: Indicates a severe memory management issue, often caused by faulty RAM, corrupted system files, or overclocking instability.

• When: Likely occurred after restoring a system image or during stress points.

• Symptoms: Crashed during operations like sfc /scannow.

3. 0x0000000A – IRQL_NOT_LESS_OR_EQUAL

• Description: Common BSOD usually caused by a driver trying to access memory it shouldn't. Often hardware-related, or caused by bad overclocks.

• When: Noted in early reports involving high CPU load or BIOS instability

4. 0x00000050 – PAGE_FAULT_IN_NONPAGED_AREA

• Description: Happens when the system cannot find data it expects in RAM. Usually tied to RAM instability, bad drivers, or anti-virus conflicts.

• When: Possibly during PortraitPro or after system image restoration. May relate to aggressive RAM tuning.

5. 0x00000124 – WHEA_UNCORRECTABLE_ERROR

• Description: A hardware error, often CPU-related. Very common with unstable overclocks, voltage misconfiguration, or failing components.

• When: Mentioned when CPU was hitting 100% load or when testing full CPU utilization.

• Fix: You resolved this by lowering P-core multipliers (from 57/60 down to 56).

6. 0x0000007E – SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

• Description: Caused by a driver or system thread failing, commonly linked to faulty software or hardware stress.

• When: Likely occurred in PortraitPro or testing other apps before reinstall.
  
  
  

So, by BIOS defaults,  2 of my 8 P-Cores, No. 4 and 5 runs at x60 multiplier, and all the rest at x57. Like this, any stress on my system leads to BSOD. When I lower these 2 cores to x57 all is fine, no matter what I am doing, more then a month now not even one crash. I do video rendering and photo editing. You can imagine what I've been through. My question is, why is this happening? Is it faulty CPU and should I 100% RMA or there are some BIOS setting that I didn't tried yet, that can give me the optimal state of my premium CPU, after all for premium price I should get premium performance, yes? I know 5% performance drop is not much but still.... Any ideas are welcomed! 

EDIT: Maybe my motherboard is not strong enough for this CPU? I am starting to think that this could be the main reason for those crashes at BIOS defaults....

[AlHill]

Try different memory.  The processor specs say:  Up to DDR5 5600 MT/s

Doc (not an Intel employee or contractor)
[This is the dawning of the age of Colossus, where peace is compulsory, freedom is forbidden, and man’s greatest achievement is man’s greatest mistake.]

[eanastasov]

Well, I actually disabled the high memory profile early on and still got the same crashes. Turns out the issue was two P-cores running at x60 — once I lowered them to match the rest at x57, everything stabilized. RAM wasn’t the cause in my case, and now the system is 100% stable — even with the high memory profile re-enabled.

EDIT: My crash types (0x124, 0x3B, etc.) are classic signs of CPU core instability, not RAM issues.

[Affenbaron]

Hello, I have exactly the Same issue and also have P4 and P5 Running with 60y how can i change this. I use a Gigabyte Mainboard and there its called for example P4 Fused Max Core Ratio: 60. I am struggling for months now. Would be Great if you can help me!

[eanastasov]

What's exactly your motherboard model and the bios version?

[Affenbaron]

Thank you its: B760 GAMING X AX and BIOS F13

[eanastasov]

Okey, here's how I hope you can fix it.

When you enter the BIOS go to advanced mode, with F2 usually, should be visible somewhere on the top or bottom of the screen. Then go to Tweaker tab -> Advanced CPU settings. There look for something like P-core Ratio Apply Mode or similar and set it to manual or per core. Then the cores should become visible under, or if you see them before but grayed out should be white now and editable. Go to core 4 and 5 and set them from 60 to 57 or something, to match the rest. Then save and reboot. Check if you have stable system like that, if no go one more point down to all. You gonna trade around 5% performance for a stability. If you just playing games it wont matter, you might lose few frames on CPU demanding games but nothing more. Keep me updated!

Edit: I watched another video and saw something else in the BIOS, in the Advanced CPU settings you should enable CPU Flex Ratio Override and then under the CPU Flex Ratio Settings should become active and allow custom ratio input per P-core or a global cap. You overwrite to 57 from 60 or to match the rest cores. I hope it lets you select each one of them individually. 

[Affenbaron]

Hello eanastasov,

I edited the P-Core Ratio like you said and it really seems like it is working for me aswell.

I am so greatful for your help!
For now the system is stable...Thank you very much for the great help.

I cant believe that Intel is not fixing this...

br

[eanastasov]

I am happy to help! I am glad this worked out for you! Yeah, maybe Intel are currently working something about it, I hope so... as a new micro code BIOS update in the nearest future...