Question I have been experiencing numerous BSODs throughout the past week and a half!

DoctorPebble

Prominent
Jan 6, 2023
11
0
510
Hey everyone. Any help here would be sincerely appreciated as I feel lost about what to do. As the title suggests, I have had roughly 7 BSODs throughout the past week and a half. I have the minidump files for three of them.

For context, I upgraded my PC on December 5th. My PC before had gone over a year without a single BSOD. However, a few days after the upgrade, I began having BSODs randomly when I am actively doing something. I left the PC on for three days without any BSODs, so these BSODs are only happening when I am actively doing something besides playing a game (I play very demanding games, so it would have BSOD if there was an issue on game stability).

The components I replaced after the upgrade were the following:
Motherboard
CPU
PSU
CPU Cooler, new case fans, and PC case

The first three are likely the relevant ones for BSOD discussion, especially since the majority of the BSODs related to MEMORY_MANAGEMENT. I have uploaded my minidump files to a google drive if anyone could kindly see if you could find out the culprit better than I can. I ran the minidumps through Windbg, but it's not really helping.

Another important thing is that I did an entire fresh install of Windows 10 today as I am writing this post. All my drivers are up-to-date, and I am still having the same errors I did before.

I am physically limited in what I can do due to muscle weakness from a condition, so I would like to know if I should absolutely start doing stuff like Memtest, which would require me to have someone help me take off the CPU cooler to do so and begin testing.

https://drive.google.com/file/d/157pHzs5KxYo7_NtGJpLvuXB2z4Ao-cOx/view?usp=drive_link

Any assistance would be greatly appreciated, and I'll be sure to check for responses often.

Edit: I should also say that my GPU is a year old and has been working perfectly on the old system. However, my RAM is roughly 4 years old now and on XMP 3200 Mhz (Like it always had been on the old system). I'm a little suspicious of the RAM, but I want to know if maybe there is something else wrong.

Additional information I should have included:

PC Specifications -

RAM - 4 x 8 Corsair Vengeance 3200Mhz (4 - 5 years old now)
CPU - Ryzen 7 5700X 8 - Core Processors 3.4 GHz (New)
GPU - MSI RTX 3060 12GB (Roughly 6 months old)
MOBO - MSI MAG B550 Tomahawk (New)
PSU - Corsair RM850x Fully Modular ATX Power Supply 80 PLUS Gold (New)
Storage Devices -
NVMe Samsung 970 EVO 500GB (C: drive) (400 GB free of 465 GB)
Samsung 2.5 inch SSD 2TB (521 GB free of 1.81 TB) (1 year old)
Western Digital 2.5 inch SSD 1TB (298 GB free of 931 GB)
Western Digital HDD 4TB (1.84 TB free of 3.63 TB)
OS: Windows 10 Home / Version 22H2 / Installed on 12/19/2024 / OS Build 19045.5247

I did a fresh install of Windows 10 today, so I only have a copy of one of the minidumps from before the Windows 10 fresh install. But I am already experiencing the BSODs similar to what I had before, so I'm going under the basis that it's not related to drivers or Windows itself.

View Reliability History -
After looking through this, I unfortunately was not able to find anything related to the BSODs besides the two bugchecks:
Bugcheck #1 - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041792, 0xffff8500be800068, 0x0000000000000010, 0x0000000000000000)
Bugcheck #2 - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xffffce0014178e70, 0x000000000000011d, 0x000000000000011e)

The third bugcheck can be found in the minidump from December 8th. Everything else in reliability history isn't giving me any useful information. Nothing looks like it's have a cause-effect situation prior to the BSOD.

Event Viewer -
After thoroughly investigating here, I was unfortunately not able to find a specific answer on what it could be. I have scrolled through event viewer a hundreds times it feels like over the past 4 years owning this PC, so I have figured out what is a normal error / warning. The only ones that pop out to me are the bugchecks I put up previously. The rest of the decernable errors are ones that are telling me that windows didn't shut down properly or anything of that nature.

Specs of the old PC vs new PC after hardware upgrades -
Old PC New PC
RAM - 4 x 8 Corsair Vengeance 3200Mhz RAM - 4 x 8 Corsair Vengeance 3200Mhz (Same)
CPU - AMD Ryzen 7 3700x CPU - AMD Ryzen 7 5700x (New)
GPU - MSI RTX 3060 12GB GPU - MSI RTX 3060 12GB (Same)
MOBO - MSI B450 Tomahawk Max MOBO - MSI MAG B550 Tomahawk (New)
PSU - Thermaltake 700W Bronze PSU - Corsair RM850x ATX 80 PLUS Gold (New)
Storage - Same as listed above Storage - Same as listed above, but C: wiped for fresh install of windows 10 to narrow down whether or not drivers were the issue or Windows itself.

Summary of personal obervations for when the BSODs happened:

BSOD #1 (Before fresh install) - I was going to shut down my PC roughly two to three days after we swapped out the hardware for upgrades. However, when I shut down the PC, about 10 seconds into the shutdown sequence, I get a BSOD.

BSOD #2 (Before fresh install) - I was redownloading a game called Rainbow Six Siege. After it downloaded the files, it began installing it. I went to step away for a minute or two to get something to drink. I came back to my PC having restarted from a BSOD. I redid the download, then it worked the second time.

BSOD #3 (Before fresh install) - I was launching a game called Helldivers 2. Once the anti-cheat menu started loaded, I had a BSOD. I've launched the game a bunch of times since then and had no issue.

Not a BSOD, but a weird occurence (Before fresh install) - When a game called Zenless Zone Zero got a major version update, I installed the update through the launcher. When I launched the game, it had a small 700 MB update. However, I kept on getting weird in-game errors about downloading the update that had nothing to do with the internet connection. I guess it couldn't give me a proper error due to something being wrong with my system?

Not a BSOD, but another weird occurence (Before fresh install) - I had been absolutely loving Marvels Rivals, but I am the only one in my friend group that is having consistent Unreal Engine 5 crashes. With these crashes, I am getting the most generic crash errors not specific to any driver like other people are getting.

BSOD #4 - This is after the fresh install of Windows 10. I had done the entire set up process with no issues, installed the drivers well, installed the basic programs I use such as MSI Afterburner, Steam, Firefox, Discord, etc. However, I wanted to see if with my new fresh install of Windows, I could download that Zenless Zone Zero update I mentioned in the prior section. I started the download in the game's launcher (before that small patch I talked about in the game itself), it downloaded 67GB of files successfully, but when it began verifying the files and updating plugins, my PC got a BSOD.

BSOD #5 - This is only roughly 8 minutes after BSOD #4. I start the download again, it starts trying to verify the files, I tab out to Firefox, everything begins freezing on Firefox alongside everything else, then I BSOD.

At first, you'd think this was an issue with my storage devices. However, I've ran CHKDSK commands to check the health alongside Disk Partition and all of them say my drives are healthy. The different games I've mention are all on the other storage mediums besides my C: drive itself. I could definitely be wrong here though.

With many of the BSODs already being MEMORY_MANAGEMENT errors, it's starting to worry me that maybe the RAM is beginning to go out or its a faulty motherboard. However, as I mentioned earlier in the post, I had this same exact RAM in the old PC and the PC did not BSOD for nearly 2 years.

What is also weirder is that I ran three max stress tests back to back, and I still couldn't get the PC to BSOD after I fresh installed windows. It is only when I begin doing the things I mentioned in the previous BSODs.

All of you are much smarter and experienced than I am when it comes to these issues as I have used Tomshardware for the five years I've been into PC building, so I was hoping that maybe with this information, one of you could maybe have an idea of what this could be based on previous experiences since I'm stumped.

Please let me know if any other information is needed and I'll give you as detailed information as possible.
 
Last edited:
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage.

Disk drive(s): make, model, capacity, how full?

= = = =

Mini-dumps have their place and value.

However, you may find it a bit more revealing by taking a look at things via Reliability History/Monitor and Event Viewer.

Reliabiity History is much more end user friendly and the timeline format may reveal patterns. Especially anything being captured just before or at the time of the noted BSODs.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Both tools support clicking on specific errors to obtain more details. The details may or may not be helpful.
 
  • Like
Reactions: DoctorPebble
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage.

Disk drive(s): make, model, capacity, how full?

= = = =

Mini-dumps have their place and value.

However, you may find it a bit more revealing by taking a look at things via Reliability History/Monitor and Event Viewer.

Reliabiity History is much more end user friendly and the timeline format may reveal patterns. Especially anything being captured just before or at the time of the noted BSODs.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Both tools support clicking on specific errors to obtain more details. The details may or may not be helpful.
Hi Ralston, I’ll go to my PC now and look at those two areas. Unfortunately, I do check in those areas, and I think I would have found the culprit if it was revealing itself there. However, I’ll go check them again and post picture and get information.

Also, I’ll edit my post to include my PC info in a little bit. Thank you for the quick response!
 
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage.

Disk drive(s): make, model, capacity, how full?

= = = =

Mini-dumps have their place and value.

However, you may find it a bit more revealing by taking a look at things via Reliability History/Monitor and Event Viewer.

Reliabiity History is much more end user friendly and the timeline format may reveal patterns. Especially anything being captured just before or at the time of the noted BSODs.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Both tools support clicking on specific errors to obtain more details. The details may or may not be helpful.
Hi Ralston, I updated my post to include any information I could think of providing. If you believe I need to add anymore specific information, I will do my best to find it.

For the moment, do you think I should go ahead and try Windows Memory Diagnostic first, then Memtest if WMD detects an error? I saw that was something people done. Like I mentioned in the post, I'm unfortunately not able to physically take apart my PC like I used to due to physical impairments without asking a friend or parent to help me, so I would love reassurance that doing RAM checks would be the best thing to do using the information I provided.
 
Just today I was getting the MEMORY_MANAGEMENT BSODs today and it turned out it was my memory, which even thought it's rated to 4266, wasn't working at even 3970 Mhz. Yesterday I was having problems w/firefox not even starting.
Test your memory. I would suggest Prime95 w/large FFTs.
 
  • Like
Reactions: DoctorPebble
Just today I was getting the MEMORY_MANAGEMENT BSODs today and it turned out it was my memory, which even thought it's rated to 4266, wasn't working at even 3970 Mhz. Yesterday I was having problems w/firefox not even starting.
Test your memory. I would suggest Prime95 w/large FFTs.
I'll wait to see what others have to say before I try Prime95 since I don't think this will help my case. Like I mentioned, I've done three stress tests using Heaven, played hardware intensive games, and still didn't get BSODs during those long gaming sessions. These BSODs have only happened when I'm starting up games or downloading games, but it's not the disk since CHKDSK and Disk Management have repeatedly told me that my drives are healthy.

Also, when I brought my RAM speed from 3200 Mhz down to the base factory 2133 Mhz, the issue I was having with that Zenless Zone Zero game I was talking about still kept consistently occurring.

I appreciate you responding to my post though!
 

Latest posts