Blue Screen of Death: Memory Management error

Hey everyone, a buddy of mine is dealing with a constant Blue Screen of Death and reached out to see if anyone here has ideas. We’ve already wasted time running MemTest—which showed absolutely nothing wrong with the RAM—and we even went through the whole headache of a clean Windows reinstall. It hasn't helped at all. The crashes are totally unpredictable; sometimes it happens during a download, sometimes right in the middle of a game, and occasionally it just dies straight up during boot...

Everything in this rig was bought just five months ago, and I can assure you, nothing has been overclocked. If anyone has a clue what else we should investigate or what might be causing this nightmare, please let me know! Any help would be huge.

AMD Ryzen 5 2400g MSI B350 PC Mate Corsair Vengeance Black 2 x8 GB DDR4 2666 MHz Corsair VS550 550w
MSI B350 PC Mate
Corsair Vengeance Black 2x8 GB DDR4 2666 MHz
Corsair VS550 550W
Midi Thermaltake Versa N21
SSD Intel 545 256 GB, SATA III, 2.5", SSDSC2KW256G8X1
HDD Interni Seagate 3.5" 1 TB, 7.200 rpm, DT01ACA100
Windows 10

http://www.resplendence.com/download...ashedSetup.exe

Grab this whocrashed tool—once you've got it installed, just hit analyze and see what it turns up. It should give us a better idea of why you're running into that Blue Screen of Death.

Look, I don't have a definitive answer to whatever issue you're facing, but I did go through something remarkably similar once.

My Windows system used to crash completely at random, without any discernible pattern—it happened daily, month after month, just an endless cycle of instability. Eventually, I decided to run some memory tests to see if I could find the culprit, and one afternoon, the software flagged a massive amount of errors. Since I was running two sticks of RAM, my plan was simple: pull them out one by one, test each individually to identify the faulty module, and then just toss the bad one in the trash. But here’s the kicker—when I tested them separately, they passed perfectly fine, yet when I put them both back in together and ran the scan again, suddenly everything looked flawless.

So, essentially, I didn't actually fix anything, nor did I actually find the source of the trouble. However, since that little mystery occurred, my Windows hasn't crashed a single time, and it's been nearly a year now. You'll have to be the judge of that. Perhaps one stick wasn't seated quite right in the slot, or maybe it was some other minor physical quirk; I haven't the slightest clue, but the problem simply vanished.

If I were you, I'd try switching the memory slots around, or perhaps just leave one stick out for a few days to see if the stability improves. If that doesn't work, swap it for the other one. Ultimately, if the hardware is still under warranty, you might just want to take it back to Best Buy and file a claim.

Sounds like you might be dealing with a bug in your network drivers (LAN/WLAN adapter)... I've run into this before. To be sure, you'd have to mess around with Driver Verifier, but that's a massive pain...

William Richardson12 said:Based on what you're saying, it’s likely a bug hiding in your network drivers—you know, the LAN or WLAN adapters. I've run into this before. To be absolutely certain, though, you’d have to mess around with Driver Verifier, which is honestly a massive, soul-crushing chore.

Is there actually any reliable way to confirm that's the culprit?

Jamie Green5 said:Look, I don't have a direct answer for your specific issue, but I dealt with something similar once.

Try swapping out the memory slots, or just pull one stick out for a few days to see if the behavior changes. Then try the other one. At the end of the day, if it's still under warranty, just take it back to Best Buy and file a claim.

It's seriously bizarre—we'll try testing them one by one and see if we find anything at all.

I've uploaded the logs from the last five crashes to Pastebin; we already went through the drivers and didn't find a single thing wrong.

https://pastebin.com/bwEBE0Dr

http://www.tomshardware.co.uk/answer...-sys-bsod.html

Check this out. Find a small dmp file and send it over to me... we'll see what's actually broken.

I’d suggest pulling up the Event Viewer to check the exact timestamp of when you hit that Kernel Security Check Failure, then doing a quick search for the specific error code. I actually ran into a similar headache once where a certain .dll file tied to my Wi-Fi drivers wasn't loading correctly whenever my laptop woke up from sleep mode. It turned out to be a simple fix—I just had to clear out one specific entry in the registry, and I haven't dealt with it since.