cancel
Showing results for 
Search instead for 
Did you mean: 

Asus X670E boot time too long

jordanKills
Level 8
Hi,

I am have an issue where my boot up time for my new PC is very slow. i know that the first time boot up when i built the PC is long but this is getting ridiculas. My old PC would start up in half the time. i have the following install:

MOBO; Asus crosshair x670E
CPU; AMD 7050x
RAM; G.Skill 32gb @ 6000: 2x 16gb
GPU; EVGA 3090ti
OS: Windows 11 home
7,354 Views
39 REPLIES 39

Hello,

Context Restore retains the last successful POST. POST time depends on the memory parameters and configuration.

It is important to note that settings pertaining to memory training should not be altered until the margin for system stability has been appropriately established.

The disparity between what is electrically valid in terms of signal margin and what is stable within an OS can be significant depending on the platform and level of overclock applied. If we apply options such as Fast Boot and Context Restore and the signal margin for error is somewhat conditional, changes in temperature or circuit drift can impact how valid the conditions are within our defined timing window.

Whilst POST times with certain memory configurations are long, these things are not there to irritate us and serve a valid purpose 🙂

 

 

 

13900KS / 8000 CAS36 / ROG APEX Z790 / ROG TUF RTX 4090

If memory training is recommended for every POST (as opposed to using Context Restore), what about waking your system out of sleep - could there be any deviations from the system parameters before putting it to sleep that could cause instability after waking it up? (I suppose that many people would prefer to put their system to sleep instead of rebooting it to avoid long POST times.)

Putting the system into S3 Resume is a perfectly acceptable remedy if finding POST / Boot times too long.


It's also a good method to check stability in terms of memory refresh (tREFI) when an overclock is applied.

13900KS / 8000 CAS36 / ROG APEX Z790 / ROG TUF RTX 4090

Thanks for the tip...

It's not just the delay itself that is irritating, it's that the fact that the UEFI doesn't tell you what it's doing...

I remember way back in the stone age when I chiselled my first PC the AMD BIOS always did a Ramtest on boot-up, but:

a) It told you it was doing it, and:

b) it didn't take long.

It's the not knowing that's the problem.

You'd have thought that computers would have got less dumb and more helpful over the years - it strikes me that the reverse is true...

Now to enable that Context Restore setting...

This setting is still there, I changed mine from Auto to Enabled, and WOW it booted fast after the initial boot.  I am assuming it skips the "memory training" portion of the boot cycle - so far no issues.  If your not changing RAM sticks or CPU or anyting else major, I can't see where it needs to re-test the memory on EVERY boot. Seems like a bad design to me, unless there is evidence otherwise I am missing.

In either case, thanks for pointing this out.  The ridiculous boot times have been getting to me, since I bought my system at lauch.

Crosshair x670 Hero, 7950X, 32 GB Gskil Neo 32. (2x16)

There are 2 context restore options (one of them is very well hidden), and both of them have to be enabled.

I have the exact same build as the OP, and this makes indeed a HUGE difference, particularly if you have the memory OC'ed (mine is 6000mhz), and even with it, it takes 40 secs from power button to windows desktop screen from which 5 seconds are the Windows "waiting" screen (loading).

Had several issues with this board, I know it has defects - had to disable sleep/hibernate because of random crashes recovering from sleep, and USB4 which is not working and was adding a 10 secs timeout to the boot time.

Not sure if my board issues are also impacting on my 40 sec boot time, but I'm pretty sure it is. Anyone with same board/cpu can you please share your boot time?

UPDATE: from what I've read from other people, looks like 35 seconds from power button to windows login is considered "normal", even if it feels way too much for a modern high end PC.

Other than the sleep/hibernate and USB4 not working properly, everything else is fine.

NOTE: I've updated the bios to 1602, didn't see any change, but I didn't feel like testing the sleep/hybernate again because I'm pretty sure it's an hardware defect, and I don't wanna get frustrated over it again.

 

I upgraded the M.2_1 to Gen5 Firecuda 540 and it never booted. Twice. I was in the early stages of WTF?

Thanks, back to installing Windows/////

I went back and changed it back to AUTO after I installed windows and drivers, and it booted normally and quickly.