I feel this happens to everyone. Buy a PC, be happy that it’s better than what it replaces, then after a few years get annoyed that’s slow.
This happened to me with my now 6/7 year old Ryzen 5 1600x. It was so much faster then my FX 6100, but my workload changed, and while multicore it’s good, single core leaves much to be desired, especially since my CAD software of choice FreeCAD is very dependent on single core/thread performance.
So I’ve been keeping an eye on the markets, waiting for a deal to be had, and I found one, with the Ryzen 5 5500 going into my budget. So I bought it thinking that my old Gigabyte B350M Motherboard would support it. I mean Gigabyte says it’s supported and they’ve never lied about anything before… let alone deny by rebate claim for my laptop.
So I installed the CPU, booted it up, and boot loop. So I took out a stick of ram and it posted, was planning on fixing that later. Configured my BIOS to my liking, saved and restarted into my OS. It booted, for 3 seconds, then promptly black screened and crashed. Not even the power and reset buttons worked, so I had to hard kill it.
OK Troubleshooting time. Check BIOS version. 52h, hummm looks good but there is a 53, lets install that. And a reboot after, no fix.
OK let ask Google, within the dozens of responses asking for BIOS version, there was reseating the RAM. That did nothing, and underclocking the CPU to 3000MHz. That shockingly worked, and I booted into my OS. Neat, I can troubleshoot that later.
Now let’s install my other stick of RAM and lets get to fixing this sucker… and it’s boot looping again. I’ve reset the CMOS, put both sticks of RAM into all slot configurations, and nothing.
So I re-installed my 1600x to sanity check myself, and it worked, with both RAM installed. So back to Canada Computers I went to get a refund. While I was tempted by the Intel CPU’s on the way out, I got new thermal paste and now I am writing this post on my PC with the 1600x.
Lessons I learned today.
-
If you are upgrading a 1000 series Ryzen stick with the 3000 series as 5000 compatibility is dodgy depending on the manufacturer.
-
The Manufacturers can and will lie about compatibility, and hardware upgradability is hit or miss depending on the Motherboard.
-
I’m not buying from Gigabyte ever again. Though I’ve heard Asus isn’t much better.
Now PLEASE NOTE BEFORE COMMENTING. I do not have the 5500 and will not go back and get it again, so no troubleshooting, please. I just wanted to share my experience and kind of warn those who plan on doing the same.
You must log in or register to comment.
How did you know the CPU wasn’t the problem? Sometimes CPUs have defects. Especially given the underclocking seemed to help.
Mostly a guess as to prove it is outside of my reach. The CPU was new out of the box, and there are a lot of reports from Reddit, and other tech forums about Gigabyte B350M boards having issues with Ryzen 5000. I forgot where I this tidbit came from, but from my understanding, Ryzen 5000 has a larger instruction set, which first gen Ryzen Motherboard BIOS Storage didn’t have the space for. Some boards would loose functionality for Ryzen 1000 if they wanted to use Ryzen 5000.
So I feel it’s a safe assumption that at least with my board it probably was an issue. Wasn’t going to dig deeper when my 1600x still worked and I was within the 15 return period.
That’s fair. It’s an all-around sucky situation regardless, and it makes sense why AMD isn’t marketing socket longevity quite as much in AM5 as they were with AM4.
I do think losing capabilities for older CPUs in favor of new ones is pretty common for long lived sockets, and is an acceptable tradeoff for longevity imo. The board I was originally using for a 2600X never promised 5000 series support, but almost added it anyways. Unfortunately it never got beyond a beta bios, and I decided that wasn’t good enough for me (and I ended up giving the old mobo to my sister in a build for them, so it all worked out anyways).
Man, if it were me, I’d probably bit the bullet and bought a new motherboard instead of returning the processor. With my luck, I’ll probably run into some issues with the ram sticks and bought some new ones. Heck, maybe I’ll run into some issues with the old gpu and buy a new one too! Then the psu would probably need to be upgraded to power the new gpu. The temperature would probably kinda hot so the case must be replaced with new one with better cooling. Heck, now the monitor is too shitty for the hardware and need to be replaced with a new one with hdr and high refresh rate. Then the mouse would suddenly died and need to buy a new one too.
I too considered that, but as I have been unlucky I’ll probably run into an issue where the power from the wall was bad and I would need to buy a new house, I felt it was safer to keep the original CPU, since it still worked.
Well I’ll be. I have the same board and the same 1600x right now. Also built around 2016 or so, if memory serves.
Not a big fan of the board, I gotta say. It’s given me lots of trouble by being finicky with the ram. Had to add a touch of voltage, loosen the timing a hair, and run it around 100mhz slower than the ram was rated for stability. Lotta hours to diagnose and verify it wasn’t one of my 4 ram sticks that was faulty, since it could go a week without crashing and running memtest stuff would normally take 12+ hours to show any errors at all.
Always a good idea to check what bios version a board requires for what processor you plan on sticking in it, and to look through all bios update notes for required updates to move up to other updates and sometimes there’s stopping points, like “for 1600x, stop here, or don’t update beyond”
It’s given me lots of trouble by being finicky with the ram.
And OP’s problem sounds exactly like a RAM problem. I had problems with RAM on my Gigabyte B550 board, and if it wasn’t RAM instability (XMP didn’t work, had to manually overclock), boosting RAM voltage too high would cause the CPU temp sensor to wash out with voltage and lock on whatever temp it last detected.
Temp sensor issue aside, which might have been a peculiarity with the ITX board specifically or the 5600G I was using, there’s several different settings between Infinity Fabric speed, locking or unlocking it to match RAM clocks, the RAM speeds themselves, etc., all of which can cause boot loops and crashes if set incorrectly (for the hardware stack).
Personally, I suspect voltage inconsistencies going to the ram ports, that change a bit depending on how many sticks you’re using.
