Upgrade Intel Core i5 12400F DDR4 to AMD Ryzen R5 7600 DDR5 – Worth It?

Intel’s Core i5 12400F was and still is a capable budget gaming CPU. When I bought this chip at the end of summer 2022, DDR5 memory was still costly, and the benefit in gaming was not worth the price by a long shot. In 2023, Intel’s 13th-gen CPUs benefit significantly from faster memory, and DDR5 prices have reached their equilibrium where DDR4 was last year. I could have taken advantage of slotting in a Core-13000 model, maybe even a 14000 variant, but I am too much of a tech enthusiast to ignore the performance I could be leaving on the table with DDR4.

As you will see, I probably would not have noticed the difference and potentially benefitted the one game that triggered the upgrade thoughts. I recently took advantage of AMD’s Starfield bundles and received a new GPU with my game purchase. I knew of all the discussion around this game’s performance profile. Intel owns this game despite it being an AMD-sponsored title. Nevertheless, the 12400 had issues in the CPU-heavy areas, like New Atlantis.

(It appears that AMD or Bethesda forgot that AMD also makes CPUs, which is baffling since AMD makes the Xbox chips and Xbox owns Bethesda…)

Anyway.

The Ryzen 7600 should walk all over the 12400 with DDR4. The Intel chip is roughly equivalent to a Ryzen R5 5600X, and compared to that processor, the R5 7600 is 30% faster in games on average, according to Hardware Unboxed’s testing published on Techspot.

I performed several gaming benchmarks that compare the i5 12400F to the R5 7600 when paired with a Radeon RX 7900 XT.

Read More »

MSI B650 Tomahawk EZ Debug LED Memory and CPU Issues – Early Adopter Woes One Year Later

I have recently treated myself to an AM5 system on an MSI B650 Tomahawk WIFI. The R5 7600 has access to 32 GB of G.Skill 6000 MT/s CL32 memory, which supports AMD’s EXPO technology. Enabling EXPO worked fine for the first hour before the trouble began.

At first, the SSD wasn’t detected anymore. I wanted to reinstall Windows because of licensing issues since I chose the wrong edition at first. Then, changing settings in BIOS did not restart the computer. The BIOS just froze up. Finally, the CPU and memory EZ Debug LEDs were both active, indicating a fried CPU and RAM.

That was a fun experience.

The Debugging

For reference, here is the layout of the debugging LEDs.

I am showing you this because the image of the error was under bad lighting conditions.

Whatever I tried, the system appeared to be dead. No more BIOS, no CMOS reset, nada. A CMOS reset had no effect even when the system would still boot into BIOS. Cutting the power… you guessed it: did nothing.

In a last hurrah, I attempted to boot with only one memory stick installed. Maybe it was just a single DIMM that unleashed hell. Lo and behold, the system booted. Testing the other stick also booted. Trying both RAM sticks again also booted. What the devil?

Changing the RAM configuration from two sticks down to one triggered something in the BIOS to reconfigure itself. A BIOS often shows a message when changes to the previously installed hardware are detected. And suddenly, a BIOS reset also worked.

The Fix

This time, I ran the RAM at 4800 MT/s while I installed Windows and tested a game for good measure. After ensuring the system was stable, I dared to perform a BIOS update.

And this was the solution to the problem. My MSI B650 Tomahawk came with BIOS version E7D75AMS.160; the latest version is E7D75AMS.170. The changelog mentions several improvements regarding RAM support.

An unreleased beta version also mentions stability improvements with EXPO enabled. I assume this also made its way into the latest release.

Since then, the system has been stable. I have run several benchmarks and played Starfield for about four hours straight without any stability problems.

The Disappointment

I am shocked that users can still run into compatibility issues like this about a year after the release of the Ryzen 7000 processors. The original installed BIOS was published in May 2023. That was already about eight months after the release of the AM5 platform, and it still had issues.

I hope this was helpful and saved you some time debugging a similar issue on the same motherboard or even a different one that behaves the same.

Thank you for reading.