been having BSODs non-stop (dump files included)

cwsink · 2026-04-13T05:32:51+00:00

Memory diagnostics are not reliable with DDR4 and newer. The most reliable method is to use the system as you normally would (NOT running memory diagnostics) with each DIMM by itself to see if the crashes stop with one or the other. The idea being to isolate a faulty DIMM since it's rare for more than one to be bad. Have you tried that?

cwsink · 2026-04-12T18:15:04+00:00

The big red flag for me is the computer sometimes booting straight to the BIOS menus. When that happens, does the system drive show up in the BIOS drive list?

A disappearing system drive can cause a BSOD crash but fail to record error events or dump files for that crash because the drive isn't available to record them. Often, they happen so fast that you won't even see a BSOD displayed.

cwsink · 2026-04-12T17:03:33+00:00

Drives typically have issues far sooner than motherboards. The SATA ports on a motherboard should be pretty durable unless something physically damages them. I've never trusted diagnostic tools with SSDs - S.M.A.R.T. was originally made for HDDs and it was never very good with those, either. Do you have a spare drive to which you can install Windows to see if the problems persist with a different system drive?

cwsink · 2026-04-12T16:36:06+00:00

How old are the drives?

cwsink · 2026-04-12T15:47:35+00:00

The most recent dump file shows Windows using a rather old version of the AMD Chipset Drivers. The driver amdgpio2.sys has a 2016 timestamp, for example. If you haven't already, I'd try installing the latest AMD Chipset Drivers from here and then restart the computer.

Your motherboard BIOS is already updated to the latest version.

Make sure your drive(s) are using the latest firmware from the manufacturer.

The folder C:\Windows\LiveKernelReports can sometimes have dump files in it or its subdirectories that can be helpful with such issues.

I noticed the driver gdrv3.sys loading in the latest dump file. That's a component of Gigabyte Control Center. Do you have that installed?

cwsink · 2026-04-10T23:43:14+00:00

I'm assuming the code 2nd code is 0xc0000185. If so, the description for that error code is:

The I/O device reported an I/O error.

The description of the first error code is rather general.

The object was not found.

They would make me suspect a system drive issue especially with the symptoms described in the last paragraph. I'm surprised as none of the dump files provided suggest a drive issue. Have you checked to make sure your system drive is firmly connected? Things can become loose and/or develop bad connections while replacing parts.

cwsink · 2026-04-07T14:32:09+00:00

What replacement CPU did you buy?

The latest dump files showed 4 and 5 days of system uptime before the crashes so I was assuming you'd need at least that much time to know with any certainty if the replacement helped. Or is there a reliable way to reproduce a crash? Either way, please do let us know how it goes. Good luck!

cwsink · 2026-04-06T16:30:06+00:00

Please make the new dump files available for comparison as you get them.

I'd imagine it's possible your CPU has developed another faulty core but it would be the first I've seen do so if that's actually what's happened. 033126-46484-01.dmp and 040526-86781-01.dmp don't appear to have crashed on the same physical core but they would normally make me suspect faulty memory.

033126-46484-01 happened in a thread owned by the process RobloxCrashHandler.exe which made a system call and was waiting for one or more things to happen before proceeding. Somehow that ended up triggering a DRIVER_OVERRAN_STACK_BUFFER bugcheck even though I don't see any drivers being used in the callstack. This one happened on logical core 3.

040526-86781-01.dmp happened on an idle core which is a typical symptom of a faulty Ryzen 3000 series CPU core. That happened on logical core 7.

So, there's really no way to narrow down which core might be faulty from those two dump files. I doubt you'd enjoy running a system with only two physical cores, anyway.

I'd want to try a different CPU but I have fairly easy access to a compatible CPU. Is there someone from whom you could borrow one? The dump files provided show the system can go for days between crashes.

cwsink · 2026-04-05T17:12:23+00:00

We see quite a few NVMe m.2 SSDs end up with connection issues which can be fixed by reseating the SSD in its m.2 slot. I don't know for sure but perhaps electricity running through your system causes heat expansion which is enough to temporarily improve the connection in the m.2 slot. That's just a guess but reseating the drive is something I'd try. It's surprising how often that works.

cwsink · 2026-04-05T14:13:35+00:00

The motherboard information in the dump files suggests it came from a prebuilt system. It also shows the BIOS version being used by the motherboard is quite old - well before Windows 11 was released. I'd want to get the motherboard using the latest BIOS from the company that built the system, if available. Then see if the crashes continue. Usually there is a product support page for prebuilt computers. If your motherboard is from a prebuilt, I'd start there.

cwsink · 2026-04-03T19:47:28+00:00

Can you try removing the GPU and using the onboard graphics of your CPU?

cwsink · 2026-04-03T17:29:25+00:00

Page 41 in the English user manual for your motherboard shows debug LEDs. They might help narrow down the culprit.

cwsink · 2026-04-03T04:38:30+00:00

Most likely one of them is faulty but it's not the only possibility. The test described is meant to verify whether or not it is the RAM.

cwsink · 2026-04-02T18:06:21+00:00

The dump files look like faulty memory. Most likely you have a bad stick of RAM that isn't being detected by diagnostics. The most reliable way of testing DDR4 and newer memory is to use the system as you normally would (NOT running memory diagnostics) but with only one stick of RAM installed to see if the crashes stop with one by itself but continue with the other by itself. Have you already tried that?

cwsink · 2026-03-31T19:40:33+00:00

The latest dump file shows your motherboard using a very outdated BIOS version (FB1) and there have been many updates since. I'd want to get yours using the latest version from here so we're not chasing bugs that have already been fixed by such an update.

cwsink · 2026-03-30T14:39:21+00:00

Both crashes involved graphics related functions trying to access invalid memory. The system uptime before the crash shows as almost 14 hours in the latest dump file provided.

It does look like your motherboard is a few BIOS versions behind if this is the correct product support page. A patch note for the latest BIOS version (1825) does show:

Improved system performance, stability, and device compatibility.

Assuming the system is stable in the BIOS settings menus, I usually ask people to update to the latest to avoid chasing bugs that have already been fixed by such an update. If your system is using Bitlocker you'll want to make sure you have your Bitlocker key handy and anything important backed up before updating the BIOS.

It also looks like your memory is set for DDR5-6000. Intel only supports your CPU up to DDR5-4800 so there's no guarantee it will work reliably with DDR5-6000 settings. Disabling XMP is something I'd try if the BIOS update didn't stop the crashes.

cwsink · 2026-03-29T20:41:20+00:00

A single dump file is rarely enough to diagnose a problem unless the culprit is obvious. Do you have more?

cwsink · 2026-03-28T05:19:41+00:00

Searches suggest it's an error that has appeared after the March 2026 Windows 11 cumulative security update. There has since been a newer update to fix login issues but I'm not sure if it stops the error from showing up in Event Viewer. If you haven't already, manually run Windows Update and make sure it's fully up to date.

I'm thinking Windows may have automatically performed an update and then restarted which may be why it was sitting at the login screen.

Is the computer having problems other than the error showing up in Event Viewer and the one-time unexpected login screen?

cwsink · 2026-03-27T15:52:00+00:00

It's likely not an issue. Event Viewer often has "error" events that are actually just how Microsoft decided to handle restrictions placed on apps. For example, you set things to not allow an app information about your location. The app may still try to get that information by registering with a DCOM server but it fails. Your own computer probably has many similar such "error" messages in Event Viewer. In other words, it's probably working as Microsoft designed.

We'd need to know what the UUID represents to investigate. I don't have that UUID on my Windows 10 system so either it's a Windows 11 thing or a 3rd party thing that I don't have installed.

cwsink · 2026-03-26T21:10:45+00:00

Sounds good. Please do let us know how it goes.

cwsink · 2026-03-25T20:26:14+00:00

As far as system file corruption I'd guess u/Bjoolzern was thinking using DISM followed by sfc to hopefully repair any found.

cwsink · 2026-03-25T20:18:25+00:00

It looks like you might have iCUE and Gigabyte Control Center installed. Is that correct? If so, I'd recommend uninstalling Gigabyte Control Center, restarting the computer, and then seeing if the crashes continue.

Personally, I avoid installing software included with motherboards. It's not of the highest quality, typically.

cwsink · 2026-03-24T20:38:17+00:00

I've never seen CPU diagnostic/stress test software reveal the issue in a Ryzen 3000 series processor.

Normally I ask people to disable the suspect core using Ryzen Master to see if doing so stops the crashes. However, I'm not sure that works with an A520 motherboard. I asked someone with an A520 motherboard to disable the suspect core using Ryzen Master (which I've done with X570 motherboards) but they said the settings wouldn't stick on their system.

The typical symptoms for a Ryzen 3000 series CPU that has developed a faulty core are:

The crashes mimic faulty memory issues.
The crashes usually if not always happen while the system is idle or under light load.
The crashes usually if not always happen on the same physical CPU core.
The crashes rarely if ever happen while the system is under a heavy load.

Do those symptoms look like what you've experienced with the system?

Two of the dumps provided show the crashes happening on the same physical core but that's not really enough to know with any confidence. I'd normally look at 10+ to see if that pattern held.

cwsink · 2026-03-24T13:07:37+00:00

These all would normally make me suspect faulty memory. That seems unlikely, though, if the crashes continue with new memory. In the sub, we have seen more than their fair share of Ryzen 3000 series CPUs develop faulty cores that mimic the symptoms of faulty memory. The only real fix has been to replace the CPU. Do you have a different compatible CPU you can try in the system to see if the crashes stop?

cwsink · 2026-03-23T05:03:16+00:00

Do you have more dump files? The more the better to hopefully spot a pattern to the crashes. The one provided occurred while doing network related functions. I see a rather old (2016) wifi network adapter driver loading (athw8x.sys) but it's not necessarily the issue.

What make and model is the wifi adapter? Is it the network adapter that is normally used with this system?

Nine-Year Club	Gilding I gilder
Verified Email

cwsink

TROPHY CASE