Question NOTHING happens when trying to start a DIY build

vmk

Jul 23, 2023
2
0
10
It's been a while since I've done it last, but I decided that I wanted to do a DIY build of my next computer. I am NOT afraid
about mucking around with the innards of desktops, having replaced video cards, CPUs, memory, disks, etc in the past.

I decided on high-end, but NOT top-of-the-line, components which consisted of:
AMD AM5 7 series CPU
ASRock X670E PG Lightning Motherboard
32 Gig G-Skill Memory (2 X 16)
Intel ARC A770 video card (16 Gig)
1 Gig SSD (for boot and programs), 14 Gig HDD (for mass storage and local backup)
Arctic Liquid Freezer II 240 A-RGB
Super Flowr 1200 W Platinum power supply
Corsair 4000D Airflow case

Got all the components and put it together. Everything in place and hit the power button and....NOTHING!
No POST, no beeps, no burning smell, no fans spinning, no lights, just NADA. No matter what I did with Power and Reset buttons

Checked the obvious. Different power cord. Checked turned on the power supply. Checked the Power and Reset wires (why so tiny
and hard to work with in a bad location?!). Checked the connections from the power supply (the 24? pin) ATX Power Connector
(ATXPWR1). Checked the 8 Pin 12 V (ATX12V1). All seem to be connected and seated correctly. Video card and memory chips
seated properly.

OK. With nothing going, got a replacement power supply (figured the most obvious point of failture), but same thing. Bit the
bullet and undid everything and replaced the motherboard. That HAS to be it, right? NOPE!

I tried using a jumper across the power connection (damn, so hard to work with it! so easy to pull out one when trying to
put in another, but they are all seated well). Same.

I'm now at a loss! Anything obvious I missed or should check again? Suggestions? HELP! Since I currently have aroud $1400
of an oversized paper weight! Really frustrating, because I was jazzed about putting together my desktop for the forseeable
future (somewhat "future-proofed").

What did I miss? What did I do wrong? (At this point, I HAVE to assume some STUPID on my part "user error" since whatever
I did wrong, I did it wrong TWICE (since I started all over again with the replacement of the motherboard, which in
retrospect, probably was NOT the problem).
 
As always, start here:

Go through ALL the steps.
Don't assume...touch and verify.
 
I appreciate the reply and I'm not being contrarian, BUT:

I might not follow the advice in order, but I believe I did (and/or checked) the trouble shooting list (or kinda
silly to assume I made the same mistake with two separate constructs, since I re-did with another mo-bo).

1) yes, I followed the user manual
2) I used the 8 pin CPU power plug (I didn't use the 4 pin, since they said only needed if intend to major overclock
(and the motherboard didn't come through with any 4 pin or "split" 8 pin cables)
3) the Corsair 4000 comes with build-in standoffs, don't need to install anything -- so says their manual
4) two plugs to the Intel ARC A770
5) haven't tried removing a memory stick, but I did check they are both seated correctly and checked which slots I used
6) I did remove the CPU cover and also from the cooler
7) I put the CPU in the correct direction and was careful with thermal paste (and I COULDN'T make the same mistake twice,
since I started from scratch with the 2nd mo-bo)
8) didn't do anything special about static discharge, but c'mon
9) no loose screws (besides, TWICE, with the 2nd mo-bo?)
10) there is no LED display, but no beep codes
11) don't have a system speaker (I think).
12) I made a mistake once about the power and reset wires, but corrected (AWFUL location, hard to work on, easy to pull
one out while trying to connect another -- why so small? why so close together?)
13) connected PSU direct to wall socket, tried another power cord -- the PSU IS on the on (I) position
14) removing CMOS battery doesn't make much sense -- TWO mo-bos, BOTH with bad batteries?!

I DID order a computer speaker. For $4, worth a shot to make hear some beeps (if they exist). I'll give a follow-up, but I'm at the point of thinking MAYBE a bad CPU? (But I'll TRIPLE all the above).