Hey everyone, I'm reaching out because my girlfriend has been dealing with a frustrating issue since we built her new PC. It has some pretty solid specs: an AMD Ryzen 7 8700f, GIGABYTE RX 9060XT GAMING OC 16GB graphics card, ASUS PRIME B650M-R motherboard, and 32GB of ADATA RAM. We're also using dual SSDs. The strange part is that she keeps getting random AMD Adrenalin error messages that cause games to crash and even pop up during normal activities like watching YouTube. The timing is all over the place - could be 10 minutes in or an hour. At first, I thought it was a driver issue, so I went through all the usual troubleshooting steps: reinstalling drivers, using DDU, trying different versions, and the like, but the problem just kept coming back. After battling with it for days, it got a little better, but it definitely wasn't fixed. Fast forward a few months and the errors became more frequent. Following a few bizarre suggestions, we tried some diagnostics from Windows which seemed to help temporarily, but then a BSOD appeared with the error code SYSTEM THREAD EXCEPTION NOT HANDLED, sending us back to BIOS. I checked the crash dump, but I'm not very familiar with these things. It referenced "ntoskrnl.exe+4fec10" but I couldn't find much help online. Should I just take the PC to a professional, or is there something else we should try? Thanks for any guidance!
3 Answers
From my experience, it might help to troubleshoot with WinDbg. It's a tool you can get from the Microsoft store that allows you to analyze those BSOD dumps. It can show you what's causing the exceptions. Usually, if you're seeing ntoskrnl.exe in your logs, the root of the issue is often linked to a faulty driver somewhere in the mix. Just a heads up though, it can get tricky to navigate if you’re not familiar with it.
I totally get where you're coming from. I had a similar situation with an AMD APU where my screen would just black out randomly, and then I'd get crash reports. It turned out to be a driver issue that took forever to troubleshoot! Keep at it, and don’t hesitate to seek professional help if it gets overwhelming.
It sounds like you've been through a lot already! First off, I'd recommend checking for additional memory dump files. If you can boot into Windows, navigate to C:WindowsMinidump and see if there are any files there. If you find any, zip them up and upload them to a sharing site like catbox.moe or MediaFire for more in-depth analysis. Multiple dumps can really help understand the issue better! If that doesn't work, let’s look at how you set up your dump settings to ensure you get more useful logs going forward.
Thanks for the tip! I'll check that folder right away and see if I can upload anything useful.
I might give WinDbg a shot, but I have to warn you, I'm not great at these things. If I get stuck, would you be able to help? I did upload that dump file link in the original post.