Device Fails to Start Following Assembly Process!
Device Fails to Start Following Assembly Process!
I began assembling a PC today using refurbished components. I acquired a new motherboard and CPU cooler. I followed the standard process: install CPU first, apply thermal paste, fit the cooler, then mount the motherboard. After that, I connected power via the 24-pin ATX and 8-pin 12VATX connectors (the PSU was already installed). I placed the RAM correctly and connected the PWR_SWC according to the manual. When I turned on the system, nothing happened. I tried reattaching everything, reset the CMOS battery, and even touched the power button pins. After some testing, I managed to power it up by touching the motherboard’s power connector, which then lit the LEDs. Later, I discovered the RAM wasn’t the issue—it was that the 24-pin plug was only halfway in, feeding just fans and LEDs. Once fully connected, the computer shut down.
My specs: Motherboard – ASRock B450M Pro4 R2.0 (new), CPU – Ryzen 5 3600 OEM (used), GPU – Gigabyte WindForce GTX 1660 Super (used), PSU – Corsair CX500M Semi-Modular (used), Cooler – AMD Wraith Stealth (new, bought separately), RAM – Kingston 2x8GB 1Rx8 PC4-2400T-U KM0VW4 DDR4-2400 PC4-19200 UDIMM (used), Case – AeroCool Bolt (new with built-in fan), Fans – EZDIY-Fab Dual-Ring 120mm RGB 5-pack (new).
I faced several hiccups: no response after power-up, failed attempts to jump the board, and a display failure. After troubleshooting, I realized the RAM wasn’t the culprit—it was the partially connected 24-pin plug feeding only fans and LEDs. Once it was fully secured, the system started again.
I also tried installing a GPU and connecting an HDMI monitor post-power-on, but no display appeared. All CPU fans kept clicking. Placing the LED bar on the case caused flickering along with the fan noise. I’m still unsure where to begin; this is quite confusing.
Unfortunately, there are a few things this could be. First thing that springs to mind is the front panel I/O header wiring. This is an easy mistake, and an easy fix. A PSU with weak capacitors could cause hard starts like this. If you aren't aware, capacitors store current for startup surge loads, and if the capacitors are flaky, they can discharge when the machine is off, which can cause startup issues like this. ADDED: Also, did the cables come with this PSU? I'm not sure why, but mixing and matching cables between PSUs is getting to be a big no-no, and has been known to fry the occasional board. In addition, Ryzens are quite fussy about RAM, so it's generally not a good idea to just throw a Ryzen build together out of used parts without verifying their compatibility (and yes, this actually is a thing with Ryzen). Even more unfortunately, ASRock didn't see fit to draft a QVL list for Matisse processors (the 3600 falls into this family) with this board. Though I wouldn't assume anything, Renoir and Matisse are both Zen 2. So in the absence of a proper one for Matisse, in the hopes they are the same in this regard, here is the QVL list for Renoir architecture . If the RAM SKU is not on the list, it doesn't mean that it WON'T work, but it doesn't mean that it WILL, either. And this can cause all manner of problems, no video starts, crashes, you name it. I chased my tail for five months chasing problems that installing a QVL-recommended RAM kit stopped dead cold. On two separate builds, I might add. Another possibility is that the board may have a BIOS version that simply does not support Zen 2. Not likely, as the site indicates 3600 is supported by all BIOS revisions applicable to this board, but let's say the board was previously flashed with the wrong BIOS, a BIOS for a different board, or a beta BIOS from which Zen 2 support had been stripped? This happened with MSI recently, on a B450M Tomahawk if memory serves. It apparently caused problems quickly enough it was rescinded and removed from MSI's site within a couple months of release. Apparently a few boards shipped with it. Edited October 20, 2022 by An0maly_76 Revised, more info
Just jump the ps_on (16) with any ground pin and that will force the PC. This shouldn't cause any harm—it just powers the system on. Before doing that, I recommend gently moving the 24 pin; sometimes that can trigger the PC to turn on. I'm not sure if it's a bad short detection issue, but it might help. Also, I'm pretty sure RAM won't stop the PC from starting at all—at the very least, it will attempt to boot.
RAM hasn't always been the root of every Ryzen issue, though it's definitely a factor that could play a role or not. I recently assisted someone with a similar situation. The RAM wasn't fully loaded and the part number didn't match any supported options. I'm searching for details about the part number now. It's frustrating that ASRock didn't provide a proper QVL for Matisse, and I'm hoping Renoir offers comparable RAM support as Zen 2. However, the current installation doesn't align closely with the 2400 Kingston kit listed in the Renoir QVL (KVR24N17S8/8). Updated October 20, 2022 by An0maly_76 Added more info
RAM mismatch doesn't always stop the system from starting properly. It may begin but then freeze or become stuck.
On page 22, the design for the DIMM slots is displayed. The section covering Matisse processors does not include an entry for a 2400mhz RAM configuration.
Well, initially it was noted that with Ryzen, unlisted RAM isn't guaranteed to work reliably—it might function but could also cause instability. If it claims compatibility with the Matisse at 2400 MHz, sticking to what it explicitly supports is wise. However, I haven’t found a comprehensive manufacturer guide yet.
The key point came from Crucial: my original Ballistix units worked across all three boards they affected. I dismissed that claim since identical RAM kits caused the same problems in different builds. The problematic kit shared the same timings and voltage as the one that resolved it, but it wasn’t listed on QVL. This shows that board compatibility doesn’t always mean any RAM will fit, even if it claims support.
I’ve generally avoided deviating from QVL with Ryzen because issues often stem from mismatched speeds, timings, and voltages—even with dual-rank kits. The Patriot Viper seems promising, but I’m hopeful they’ll release a compatible set for your 3600. Dual-rank RAM appears to work better in theory, though it’s not a universal fix.
As long as you double-check the SKU or part number and match the board’s recommended settings, you should be able to run it smoothly. Just remember to verify DOCP timings if they differ from what the board specifies.
The CPU installation went wrong. I tried to set it up carefully at first, but now I’m facing another issue. Once everything is connected—including case fans, power connectors, RAM modules (installed in A1 and B1 with 8GB each), power cables, M.2 SSD, and a 1TB HDD—the computer powers on and all fans spin, including the GPU fans. I’ve secured the RAM firmly, used the 8-pin PCIe plug for the GPU, and made sure everything is snapped in place. There’s no display from the GPU, and it restarts every 20 seconds. Since this board lacks built-in lighting or a speaker, I can’t read error codes. I’m aware that RAM problems often cause these issues, so I’ve removed the RAM, cleaned the pins with an eraser, cleared out ports, and tested with single sticks in different slots—none worked.
This was among several problems I encountered when my board didn’t accept my RAM. It would freeze during sleep mode and not show any video after every 8-10 cold starts. The same happened on another board with matching DIMMs as well. Another member suggested it’s a memory-training issue triggered at startup, possibly due to a mismatched hardware setup. I also experienced a few random crashes. Only after returning the board for an RMA and swapping in new DIMMs did the issue become clear. However, since the CPU wasn’t installed properly initially, it’s hard to confirm without checking visually—there’s a chance the CPU might be damaged. I’d advise bringing it to a repair shop; testing it with another CPU or board would be wise. In some situations, a BIOS version problem could be the cause, but I’m less confident about that here. Edited October 21, 2022 by An0maly_76 Updated with more details