sorry long post
I’m trying to determine whether my i9-14900K is defective before pursuing an Intel warranty replacement.
PC Specs
- CPU: Intel Core i9-14900K
- Motherboard: ASUS TUF GAMING Z790-PLUS WIFI
- BIOS: 1836 (updated from 1805)
- RAM: 96GB Corsair DDR5 (2×48GB), running at 4800 MT/s with XMP disabled
- GPU: NVIDIA RTX 3090 Founders Edition
- Cooling: 360mm AIO liquid cooler
- Original Windows SSD: Samsung 970 EVO Plus 1TB
- New SSD: Samsung 990 PRO 2TB
- Storage: Samsung 870 EVO 4TB
- OS: Windows 11 Pro
Initial symptoms
It started with Minecraft Bedrock crashing randomly, sometimes while loading chunks and sometimes while doing absolutely nothing. Other players on the same Realm weren’t crashing.
Eventually I discovered much broader instability:
- Dozens of Windows Reliability Monitor critical events
- Windows Search Indexer, Software Protection Platform, Windows Modules Installer, and other services repeatedly crashing
- Multiple BSODs and unexpected shutdowns
- Windows system-file/component-store corruption
Crash evidence
Event Viewer recorded:
WHEA-Logger Event ID 19
- Reported by: Processor Core
- Error source: Corrected Machine Check
- Error type: Internal parity error
- Processor APIC ID: 41
I also analyzed five minidumps:
- Four crashes with 0x3B (SYSTEM_SERVICE_EXCEPTION)
- One crash with 0x50 (PAGE_FAULT_IN_NONPAGED_AREA)
- Access violation 0xC0000005
- WinDbg identified crashes involving ntkrnlmp.exe and Ntfs.sys, including Ntfs!NtfsReadFileRecord
Troubleshooting already performed
BIOS / CPU
- Updated ASUS BIOS to version 1836
- Selected Intel Default Settings — Performance
- Disabled ASUS MultiCore Enhancement (Enforce All Limits)
- Disabled XMP
- Intel Processor Diagnostic Tool: PASS
- OCCT CPU test stopped at its 90°C temperature safety threshold, with no computation errors detected before stopping
RAM
- OCCT 30-minute memory test: PASS
- Tested each 48GB stick individually in the recommended A2 slot
- Both produced the same Windows startup failure
- BIOS consistently recognizes both modules
Storage / Windows
- Both original Samsung SSDs reported Healthy / OK
- chkdsk C: /scan found no file-system errors
- DISM detected repairable component-store corruption
- DISM RestoreHealth failed with errors including 1726 and 0x800F0915
- SFC initially reported a pending repair, then later failed at 65%
- Completed Windows 11’s built-in repair installation, but component-store corruption persisted
- Windows Automatic Repair eventually failed, leaving Windows unable to boot
Current problem: Fresh Windows installation fails
I disconnected the original 1TB Windows SSD and installed a Samsung 990 PRO 2TB for a completely clean Windows 11 Pro installation.
Used Microsoft’s Windows 11 USB installation media and completely cleared the 2TB drive.
Windows Setup creates the EFI, MSR, and primary partitions, but the system restarts and goes back to BIOS with no Windows Boot Manager.
After multiple attempts, I checked the SSD using DiskPart. There is no D:\Windows directory. Only the temporary $Windows.~BT installation folder exists.
Setup logs show the installer preparing/restoring Windows image application operations, but no clear fatal installation error. The computer seems to restart before Windows finishes installing.
Temperatures
- CPU idles around 32–37°C in BIOS
- AIO liquid temperature around 31°C
- Left the PC in BIOS for 20 minutes; CPU temperature remained approximately 35°C
- No obvious overheating at idle
My questions
- Does this sound like a degraded i9-14900K, given the processor-core internal parity error, unrelated application crashes, and repeated BSODs?
- Could the CPU’s memory controller or motherboard explain this even though both RAM sticks behave similarly?
- What additional testing would best isolate the CPU before requesting a warranty replacement?
- Has anyone experienced Windows 11 installation failures like this with a failing 14900K?
I’m trying to avoid blindly replacing components, but at this point I’m strongly considering an Intel CPU warranty claim. Any guidance would be appreciated.
File: 101226-10453-01.dmp | Crash date: 2026-10-12
Stop code: 0x0000003B (SYSTEM_SERVICE_EXCEPTION)
Bugcheck exception parameter: 0xC0000005 (access violation)
Detailed WinDbg faulting-module output: not available in supplied evidence
File: 101326-10109-01.dmp | Crash date: 2026-10-13
Stop code: 0x0000003B (SYSTEM_SERVICE_EXCEPTION)
Bugcheck exception parameter: 0xC0000005 (access violation)
Detailed WinDbg faulting-module output: not available in supplied evidence
File: 101326-10359-01.dmp | Crash date: 2026-10-13
Stop code: 0x0000003B (SYSTEM_SERVICE_EXCEPTION)
Bugcheck exception parameter: 0xC0000005 (access violation)
Detailed WinDbg faulting-module output: not available in supplied evidence
File: 101326-10718-01.dmp | Crash date: 2026-10-13
Stop code: 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)
WinDbg process: sppsvc.exe
WinDbg reported image: ntkrnlmp.exe
Reported fault symbol: nt!RtlpUnwindPrologue+520
WinDbg failure bucket: AV_nt!RtlpUnwindPrologue
File: 101326-11859-01.dmp | Crash date: 2026-10-13
Stop code: 0x0000003B (SYSTEM_SERVICE_EXCEPTION)
Bugcheck exception parameter: 0xC0000005 (access violation)
WinDbg process: svchost.exe
WinDbg reported image: Ntfs.sys
Reported fault symbol: Ntfs!NtfsReadFileRecord+72
WinDbg failure bucket: AV_Ntfs!NtfsReadFileRecord