cancel
Showing results for 
Search instead for 
Did you mean: 

14900ks no post.

Spork72
Level 7

Z690 extreme with 14900ks showing code 00 on LCD and 98 on mobo LED

Upgraded from 12900ks which was working perfectly.

Updated bios to 3302, cleared CMOS.

Put 12900ks back in with same results. 

 

Maximus z690 extreme 

2x32 Corsair dominator platinum 5600mhz 

Strix 4090 

Dark power pro 13 1300w

394 Views
12 REPLIES 12

chappetiti
Level 7
Already tried because when I installed the 14900ks I was in bios 3101 and it already worked very poorly...

FixItWorse
Level 9

FYI, there's not a whole lot of overclocking left to do on a 14900KS, they've already pushed the thing pretty much as far as it can go, there's very little headroom left. Focus on getting stable at defaults.

I don't know this for certain, but I would assume that the required signal integrity for a 14900 is more strict than 12th Gen. If you're using an AIO, make sure it isn't too tight, you'd be surprised the difference that overtightening it can make, it can and does slightly flex the CPU and socket causing the types of issues you're talking about. Get it snug by hand only, not with a screwdriver, gradually in an x pattern.

I've seen Asus tighten up the signal integrity limits in UEFI updates before.

Anyway, food for thought.

Hisense U7G 55" 4K, HDR, 120hz w/FreeSync VRR Primary Display
Corsair 5000X Black iCue, ROG STRIX Z690-E GAMING WIFI w/ Intel 12700K, AIO Cooled by Corsair H150i Elite Capellix, Gigabyte Aorus Master RTX 3080 Ti, 64GB (4x16) Corsair Dominator Platinum @ XMP I, 4x 1TB WD850 Black NVMe, 2x on HyperCard in Raid 0, and 2x in M2.2 and M2.3 on Mobo.
SeaSonic TX1000W Platinum PSU, Corsair K70 RGB MK2 Wired Keyboard, Corsair M65 RGB Ultra Wired Mouse, Logitech Brio 4K w/Windows Hello Face. Windows 11 Home 23H2

I have tried all that. I have managed to get it to post, but then had troubles with it booting to windows and with even fresh install. 

The only way I could get it to boot OS was with turning turbo mode off and it running at 3.2ghz. Iv put it down to a faulty cpu