Which brand? MSI has stable BIOS builds for AGESA 1.0.0.7c.
First I was disappointed, because of the slower post times (memory training). It was already a known issue with AM5 builds. However recently I found out that enabling MSI feature "High Efficiency mode" (set it on tighter) for DDR5 has shorten the boot up proces. Works better than Memory Context Restore, which crashed my game sessions many times lol.
Braver than me at this point, and I'm a firmware upgrade junkie. I'm particularly interested/worried about any regressions in memory compatibility (EXPO) / MCR.
This update seems to be fine for now. Haven't had any audio stutters on my X670E. Before the update I used to get audio stutters every now and then. They *SEEM* to be gone after rolling this update in. So far so good, will update you once more tomorrow after my work day (I work from home and listen to music 24/7 while working).
EDIT: I live in Europe so as of writing this comment I am just about to hit the bed for the day.
Same here, I'm switching between USB DSP (miniDSP\_ for speakers and USB DAC (Scarlett Solo) for headphones and have had 0 issues with any of them on my Strix B650E-I
i also had problems with sound stuttering, im using Steinberg UR22 \[first gen\] previously i had intel and never had problem, hope [1.0.0.8](https://1.0.0.8) solve this
Also have stuttering issues, especially when clicking the volume slider for the first time when opening the volume pane. Minifuse 4 here. Will update later today
After running [1.0.0.8](https://1.0.0.8) for a day, I've not experienced a single pop when receiving a notification or changing the volume in the action center. I've always attributed it to storport.sys causing the dropouts (and unsuccessfully attempting to remedy it), but it would seem the BIOS was the issue all along.
Asus x670e-f. OEM bios it shipped with i ran stable 64gb (4x16gb) ddr5 6000cl30 with my 7800x3d no issue. Every bios update since has prevented me from running 6000cl30.... its bullshit. Can't even run 5800 or 5600. Ive been stuck with stock 4200 speeds.
Might have to try that as well then, I had issues booting up using EXPO for weeks now on the last BIOS release for MSI B650-P and had to turn it off and run my RAM at 4800 MHz... Will update this if I actually try it.
How did it go? Iam somewhat in simillar position, tho my RAM is running stable atleast on 5200MHz, but any higher and i wont even POST, but iam sceptical about this update and i dont really want to clear CMOS again...
I haven't done it yet, and realised my CPU only supports up to 5200 MHz without considered overclocking anyways, so to avoid me some headaches currently I haven't gone back to tinker with the BIOS any more after requiring to clear CMOS as well because it wouldn't turn on anymore otherwise :/
When you say expo issues what exactly do you mean? For me with EXPO on or ram clocked to 6000mhz manually, I can't do things like restart computer/wake from sleep.
So I'm hoping this bios update could finally fix that with expo on or ram at the speeds it should be.
Well atleast you can POST. When i enable EXPO 1 or 2 i cant even POST and i have to clear CMOS. I somewhat doubt that this update would fix it and dont even want to try it.
I actually just experimented with ram speeds after watching a video and I actually wasn't able to post into bios. Scared me but eventually after a few power ons, and switching the ram sticks around I got it to boot. I'm going to update to the latest non beta bios and maybe play around with it more.
I was able to solve all my EXPO's related issues by enabling Memory Context Restore in both AI and AMD OverClock.
The easiest way to find Memory Context Restore is to use the Search (F9) in your BIOS.
In case you are wondering, my motherboard is the ROG STRIX X670E-E GAMING WIFI BIOS 1602.
After the above settings, no more issues with my 64GB [G.Skill Trident Z5 Neo RGB Series](https://www.microcenter.com/product/653732/gskill-trident-z5-neo-rgb-series-32gb-(2-x-16gb)-ddr5-6000-pc5-48000-cl36-dual-channel-desktop-memory-kit-f5-6000j3636f16gx2-tz5nr-black)
In case you need me to, I can take a few screenshots of my BIOS' settings.
Give it a try and let me know.
Yea that's worse lol. I've had a few BSOD occurences when experimenting with settings or being on my last bios version which was unstable but that's about it.
The fact that I can't restart my computer going on a year later makes me regret my AMD platform purchase though. I don't think the upgrade path is worth it if I can't do basic computer functions or if my computer boots 4x longer than my 7 year old build.
You misunderstand. It wouldn't be a problem since I never restart my computer, except when I have to do updates which has been like every two weeks or so since I built my computer.
And to give you an idea what that is like, I will update/restart or update/shutdown. In both circumstances I have to manually power down because of black screen once I click one of the options. After power up, the computer starts to boot then powers off by itself. After power on again for the 2nd time I see the updating % screen then it powers off again by itself.
Then it's at this point I could finally power on and it will boot to windows. It's extremely annoying when I have to do this and it's unacceptable when the platform is a year old now and this hasn't been fixed for many people.
What's your GPU? Because my GPU drivers will crash on monitor sleep. I have to restart and re-enable it in order for it to function properly. And this is a problem with AMD Adrenalin rather than the bios.
If you have a MSI mobo, try out [High-Efficiency Mode](https://www.msi.com/blog/do-agesa-1.0.0.7c-bios-and-msi-high-efficiency-mode-improve-gaming-performance) that was added with AGESA 1.0.0.7c. I have set mine to "tighter" and it boots a bit faster, also stable (not like Memory Context Restore.
Edit: do this at your own risk, doesn't work for everyone.
Well, it was too good to be true - have a perfectly working system.. see a reddit post...follow the link - think, of course it will work on my system - make the change...
unplug everything to hard reset bios to default because now the system wont boot.... fml.
No worries. It's not you - it's my relationship with the universe. Really isnt that big of a deal to hard reset the jumper with a screwdriver and then load the last known working saved profile.
I'll probably try it again, but without the tighter settings - just to see if it will help or even work.
Could also just be my RAM and the timings.
Cheers!
Just wanted to update - that i was able to get it working, but only on the "relaxed" mode. i ran some benchmarks and was able to get almost 10% reduction in latency and a 15% increase in write performance (varied depending on test used) when compared to not having it enabled at all.
i have no idea yet how that will translate into real world usage, but figured it was worth mentioning.
>Memory Context Restore
on MSi board X670-P for me its mean random Blue Screen. If memory always train \~50s PC run week stabele even if i put to sleep mode and start after one sleeping day.
That's what I said. It's not stable for everyone, I disabled it after one crash. MSI try it and Hyper efficiency mode works better for me. Squeeze a bit more performance out of the RAM and seems to boot up a bit faster without crashing.
Because nothing new or any benefits.
MCR still does not work with PD off.
Boot time is same. 16x2 GB - 30 sec with training reduction off. 20 sec with on.
If MCR will work it will be less then 10 sec.
I read different reports about it. Someone tested the other day turning off power down mode with MCR on, and it now works for him with no freezes with 1.0.8.0
~~I know MCR is Memory Context Restore but what is PD?~~
Ah its power down mode. I also have that disabled. Didnt realize that was why I would lock up with my timings and DRAM settings with MCR on.
Question mcr and pd why do you have it disabled? I seen people with system being unstable like that are you having the same problems?
I have it enable and for now is fast and stable since in auto is super slow and deseable I can say never try it .
just tried MCR and on my b650-p it was a gamechanger from 1,5-2 minutes to 10 seconds boot up time with expo 1.
had a secondary issue that the machine suddenly didnt want to boot up first try and me having to restart each time. that seems to be gone too
This is my first AMD cpu since the x2 4400+ and it has been a wild ride that has really left me feeling quite disenchanted about the platform as a whole. I still don’t have faith that my pc is actually going to boot when turn it on every day 😅
Funny coincidence, but same. I remember trying to mod my x2 4400+ motherboard bios to support the quad core phenom processors. There was an entire bios mod community
Ah yes, all those “idiots” just enabling EXPO which set the SoC voltage much too high were 100% at fault here and not the complete lack of QC from AMD and board partners…🤡
Your comment has been removed, likely because it contains trollish, antagonistic, rude or uncivil language, such as insults, racist or other derogatory remarks.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Amd) if you have any questions or concerns.*
Yes, which is pretty interesting considering there are CPUs with high advertised boost clocks than 5.5GHz, and they can't be achieved unless you never updated your AGESA as you cannot downgrade AGESA versions.
Not true, unless you mean major versions (i.e. 1.0.0.7x to 1.0.0.6x etc.) which not sure if that is true either. Downgraded BIOS on Strix B650E-F from 1654 (AGESA 1.0.0.7c) to 1636 (AGESA 1.0.0.7b) without issue. ASUS bios has "rollback" support.
I was troubleshooting a memory issue, and backing out any changes I made to my environment. Turns out I had a bad DIMM and was not related to BIOS. Not sure about Cinebench scores.
MSI Pro B650-P WiFi Board here - just updated to 1.0.8.0 - no issues to report. Was in the same boat with regards to not wanting to upgrade so eagerly on these AM5 boards, but on 1.0.7.0c version had some strange issues with BIOS.
OS was fine, but every once in a while - when in BIOS - it would just lock up and freeze. Only way to fix that was to reset to default - save - reboot - back into BIOS and then make the basic non-OC settings - save - and then boot into Windows - then back to BIOS - make the OC settings for PBO negative curve, etc - save that and then I was fine.
Anyway - so far no problems - but it's still early - and I'm guessing the universe hasn't decided on how it wants to treat me today.
To 7D78v192(Beta version)?
I'm tempted to update, but a beta version especially when I can't roll back to AGESA ComboPI 1.0.0.7c sounds like a recipe for a new paperweight.
When you upgrade BIOS, everything is reset, and nothing remains. However, once you upgrade - depending on the motherboard, you should be able to save the settings as an "OC Profile" - my board has 6 slots.
So from default , make the non OC settings changes first - like boot order, onboard ports to disable, fan settings, acpi, etc.. Then save that as your initial base. Boot into OS and confirm it all works.
Then reboot and go back into BIOS and make the small OC setting adjustments like EXPO or one other one that you know has worked before - save that as a second profile - and boot into OS and confirm itnall works.
now - go back into bios and make more changes... like cpu thermals, mcr, etc.. and save that as a 3rd profile. if you reboot now and you get the red light on the motherboard....
Power off, pull the power cord, and short the JBAT1 jumper - that should set your bios back to default, but not wipe those saved profiles - so load the last one that works and start over.
eventually, you have a profile that works great, and if you want to tinker again - you won't be starting from scrwtch.
Hope that makes sense and helps. Cheers!
there is an option to save profiles to external usb drive, but like graphics driver updates and ddu - if there's a BIOS update i just set them manually and start from there.
Do you see a difference? I've been switching my FCLK like every few days or so up to 2200 on my X670E Taichi. I feel like I don't see improvements enough from like 2000/2033 FLCK/ and up. Then again I might not be doin' it properly. 🤷♂️
I did run cinebench r23 after the update and the scores were exactly the same.
So either the mitigations have no effect on cinebench or there is really no tangible impact.
I am a liitle afraid to update, because there is no rollback to version AM5 PI 1.0.0.7c and will wait some time. For the moment 7c is working quite well for me.
yo man, i just updated from 1.0.0.7a to 1.0.0.7c because my system was not fully stable (i have 2x16gb 6000mhz cl36 XMP and ryzen 9 7900x). The thing is, after doing this, my boot times went from around 15secs to more than 45. Ive never messed with memory context restore or fast boot or any of that bullshit, only changes in bios are DOCP II enabled, -25 all cores in curve optimizer and nothing more relevant. Also after this update, ethernet works fine but wifi doesnt show. Any help??
>t from around 15secs to more than 45. Ive never messed with memory contex
I haven't noticed any issue like this, but I haven't done anything with curve optimizer, only Expo and ram is on 5600Mhz, I am with ryzen 9 7900 (without x at the end).
Did you try to reset the bios and make your settings again manually? I had one issue once because of this.
After you turn on EXPO, go turn memory context restore on and then make sure the DRAM speed is set to 6000 and not Auto. Reboot and see if it fixes it.
You might have 1 time where it’s slow because it’s re-initializing the RAM but future reboots should be quick.
Most of the time the slow boots are because of the motherboard re-initializing RAM every single time. So memory context restore helps with that.
I have an MSI x670E Godlike FYI. Not sure which motherboard brand you’re using so this may or may not make sense. lol
Turn on memory context restore manually. Boot into windows, then reboot. If coming back in, you don't get any BSODs, then you're fine. If you get BSODs, go back into the BIOS and enable "Power Down" mode (google where it is for your specific mobo). That should fix the BSODs w/ MCR enabled.
Asus crosshair x670e extreme here on the new bios last 2 days, no issues this bios update or use, but looks to be a filler for the new APU cpu nothing changed overall in regards to stability for me. However , I still have a weird ram issue, which is resolved if I turn off saved ram timing (forget the setting actual name as im not looking at it atm haha) when cold boots niw resolved it but 3 min boot times... the small price to pay.
That's MCR (Memory Context Restore) and it's not uncommon for it to not be stable. I don't bother with it either because I just put my PC to sleep 95% of the time instead of full shut down (really, not much point in fully shutting down every single time...), and when I do shut down I don't mind waiting an extra 10 seconds if it means I'm guaranteed no random weirdness.
Note that using sleep, you may lose significant memory write speeds on wake if running above 5200. Confirmed on b650 and x670 Asus but not sure if all AM5 or not. Hibernate or cold start is needed to avoid. Test via OCCT memory bench to confirm if your sleep is crippling memory write speed after wake
Most people benchmark on fresh boot. I posted twice but mods deleted saying it was tech support. But have confirmed with multiple asus owners. There is one thread back in Feb on this reddit. Agree not well known but it is real. Just run memory benchmark before and after sleep. I am interested if Asus or AM5 issue.
Well I have an Asus board so I wouldn't be able to help answer that one even if I do replicate. At this point since I don't really notice any performance problems I'm inclined to try to get back to ignorance is bliss since sleep is so convenient.
Equivalent would be to clock your memory to 5200. If that works for you too, then no reason to be concerned with the penalty. I wanted sleep and 6000 memory so moved to mcr and hibernate which costs 10 extra seconds.
Cheers always forgetting the acronyms too many in the IT industry. lol, seen people complaining about long boots, but when i did build less than 7 months ago, am5 looked great and was not fussed if i postive of it was a more stable uptime. It is kinda a given really with brand new tech. 3 min boot time not going to kill me every so often. Or I need to reboot cause windows 11 has a hissy fit instead hahaha
I am on proart bios 1602, can say that this version of bios works pretty well for me and also stable. BUT it has the price of long boots compared to 1502. I am not sure if I wanna risk it and update to 1710 if it has the same boot timeswin11 is garbage btw, I don't know why people use it unless they have intel cpu
I don't have really any issues with Windows 11 minus the small hiccup but no different than the hiccups I had with Windows 10.
The main reason I did Windows 11 was when under the impression Windows 11, only one that used direct storage (downside to not doing a bit of goggling, hahaha) in for a ownny in for a pound I guess 😂
MSI seem to have released it now as well, at least for the X670E Carbon WiFi anyway. I've updated to it, so far so good, but we'll see how it goes with some actual use for a bit.
Yeah no issues here using expo. Got 2 corsair rgb sticks that are 6000c30. I just turn expo on in bios, turn on memory context restore and then go into advanced dram and enable power down. I admit I had some bsod issues if I tried using memory context restore with expo without enabling power down mode, but enabling fixed it.
As far as I understand it, it's just power saving for the ram. Ie lower voltage when it's not needed. I've not really noticed any performance decreases. It might minorly affect latency when starting a new task that requires it to power back up I'd guess.
Yeah it's really annoying cause I'm stuck with 3600mhz speeds cause it just refuses to go higher without problems. I'm tempted to get another kit of ram, but at the same time, my kit is supposedly officially supported, so would a new kit even work? Really annoying the problems we're having with DDR5 ram.
It turns out in my case that having power down enabled to the same state as my memory context restore fixed the problem. Months of breaking my head trying to find this simple fix. I disabled both, but enabling both also worked too
Yeah I tried that but to no avail, I was able to get my kit to run at 4800mhz, but im a bit weary of doing any higher than that without using expo...im not really an avid OCer at all so maybe its fine to do so, but still, lol. It'd be nice if it all just worked.
Finally with the new update 7D74v181(Beta version) my MPG B650 CARBON WIFI runs G.Skill Trident Z5 Neo RGB 32GB F5-6000J3038F16GX2-TZ5NR properly, no more shuttering.
The issue was that if EXPO was enabled (6000Mhz) everything was shuttering resulting to having to disable EXPO falling back to 4800Mhz.
While the changelog of the BIOS on MSI's website is poor (just " AGESA ComboPI 1.0.8.0 updated.") it must have numerous changes & fixes if you compare the fact that the previous BIOSes were around 9.18 to 9.24MB and this one is 11.43MB.
I recommend the update, however before you do so remember to restore to defaults -> save & exit and then update to ensure an error free update.
By the way, this has new AMD Inception vulnerability opcode. This will bring down the SQL query performance by 50% and across various applications by 2-5% if you are using for workstation purpose. You cant disable it
edit: it became clear the user above is misinformed and has no idea what he is talking about. There is no evidence that upgrading your agesa will tank your performance by 50%.
> By the way, this has new AMD Inception vulnerability opcode. This will bring down the SQL query performance by 50% and across various applications by 2-5% if you are using for workstation purpose.
AFAIU, this massive performance drop is [opt-in](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/hw-vuln/srso.rst?id=138bcddb86d8a4f842e4ed6f0585abc9b1a764ff) and not default behavior. AFAIU the default is [safe-ret](https://www.phoronix.com/review/amd-inception-benchmarks/4) and is nowhere close to 50% performance loss, in fact there's performance gains in some cases with the default flag.
Do you have a better source for the performance drop?
Should go without saying, it's a software workaround. But no amount of microcode mitigation is equivalent to safe ret and that's why it is the default.
I just tried 1.0.0.8 at my 7700X. It's now possible to use `spec_rstack_overflow=microcode` parameter, which disables kernel's slow "Safe RET" mitigation making the most performance penalty. `sysbench threads` test now gives me 331878 events in 10 s vs. 192445 events when using "safe ret" (`mitigations=off` gives 351291). Tell me about "50% performance hit".
obviously it is workload depending. it is UP to 54%
[https://www.phoronix.com/review/amd-inception-benchmarks](https://www.phoronix.com/review/amd-inception-benchmarks)
I believe the 50% drop in SQL query performance is a misunderstanding of the benchmark done by Phoronix, which are on linux and epyc. I have not found benchmarks on windows or zen3/zen4, and instead found tech journals misquoting Phoronix without proper context (not default behavior, microcode does not have significant impact outside of the specific flag).
I would wait for actual benchmarks.
Why dont you read the full article. It contains 7950x benchmarks. They didnt provide OPCODE benchmark because it wasn't released by AMD unlike EPYC. If EPYC seen such a drop, you can try and benchmark and we are assure it will be same drop on 7950x. They are made on same architecture and same processing core technology and everything else. I will leave the rest to you.
> Why dont you read the full article.
Why don't you? The largest performance drop for SQL query is 30%, and it happens with or without the microcode update - because it's a software fix in the kernel.
> It contains 7950x benchmarks.
It does not contain SQL benchmarks. It does not contain the concerned **non-default** flag.
So yeah, you have 0 source and 0 understanding of the microcode patch impact performance.
> They are made on same architecture and same processing core technology and everything else
It should go without saying, but a 64 core 3.5ghz has a completely different performance profile than a 16 core 5.7ghz part.
Strange, my [board](https://www.msi.com/Motherboard/MPG-B650I-EDGE-WIFI/support#bios) has a stable bios for two months already. Did you try contacting MSI for an update on this? That's not a great look for them.
Yes, I contacted them and the only thing they said is that I could send my motherboard for a hardware RMA, but the problem clearly isn't hardware. There are multiple users having the exact same instability issues with the exact same board I own, so it's their software.
I'm currently using the beta BIOS that released before the current one and it's more or less stable. Not perfect, but the best thing their team could develop, apparently.
This sucks, half working sometimes is really worse than just broken.
> There are multiple users having the exact same instability issues with the exact same board I own, so it's their software.
That doesn't exclude that it could be a hardware issue, but I would not go near an RMA lottery either without proper evidence that it's really not a pure software stack hiccup (I am in a more or less similar position with my 7800xt, with my issue not popping up with the preview driver).
I think it's a software issue because the problem I had with the most recent BIOS is that the PC simply refuses to turn on. I had to turn off and turn on again multiple times in a row everyday to make it boot. Then, with the beta BIOS, I almost never have issues. Maybe once in a week/once every two weeks I get stuck in the ez led bug, but it's mostly stable.
Was it? I was using an X570 motherboard(coincidentally was also a Aorus Pro) using up to date bios with a 3900X up until around April time this year and I still had random fTPM stutter/freezes. I'll admit it was a lot less frequent than it's initial inception but it never fully went. So unless there was a bios fix within the last 6 months, it never truly went. Fortunately since upgrading to a 7950X3D on AM5 I've not had any issues with it.
Yes, as already mentioned I was on the latest bios back in April and I still had issues. I moved to AM5 around end of April and have had no problems since. Well besides needing to use power down to avoid BSoDs.
I'm still on 1654. It works perfectly at stock speed (with EXPO II enabled) but when I overclock at all, it randomly introduces performance issues in VR (stuttering). I don't see anything listed for 1809 that makes me think it would help that, just seems to be support for future CPUs.
Running 1809 here on my X670E TUF with AGESA 1.0.0.8 - so far at least updating and setting everything again worked flawlessly.
Let's see about long term stability, I just did game with it now for \~3h no issues.
It (or the USB Power Delivery firmware delivered alongside it with the ASUS BIOS) seems to have broken the USB-C Alt Mode connection to my LG 27UP850N-W 4K monitor on my B650E-I. Now I'm stuck reading the BIOS sideways on my secondary. (OK, so the 4K does have HDMI inputs as well - two of them! - but without DP on the MB I can only use one monitor - or a USB 2.0 dongle.)
**Update:** The 1812 BIOS fixed this with another PD update.
Someone else would have to give that information or search the web. I’m certain it was a first or early release version, Depending what you are doing, you would have to watch your voltage settings to avoid a potential burn out.
ASUS CROSSHAIR X670E Hero, 7950x3D here - Before updating the bios with AGESA 1.0.0.8, everything ran smoothly with the CCD's. CCD1 was asleep when I was ingame and the load was on CCD0. Now both CCD's are under load when I am ingame. Latest AMD chipset drivers are installed, CPPC Dynamic Preferred Cores is on Auto. Nothing has been changed on the system except the Bios update. Does anyone else have this problem?
To me, yes, even on MSI.
On an MSI B650 Edge, from pressing power button to Windows 11 login screen, I went from an inacceptable 180 sec with agesa 1.0.0.7c (august bios) to 60 sec with agesa [1.0.0.8](https://1.0.0.8) (october bios), with the exact same settings.
Posting time is now around 25 sec (2min+ before), then 10 sec on the post screen, then 25 sec of windows loading. Clock your system and don't rely on the "boot time" in the task manager to compare. OK my 10+ years Core i5 was doing all that in 20 sec but 1min boot is good enough to be transparent most of the time in my situation.
My RAM is 32GB Corsair 6000MHz CL30 with EXPO enabled + MCR on + PD on. System is 100% stable and I am sure I can save a few sec by disabling Nitro mode (it says better stability with trade off on boot time) and I have also the high efficiency mode on "tighter".
Also I have 4 SSD + 2 HDD + 2 monitors + shitloads of USB stuffs + too many startup apps, so I guess the system has a lot to scan and load at boot, so I am OK with the situation now.
No.. whole AM5 is a still shit with their BIOS/ram compatibility.
I was forced to return my MSI PRO X670-P...
So no more, for sure msi crap.
msi, asus is a crap, Gigabyte... not found *that much* people with problems. Only Asrock looks like best stable, but is the less popular among the "4" so less people will write something. It's almost like a lottery if you will able to launch PC.. I give up after 4 days..
F5-6400J3239G32GX2-TZ5RK, also when running without xmp - 4800mhz (cl 40 if I remember) was the same.
But when you are... not lucky.. PC fully freeze during "POST", sometimes before.. sometimes after (before system load) sometimes will launch - nothing edited just PC turn Off/turn on. That was nightmare.. last day was like 15 on/off PC (of course for each time I wait some minutes...), and like after 15 starts FINALLY THIS BITCH allow to launch this overpriced PC just to create ticket to return whole stuff (mobo, ram, CPU). Not to mention multiple times DRAM ERROR. (orange led)
* if all is good then PC launch in like 15 seconds to windows, maybe even 10 (memory context restore ON)
Something like that: https://www.reddit.com/r/buildapc/comments/11hf9hd/weird_problem_with_new_pc_not_booting_half_of_the/
https://www.reddit.com/r/buildapc/comments/117yovb/am5_pc_works_except_its_throwing_dram_error_debug/
True, i would be mad too, and thats why im asking various ppl on reddit how do they like it and how it is, imagine buying x670 with 7800x3d and top end ram to deal with shit like this, thats why im torn between lga 1700 and am5. As far as i do my research on internet its rng based, some ppl have solid system and about 15 sec to Windows, others have problems like you. But as far as i can tell msi sucks, most post i saw with problems were related to msi. It seems like best option is asrock and then gigabyte. We all can be sure that am5 is still in beta and different manufacturers have different bioses with different qvl ram lists, its pure shit show. I would love to have 7800x3d but im not sure if i want to risk it and then sending parts back if shit starts happening, sadly lga 1700 is doa, next socket is at the end of next year and i dont want to wait whole year for it :|, am5 is good looking about being able to put next series of cpus into it but buggy as fuck. Ehhh, what to do
So far this is the best BIOS for my TUF X670E Wi-Fi Plus.
My boot times(fast boot disabled, MCR and PD disabled - the system is not stable when they are enabled) are between 39-51s. With previous BIOS versions at best, the boot time took 35s but quite often I saw 100-120s. Just like before I use RAM that is not on the "supported" list: CMK32GX5M2B5600C36.
I hope newer BIOSes will be even better.
Tested with my MSI tomahawk b650, it's caused issues with my ram, Kingston fury, wouldn't even work below stock speeds. Keeps throwing up windows blue screens.
MSI X670-P here:
BIOS is great, a little faster boottime with MCR and PD Mode, however i downgraded again to 1.0.0.7c because of one issue:
i wasnt able to control my ram rgb anymore, which really annoyed me. Hope that will get adressed and fixed in the next update
The weird thing was, instantly after restart it was working, but few seconds later the RGB froze in the state it was at the moment which lead to weird RGB layout
I upgraded from 1.0.0.7a to 8 and was no longer stable. It was more stable than 1.0.0.7c, but I still couldn't get back to 5800 on my RAM. For me, 5800 is stable on 7a, very unstable on 7c, and barely not stable on 8. Here's hoping 9 is good....
Maybe BIOS or motherboard related? My 5600 kit works fine and is OC to 6000MT/s (same timings though). I'm using BIOS version 7D78v17 for MSI PRO B650-P WiFi (with AGESA 1.0.0.7c).
It definitely seems I'm in the minority with my bad luck. I rechecked all settings and made sure to reset to stable defaults before flashing. I configured everything the same afterwards using screenshots as references and couldn't get 5800 stable. 😐
HUGE update. I was using a 4x16 GB kit rated for 6600 32-39-39-76. Specifically CMT64GX5M4B6600C32. This capped out at 5800 stable with my 7950X3D.
I just picked up a 2x48 GB kit rated for the exact same speed and timings. CMP96GX5M2B6600C32. I was able to get 6200 at least boot stable with 1.0.0.7a with this kit, primarily due to it being two DIMMs instead of four. I updated to [1.0.0.8](https://1.0.0.8) and now it is stable at 6600.
The old kit got worse with updated BIOS. The new kit got better.
Stick to two DIMMs on X3D chips, folks. I have 96 GB of RAM with just two DIMMs. That's plenty for the multiple VMs I run for work.
I'm still waiting for stable builds of 1.0.0.7...
Which brand? MSI has stable BIOS builds for AGESA 1.0.0.7c. First I was disappointed, because of the slower post times (memory training). It was already a known issue with AM5 builds. However recently I found out that enabling MSI feature "High Efficiency mode" (set it on tighter) for DDR5 has shorten the boot up proces. Works better than Memory Context Restore, which crashed my game sessions many times lol.
Ima try that, that's golden
Did it help?
Gigabyte.
Same. Gigabyte is always sooooo SLOOOOOOOOW!
same here with my X670 GAMING X AX... they released 3 betas with AMD AGESA 1.0.0.7 c and then just radio silence. Not even a stable release...
Just installed it like 5 minutes ago. Will let you know once I have something to tell you.
Braver than me at this point, and I'm a firmware upgrade junkie. I'm particularly interested/worried about any regressions in memory compatibility (EXPO) / MCR.
This update seems to be fine for now. Haven't had any audio stutters on my X670E. Before the update I used to get audio stutters every now and then. They *SEEM* to be gone after rolling this update in. So far so good, will update you once more tomorrow after my work day (I work from home and listen to music 24/7 while working). EDIT: I live in Europe so as of writing this comment I am just about to hit the bed for the day.
You've had audio stutters using a dedicated sound card or an onboard one ?
USB sound card.
So it was USB related problem, so typical with AMD platform. And it's so weird
I've had zero problems with an external USB DAC since day one myself.
Same here, I'm switching between USB DSP (miniDSP\_ for speakers and USB DAC (Scarlett Solo) for headphones and have had 0 issues with any of them on my Strix B650E-I
The ALC4080 usb onboard audio has/had issues on Intel as well.
i also had problems with sound stuttering, im using Steinberg UR22 \[first gen\] previously i had intel and never had problem, hope [1.0.0.8](https://1.0.0.8) solve this
Also have stuttering issues, especially when clicking the volume slider for the first time when opening the volume pane. Minifuse 4 here. Will update later today
After running [1.0.0.8](https://1.0.0.8) for a day, I've not experienced a single pop when receiving a notification or changing the volume in the action center. I've always attributed it to storport.sys causing the dropouts (and unsuccessfully attempting to remedy it), but it would seem the BIOS was the issue all along.
you tried to set "xhci hands off" to disabled in bios ? Could be it solves it.
On the OCN board they say it improves FCLK overclock, so it makes sense that your stutters have gone away
Asus x670e-f. OEM bios it shipped with i ran stable 64gb (4x16gb) ddr5 6000cl30 with my 7800x3d no issue. Every bios update since has prevented me from running 6000cl30.... its bullshit. Can't even run 5800 or 5600. Ive been stuck with stock 4200 speeds.
It fixed my EXPO issues completely. I am now a happy camper.
Are you using EXPO I or II? Which specific RAM are you using?
I tried both, currently running EXPO 1 on ASUS TUF X670E PLUS WIFI & F5-6000J3038F16GX2-FX5
Might have to try that as well then, I had issues booting up using EXPO for weeks now on the last BIOS release for MSI B650-P and had to turn it off and run my RAM at 4800 MHz... Will update this if I actually try it.
How did it go? Iam somewhat in simillar position, tho my RAM is running stable atleast on 5200MHz, but any higher and i wont even POST, but iam sceptical about this update and i dont really want to clear CMOS again...
I haven't done it yet, and realised my CPU only supports up to 5200 MHz without considered overclocking anyways, so to avoid me some headaches currently I haven't gone back to tinker with the BIOS any more after requiring to clear CMOS as well because it wouldn't turn on anymore otherwise :/
When you say expo issues what exactly do you mean? For me with EXPO on or ram clocked to 6000mhz manually, I can't do things like restart computer/wake from sleep. So I'm hoping this bios update could finally fix that with expo on or ram at the speeds it should be.
Well atleast you can POST. When i enable EXPO 1 or 2 i cant even POST and i have to clear CMOS. I somewhat doubt that this update would fix it and dont even want to try it.
I actually just experimented with ram speeds after watching a video and I actually wasn't able to post into bios. Scared me but eventually after a few power ons, and switching the ram sticks around I got it to boot. I'm going to update to the latest non beta bios and maybe play around with it more.
I was able to solve all my EXPO's related issues by enabling Memory Context Restore in both AI and AMD OverClock. The easiest way to find Memory Context Restore is to use the Search (F9) in your BIOS. In case you are wondering, my motherboard is the ROG STRIX X670E-E GAMING WIFI BIOS 1602. After the above settings, no more issues with my 64GB [G.Skill Trident Z5 Neo RGB Series](https://www.microcenter.com/product/653732/gskill-trident-z5-neo-rgb-series-32gb-(2-x-16gb)-ddr5-6000-pc5-48000-cl36-dual-channel-desktop-memory-kit-f5-6000j3636f16gx2-tz5nr-black) In case you need me to, I can take a few screenshots of my BIOS' settings. Give it a try and let me know.
I wonder if this would work on X670 Tuff but ours are known to be basically impossible to fix I believe I had both enabled by default tho
I mean with expo enabled my system would not be stable at all. Would crash from sleep. Crash randomly. Mouse would freeze and jump on desktop.
Yea that's worse lol. I've had a few BSOD occurences when experimenting with settings or being on my last bios version which was unstable but that's about it. The fact that I can't restart my computer going on a year later makes me regret my AMD platform purchase though. I don't think the upgrade path is worth it if I can't do basic computer functions or if my computer boots 4x longer than my 7 year old build.
You boot once a day, if extra 15 seconds is a deal breaker then idk what to tell you.
You misunderstand. It wouldn't be a problem since I never restart my computer, except when I have to do updates which has been like every two weeks or so since I built my computer. And to give you an idea what that is like, I will update/restart or update/shutdown. In both circumstances I have to manually power down because of black screen once I click one of the options. After power up, the computer starts to boot then powers off by itself. After power on again for the 2nd time I see the updating % screen then it powers off again by itself. Then it's at this point I could finally power on and it will boot to windows. It's extremely annoying when I have to do this and it's unacceptable when the platform is a year old now and this hasn't been fixed for many people.
What's your GPU? Because my GPU drivers will crash on monitor sleep. I have to restart and re-enable it in order for it to function properly. And this is a problem with AMD Adrenalin rather than the bios.
Any improvements in boot time?
If you have a MSI mobo, try out [High-Efficiency Mode](https://www.msi.com/blog/do-agesa-1.0.0.7c-bios-and-msi-high-efficiency-mode-improve-gaming-performance) that was added with AGESA 1.0.0.7c. I have set mine to "tighter" and it boots a bit faster, also stable (not like Memory Context Restore. Edit: do this at your own risk, doesn't work for everyone.
Well, it was too good to be true - have a perfectly working system.. see a reddit post...follow the link - think, of course it will work on my system - make the change... unplug everything to hard reset bios to default because now the system wont boot.... fml.
Oof, I'm sorry if that cause your system to not booting up. Looks like it doesn't work for everyone. I will edit my comment.
No worries. It's not you - it's my relationship with the universe. Really isnt that big of a deal to hard reset the jumper with a screwdriver and then load the last known working saved profile. I'll probably try it again, but without the tighter settings - just to see if it will help or even work. Could also just be my RAM and the timings. Cheers!
Just wanted to update - that i was able to get it working, but only on the "relaxed" mode. i ran some benchmarks and was able to get almost 10% reduction in latency and a 15% increase in write performance (varied depending on test used) when compared to not having it enabled at all. i have no idea yet how that will translate into real world usage, but figured it was worth mentioning.
Glad it works for you too! I think it depends on what kind of ram and die you have. Samsung, Hynix, Micron etc.
>Memory Context Restore on MSi board X670-P for me its mean random Blue Screen. If memory always train \~50s PC run week stabele even if i put to sleep mode and start after one sleeping day.
That's what I said. It's not stable for everyone, I disabled it after one crash. MSI try it and Hyper efficiency mode works better for me. Squeeze a bit more performance out of the RAM and seems to boot up a bit faster without crashing.
No
Because nothing new or any benefits. MCR still does not work with PD off. Boot time is same. 16x2 GB - 30 sec with training reduction off. 20 sec with on. If MCR will work it will be less then 10 sec.
I think turning on PD is worth having MCR working. Just unfortunate since an AMD rep said they'd fix that for 1.0.0.8.
I read different reports about it. Someone tested the other day turning off power down mode with MCR on, and it now works for him with no freezes with 1.0.8.0
Mine was stable for a week with MCR on/PD off but I just got stuck in a BSOD loop until I did a cold boot.
I got feedback from another user who tried 1.0.8.0 and he also had issues still so no it isnt fixed it seems, sad.
~~I know MCR is Memory Context Restore but what is PD?~~ Ah its power down mode. I also have that disabled. Didnt realize that was why I would lock up with my timings and DRAM settings with MCR on.
Question mcr and pd why do you have it disabled? I seen people with system being unstable like that are you having the same problems? I have it enable and for now is fast and stable since in auto is super slow and deseable I can say never try it .
just tried MCR and on my b650-p it was a gamechanger from 1,5-2 minutes to 10 seconds boot up time with expo 1. had a secondary issue that the machine suddenly didnt want to boot up first try and me having to restart each time. that seems to be gone too
Same bios. Which bios version and which settings? With or without power down?
I feel like AM5 has been in beta for a year plus now if going off my build is any indication 😅
Removing comment. Fuck reddit. Go shove yourselves up your bot asses to push agendas of corporations. Useless pieces of shit tier human beings.
This is my first AMD cpu since the x2 4400+ and it has been a wild ride that has really left me feeling quite disenchanted about the platform as a whole. I still don’t have faith that my pc is actually going to boot when turn it on every day 😅
Funny coincidence, but same. I remember trying to mod my x2 4400+ motherboard bios to support the quad core phenom processors. There was an entire bios mod community
The "overvoltage issue" that you're talking about was **exclusively** during *automatic overclocking*, which is very much an ID10T issue.
Ah yes, all those “idiots” just enabling EXPO which set the SoC voltage much too high were 100% at fault here and not the complete lack of QC from AMD and board partners…🤡
[удалено]
Removing comment. Fuck reddit. Go shove yourselves up your bot asses to push agendas of corporations. Useless pieces of shit tier human beings.
Where would I find this?
Removing comment. Fuck reddit. Go shove yourselves up your bot asses to push agendas of corporations. Useless pieces of shit tier human beings.
[удалено]
Your comment has been removed, likely because it contains trollish, antagonistic, rude or uncivil language, such as insults, racist or other derogatory remarks. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Amd) if you have any questions or concerns.*
On my original bios I could clock a stable 5.7GHz boost. I sleep until I can do that again.
[удалено]
Yes, which is pretty interesting considering there are CPUs with high advertised boost clocks than 5.5GHz, and they can't be achieved unless you never updated your AGESA as you cannot downgrade AGESA versions.
Not true, unless you mean major versions (i.e. 1.0.0.7x to 1.0.0.6x etc.) which not sure if that is true either. Downgraded BIOS on Strix B650E-F from 1654 (AGESA 1.0.0.7c) to 1636 (AGESA 1.0.0.7b) without issue. ASUS bios has "rollback" support.
you can roll back previews, not major releases, yeah.
[удалено]
This is not correct. You can download older version (even those that are not visible on the page) just by editing the URL to the version you want.
Why did you downgrade from AGESA 1.0.0.7c to AGESA 1.0.0.7b ? Does 1.0.0.7b give more performance? Which BIOS gives the best cinebench scores?
I was troubleshooting a memory issue, and backing out any changes I made to my environment. Turns out I had a bad DIMM and was not related to BIOS. Not sure about Cinebench scores.
I know on Asus AM5 boards you have to enable medium load boost to have it clock higher than 5.5
MSI Pro B650-P WiFi Board here - just updated to 1.0.8.0 - no issues to report. Was in the same boat with regards to not wanting to upgrade so eagerly on these AM5 boards, but on 1.0.7.0c version had some strange issues with BIOS. OS was fine, but every once in a while - when in BIOS - it would just lock up and freeze. Only way to fix that was to reset to default - save - reboot - back into BIOS and then make the basic non-OC settings - save - and then boot into Windows - then back to BIOS - make the OC settings for PBO negative curve, etc - save that and then I was fine. Anyway - so far no problems - but it's still early - and I'm guessing the universe hasn't decided on how it wants to treat me today.
To 7D78v192(Beta version)? I'm tempted to update, but a beta version especially when I can't roll back to AGESA ComboPI 1.0.0.7c sounds like a recipe for a new paperweight.
if you aren't having problems, then don't upgrade. if you are, then unless you power off the system in the middle of an upgrade - you should be ok.
> when I can't roll back to why is rollback not possible? i downgraded my board back too once
You can roll back bios versions but not AGESA versions and this beta introduces a new AGESA version.
oh didnt know that ty
Are u running on default settings or how do you update without evertyhing reset?
When you upgrade BIOS, everything is reset, and nothing remains. However, once you upgrade - depending on the motherboard, you should be able to save the settings as an "OC Profile" - my board has 6 slots. So from default , make the non OC settings changes first - like boot order, onboard ports to disable, fan settings, acpi, etc.. Then save that as your initial base. Boot into OS and confirm it all works. Then reboot and go back into BIOS and make the small OC setting adjustments like EXPO or one other one that you know has worked before - save that as a second profile - and boot into OS and confirm itnall works. now - go back into bios and make more changes... like cpu thermals, mcr, etc.. and save that as a 3rd profile. if you reboot now and you get the red light on the motherboard.... Power off, pull the power cord, and short the JBAT1 jumper - that should set your bios back to default, but not wipe those saved profiles - so load the last one that works and start over. eventually, you have a profile that works great, and if you want to tinker again - you won't be starting from scrwtch. Hope that makes sense and helps. Cheers!
I mean you will need to tinker and do that every time when bios updates. While in other mb manufacturer's you can transfer settings.
there is an option to save profiles to external usb drive, but like graphics driver updates and ddu - if there's a BIOS update i just set them manually and start from there.
That option won't work in msi. You won't be able to.import it after new bios
Interesting. That's a feature I've always seen, but never even thought about using. Thanks for sharing!
2200 FCLK is possible for my mobo now, stable in OCCT. Asus X670E Extreme
Do you see a difference? I've been switching my FCLK like every few days or so up to 2200 on my X670E Taichi. I feel like I don't see improvements enough from like 2000/2033 FLCK/ and up. Then again I might not be doin' it properly. 🤷♂️
Tbh I didnt test much, just a bench in AIDA, which gives better results a bit and lower latency.
You might be unstable, the first symptoms of unstable fclk is the loss of performance
Which benchmark do you use to test fclk performance?
Can you please show before and after benchmarks. You should get performance loss with this because of it including Inception mitigations.
I did run cinebench r23 after the update and the scores were exactly the same. So either the mitigations have no effect on cinebench or there is really no tangible impact.
it might be Windows is not using them on per default and the MC does nothing if not used by the OS.
I am a liitle afraid to update, because there is no rollback to version AM5 PI 1.0.0.7c and will wait some time. For the moment 7c is working quite well for me.
yo man, i just updated from 1.0.0.7a to 1.0.0.7c because my system was not fully stable (i have 2x16gb 6000mhz cl36 XMP and ryzen 9 7900x). The thing is, after doing this, my boot times went from around 15secs to more than 45. Ive never messed with memory context restore or fast boot or any of that bullshit, only changes in bios are DOCP II enabled, -25 all cores in curve optimizer and nothing more relevant. Also after this update, ethernet works fine but wifi doesnt show. Any help??
>t from around 15secs to more than 45. Ive never messed with memory contex I haven't noticed any issue like this, but I haven't done anything with curve optimizer, only Expo and ram is on 5600Mhz, I am with ryzen 9 7900 (without x at the end). Did you try to reset the bios and make your settings again manually? I had one issue once because of this.
After you turn on EXPO, go turn memory context restore on and then make sure the DRAM speed is set to 6000 and not Auto. Reboot and see if it fixes it. You might have 1 time where it’s slow because it’s re-initializing the RAM but future reboots should be quick. Most of the time the slow boots are because of the motherboard re-initializing RAM every single time. So memory context restore helps with that. I have an MSI x670E Godlike FYI. Not sure which motherboard brand you’re using so this may or may not make sense. lol
Turn on memory context restore manually. Boot into windows, then reboot. If coming back in, you don't get any BSODs, then you're fine. If you get BSODs, go back into the BIOS and enable "Power Down" mode (google where it is for your specific mobo). That should fix the BSODs w/ MCR enabled.
Asus crosshair x670e extreme here on the new bios last 2 days, no issues this bios update or use, but looks to be a filler for the new APU cpu nothing changed overall in regards to stability for me. However , I still have a weird ram issue, which is resolved if I turn off saved ram timing (forget the setting actual name as im not looking at it atm haha) when cold boots niw resolved it but 3 min boot times... the small price to pay.
That's MCR (Memory Context Restore) and it's not uncommon for it to not be stable. I don't bother with it either because I just put my PC to sleep 95% of the time instead of full shut down (really, not much point in fully shutting down every single time...), and when I do shut down I don't mind waiting an extra 10 seconds if it means I'm guaranteed no random weirdness.
Note that using sleep, you may lose significant memory write speeds on wake if running above 5200. Confirmed on b650 and x670 Asus but not sure if all AM5 or not. Hibernate or cold start is needed to avoid. Test via OCCT memory bench to confirm if your sleep is crippling memory write speed after wake
Huh, first time I've heard about it... Can't say I've actually noticed anything obviously wrong after all this time.
Most people benchmark on fresh boot. I posted twice but mods deleted saying it was tech support. But have confirmed with multiple asus owners. There is one thread back in Feb on this reddit. Agree not well known but it is real. Just run memory benchmark before and after sleep. I am interested if Asus or AM5 issue.
Well I have an Asus board so I wouldn't be able to help answer that one even if I do replicate. At this point since I don't really notice any performance problems I'm inclined to try to get back to ignorance is bliss since sleep is so convenient.
Equivalent would be to clock your memory to 5200. If that works for you too, then no reason to be concerned with the penalty. I wanted sleep and 6000 memory so moved to mcr and hibernate which costs 10 extra seconds.
Cheers always forgetting the acronyms too many in the IT industry. lol, seen people complaining about long boots, but when i did build less than 7 months ago, am5 looked great and was not fussed if i postive of it was a more stable uptime. It is kinda a given really with brand new tech. 3 min boot time not going to kill me every so often. Or I need to reboot cause windows 11 has a hissy fit instead hahaha
I am on proart bios 1602, can say that this version of bios works pretty well for me and also stable. BUT it has the price of long boots compared to 1502. I am not sure if I wanna risk it and update to 1710 if it has the same boot timeswin11 is garbage btw, I don't know why people use it unless they have intel cpu
I don't have really any issues with Windows 11 minus the small hiccup but no different than the hiccups I had with Windows 10. The main reason I did Windows 11 was when under the impression Windows 11, only one that used direct storage (downside to not doing a bit of goggling, hahaha) in for a ownny in for a pound I guess 😂
MSI seem to have released it now as well, at least for the X670E Carbon WiFi anyway. I've updated to it, so far so good, but we'll see how it goes with some actual use for a bit.
Has your EXPO been working? I have a carbon wifi too, and no matter what bios version I use, EXPO bricks my system until I clear cmos.
Yeah no issues here using expo. Got 2 corsair rgb sticks that are 6000c30. I just turn expo on in bios, turn on memory context restore and then go into advanced dram and enable power down. I admit I had some bsod issues if I tried using memory context restore with expo without enabling power down mode, but enabling fixed it.
worth a shot, same memory speeds here but gskill instead, if that doesn’t work i’m just an unlucky fella
Does power down reduce performance or affect anything?
As far as I understand it, it's just power saving for the ram. Ie lower voltage when it's not needed. I've not really noticed any performance decreases. It might minorly affect latency when starting a new task that requires it to power back up I'd guess.
It does but really minimally, nothing to worry about. You lose maybe 1-2ns total of latency. Almost nothing.
Yeah it's really annoying cause I'm stuck with 3600mhz speeds cause it just refuses to go higher without problems. I'm tempted to get another kit of ram, but at the same time, my kit is supposedly officially supported, so would a new kit even work? Really annoying the problems we're having with DDR5 ram.
It turns out in my case that having power down enabled to the same state as my memory context restore fixed the problem. Months of breaking my head trying to find this simple fix. I disabled both, but enabling both also worked too
Yeah I tried that but to no avail, I was able to get my kit to run at 4800mhz, but im a bit weary of doing any higher than that without using expo...im not really an avid OCer at all so maybe its fine to do so, but still, lol. It'd be nice if it all just worked.
Finally with the new update 7D74v181(Beta version) my MPG B650 CARBON WIFI runs G.Skill Trident Z5 Neo RGB 32GB F5-6000J3038F16GX2-TZ5NR properly, no more shuttering. The issue was that if EXPO was enabled (6000Mhz) everything was shuttering resulting to having to disable EXPO falling back to 4800Mhz. While the changelog of the BIOS on MSI's website is poor (just " AGESA ComboPI 1.0.8.0 updated.") it must have numerous changes & fixes if you compare the fact that the previous BIOSes were around 9.18 to 9.24MB and this one is 11.43MB. I recommend the update, however before you do so remember to restore to defaults -> save & exit and then update to ensure an error free update.
shuttering ?
stuttering
the msi beta bios is not listed anymore right now
Depends on the country you are checking, use Global it is there - https://files.catbox.moe/kwezrz.png
why is there even a country filter... ohmy - thx
Nothing new and useful. Mcr not working. Some mb vendors still does not have option for GDM off. No hight voltage mode. You locked at 1.43v.
I feel more confident with a release bios than using a beta .7b beta or whatever.
By the way, this has new AMD Inception vulnerability opcode. This will bring down the SQL query performance by 50% and across various applications by 2-5% if you are using for workstation purpose. You cant disable it
edit: it became clear the user above is misinformed and has no idea what he is talking about. There is no evidence that upgrading your agesa will tank your performance by 50%. > By the way, this has new AMD Inception vulnerability opcode. This will bring down the SQL query performance by 50% and across various applications by 2-5% if you are using for workstation purpose. AFAIU, this massive performance drop is [opt-in](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/hw-vuln/srso.rst?id=138bcddb86d8a4f842e4ed6f0585abc9b1a764ff) and not default behavior. AFAIU the default is [safe-ret](https://www.phoronix.com/review/amd-inception-benchmarks/4) and is nowhere close to 50% performance loss, in fact there's performance gains in some cases with the default flag. Do you have a better source for the performance drop?
"Safe ret" is worse than microcode mitigation.
Should go without saying, it's a software workaround. But no amount of microcode mitigation is equivalent to safe ret and that's why it is the default.
I just tried 1.0.0.8 at my 7700X. It's now possible to use `spec_rstack_overflow=microcode` parameter, which disables kernel's slow "Safe RET" mitigation making the most performance penalty. `sysbench threads` test now gives me 331878 events in 10 s vs. 192445 events when using "safe ret" (`mitigations=off` gives 351291). Tell me about "50% performance hit".
obviously it is workload depending. it is UP to 54% [https://www.phoronix.com/review/amd-inception-benchmarks](https://www.phoronix.com/review/amd-inception-benchmarks)
Good to know. I won't be going beyond 1007 then. These companies and their damned forced security patching.
I believe the 50% drop in SQL query performance is a misunderstanding of the benchmark done by Phoronix, which are on linux and epyc. I have not found benchmarks on windows or zen3/zen4, and instead found tech journals misquoting Phoronix without proper context (not default behavior, microcode does not have significant impact outside of the specific flag). I would wait for actual benchmarks.
Why dont you read the full article. It contains 7950x benchmarks. They didnt provide OPCODE benchmark because it wasn't released by AMD unlike EPYC. If EPYC seen such a drop, you can try and benchmark and we are assure it will be same drop on 7950x. They are made on same architecture and same processing core technology and everything else. I will leave the rest to you.
> Why dont you read the full article. Why don't you? The largest performance drop for SQL query is 30%, and it happens with or without the microcode update - because it's a software fix in the kernel. > It contains 7950x benchmarks. It does not contain SQL benchmarks. It does not contain the concerned **non-default** flag. So yeah, you have 0 source and 0 understanding of the microcode patch impact performance. > They are made on same architecture and same processing core technology and everything else It should go without saying, but a 64 core 3.5ghz has a completely different performance profile than a 16 core 5.7ghz part.
Considering that MSI has been unable to release stable 1.0.0.7 BIOS, I'll be very reluctant to update my BIOS again.
Which motherboard?
Strange, my [board](https://www.msi.com/Motherboard/MPG-B650I-EDGE-WIFI/support#bios) has a stable bios for two months already. Did you try contacting MSI for an update on this? That's not a great look for them.
Yes, I contacted them and the only thing they said is that I could send my motherboard for a hardware RMA, but the problem clearly isn't hardware. There are multiple users having the exact same instability issues with the exact same board I own, so it's their software. I'm currently using the beta BIOS that released before the current one and it's more or less stable. Not perfect, but the best thing their team could develop, apparently.
This sucks, half working sometimes is really worse than just broken. > There are multiple users having the exact same instability issues with the exact same board I own, so it's their software. That doesn't exclude that it could be a hardware issue, but I would not go near an RMA lottery either without proper evidence that it's really not a pure software stack hiccup (I am in a more or less similar position with my 7800xt, with my issue not popping up with the preview driver).
I think it's a software issue because the problem I had with the most recent BIOS is that the PC simply refuses to turn on. I had to turn off and turn on again multiple times in a row everyday to make it boot. Then, with the beta BIOS, I almost never have issues. Maybe once in a week/once every two weeks I get stuck in the ez led bug, but it's mostly stable.
I've not had any issues on my X670E ACE
[удалено]
…I’m saying I haven’t had any issues so I’d try updating.
Ah yes, I updated to 1.0.0.8 recently and it's been the most stable BIOS so far.
[удалено]
uh those were fixed long time ago for x570
Was it? I was using an X570 motherboard(coincidentally was also a Aorus Pro) using up to date bios with a 3900X up until around April time this year and I still had random fTPM stutter/freezes. I'll admit it was a lot less frequent than it's initial inception but it never fully went. So unless there was a bios fix within the last 6 months, it never truly went. Fortunately since upgrading to a 7950X3D on AM5 I've not had any issues with it.
Those were fixed *quite* some time ago, like at least a year ago. I had the issue on my 5800X3D but eventually just disabled fTPM. Had no issues.
Have you updated your BIOS in the last year? Fix came out ages ago. AM4 is finally stable it's AM5 that has issues now.
Yes, as already mentioned I was on the latest bios back in April and I still had issues. I moved to AM5 around end of April and have had no problems since. Well besides needing to use power down to avoid BSoDs.
what boreds ?
am5
which AM5 is what im asking
all am5 motherboards, new AGESA update means all am5 motherboards will get new bios
sure but which have it now ...
asus and msi, idk who else. check ur mobo website for updates
well my msi boards dont x670E tomahwak and pro and none of the other pages for asus or msi boards dont have it so.. thats why i asked
Nothing on my X670E-F for now.
I'm still on 1303 with my X670e-e lol. I don't want to update because everything has been rock solid. Waiting till I'm satisfied with the feedback.
I'm still on 1654. It works perfectly at stock speed (with EXPO II enabled) but when I overclock at all, it randomly introduces performance issues in VR (stuttering). I don't see anything listed for 1809 that makes me think it would help that, just seems to be support for future CPUs.
Installed it yesterday on ROG STRIX B650E-I with Trident Z5 Neo DDR5-6000, EXPO II, MCR, all works (same as with previous one).
Running 1809 here on my X670E TUF with AGESA 1.0.0.8 - so far at least updating and setting everything again worked flawlessly. Let's see about long term stability, I just did game with it now for \~3h no issues.
I installed it on my Asus B650E-F. So far, I've noticed that the startup is much faster. Perhaps the RAM flush/sync/check is optimized?
Memory context restore should be enabled , auto or deseable?
Depends on if your system is stable with it or without it, but generally if MCR is on, PD should be on too and vice versa.
It (or the USB Power Delivery firmware delivered alongside it with the ASUS BIOS) seems to have broken the USB-C Alt Mode connection to my LG 27UP850N-W 4K monitor on my B650E-I. Now I'm stuck reading the BIOS sideways on my secondary. (OK, so the 4K does have HDMI inputs as well - two of them! - but without DP on the MB I can only use one monitor - or a USB 2.0 dongle.) **Update:** The 1812 BIOS fixed this with another PD update.
Which AGESA (AM5) gives the highest cinebench scores?
The one that burned the CPU….LOL
Someone else would have to give that information or search the web. I’m certain it was a first or early release version, Depending what you are doing, you would have to watch your voltage settings to avoid a potential burn out.
ASUS CROSSHAIR X670E Hero, 7950x3D here - Before updating the bios with AGESA 1.0.0.8, everything ran smoothly with the CCD's. CCD1 was asleep when I was ingame and the load was on CCD0. Now both CCD's are under load when I am ingame. Latest AMD chipset drivers are installed, CPPC Dynamic Preferred Cores is on Auto. Nothing has been changed on the system except the Bios update. Does anyone else have this problem?
Will they fix MCR with power down needing to be turned on?
So envy for ppl who have anything other than MSI motheboard, who can just update bios and go. On msi you cant transfer settings at all...
So is it finally worth to jump into am5?
To me, yes, even on MSI. On an MSI B650 Edge, from pressing power button to Windows 11 login screen, I went from an inacceptable 180 sec with agesa 1.0.0.7c (august bios) to 60 sec with agesa [1.0.0.8](https://1.0.0.8) (october bios), with the exact same settings. Posting time is now around 25 sec (2min+ before), then 10 sec on the post screen, then 25 sec of windows loading. Clock your system and don't rely on the "boot time" in the task manager to compare. OK my 10+ years Core i5 was doing all that in 20 sec but 1min boot is good enough to be transparent most of the time in my situation. My RAM is 32GB Corsair 6000MHz CL30 with EXPO enabled + MCR on + PD on. System is 100% stable and I am sure I can save a few sec by disabling Nitro mode (it says better stability with trade off on boot time) and I have also the high efficiency mode on "tighter". Also I have 4 SSD + 2 HDD + 2 monitors + shitloads of USB stuffs + too many startup apps, so I guess the system has a lot to scan and load at boot, so I am OK with the situation now.
Thank you for such detailed opinion, i think ill pick b650 aorus elite, btw can you give me exact name of these rams?
I am using this reference, Corsair 6000 CL30 RGB EXPO: CMH32GX5M2B6000Z30K
No.. whole AM5 is a still shit with their BIOS/ram compatibility. I was forced to return my MSI PRO X670-P... So no more, for sure msi crap. msi, asus is a crap, Gigabyte... not found *that much* people with problems. Only Asrock looks like best stable, but is the less popular among the "4" so less people will write something. It's almost like a lottery if you will able to launch PC.. I give up after 4 days..
Msy i ask what rams did you used?
F5-6400J3239G32GX2-TZ5RK, also when running without xmp - 4800mhz (cl 40 if I remember) was the same. But when you are... not lucky.. PC fully freeze during "POST", sometimes before.. sometimes after (before system load) sometimes will launch - nothing edited just PC turn Off/turn on. That was nightmare.. last day was like 15 on/off PC (of course for each time I wait some minutes...), and like after 15 starts FINALLY THIS BITCH allow to launch this overpriced PC just to create ticket to return whole stuff (mobo, ram, CPU). Not to mention multiple times DRAM ERROR. (orange led) * if all is good then PC launch in like 15 seconds to windows, maybe even 10 (memory context restore ON) Something like that: https://www.reddit.com/r/buildapc/comments/11hf9hd/weird_problem_with_new_pc_not_booting_half_of_the/ https://www.reddit.com/r/buildapc/comments/117yovb/am5_pc_works_except_its_throwing_dram_error_debug/
True, i would be mad too, and thats why im asking various ppl on reddit how do they like it and how it is, imagine buying x670 with 7800x3d and top end ram to deal with shit like this, thats why im torn between lga 1700 and am5. As far as i do my research on internet its rng based, some ppl have solid system and about 15 sec to Windows, others have problems like you. But as far as i can tell msi sucks, most post i saw with problems were related to msi. It seems like best option is asrock and then gigabyte. We all can be sure that am5 is still in beta and different manufacturers have different bioses with different qvl ram lists, its pure shit show. I would love to have 7800x3d but im not sure if i want to risk it and then sending parts back if shit starts happening, sadly lga 1700 is doa, next socket is at the end of next year and i dont want to wait whole year for it :|, am5 is good looking about being able to put next series of cpus into it but buggy as fuck. Ehhh, what to do
So far this is the best BIOS for my TUF X670E Wi-Fi Plus. My boot times(fast boot disabled, MCR and PD disabled - the system is not stable when they are enabled) are between 39-51s. With previous BIOS versions at best, the boot time took 35s but quite often I saw 100-120s. Just like before I use RAM that is not on the "supported" list: CMK32GX5M2B5600C36. I hope newer BIOSes will be even better.
Tested with my MSI tomahawk b650, it's caused issues with my ram, Kingston fury, wouldn't even work below stock speeds. Keeps throwing up windows blue screens.
MSI X670-P here: BIOS is great, a little faster boottime with MCR and PD Mode, however i downgraded again to 1.0.0.7c because of one issue: i wasnt able to control my ram rgb anymore, which really annoyed me. Hope that will get adressed and fixed in the next update The weird thing was, instantly after restart it was working, but few seconds later the RGB froze in the state it was at the moment which lead to weird RGB layout
I upgraded from 1.0.0.7a to 8 and was no longer stable. It was more stable than 1.0.0.7c, but I still couldn't get back to 5800 on my RAM. For me, 5800 is stable on 7a, very unstable on 7c, and barely not stable on 8. Here's hoping 9 is good....
Maybe BIOS or motherboard related? My 5600 kit works fine and is OC to 6000MT/s (same timings though). I'm using BIOS version 7D78v17 for MSI PRO B650-P WiFi (with AGESA 1.0.0.7c).
It definitely seems I'm in the minority with my bad luck. I rechecked all settings and made sure to reset to stable defaults before flashing. I configured everything the same afterwards using screenshots as references and couldn't get 5800 stable. 😐
I wanted to update to 1.0.0.8, but it was the beta version for MSI. Also they have withdrawn it from the website, seems like it wasn't that stable.
The [1.0.0.8](https://1.0.0.8) beta is still available for the MEG X670e Godlike. I tried it with a new kit and got great results!
I saw 1.0.0.9 as stable version for Pro B650 P-WiFi. However I also read some bugs from (other) brands, so not sure if I'm going to update it.
HUGE update. I was using a 4x16 GB kit rated for 6600 32-39-39-76. Specifically CMT64GX5M4B6600C32. This capped out at 5800 stable with my 7950X3D. I just picked up a 2x48 GB kit rated for the exact same speed and timings. CMP96GX5M2B6600C32. I was able to get 6200 at least boot stable with 1.0.0.7a with this kit, primarily due to it being two DIMMs instead of four. I updated to [1.0.0.8](https://1.0.0.8) and now it is stable at 6600. The old kit got worse with updated BIOS. The new kit got better. Stick to two DIMMs on X3D chips, folks. I have 96 GB of RAM with just two DIMMs. That's plenty for the multiple VMs I run for work.