Frequent BSOD memory_management

There was no definitive bsod misbehaving driver when the mini dump file was debugged.

When the bsod happened were you actively using the computer?
If so do you remember what was being done?

Please turn off windows driver verifer.

Open file explorer > this PC > local C: drive > right upper corner search > type: C:\Windows\MEMORY.DMP

Using one drive or drop box please post a share link into the thread.

If the misbehaving driver is displayed in the memory dump it can be fixed.
If it is not then give windows driver verifier a rest for a few days and when you can please turn it back on for 48 hours with the same customized settings.

Code:

BugCheck 1A, {41793, ffff890135586ff0, fb, fa}Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+11b980 )

Thanks Zbook.

I remember everything was closed, the system had been on for a few hours, and the BSOD happened almost immediately after launching edge web browser. However, it doesn't always happen like that.

There was no memory.dmp to be found. I've changed the settings to hopefully write a complete dump for next time (it was set to 256kb).

Please keep the setting on automatic.

By default the memory dump should always be created when there is a bsod.

Please post using a share link the memory dump file.

To turn off windows driver verifier: open administrative command prompt and type: verifier /reset

If the memory dump has a new misbehaving driver it can be fixed.

If not consider a time period in which the computer will be actively used and then turn on windows driver verifer for approximately 48 hours using the customized settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

I ended up replacing the 4x4gb sticks with a single 8gb stick and I haven't had a single BSOD for a month.

I recently tested each memory stick individually with memtest (albeit in the same socket) and still no errors were detected. So I'm guessing there was an undetectable issue, or one of my sockets has a problem, or there was a compatibility issue.

Thanks for everyone's suggestions and support.

My advice for anyone stumbling across this thread with symptoms similar to mine - just try replacing the memory first.