Windows 10: with .dmp files BSOD with MEMORY stop code MEMEORY_MANAGEMNT ... etc

After I purchased my MEMORY kit, my PC was resting when playing heavy games such as Call of Duty: Modern Warfare. I searched online and found a guy who had the same problem and he fixed it by increasing the RAM voltage by +0.05V he also has an AMD R9 5900x CPU, so I followed his solution and it worked for a while.But week age ,After formatting my PC, I received a few errors indicating file corruption. However after searching, I found it may be a RAM issue.And I was able to resolve the issue by borrowing a temporary memory stick from a friend and installing Windows 10 successfully.Whenever I

:)

 

BSOD Stop Code: Memory Management and driver_irql_not_less_or_equal

I have set up a new computer with windows, as I was playing games my computer started to crash. I found a thread related to the Stop Code: Memory Management that suggested I run the Driver Verifier (link below). I found the minidump log files .dmp, I have
no idea how to interpret them - I have 3 .dmp files in total. One of them referenced the Ryzen Master which I downloaded for the CPU so I will try removing that. One important thing to note is I increased the RAM memory speed to 3600 and increased the voltage
- both the mobo and RAM supports this but I am wondering if this is causing an issue.

MS Help - Driver Verifier

One Drive .dmp files

***Modified title from: BSOD - Stop Code: Memory Management and driver_irql_not_less_or_equal - Is this a Driver Issue?***

 

DMP Files after BSOD, rotating between "Memory_Management", "Attempted_Write_To_Read-Only_Memory"

Greetings,

My computer has been restarting extremely frequently in the last 3 days or so. I've been getting the BSOD with the stop codes listed in Subject. I have tried running verifier and it indeed crashed, saying "DRIVER_VERIFIER_DETECTED_VIOLATION".

The link to the previous three DMP files is DMP Files.zip

Any help would be much appreciated!

 

BSOD Stop Code: Memory Management

Could I not simply post a .dmp? Wouldn't that be able to tell you what failed? Not super educated but I've been stalking forums for days now trying to solve my repeated BSOD's. Had a good few with various different codes but 90% of them where Driver issues
I was able to fix. First time I've gotten the memory code, and I just had a critical process died code as well.