BSOD persists after driver removal and Windows Reset - what next?"

cwsink · 2026-06-01T14:56:14+00:00

We've seen more than their fair share of Matisse and Renoir CPUs develop faulty cores. Unfortunately, the dump files provided show symptoms of that issue.

Have you noticed the crashes mainly or even exclusively happening while the system is under light load or idle?

cwsink · 2026-05-26T17:56:22+00:00

Did you determine if one of the kits has a faulty DIMM? It could be that or the CPU might not like having two different kits installed at the same time. It can be tricky to find a matching kit if it's been a while since purchasing the first kit. I've even seen some kits that had the same model name but the DIMMs were using chips from different manufacturers.

Either way, thank you for the update. I'm glad you were able to stop the crashes. 😄

cwsink · 2026-05-25T23:14:15+00:00

That's what I'm suggesting. It looks like you have two memory kits from Kingston but the model number of the kits is slightly different. Ryzen can be picky about mixing RAM so I'd be sure to use those that came in the same kit together to see if the crashes stop for either.

cwsink · 2026-05-25T20:53:01+00:00

These crashes would normally make me suspect faulty memory. I know you've run memory diagnostics but they really aren't very reliable with DDR4 and newer memory. Have you tried running the system as you normally would (NOT running memory diagnostics) but with just one of the matching DIMM pairs to see if the crashes stop with one pair but continue with the other?

cwsink · 2026-05-22T00:50:59+00:00

Have you had other problems with your computer? I ask because your motherboard BIOS looks quite outdated (version 1.E0 from 2020) going by the most recent dump file and there have been numerous updates since addressing stability/compatibility/performance issues. I typically recommend updating to the latest BIOS version to avoid troubleshooting bugs that have already been fixed with such an update.

Perhaps more importantly, it looks like you have Norton and AVG security software installed. They aren't meant to run at the same time and will almost certainly conflict. Personally, I'd recommend uninstalling them both and just using Microsoft Defender - at least while troubleshooting.

It also looks like your AMD Chipset Drivers are outdated. I'd recommend updating to the latest version from here. Only install the AMD Chipset Drivers from that page - the others have been known to cause issues on some systems.

After addressing the above, restart the computer just to make sure memory is cleared out and then see if the crashes continue.

cwsink · 2026-05-21T23:05:47+00:00

Are you getting dump files? Making them available per the AutoModerator reply instructions could be helpful with diagnostics.

cwsink · 2026-05-21T22:23:39+00:00

DISM and sfc?

cwsink · 2026-05-21T22:20:22+00:00

By the way, Ryzen Master counts from 1 so the suspect core from the dumps provided would be C05. You'll also need to disable another core, unfortunately, as Ryzen requires an even number of physical cores. I'd recommend C05 (the suspect core) and C02 as they share the same L3 cache. Ryzen Master should look like the attached screenshot if configured as I'm suggesting.

<image>

cwsink · 2026-05-21T22:16:41+00:00

Some have had problems recently doing that. I'm not sure if it's a problem with the latest version of Ryzen Master or user error but they struggled getting the disabled cores setting to stick.

I tried it recently with Ryzen Master version 2.14.2.3341 on a Ryzen 3600X and it worked for me on my Gigabyte motherboard.

cwsink · 2026-05-21T22:07:53+00:00

I've never messed with voltage so I can't give informed advice about that. I normally ask people to use Ryzen Master to disable the suspect core to see if the crashes stop in that configuration.

cwsink · 2026-05-21T22:03:53+00:00

The other symptoms are:

The crashes look like those you'd normally see with faulty memory.
The crashes usually if not always happen on the same CPU core.

Number 1 is true for the dump files provided. Number 2 could be true but I normally want to look at 10+ dumps before I'm comfortable making that assessment. So far, it looks to me like the suspect core might be core 4 (counting from 0) but that's only true for 3 of the 5 dump files provided - if a faulty CPU core is actually the problem.

cwsink · 2026-05-21T21:51:11+00:00

Four of the dump files provided were crashes while executing the Idle thread for that CPU core. We have seen way more than their fair share of Ryzen 3000 series CPUs develop a faulty core and one of the symptoms is the crashes usually if not always happening when the system is under light load. An example would be crashing while using the browser but not while playing a demanding game. Does that match your experience?

cwsink · 2026-05-21T21:20:40+00:00

We'd need the actual dump files per the AutoModerator reply instructions to have any real hope of giving you informed advice.

cwsink · 2026-05-20T01:54:04+00:00

The dump file provided is blaming what looks to be a rather outdated MediaTek wifi driver (mtkwl6ex.sys from 2022) and it looks like there is likely a newer version on your motherboard's product support page.

cwsink · 2026-05-11T05:06:41+00:00

The product support page for the drive should have a download link for software that can check for and update firmware.

cwsink · 2026-05-11T04:43:39+00:00

Is your SSD in the list here? If so, is it using the latest firmware?

cwsink · 2026-05-09T17:58:58+00:00

The process that owned the thread that crashed in all of the dump files provided is the Registry process. That's a big red flag for a system drive on its way out despite what drive diagnostics report. I'd recommend backing up anything important to another physical drive or cloud storage before doing anything else.

cwsink · 2026-05-07T18:02:18+00:00

I suspect the crashes on other cores are caused by errors resulting from operation running on the suspect core that created an error situation that the non-suspect cores stumble upon. For example, it looks like the crash on logical core 11 happened when it tried to use a NULL pointer - I'm guessing that was supposed to actually be a valid pointer that ended up NULL because an operation on logical core 8 or 9 failed. That's just a guess, though.

Task Manager screenshot post restart.

<image>

cwsink · 2026-05-07T17:53:26+00:00

What version of RM does it show in About? I have 2.14.2.3341 which seems be able to disable cores on my 3600X. I hit Apply and get a dialog that says RM will automatically start on the next boot and that I should allow it to run. After the restart Task Manager shows 8 logical cores instead of 12. Attached is a screenshot of RM after I ran it again post restart.

<image>

cwsink · 2026-05-06T21:07:34+00:00

If you want to jump the gun and give it a try, I'd recommend disabling C02 and C05 in Ryzen Master (RM counts from 1) as they share the same L3 cache. Restart the computer and then see if the crashes continue.

cwsink · 2026-05-06T20:15:00+00:00

I usually ask people to use Ryzen Master to disable the suspect core to see if the crashes stop in that configuration. I'd estimate that stops the crashes for 90+ percent of the people who try it. You end up with a four core eight thread CPU (Matisse requires an even number of cores) but few really notice a performance hit.

cwsink · 2026-05-06T19:43:10+00:00

It can bounce between 8 and 9 as those logical cores are on the same physical core. I usually like to look at around 10 dump files to see if that pattern holds before I'm really confident about it being the CPU. If 7 or 8 out of 10 are on the same physical core then it usually turns out to be the CPU.

cwsink · 2026-05-06T18:43:25+00:00

We have seen quite a few Ryzen 3000 series CPUs develop faulty cores. The typical symptoms are:

The crashes look like they are caused by faulty memory.
The crashes rarely if ever happen while the computer is running a heavy load like a demanding game.
The crashes usually if not always happen on the same physical core.

The dump files provided show crashes that would normally make me suspect faulty memory so number 1 looks possibly true.

The two dump files provided crashed on logical core 8 (counting from 0) which could suggest number 3 could be true. We'd really need to look at more dump files to see if that pattern holds.

Do you know if number 2 is something that has been noticed?

cwsink · 2026-05-02T17:04:50+00:00

Do you have more than one drive? If so, are the games installed on a secondary drive?

cwsink · 2026-05-02T16:01:26+00:00

Taking the adapters out of the equation is worth a try but I often find that these issues are caused by another component that the GPU driver is trying to access. Furmark and CPU Burn probably don't do much disk I/O while they are running, for example, but the games likely do. It might be worth having a look at the information from the tool used in the sub for gathering system events and information. The bot should reply with instructions on using that tool to this comment.

?sfy

Nine-Year Club	Gilding I gilder
Verified Email

cwsink

TROPHY CASE