Where have I gone wrong?

[lashomb]

On my second iteration of trying to get a new pc build to work for my son. My prior experience building PCs is 10+ years old, back when SSD drives were still SATA. Never had issues like this before, but I’m trying to understand if I’m doing something obviously wrong, before I just return this all and go pre-built. It’s been close to a week with all this, and a few trips to MicroCenter.

Problem that has now persisted between two builds using different motherboards:
I get this working, Windows installed and booting, but then after shutting it down, I won’t be able to get it to boot back up again. Sometimes some combination of shorting the CMOS pins, or pulling the battery, or on the Gigabyte board pushing the reset_sw button, will sometimes bring it back. I’ve tried reseating RAM. After a few days in the first run with a ROG Strix board, I ended up returning it and picking up a Gigabyte board. But I’m hitting the same thing again. Currently the Gigabyte board shows a red LED light.

I haven’t overlocked anything, everything is stock bios settings.

 

Parts:

AMD 7600X3D
ASUS Rog Strix B650A ATX motherboard (First build)

Gigabyte B650 AORUS Elite AX motherboard (Second build)

Samsung 990 Pro M2 SSD

Corsair Vengence RGB DDR5 RAM

AsRock Steel Legend 9060 XT 16GB
PowerSpec 650W PSU
Artic Freezer 36 A-RGB CPU Cooler

Montech X5 case (First build)

NXZT H5 Flow case (Second build)


On both the ASUS and Gigabyte boards, I updated to the latest BIOs. Both booted into Windows and worked for a while, but in shutting them down and trying to boot back up, it will be ‘it’s not working again’. Then I’ll try reseating the RAM, resetting the CMOS, pulling the battery, and pressing the reset_sw button. I’m at a loss here as to where I’ve gone wrong. I should have good quality components here.


Thanks for taking a look.

[Dedayog]

2 minutes ago, lashomb said:

On my second iteration of trying to get a new pc build to work for my son. My prior experience building PCs is 10+ years old, back when SSD drives were still SATA. Never had issues like this before, but I’m trying to understand if I’m doing something obviously wrong, before I just return this all and go pre-built. It’s been close to a week with all this, and a few trips to MicroCenter.

Problem that has now persisted between two builds using different motherboards:
I get this working, Windows installed and booting, but then after shutting it down, I won’t be able to get it to boot back up again. Sometimes some combination of shorting the CMOS pins, or pulling the battery, or on the Gigabyte board pushing the reset_sw button, will sometimes bring it back. I’ve tried reseating RAM. After a few days in the first run with a ROG Strix board, I ended up returning it and picking up a Gigabyte board. But I’m hitting the same thing again. Currently the Gigabyte board shows a red led light.

I haven’t overlocked anything, everything is stock bios settings.

 

Parts:

AMD 7600X3D
ASUS Rog Strix B650A ATX motherboard (First build)

Gigabyte B650 AORUS Elite AX motherboard (Second build)

Samsung 990 Pro M2 SSD

Corsair Vengence RGB DDR5 RAM

AsRock Steel Legend 9060 XT 16GB
PowerSpec 650W PSU
Artic Freezer 36 A-RGB CPU Cooler

Montech X5 case (First build)

NXZT H5 Flow case (Second build)


On both the ASUS and Gigabyte boards, I updated to the latest BIOs. Both booted into Windows and worked for a while, but in shutting them down and trying to boot back up, it will be ‘it’s not working again’. Then I’ll try reseating the RAM, resetting the CMOS, pulling the battery, and pressing the reset_sw button. I’m at a loss here as to where I’ve gone wrong. I should have good quality components here.


Thanks for taking a look.

How long are you waiting when you reboot?  

 

DDR5 has memory training, and this can take minutes.

[lashomb]

Just now, Dedayog said:

How long are you waiting when you reboot?  

 

DDR5 has memory training, and this can take minutes.

I’ve waited 2-3 minutes, but probably not everytime… would the red LED still show if it was doing memory training?

[Dedayog]

1 minute ago, lashomb said:

I’ve waited 2-3 minutes, but probably not everytime… would the red LED still show if it was doing memory training?

I think so.  Give it another run, let it sit.  It's not a guarantee but memory training CAN take longer than you're letting it.

 

Its odd that you can get into Windows, and then the reboot won't.  So let's nix the memory training first.

[lashomb]

I’ve rebooted from Windows, and that’s fine. What usually happens is this PC was used yesterday, and shutdown (from Windows menu), and then today it wouldn’t boot. That also happened in the ROG Strix build.

[-rascal-]

The PSU seems to be a little suspect, especially when the system is fully "shut down."

Does this problem happen if you...instead use 'Sleep' instead of 'Shut Down'?

[lashomb]

If I get it to boot again, I’ll give that a try. Have let it sit for 10+ minutes now, so I’m guessing the RAM is probably done training?

[-rascal-]

7 minutes ago, lashomb said:

If I get it to boot again, I’ll give that a try. Have let it sit for 10+ minutes now, so I’m guessing the RAM is probably done training?

 

The FIRST time training, it may take a few minutes.

The subsequent times you fire the PC up, it should be faster and faster, as should start to just recall the last known settings.

 

What is the part number or model number of the Corsair memory kit?

Some Corsair memory kits don't play nice with AMD Ryzen systems...

 

Also, when you said  Red LED, is it one of these?

Cycling through them during P.O.S.T. is normal. If it gets STUCK on one, it means that part of the check has encountered an error.

[lashomb]

Ah, I didn’t not realize that was 4 indiividual lights… I zoomed in with my phone, and it’s DRAM that is red. Thank you!

[lashomb]

OK, I pulled the B2 stick of RAM, and it completed POST and booted. I’m not sure what this means though? Do I have a bad RAM stick?

[lashomb]

Replaced the removed stick with the one in the A2 slot, and it won’t post so that would be seem to be bad. Thanks all for the troubleshooting advice, I really appreciate it. I’ll return the pair in the morning (and may avoid Corsair).

[-rascal-]

30 minutes ago, lashomb said:

Ah, I didn’t not realize that was 4 indiividual lights… I zoomed in with my phone, and it’s DRAM that is red. Thank you!

 

27 minutes ago, lashomb said:

OK, I pulled the B2 stick of RAM, and it completed POST and booted. I’m not sure what this means though? Do I have a bad RAM stick?

 

Progress...

 

Again, what is the P/N or model of the Corsair Memory kit?

 

Which memory slots are you using?

I'm assuming 2x memory sticks, Gigabyte recommends that you fill slots A2 and B2 first.

[ CPU Socket] [A1] [A2] [B1] [B2]

 

 

 

 

You MAY  have a faulty stick of RAM. That can definitely cause symptoms such as P.O.S.T. or boot issues.

You can run a memory stability test and see if it encounters any errors.

 

Either one should catch immediate errors pretty quick...

• AIDA64 Stability Test -> select Memory
• OCCT Stability Test -> Memory
• MemTest86 - longer, more thorough

 

[lashomb]

9 minutes ago, -rascal- said:

 

 

Progress...

 

Again, what is the P/N or model of the Corsair Memory kit?

 

Which memory slots are you using?

I'm assuming 2x memory sticks, Gigabyte recommends that you fill slots A2 and B2 first.

[ CPU Socket] [A1] [A2] [B1] [B2]

 

 

 

 

You MAY  have a faulty stick of RAM. That can definitely cause symptoms just a P.O.S.T. or boot issues.

You can run a memory stability test and see if it encounters any errors.

 

Either one should catch immediate errors pretty quick...

• AIDA64 Stability Test -> select Memory
• OCCT Stability Test -> Memory
• MemTest86 - longer, more thorough

 

Definitely A2/B2 for both of my builds. I’m not sure how I would run that test software if the machine doesn’t POST with the RAM pair installed. My test was more basic, but the fact that it posts with one stick in A2 and not the other tells me something is up with that. And the fact that I’ve seen this happen now on the ROG Strix and Gigabyte boards tells me a swap is probably a good idea to rule that out. Thanks again for the detailed response.

[lashomb]

Final follow up here, replaced the Corsair Vengeance with TeamGroup Delta pair, and things are fine. Even enabled Expo.

 

For others that come across this, maybe with the same motherboard, RAM training wasn’t more than 30 seconds when I had a working pair.

[Dedayog]

2 minutes ago, lashomb said:

Final follow up here, replaced the Corsair Vengeance with TeamGroup Delta pair, and things are fine. Even enabled Expo.

 

For others that come across this, maybe with the same motherboard, RAM training wasn’t more than 30 seconds when I had a working pair.

I probably should have mentioned people had Corsair RAM issues when DDR5 first came out, all over the forums here.  Hadn't heard much lately, so hope this is just a manufacturing issue.

 

Glad you got it sorted.