i9-13900k Corrected Hardware Error has Occurred

[JavierJ]

Hello, I've had an issue for a couple weeks where my computer had BSOD and I had to reinstall windows to be able to log in. Later I found out xmp what making my computer BSOD during gameplay (randomly started after computer built 2 months ago).  Initially thought it was the GPU because it only happened in games. But then this BSOD also happened in CPU Benching/Stress test. So then thought of the CPU. I turned off xmp and undervolted and as far as I know it runs ok but doesn't use all the cores and threads. When I run certain games such as Minecraft Java Edition I get exit code 1. Then WHEA-Logger event 19 and 2 saying I have a corrected hardware error has occurred. message with details below. I'll also attach the file I was given Minecraft crashed. I want to know if this is something I should RMA the CPU for, because I tried 3 weeks of potential fixes since this started and I'm still having issues on a brand new system. Specs: Asus Strix OC 4090. CPU: i9-13900K, PSU: Asus Thor 1200W, Ram: Dominator 6600 CL32.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Translation Lookaside Buffer Error
Processor APIC ID: 16

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 40

[s4mor4i]

I Bought it from a vendor. I called them today they said they have to test and send it back and wait for a replacement.  I don't know how exactly things work in here. I think they will end up sending a 14900k instead. hope they get done with it quick. 

[s4mor4i]

Hey there, it's been a long time. finally, they replaced my i9 13900k with a 14900k. and I still have issues with windows. a friend of mine done the same thing and he still has issues with the 14900k. BSOD and other games and applications refusing to work or crash. the only thing we have in common is and ASUS motherboard. tested the CPU on OCCT with no errors.  everything else is working fine RAM, GPU and M.2s.
Any idea what's wrong? 
we are currently thinking of replacing the board, since it's the only thing we have in common.

this is only for one week or less of using windows on the i9 14900k. is it a normal thing to have all these crashing.

[xycia]

Hey there. I was having issues too and took the advice from another poster and I decided to downgrade to the i7-13700k and haven't looked back. All of the issues I had with the i9-13900k all magically disappeared. There is an obvious issue with these processors.

[s4mor4i]

hey, hope you are doing great. I thought about getting an i7 but it's too late they've already replaced it with a 14900k, and it took almost 2 months. could it be the AIO Cooler. I have a 240m cooler from arctic. temps when I'm gaming go up to 86 sometimes 88 c.  maybe it's causing damage to the CPU. 

[n_scott_pearson]

Most motherboards require a BIOS upgrade before they can fully support the 14th gen processors. Did you look to see if a BIOS upgrade was made available by your motherboard manufacturer? If so, install it and see whether that resolves the issues.

Hope this help,

...S

(Edited for bad grammar)

[s4mor4i]

yes, I did, unfortunately it didn't work. 

[peeceful]

Started having this issue a couple of days ago.

Fortunately, only my application (Davinci resolve) and my games are crashing. No BSOD as of yet.

I am at a total loss as to what is causing the issue. Everything thats happening is pointing towards a dying GPU which I hope not since its a 4090 but the event viewer is throwing this fault.

Bios has the latest version and I have done multiple different checks.

Disabling XMP didnt work and my logs from userbenchmark show that all HW is performing perfectly.

The only issue I can think of when it started is that I installed a windows update which I believe have now uninstalled. The system recovery wont go back far enough for me to restore to a point before this.

XML Dump:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />

  <EventID>19</EventID>

  <Version>0</Version>

  <Level>3</Level>

  <Task>0</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000000000000000</Keywords>

  <TimeCreated SystemTime="2024-03-21T18:26:23.8805084Z" />

  <EventRecordID>62898</EventRecordID>

  <Correlation ActivityID="{0d501d18-e50e-47be-946c-0d655d704f40}" />

  <Execution ProcessID="7612" ThreadID="9108" />

  <Channel>System</Channel>

  <Computer>peeceful_2_0</Computer>

  <Security UserID="S-1-5-19" />

  </System>

- <EventData>

  <Data Name="ErrorSource">1</Data>

  <Data Name="ApicId">24</Data>

  <Data Name="MCABank">0</Data>

  <Data Name="MciStat">0x8000004000040005</Data>

  <Data Name="MciAddr">0x0</Data>

  <Data Name="MciMisc">0x0</Data>

  <Data Name="ErrorType">12</Data>

  <Data Name="TransactionType">256</Data>

  <Data Name="Participation">256</Data>

  <Data Name="RequestType">256</Data>

  <Data Name="MemorIO">256</Data>

  <Data Name="MemHierarchyLvl">256</Data>

  <Data Name="Timeout">256</Data>

  <Data Name="OperationType">256</Data>

  <Data Name="Channel">256</Data>

  <Data Name="Length">1003</Data>

  <Data Name="RawData">435045521002FFFFFFFF04000200000002000000EB030000161A1200150318140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A35C8F68CCB87BDA01000000000000000000000000000000000000000000000000A0010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000060020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D00000000000000000000000000000000020000000000000000000000000000000000000000000000A0020000240100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000020000000000000000000000000000000000000000000000C4030000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC000000000000000000000000000000000300000000000000000000000000000000000000000000005721000000000000000208000000000071060B00010000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000180000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000180000000000000071060B0000088018FFFBFA7FFFFBEBBF000000000000000000000000000000000000000000000000000000000000000003000000010000008351E946BD7BDA0106000000000000000000000000000000000000000000000005000400400000800000000000000000000000000000000000000000180000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000</Data>

  </EventData>

  </Event>

 
------------------------------------------------------------------------------------------------------------------------------

--- IPDT64 - Revision: 4.1.9.41
--- IPDT64 - Start Time: 21/03/2024 19:29:02

----------------------------------------------
-- Testing
----------------------------------------------
CPU 1 - Genuine Intel - Pass.
CPU 1 - BrandString - Pass.
CPU 1 - Cache - Pass.
CPU 1 - MMXSSE - Pass.
CPU 1 - IMC - Pass.
CPU 1 - Prime Number - Pass.
CPU 1 - Floating Point - Pass.
CPU 1 - Math - Pass.
CPU 1 - GPUStressW - Pass.
CPU 1 - CPULoad - Pass.
CPU 1 - CPUFreq - Pass.

IPDT64 Passed
--- IPDT64 - Revision: 4.1.9.41
--- IPDT64 - End Time: 21/03/2024 19:32:49

----------------------------------------------
PASS

[sverkpol]

I've similar problem on 13600K, but it looks really weird. My hand-assembled PC was running absolutely OK for a year or so and started randomly powering off and rebooting from 28-Apr-2024. No BSOD - just power off with 'click' in PSU and auto-reboot in 2-3 seconds.
I see in event log the first single WHEA-Logger regarding Processor Core appeared 2 months before that and it became rather frequent afterwards.

Warning 01.05.2024 05:48:41 WHEA-Logger 19 None
Warning 28.04.2024 12:07:10 WHEA-Logger 19 None
Warning 28.04.2024 00:57:57 WHEA-Logger 19 None
Warning 28.04.2024 00:57:55 WHEA-Logger 19 None
Warning 28.04.2024 00:57:50 WHEA-Logger 19 None
Warning 28.04.2024 00:10:28 WHEA-Logger 19 None
Warning 28.04.2024 00:08:01 WHEA-Logger 19 None
Warning 28.04.2024 00:03:21 WHEA-Logger 19 None
Warning 03.02.2024 11:56:08 WHEA-Logger 19 None

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Internal parity error
Processor APIC ID: 24

The strange thing in my case - system dies only at the moments of "no load", this happens especially frequently when I switch to "power saver" scheme and LibreHardwareMonitor shows power usage of CPU package around 3-4 Watts.
It never happened under load. To my experience with hand-assembled PCs - if system works stably for the first week, it typically works without problems for years until replace with more modern hardware, unfortunately not in this case :(.

I tried disabling “Intel SpeedShift” and “Intel TurboBoost” (workaround mentioned by sibidharan earlier) - this causes CPU to work at stable frequency and stable power load of around minimal 15-20 Watts. System did not crash in that config for few hours so far.

No idea what to do with that CPU, most probably it needs replacement.

My hardware is: 13600K + MB Z790M PG Lightning/D4 + PSU beQuiet Straight Power 11 750W + G.Skill F4-4400C19-16GVK 2*16MB

[s4mor4i]

hey there, hope you're doing great. 

for me what solved the issue was limiting the short and long duration load line to 253 watts and iccmax to 307. I did that after I replaced my motherboard with an Asus Z790 hero (totally unnecessary)

and watch this: https://www.youtube.com/watch?v=HIubZYwBfPc

360 AIOs can't cool i9 13th and 14th gen without the intel limits.

[MadMartian]

This isn't just 13th gen i9, I have experienced this issue on both a 13900K and a 14900K on two separate mother boards on a new build.  I'm starting to think the definition of a desktop PC is a furnace for burning money.

I first built this rig last September with the 13th G processor, which some months later failed stress tests.  That prompted me to replace both the CPU and the MoBo earlier this year in March.

Now with a new MoBo and 14th G processor, I experience periodic and frequent MCEs: most of the MCAs are internal parity errors, some instruction TLB level-0 errors, and one L1 cache instruction fetch error.  I've collected ~30 of these events over the past couple of weeks.

What's strange is that I get consistent behavior from the same software applications:

• IntelliJ Ultimate freezes, then logs a VM-level crash report
• Running Node.js Jest tests causes the system to freeze and then reboot
• Browser tabs randomly crash

`dmesg` shows that logged MCEs coincide with these crashes.

Everything else seems stable and doesn't instigate any issues, including (but not limited to):

• Zoom
• OBS
• IntelliJ CLion or PyCharm
• Docker containers
• Windows VM (via VMware)
• Various games
• Local GPT (shouldn't matter, that's the GPU guzzling amps from the electron hose)

And I'm not looking forward to testing 128 GB of RAM, especially if there's little evidence of that.

What's the lesson learned here? to ensure the BIOS respects Intel power limits? should I have gone with AMD instead? 360mm AiO isn't cool enough?  I've had only one other AMD build, other than that I've been building Intel-based PCs since the 90s.  This is the first time I've ever experienced such system instability as the result of a faulty CPU.