Question I may be building a new system soon, but not "cutting edge"

[jose]

I've been building systems since the 486DX days,, Used Intel almost exclusively for both myself and my customers. But if I had to build a new high end workstation, I'd use the 7800x3d w/ 64 gigs of CL30 ram. on an x870E based mobo w/ a thermalright phantom spirit 120 se cooler. I just built in Jan. a HTPC for my son w/ a i5 13600kf and wish I had paid more attention to the 13/14th gen problems. I did build an AMD Athlon system once but switched back to Intel. Nothing was wrong w/ the system , just wanted to stay w/ Intel + nvidia. I would not invest in a 12 gen cpu while there's a great alternative available.. 7800x3d + 4080 .

 

[igor_kavinski]

I just built in Jan. a HTPC for my son w/ a i5 13600kf and wish I had paid more attention to the 13/14th gen problems.

Flash the microcode 0x129 BIOS update and the 13600KF should be fine.

 

[BoomerD]

Flash the microcode 0x129 BIOS update and the 13600KF should be fine.

The last MSI BIOS update for my board updated the Microcode 0x125.
The most current BIOS updates the Microcode 0x129.
I'm running the i5-13600K with no problems so far. <knock on wood>

 

[igor_kavinski]

I'm running the i5-13600K with no problems so far. <knock on wood>

Just be warned that the Dell i5-12500 that I updated to 0x129, is now going to a black Windows screen where only the mouse pointer is visible. I don't know if it's a borked Windows update or something to do with the microcode where it corrupted something important in Windows and preventing it from loading to desktop. If you have the same issue sooner or later, it could be the microcode (but for now, rest easy).

 

[BoomerD]

Just be warned that the Dell i5-12500 that I updated to 0x129, is now going to a black Windows screen where only the mouse pointer is visible. I don't know if it's a borked Windows update or something to do with the microcode where it corrupted something important in Windows and preventing it from loading to desktop. If you have the same issue sooner or later, it could be the microcode (but for now, rest easy).

So far...no problems...so far.