Random BSODs even while doing non-gaming tasks

[parforthecourse]

Hi hoping some expert can help identify what's wrong,

 

My computer has been randomly hitting Blue Screens of Death for the past month no matter the task I'm doing. Sometimes I'll be playing games, and sometimes I'm just casually browsing and it's extremely frustrating. The typical STOP_CODE I see is "MEMORY_MANAGEMENT" and "SYSTEM_SERVICE_EXCEPTION" but the process is almost ALWAYS ntkrnlmp.exe. I've run memtest86 for 4 full passes overnight and it always comes up with 0 errors.

 

Other things I've tried:

• I've tried switching the RAM to different DIMM slots
• Swapped motherboards with a friend
• Monitored temps (always well below 65 degrees celsius on cpu/gpu)
• Clean Windows Install
• Bios Update
• Chipset driver update
• DDU
• Monitored PSU voltages, looks well within spec.
• Tried resetting to NON-XMP ram settings
• I should add I've tried both the latest bios and an older one.

Really at a loss for what to do at this point.

 

SPECS:

• CPU: Ryzen 5800X3D
• RAM: ADATA 16GB 3000MHZ
• MOBO: ASUS X370-F STRIX
• GPU: RTX 3060 12GB
• PSU: Corsair RM850X
• STORAGE: KINGSTON KC3000

020425-9265-01_dmp.zip

[Sawa Takahashi]

2 minutes ago, parforthecourse said:

The typical STOP_CODE I see is "MEMORY_MANAGEMENT" and "SYSTEM_SERVICE_EXCEPTION".

It's clear that you have a hardware issue. The question is which component is not playing nice.

From these error codes, I'd say it is memory related. So, the RAM, the CPU or the motherboard are suspects. (With a slight chance of PSU).

You already tested the RAM. Lets assume it is not the culprit.

You tested with another motherboard and the behavior did not change. So the motherboard is probably correct too.

That leaves the CPU. Can you run your CPU in that friend's computer or borrow his CPU to run in your computer ?

While swapping CPUs, take time to check the socket and the CPU pins to make sure everything is clean and undamaged.

If your CPU is testing ok, then I am stomped. You can test with another PSU just in case or try with another SSD, then another GPU.

Good luck !  

[Bjoolz]

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

[parforthecourse]

22 hours ago, Sawa Takahashi said:

It's clear that you have a hardware issue. The question is which component is not playing nice.

From these error codes, I'd say it is memory related. So, the RAM, the CPU or the motherboard are suspects. (With a slight chance of PSU).

You already tested the RAM. Lets assume it is not the culprit.

You tested with another motherboard and the behavior did not change. So the motherboard is probably correct too.

That leaves the CPU. Can you run your CPU in that friend's computer or borrow his CPU to run in your computer ?

While swapping CPUs, take time to check the socket and the CPU pins to make sure everything is clean and undamaged.

If your CPU is testing ok, then I am stomped. You can test with another PSU just in case or try with another SSD, then another GPU.

Good luck !  

When I swapped motherboards with my friend that's what I made sure to look out for. There were no damaged pins. Is there any sort of testing I can do on my own to isolate the CPU? My friend really does not want to take apart his PC to lend his CPU/or test mine.

 

20 hours ago, Bjoolz said:

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

I have attached it just now. Thanks for responding

[Bjoolz]

1 hour ago, parforthecourse said:

When I swapped motherboards with my friend that's what I made sure to look out for. There were no damaged pins. Is there any sort of testing I can do on my own to isolate the CPU? My friend really does not want to take apart his PC to lend his CPU/or test mine.

 

I have attached it just now. Thanks for responding

You only had one dump file? With memory errors it can be really random when Windows detects the issue so it can be hard to track down what the actual root cause is without multiple dump files. From just this one, it looks like the RAM or the CPU. The memory controller is in the CPU so errors in that looks identical to RAM. 

 

To test the RAM, I much prefer just using the PC normally with one stick at a time (One pair at a time is fine if you have four sticks). Check the manual for the motherboard for which slot to use with one stick, but it's usually the second slot from the CPU on boards with four slots, closest to the CPU on boards with two slots. 

 

If it crashes with either stick the CPU would be the next suspect. But please provide more dump files if you have/get more. 

[parforthecourse]

8 hours ago, Bjoolz said:

You only had one dump file? With memory errors it can be really random when Windows detects the issue so it can be hard to track down what the actual root cause is without multiple dump files. From just this one, it looks like the RAM or the CPU. The memory controller is in the CPU so errors in that looks identical to RAM. 

 

To test the RAM, I much prefer just using the PC normally with one stick at a time (One pair at a time is fine if you have four sticks). Check the manual for the motherboard for which slot to use with one stick, but it's usually the second slot from the CPU on boards with four slots, closest to the CPU on boards with two slots. 

 

If it crashes with either stick the CPU would be the next suspect. But please provide more dump files if you have/get more. 

I had multiple dump files but that was just the most recent one. Although I think I figured it out thanks to how you were strongly leaning into something wrong with the CPU. So far my past three reboots are without hiccups when previously it would blue-screen randomly within half an hour. I think the culprit is that PBO is enabled by default on the X370-F Strix as opposed to my previous B350 mobo, which were free from these problems for 2+ years. I suppose I wasn't very lucky with the silicon lottery on my 5800X3D that an Auto-enabled setting is enough to cause instability.