Somewhat related, is there a reason it says in the motherboard manual and on the site to rename the file "##X570P.CAP"? I've flashed both original and renamed and seen no difference. It seems a strange thing for them to go out of their way to mention. Is it about file name lengths that could affect some people?
I went from 1407 to 2407 on my Prime X570 - P and windows wouldn't boot. It enabled sata raid by default. It was fine once I disabled it. I'm running memtest86 to confirm my RAM settings now.Oh wow. Since flashing the latest Asus bios I can't boot even with super safe memory timings. No idea what happened, but I'd better be able to go back.
To be clear are we talking booting or posting?It was 2407 that hated my memory settings. Flashed 2204 and it booted no problem with the same saved settings.
I went from 1407 to 2407 on my Prime X570 - P and windows wouldn't boot. It enabled sata raid by default. It was fine once I disabled it. I'm running memtest86 to confirm my RAM settings now.
Weird. I re-entered all of my voltages and timings. It just blanked out a bunch of stuff when I loaded the old 1407 profile so i reset to default and re-entered my settings. Mine posted fine with the previous memory settings but wouldn't boot windows because of the SATA RAID bug. I just re-assembled the system with some hardware changes yesterday so I'm still working out kinks. It keeps crashing realbench and tossing WHEA errors which is why i updated the bios after I saw there were new versions.POST. It would hang at the DRAM debug LED.
when I loaded the old 1407 profile so i reset to default and re-entered my settings.
I flashed 1407 (which was the latest version) when I post tested my board shortly after buying it 2ish weeks ago. I didn't have any SATA weirdness with my single SATA SSD before 2407. I've never had any kind of RAID setup on this system or even had a second SATA drive plugged in.With Bios 1405,1407 after I flashed them my system would hang at the bios splash screen on the first boot after flash unless I plugged the my sata drives in Raid 0. After that I could boot into the bios then enable the raid and tell it to boot off my M2 drive where windows is.
After flashing 2203 that was no longer needed system saw everything after that first reboot. The Raid Array was working and boot order correct.
I will try 2407 tomorrow morning.
I was told old profiles won't work once you upgrade to 2203 and newer and you should be recreating them.
Weird. I re-entered all of my voltages and timings. It just blanked out a bunch of stuff when I loaded the old 1407 profile so i reset to default and re-entered my settings. Mine posted fine with the previous memory settings but wouldn't boot windows because of the SATA RAID bug. I just re-assembled the system with some hardware changes yesterday so I'm still working out kinks. It keeps crashing realbench and tossing WHEA errors which is why i updated the bios after I saw there were new versions.
F20b apparently has the SVM not disabling bug fixed - SVM virtualization would remain active even if set to Disabled in the BIOS.
Me too. Just passed Memtest86 and 8 hrs of realbench. After the weird SATA RAID being enabled thing after the flash everything is working right. No more WHEA errors and temps dropped a few degrees.I just flashed 2407 and no issues everything is working fine for me.
MSI has an update for it's x570 boards, but it's in beta
"- Updated AMD AGESA ComboAm4v2PI 1.0.0.2 "
MSI has an update for it's x570 boards, but it's in beta
"- Updated AMD AGESA ComboAm4v2PI 1.0.0.2 "
No, decided to stay away from Beta releases.Did you try it yet? I saw it for my MB, but didn't flash it.




Looks like it's close to my 3900X from last year. Though I never had a Pi run that fast. I did break 9s once or twice. Fastest ST CBR15 I've got on record is 211 (haven't tried that hard) and MT is 3453. Careful with the voltage.
Have you tested the chips IF limits yet?
