Long AM5 POST times

[AusWolf]

No reason why it shouldn't have worked. Maybe you had a bad motherboard or the memory is at fault.

Its also possible things like High Memory Bandwidth, Low Latency or Context Restore was enabled. one or more of those are guarantee to give boot problems. I can't use Context Retore myself, just BSOD the computer.

This...

They won't be enabled unless you enable them. Return and get another one. Make sure to update the BIOS too.

And this. My motherboard was hot garbage with the factory BIOS, but MSi fixed most of the issues pretty soon. Now, it is a board that I can actually recommend (in my profile). No fuss, no fanciness, it just works.

 

[ir_cow]

After trying the newest AMD AGESA 1.1.0.2 b, I noticed 10 fps drop (low settings) in my benchmarks and 1500 points lost in 3DMark CPU test. Tried a bunch of different settings and ram, but it is still a permanent loss. Went back to AMD AGESA 1.0.7.c. Gained all the performance back.

While I like the sub 30 second boot now with 1.1.0.2 band DDR5-8000 support, the perf loss is a bit much.

Example: 5.2 GHz 7950X. 3DMark TimeSpy CPU Score. (1.0.7.c) 16777 vs (1.1.0.2 b) 14200

 

[Super Firm Tofu]

After trying the newest AMD AGESA 1.1.0.2 b, I noticed 10 fps drop (low settings) in my benchmarks and 1500 points lost in 3DMark CPU test. Tried a bunch of different settings and ram, but it is still a permanent loss. Went back to AMD AGESA 1.0.7.c. Gained all the performance back.

While I like the sub 30 second boot now with 1.1.0.2 band DDR5-8000 support, the perf loss is a bit much.

Example: 5.2 GHz 7950X. 3DMark TimeSpy CPU Score. (1.0.7.c) 16777 vs (1.1.0.2 b) 14200

*sigh*

I guess I'll stay on 1007c then. I've been putting off any updates and was going to finally do it this weekend, but with that type of regression, I'll take the security risks.

 

[ir_cow]

I haven't tried anything in between. It could just be the newest.

 

[AusWolf]

After trying the newest AMD AGESA 1.1.0.2 b, I noticed 10 fps drop (low settings) in my benchmarks and 1500 points lost in 3DMark CPU test. Tried a bunch of different settings and ram, but it is still a permanent loss. Went back to AMD AGESA 1.0.7.c. Gained all the performance back.

While I like the sub 30 second boot now with 1.1.0.2 band DDR5-8000 support, the perf loss is a bit much.

Example: 5.2 GHz 7950X. 3DMark TimeSpy CPU Score. (1.0.7.c) 16777 vs (1.1.0.2 b) 14200

That's weird. I didn't see anything chance with 1.1.0.2b on my system.

 

[danc]

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7005.html

Inception fix? I think you can disable that in bios

I do not notice 10% loss in AGESA 1.1.0.2 though i did not rebench too much. New AGESA allows higher FCLK though.

 

[AusWolf]

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7005.html

Inception fix? I think you can disable that in bios

I do not notice 10% loss in AGESA 1.1.0.2 though i did not rebench too much. New AGESA allows higher FCLK though.

I just ran Cinebench R23. No performance loss, 18k points, just like before.

 

[Launcestonian]

After ir_cow reporting poor performance with latest agesa. I'm staying on 1.1.0.0 with my Asrock board.
Think it depends on how mobo vendors implement agesa updates, cause' not everyone is getting the same performance degradation. But I can't be bothered risking it, the 2.02 bios has proven very stable with quick boots for me anyway.

 

[ir_cow]

Could just be the GB one. Its being investigated . What I can tell you is the loss is only noticeable is certain games when benchmarking plus 3dmark stuff.

I didn't notice at first until I compiled all the data for RTX 4090 benchmarks. Odd 4800 CL40 beats 6000 CL30 I said to myself... Wasted half the day checking other ram, changing BIOS settings to narrow it down. I realized I went to F22 to play with DDR5-8000. Back to F13C (10007) and everything lined up again.

Here is the rub. AIDA64 reports same latency and bandwidth. Loss on GPU stuff is margin of error for GPU bound. Cinebench and Blender is (lower), but unless you locked the frequency - impossible to tell.

3Dmark CPU scores that are affected by memory and of course games not CPU bound is the problem. So its somehow CPU and memory related, but subtle. 3Dmark was the only easy one to catch if you aren't actually looking.




I don't know if anyone will notice unless you have a massive set of data already like me.

 

[ir_cow]

A little update. Gigabyte got back to me and said they don't see the performance drop. So I swapped motherboards to ASUS. Yep exactly the same thing. Timespy and Firestrike drops 1k in score with the same memory, OS and CPU freq.

Going from 1.0.0.7 to AGESA 1.1.0.2 = loss in "performance" , though you are probably unlikely to ever notice.

 

[danc]

maybe it is the software also affecting the scores unless you have kept everything else 1:1 between agesa.

Asus also allows you to turn off/revert INCEPTION mitigation introduced in 1.0.0.8. IIRC it is somewhere in CBS or PBS menu, you change to "most predictive" to get back pre mitigation settings

 

[ir_cow]

maybe it is the software also affecting the scores unless you have kept everything else 1:1 between agesa.

All 1:1. This is a striped down is too. Nothing is running in the background that isn't essential.

Plus I have 3 copies of Windows 11, all are similar. Doubt is OS related

Even though zentimings is the same and CPU is locked to 5.2 all-core. Maybe some BIOS enchantment that was on auto is now off. Though, really not sure what effect that would have if neither the CPU or anything related to memory is unchanged.

Either way this is the new AGEAS. Have new benchmarks for 2024 and all previous stuff is scrapped. This drop in performance just gave me the final push to start fresh again.

 

[chrcoluk]

After trying the newest AMD AGESA 1.1.0.2 b, I noticed 10 fps drop (low settings) in my benchmarks and 1500 points lost in 3DMark CPU test. Tried a bunch of different settings and ram, but it is still a permanent loss. Went back to AMD AGESA 1.0.7.c. Gained all the performance back.

While I like the sub 30 second boot now with 1.1.0.2 band DDR5-8000 support, the perf loss is a bit much.

Example: 5.2 GHz 7950X. 3DMark TimeSpy CPU Score. (1.0.7.c) 16777 vs (1.1.0.2 b) 14200

Wow thats the kind of performance loss typically seen when nasty CPU vulns get patched, was there a microcode update on the CPU on the new bios?

 

[Shou Miko]

I had really long post times on my Asus Prime X670-P WiFi didn't matter what bios version I tried until I switched to my current AsRock B650M PG Riptide, using the same memory with EXPO enabled and it is blazing fast in been it was like my Asus board was re-testing the EXPO on every boot and reboot I made was annoying.

 

[danc]

I had really long post times on my Asus Prime X670-P WiFi didn't matter what bios version I tried until I switched to my current AsRock B650M PG Riptide, using the same memory with EXPO enabled and it is blazing fast in been it was like my Asus board was re-testing the EXPO on every boot and reboot I made was annoying.

memory context restore and power down mode, set both to enabled.

fast boot times on Asus, same as AM4

typo should be power down mode

 

[Shou Miko]

memory context restore and gear down mode, set both to enabled.

fast boot times on Asus, same as AM4

Never saw this setting on my board, and on AM4 with my Asus ROG Crosshair VIII Dark Hero board I never changed anything but D.O.C.P.

 

[ir_cow]

memory context restore

That's just asking for stability issues.

 

[danc]

That's just asking for stability issues.

100% no issue, in Asus bios if you enable MCR, it also enables power down automatically. You need both enabled. Just make sure your ram timings are stable first, and turn on MCR, 100% no issue. Give it a try

Never saw this setting on my board, and on AM4 with my Asus ROG Crosshair VIII Dark Hero board I never changed anything but D.O.C.P.

It is likely in your DRAM timing page, scroll all the way down. At least for Asus bios, it is located there. Memory context restore and Power down enable

 

[Launcestonian]

I've had on my Asrock board MCR enabled & PD mode disabled for months already now @ 6000MT/S 1:1 with AGESA 1.1.0.0. Quick boots, stable OC tested with many apps so gaming is FUN! never crashes.
Think the problem here with slow boots is how the mobo vendor implements the AGESA version. Not all of them do it exactly the same way, its their call being their product they support, so there's that too.

 

[Shou Miko]

100% no issue, in Asus bios if you enable MCR, it also enables power down automatically. You need both enabled. Just make sure your ram timings are stable first, and turn on MCR, 100% no issue. Give it a try



It is likely in your DRAM timing page, scroll all the way down. At least for Asus bios, it is located there. Memory context restore and Power down enable

Can't test anymore with Asus, I am on AsRock for now and it just works out of the box, even updated bios yesterday.

 

[AusWolf]

100% no issue, in Asus bios if you enable MCR, it also enables power down automatically. You need both enabled. Just make sure your ram timings are stable first, and turn on MCR, 100% no issue. Give it a try

MCR didn't work on the original MSi BIOS. Then they fixed it and it worked for a while. On the latest BIOSes, though, it doesn't work again. So I'd say, it highly depends on your system, mainly the motherboard.

 

[ir_cow]

MCR didn't work on the original MSi BIOS. Then they fixed it and it worked for a while. On the latest BIOSes, though, it doesn't work again. So I'd say, it highly depends on your system, mainly the motherboard.

Yep can confirm its broken on Gigabyte X670E Master F22 BIOS. It "works" but if the system goes to sleep, you get a blue screen usually after it wakes up.

MCR was never supposed to be a option until people complain about boot times. Ahh the days where 5 minutes was short. Dial up, floppy and 30MB/s HDD. We are spoiled now.

 

[AusWolf]

Yep can confirm its broken on Gigabyte X670E Master F22 BIOS. It "works" but if the system goes to sleep, you get a blue screen usually after it wakes up.

MCR was never supposed to be a option until people complain about boot times. Ahh the days where 5 minutes was short. Dial up, floppy and 30MB/s HDD. We are spoiled now.

Yep, those were the days! That's why I'm not complaining about boot times now. Heck, memory training time isn't even enough to make a cup of coffee!

 

[Finnedsgang]

hi everyone, back to this thread because i still haven’t found a solution to the memory training failings. This is not just something related to long post timings, but it’s also preventing me from updating bios.

As with the old mb and memories, With this new mb b650 Aorus Elite X Ax Ice, I’m stuck at f1 bios, because when I try to update bios, after the secure boot requested for updating bios, it hangs up at posting. This is not changing with different compatible modules.

I’m writing while 20 minutes have passed with no response from pc. Everything is on default (I erased cmos)

In the pic dram/cpu leds are blinking

 

[chrcoluk]

hi everyone, back to this thread because i still haven’t found a solution to the memory training failings. This is not just something related to long post timings, but it’s also preventing me from updating bios.

As with the old mb and memories, With this new mb b650 Aorus Elite X Ax Ice, I’m stuck at f1 bios, because when I try to update bios, after the secure boot requested for updating bios, it hangs up at posting. This is not changing with different compatible modules.

I’m writing while 20 minutes have passed with no response from pc. Everything is on default (I erased cmos)

In the pic dram/cpu leds are blinking

Maybe set RAM to jedec before flashing? that might make the training much quicker.