AM5 boot times improve RADICALLY with memory context restore enabled

[LethaR]

Just wanted to post my results when enabling memory context restore in a msi b650m project zero motherboard, ryzen 9 7900x and 64gb 6400mhz cl32 ram.
Went from (not even lying) over 260 seconds of boot time to literally 10.9 seconds on my first boot after letting the pc train the enabled feature. Im blown away by the difference. Windows is stable for now, no blue screens and shit. I'll post here if something goes wrong, but, for now, i encourage and recommend any am5 and over 32gb of ram of 6000mhz or more with pretty slow boot times user to try this.

 

[wheresmycar]

A friend of mine had his MSI tomahawk + 7800X3D (mem 6000/30) taking around 4mins to load up. We did the same... CMOS HR, BIOS update to the latest patch and then "enabled" memory context restore. End result: 4 mins reduced to 17 seconds. Since enabling, no issues encountered.

 

[Space Lynx]

@W1zzard Do you know of any logic/reason why this would not have been enabled by default by AMD through a BIOS update in the AGESA releases? Or by motherboard manufacturers in general?

What are we missing here? I feel like Lisa Su is smart enough to not make people have long boots if she didn't have to.

 

[R-T-B]

@W1zzard Do you know of any logic/reason why this would not have been enabled by default by AMD through a BIOS update in the AGESA releases? Or by motherboard manufacturers in general?

What are we missing here? I feel like Lisa Su is smart enough to not make people have long boots if she didn't have to.

Memory PowerDown Disable breaks it for starters.

 

[ir_cow]

I would just update the BIOS for faster boot times. Context Restore is iffy. Might be good for a week, maybe a day or a month. Last I tried with AGEAS PI 1.1.0.2b and it crashed after leaving it In sleep mode. But it probably was because of PowerDown Mode. Its on by default.

 

[Fokker]

Absolutely. Last AM5 I built went from "Maybe I'll boot in 5 minutes," to 10 seconds from power on.

 

[Space Lynx]

Well AsRock has the best boot times around, I don't mind waiting 30-45 seconds for a proper boot, so I am going to leave everything default with an updated BIOS.

 

[ir_cow]

For single rank, I'm down to 20ish seconds (into windows) Dual-rank 6400 in 1:1 still takes 90 seconds.

 

[Space Lynx]

For single rank, I'm down to 20ish seconds (into windows) Dual-rank 6400 in 1:1 still takes 90 seconds.

I haven't actually timed mine yet. I will do so and update with results this weekend, bookmarking this thread now ^^

 

[Panther_Seraphin]

I should test mine as I am probably worst case scenario. All DIMMs populated......

A test incoming this weekend

 

[lolek86]

People still think Memory context restore and Power down are causing problems? I works flawlessly an is enabled by default since july of last year. Enabled and combined with fast boot gives me 9.5seconds boot time here on asus b650 motherbord and 32gig of tuned memory 7Gig pcie nvme drive. You can decrease it by another few seconds if you disable sata drives self check on post.

For those testing, shortest boot time will be achieved few reboots after enabling it for first time. First boot will be still 30-something seconds

 

[R-T-B]

People still think Memory context restore and Power down are causing problems?

Factually, I tried it with latest AGESA on my board just yesterday. Disable PowerDown and enable MCR and you will have memory corruption bsods on reboot in literally less than a minute, sometimes even in bios trying to change it back you'll get freezes.

As for the "why?" question, Powerdown slightly increases latency.

@ir_cow, our memory reviewer, confirmed my findings as well.

 

[lolek86]

In that case yes it will end up with corruption. Well, its well known fact that you don't disable power down if enabling memory context restore. those two features works together, even was confirmed by amd employee on reddit long time ago.

 

[W1zzard]

@W1zzard Do you know of any logic/reason why this would not have been enabled by default by AMD through a BIOS update in the AGESA releases? Or by motherboard manufacturers in general?

Last I turned it on I was getting random bluescreens in Windows and didn't know why

 

[ir_cow]

@ir_cow, our memory reviewer, confirmed my findings as well.

I tried this with multiple motherboards too. I personally don't think content restore has ever been fully stable. For me it will be fine for a day or so and than BSOD. Can't blame anything else either. Voltages are locked, same memory config, etc.


Edit: I forgot you had me try with PowerDown off. I remember now. Same results.

Last I turned it on I was getting random bluescreens in Windows and didn't know why

Yep me too

 

[Space Lynx]

yep, thanks

I will just stick to what I am doing cause it works and is stable, EXPO, negative offset for CPU, and that's only changes I make in BIOS, reboot done. rock solid stable 24.7 and still quick boot times.

MSI screwed up with AM5, AsRock imo is the king of AM5 platform, just very optimized.

 

[ir_cow]

MSI screwed up with AM5, AsRock imo is the king of AM5 platform, just very optimized.

How so? Asrock, ASUS, Gigabyte and MSI all have good MBs.

 

[tabascosauz]

I tried this with multiple motherboards too. I personally don't think content restore has ever been fully stable. For me it will be fine for a day or so and than BSOD. Can't blame anything else either. Voltages are locked, same memory config, etc.


Edit: I forgot you had me try with PowerDown off. I remember now. Same results.

Yep me too

Been running for a while now with zero issues with MCR. But it is allergic to Powerdown Off.

Either MCR On with Powerdown On
Or MCR Off with Powerdown Off

Boot time is long enough that honestly MCR Off is kinda unworkable depending on what you do with the PC

 

[R-T-B]

In that case yes it will end up with corruption. Well, its well known fact that you don't disable power down if enabling memory context restore. those two features works together, even was confirmed by amd employee on reddit long time ago.

Why on earth should they require each other?

 

[AsRock]

@W1zzard Do you know of any logic/reason why this would not have been enabled by default by AMD through a BIOS update in the AGESA releases? Or by motherboard manufacturers in general?

What are we missing here? I feel like Lisa Su is smart enough to not make people have long boots if she didn't have to.

Yeah mines enabled by default, how ever after a bios update i leave it on for a few reboots and turn it off.

 

[tabascosauz]

Why on earth should they require each other?

Who knows? All I know is that not respecting the rule regarding the two is a one-way street to crashes/reboots/BSODs.

I will say though, MCR doesn't like borderline stability/instability on either the memory controller or RAM itself. Best save it for when UCLK and RAM are both tested stable

 

[Space Lynx]

How so? Asrock, ASUS, Gigabyte and MSI all have good MBs.

he said boots were taking 4 minutes long on his MSI board.

no AsRock board even took 1 minute even in the beginning to my knowledge. and I showed the graph a few days ago showing the ASRock b650m doing a boot in 16 seconds and it didn't need that fix to do it.

 

[Deleted member 223428]

he said boots were taking 4 minutes long on his MSI board.

no AsRock board even took 1 minute even in the beginning to my knowledge. and I showed the graph a few days ago showing the ASRock b650m doing a boot in 16 seconds and it didn't need that fix to do it.

I think you forgot the ASRock memory slot sticker at AM5 launch.

 

[Space Lynx]

I think you forgot the ASRock memory slot sticker at AM5 launch.

View attachment 346791

1m 40 seconds is still heck of a lot faster than the 4 mins the MSI guy was talking about in this thread.

 

[Fokker]

he said boots were taking 4 minutes long on his MSI board.

no AsRock board even took 1 minute even in the beginning to my knowledge. and I showed the graph a few days ago showing the ASRock b650m doing a boot in 16 seconds and it didn't need that fix to do it.

I was dealing with an MSI B650 Tomahawk with latest BIOS. Enabling MCR sorted the RAM testing/training cycle issues after a stable boot. At least three dozen boots with zero issues before delivering to the customer. They've not reported any issues and this was handed to them months ago.