[SOLVED] PC wont boot on first startup after shutdown. Needs to be turned off and on again to boot correctly.

Status
Not open for further replies.
Dec 27, 2021
16
0
20
Recently I've been experiencing this issue that did not happen at all before and is pretty random. After shutting down my computer when I go to start it up again everything turns on in the computer but it will not boot, giving either the EZ debug LED for the CPU or DRAM. In order for it to boot I have to hold the power button or turn off the power supply and then start it up again and it works fine. I have 0 issues outside of this though, and I run pretty intensive programs regularly on it. I have already cleared the CMOS which seemed to fix the issue for 1 day but its back to doing it again. This is a somewhat minor inconvenience but I would like to resolve it if possible.
 
Solution
if you weren't on win 11 I would suggest turning fast startup off. It should be off now by default.

Worth looking I guess.
Search for control panel
change view to large icons
pick power options
pick Choose what power button does
If there is a tick next to Turn on fast startup,
click the link next to the shield that says Change settings that are currently unavailable
now untick Fast startup and save changes

it is meant to be off by default in win 11. especially on PC with ssd/nvme. You don't need it.
which motherboard? might help figure out cause.

is the 32gb of ram a set or did you just add more ram? Did you have this problem before changing ram?
I'm not entirely sure if i had the problem before changing the ram or not, but i did buy the same kit of 16gb that i previously had and just added it in. Verified at the store with the boxes to make sure it was the same one. I have the MSI MPG B550 Gaming edge wifi mobo.
 
So do you have 4 sticks now? 4 x 8gb?

sticks in sets tested to work with each other, not other sets. So its possible the extra ram is reason for strange boots. Even if they same boxes, its not a guarantee they same ram. Some ram makers use different memory makers, even on the same family of sticks. Corsair can be Micron or Samsung, for instance.

what sticks are they?

Ryzen CPU picky about ram. More so than Intel.
 
You don't have to do it right now... its your problem, take your time. DO it when you have time :)

the more sticks you add that don't match, the more chance of errors. It might work fine with 3 but 4 is too many.

Are the sticks in XMP? could try running stock speeds and see if that helps.
 
Are the sticks in XMP? could try running stock speeds and see if that helps.
You know i think it might be that because after i reset the CMOS it disabled XMP, which i then reenabled and it seemed to start again after that. I can try without XMP but i seem to recall getting significantly lower FPS when it was running without XMP enabled.
 
if you weren't on win 11 I would suggest turning fast startup off. It should be off now by default.

Worth looking I guess.
Search for control panel
change view to large icons
pick power options
pick Choose what power button does
If there is a tick next to Turn on fast startup,
click the link next to the shield that says Change settings that are currently unavailable
now untick Fast startup and save changes

it is meant to be off by default in win 11. especially on PC with ssd/nvme. You don't need it.
 
Solution
its meant to speed up boot but on a nvme you are so fast it makes no difference. Its more for hdd where any little bit helps to make it look faster. A nvme running at 3500mbs is fast enough to load all drivers from scratch at start.

I have A 970 Evo plus, I turned it off on win 10 for same reason.

Another difference is it changes shut-down. PC with fast start-up on isn't off when you shut it down, its in a hybrid hibernate. It can mess with old drivers not written for mode.
If you have fast start up off, PC is actually off at shut-down
handy if you need to unplug PC after.
 
Problem solved by disabling Memory Fast Boot in the bios and then manually setting the speed to DDR4-3600. Thanks for the advice, turns out it was partially XMP's fault
 
Status
Not open for further replies.