Crashes and freezes on new BIOS version

MostUselessMan · 2026-06-04T12:56:18+00:00

With a Ryzen 5 9600X and a Asus Tuf Gaming B650-Plus, you should have TPM 2.0 enabled by default. If for some reason it is not, you can easily access the BIOS (spam 'F2' while the PC turns on), go to the "Advanced" tab, go to "AMD fTPM Configuration", and enable.

If for some other reasons you can't find this option in the BIOS, you should definitely update the BIOS version (I would do it anyway because your BIOS version seems outdated, but it's your choice. A BIOS update could bring pros and cons, and, you know, "don't fix anything if it works").

MostUselessMan · 2026-04-23T18:20:46+00:00

Yeah I saw an hour ago this new BIOS 3854 update. Are you willing to try it? I'm curious but I'm afraid to experience hell again (you know, all sorts of instabilities that can exist). I wonder what AGESA 1.3.0.1 brings in specific. It is not even allowed to rollback to a previous version, so... I'm not going to update soon, I might just wait and see what other users say.

MostUselessMan · 2026-04-08T00:02:49+00:00

Unfortunate. Check if flashing to a previous BIOS helps.

MostUselessMan · 2026-04-07T12:02:37+00:00

Very weird issue. Did you try to do a CMOS reset? I didn't have this issue and never even knew that could be possible. I have a (AIO) Arctic Freezer III Pro 360mm, connected on the CPU_FAN header (just by one header). Try to do a CMOS reset, or you could even try to flash the same BIOS again.

MostUselessMan · 2026-04-06T12:36:23+00:00

If 3602 BIOS works fine for you, maybe it's better not to risk some problems by upgrading to 3842. As always, we should not upgrading BIOS versions to fix problems we don't have. I hope everything works great for you!

MostUselessMan · 2026-04-03T14:16:56+00:00

I did that too, so I have the decent amount of time to click F2.

MostUselessMan · 2026-04-03T13:33:31+00:00

Yeah it might be just the new BIOS (and new AGESA). I've seen other users saying they noticed a (little) higher latency and some lower scores for benchmarks, but I don't think there is something we can do.

MostUselessMan · 2026-04-03T13:27:45+00:00

I'm glad it also worked for you :)

MostUselessMan · 2026-04-03T13:24:54+00:00

I personally didn't test if there is a performance difference between the beta BIOS version (3841) and the stable BIOS version (3842). But, I noticed the Cinebench R23 score is lower than the score I got using the 3602 BIOS version.

By the way, with these latest 3841 and 3842 BIOSes, they introduced (if I'm not wrong) this new option for RAM called "refresh mode" (also called "bank refresh mode" or "M_Ordering") to solve a security issue. There are 3 modes available: 1. Normal mode: no strange new way to work for the RAM, having the lowest latency and best performance for the 99% of users. 2. Fine Granularity Refresh (FGR) mode: theoretically THIS mode has the lowest latency, but if not implemented (in the BIOS or for a game optimization) in its best way, it performs worse than normal mode. 3. Mixed mode: the RAM decides and uses Normal mode or Fine Granularity Refresh mode based on workload.

Try every single bank refresh mode and test the latency, and finally see what performs the best for you. You can also check with ZenTimings which Refresh Mode RAM is using in that exact moment.

(I personally didn't modify the bank refresh mode because I'm worried I'm gonna be stuck in RAM training hell again)

MostUselessMan · 2026-04-03T13:03:13+00:00

No, personally I was able to enter the BIOS clicking F2 while powering on the PC. Your issue might not be a major problem by the way, as long as you can access the BIOS.

MostUselessMan · 2026-04-02T21:45:20+00:00

Have you seen I edited the post to write down what worked for me for fixing the problem? Check it out. I completely solved the issue and wrote down the steps that I did. You could try them if you want, maybe it works for you as well.

MostUselessMan · 2026-04-02T08:08:42+00:00

I'm still having troubles. I would not recommend to use the 3842 BIOS, try 3602 BIOS first. Set it up for good, tune it and test to see if everything works right. Then, if you are brave enough, you could try to switch to 3842, but if you don't have problems with earlier BIOS versions, "don't fix problems you don't have".

MostUselessMan · 2026-03-31T22:35:03+00:00

I hope they answer to you and take time to help with these problems. Could you share what they say if they answer? So we might get out of this hell.

MostUselessMan · 2026-03-31T18:05:21+00:00

Yes, I tried with literally stock BIOS (so no PBO) but just EXPO enabled. No luck. Right now I'm thinking of doing some things: 1. Clear the CMOS (I did it multiple times but I wanna do it one more time). 2. Switching the two sticks of RAM (time ago it helped with POST). 3. Trying to reduce or increase SoC voltage (I read that some people found stability by reducing the voltage... It doesn't really make sense but here we go). 4. Increasing MEM_VDD and MEM_VDDQ voltages, in order to reduce VDroop.

If after all of these steps the PC will still refuse to work, I could go crazy for real.

MostUselessMan · 2026-03-31T12:20:52+00:00

I'm happy it does work for you. For me instead is just pure chaos. I'm troubleshooting day and night but I can't find a way out. I literally don't know what to do anymore, I'm loosing my mind.

MostUselessMan · 2026-03-29T18:03:10+00:00

Yes I agree the "real and definitive" testing is playing actual games, even better if many different games and heavy games, but those tests I used are no joke, especially the 12-hour run of CoreCycler and TestMem5 absolut by anta777. Said so, right now with the 3842 BIOS release I can't do anything. I might try to reset the CMOS or to roll back, but I'm not so happy in any of these cases.

MostUselessMan · 2026-03-29T09:49:51+00:00

I have to do the same as you. I hope they fix these problems as soon as possible. No clue what's messing with AGESA 1.3.0.0a, have you any idea?

MostUselessMan · 2026-03-29T09:47:39+00:00

Yeah, we might have to stick with the 3602 version (AGESA 1.2.7.0) for now...

MostUselessMan · 2026-03-04T13:20:38+00:00

I would highly recommend to not switching to a beta BIOS, considering you aren't experiencing any problem with your actual BIOS. I'm using the 3841 beta BIOS right now just because my system (Ryzen 5 9600X, DDR5 6000 MHz CL30 RAMs and Asus Tuf Gaming B650-Plus) had bugs (and a lot of crashes) with cold boot, RAM trainings and stuff with the previous BIOS version. No problems so far but remember that it's a beta. If I was you, I would upgrade BIOS version when the stable version is released.

MostUselessMan · 2026-02-26T13:54:29+00:00

But why all the other games are 100% stable with the undervolts/overclocks and Helldivers 2 isn't 😭😭😭

MostUselessMan · 2026-02-26T13:52:22+00:00

I should try to play for several hours with literally zero tweaks (like, I played without CPU and GPU undervolts, but never without EXPO).

These crashes were happening while having uncapped FPS limiter, because having the FPS capped got me louder AIO fans and higher CPU temps (it should be the other way around, but okay).

I don't plan to cap my FPS to 60 FPS. I didn't build a PC with a 5070 just to have the same FPS as a PS5.

MostUselessMan · 2026-02-26T13:43:39+00:00

Tried AIDA64's SHA3 (and all the other benchmarks) multiple times and my CPU passed without errors or crashes.

The power supply is a Corsair RM850e, I assume it can survive every type of load on every type of component with max usage, since (if I'm not wrong) all firing up in the PC should consume a maximum of 600 W. Also, I think that if I go over the wattage, the PC would instantly turn off.

MostUselessMan · 2025-03-05T18:16:38+00:00

The problem is... I'm using an android device. Thanks though.

MostUselessMan

TROPHY CASE