Good morning,
I am experiencing some issues with my board (128GB model). In both Windows and Fedora Linux I am getting crashes and hard lock ups in AI and gaming. BIOS is at version 3.04, tried Frameworks driver pack (windows), latest AMD drivers, multiple kernels in Linux.
Looking for some advice. I see some people have rolled back their BIOS to 3.03. Any other thoughts would be greatly appreciated.
Kyle
Any more details on the said crashes ?
In Windows some of the kids games have just locked hard. Needed to long press the power button to re-boot the system. Event viewer has no clues.
Loading LLMs Fedora Linux under LM Studio has gotten less reliable. LLMs frequently get stuck close to the end of the load and now have caused kernel panics with large ones. If you know what logs I could pull to help identify the issue that’d be great.
Thank you!
Kyle
What games, did you got a hard lock on? And what timeframe, like in the first 10 minutes or after sometime, and thus it happen only in windows.
What is your current driver versions for the gpu/chipset & was the driver a upgrade install or a fresh install by using AMD Cleanup Utility for windows?
I’m testing myself with windows only, so can’t help with linux, but that info would be help full for community at large.
Ps, When a game locks thus the game sound still keep going?
In the last week I’ve had three hard locks in Windows. Also on Bios 3.04, 128GB model.
Twice while playing Battlefield 6, probably ~10 minutes into booting. No sound, screen frozen, can’t get into task manager.
I also had 1 hard lock using LM Studio while loading a model, also no ability to interrupt and so had to hard power off.
I also boot with Fedora on this machine and not had an issue yet but that could be coincedence rather than a rule.
Hi,
Currently on:
Chipset: 8.02.18.557
Graphics: 26.2.2
I have also tried with Framework’s package. Had the same result. Sound stops as well. No mouse input. Fans keep running hard.
Windows 11: 25H2
Had Insurgency Sandstorm and Battlefield 1 lock up hard around 5-15 minutes in. But, I was able to run Furmark in GL and Vulkan for more than 20 mins using far more GFX % without crashing.
Kyle
I did do some testing, and got stuck in windows safe mode boot loop, when I tried to use (AMD Cleanup Utility) because Windows Hallo PIN didnt work in safe mode, and I didn’t get any Sign-In option to swich to password.
After a hour with AI, only by restarting while pressing down shift to get in to windows recorery than Troubleshoot > Advanced and open *Command Prompt and use bcdedit /deletevalue {default} safeboot press enter. If it successful, then use exit and select continue what will restart the system.
Not even system restore got me out of the safe boot loop, because you cant login with a pin.
I need to disable my PIN before, using AMD Cleanup Utility or make a extra local admin account with password only.
*(If bitlocker is set you need your bitlocker pass string to open Command Promp in Windows recovery, make sure to get it before trying to use safe mode by using this: manage-bde -protectors -get C:in command promp in admin mode in normal windows when your still logged in, or get it from your MS Account if your lucky as a last resort. Or you might have to reinstall Windows!! So get your bitlocker pass string added to your password manager so you got it save for future use)
Just some notes for me/community.
Now, I did do some testing before all of this safe mode crap.
@Kyle_Morrison & @Guest584 There is a unstable boost going on for the first 9 minutes. I fix this by reseting game profiles in AMD Adrenalin Edition client. Go to Gaming tab and at the leftside on the bar with Games & Graphics you will find reload icon use it and select Reset all Experiences that fixed that behaviour for me, even if I put a game on HYPR-RX profile.
Next for testing/default, make sure to set under Globel Gaming Experience part of the Graphics tab to Default and make sure everything is OFF with the sliders than in your game, go in the game settings menu, make sure to disable AMD FSR Upscaling and AMD FSR Frame Generation options and restart your game after to make sure those are off in your game.
Also let me know if any other games you got do work without problems? may be not based on unreal or frostbite engines. Just have look at changelogs for the drivers > here as there’re some issues.
Don’t enable anything on the game profile while testing, and always keep Globel Gaming Experience on Default with everying OFF with the slides. If your game is stable you can try on the games tab to change something per game.
If that’s not working, I recommend contacting support. And if you get to a solution, please to put it here, so not everyone has to open a ticket. 
Been having the same kind of crashing with Marathon, NAKWON, and Wreckfest 2. Either the system would hard freeze or a BSOD with ‘DPC_WATCHDOG_VIOLATION’
AMD Software: Adrenalin - 26.2.2
VRAM set to 16gb for the 64gb Desktop
AMD Chipset 8.02.18.557
WhoCrashed
Event Viewer
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000500, 0x0000000000000500, 0xfffff807ee3c43b8). A dump was saved in: C:\WINDOWS\Minidump\031926-21109-01.dmp. Report Id: 45c5888e-8c37-4824-954b-d888a375830c.
Going to resort back to using the drivers provided directly from Framework for the time being until I notice a new AMD update come out. Just going to use DDU as AMD Cleanup just always wants to run in safemode but Windows 11 sucks as last time it had that ‘no pin available’ issue and not going to be stuck in that softloop again.
I’m still on 26.2.2, I didn’t have much time to do some game testing yet, as my elderly mother is not doing well at the moment. And that is mostly been eating up my time, to even make use of my framework desktop.
I only got one lock up with sound still going, on 3dmark Night Raid test. I was planing to try GPU driver clean up, but got a PIN softloop, atleast I learned something, how fix that. Anyway let us know how 25.10.2 is going for when it comes to stability? I will be testing different games like Elite Dangerous, No Man’s Sky & 7 Days to Die. I’m not much a shooter type, plus I’m coming from Xbox.
As for the AMD Cleanup Tool, you can still run it in normal windows. You just click on NO, if it asks you to restart in safe mode, or you create extra local account with password for it.
I would not let that tool put me in safe mode again, as it edits bcdedit, just start up safe mode manually by pressing shift key while you reset than Troubleshoot > Startup Options! Make sure to get your bitlocker key string, before you do that, if you using ms account. You will need that to even get in to Startup Options.
Also AMD just has released: Adrenalin Edition 26.3.1 (change logs). I will wait a bit to test that one, may be there will be 26.3.2 released before the end of this month.
I went back to framework drivers and had a crash then upgraded drivers via AMD Adrenalin and it crashed again. I’m not much of a windows power user so any suggestions I will try and follow, I’m tempted to just try and re-install windows and start again. It’s just a gaming partition for me and the fact I haven’t had the same in Fedora makes me think I’ve just got some weird software interaction.
Now I was a windows power user with windows 10, but 11 is abit of a mess right now.
But let us know if windows install works, as your supposed to install windows and then update it first before installing the driver pack. I’m not sure if I did it that way, plus there is still much to try before I do that. And event viewer is also looking good, no critical error’s, when I got gpu system hang I don’t get any logs of the event so that it not helping.
I did do a small test yesterday, while I was recovering my pc elite dangerous account, with the game elite dangerous. And it looked good, with v sync/ 60 fps limit, but when I disabled it, and opend the galaxy map the frames when to 400+ to 10 to 100 and the system locked up for me again. It reminded me of the early xbox series x days, as for me the sound still keeps going, after a minute or 2 that sounds starts to stutter more and more.
Looks like 26.2.2 is no good, I think it’s a spiking issue with the this driver. I will have to test it more, by putting the game in windows mode, and running hwinfo with some graph open on temps and gpu clocks so I can see what is going on. But first I will do some memory testing, when I have time, before getting back to this issue. As I would like Framework to update their OEM drivers, and that will take time anyway, if they even test windows gaming at all.
I’m also still on 3.0.3 bios, but I don’t think it a bios issue, plus I would like to wait for 3.0.5 full release. My understanding the beta is set somewhere in early April, so may be end April or early May for full release if we are lucky.
@Nix1 Did going back to the driver pack driver 25.10 fix your gaming crashes? I only did do some 3dmark tests, but for that driver it was stable for me. It also 5 to 20% slower than 26.2.2. I don’t remember the gpu clocks in the OEM driver, but I do believe it was 200 to 400 MHz slower then 2600 MHz
@Guest584 ps, Do you game on Lixus as well? And that is stable, if you do game? What driver version is that using?
For me to switch to Linux is the last option, as I’m a Linux noob. Plus I don’t like to run a dual boot on my 1 ssd with windows, as windows is known to break that. So it’s one or the other for the moment.
Small update: since using the AMD cleanup tool and then installing the latest AMD drivers I have not had any game freezes in Windows 11. Installed version is 26.3.1 for the graphics and 8.02.18.557 for chipset.
Haven’t gone back into Linux just yet. Thinking I’ll wait for the new Ubuntu LTS and start again there.
Kyle
I’ve hadn’t been able to be exactly sure since I forgot to also uninstall/stop the AMD Install Manager from auto-updating and it updated me to a newer one then the one that I was crashing on rather frequently. Version 26.3.1 seems to have been a lot better than 26.2.2 in regards to these hard system freezing that I’ve gotten, probably be another week or two before I post another update regarding that prior hard crashing I kept getting on multiple games, if it still happens or if it was just that driver version being really bad.
