Windows 10: MEMORY MANAGEMENT BSOD When Overclocking RAM

I recently built a new PC and enabling XMP to clock my RAM to 3200mhz and after a little while of use I got a BSOD with the stop code: MEMORY_MANAGEMENT.


It then brought me to the 'Recovery, Your PC/Device needs to be repaired' screen where I was given the options to press enter to try again or f8 for start up settings. Neither of these options worked, when I pressed the keys my screen just flashed black and then returned to the recovery screen.


I powered off my PC manually and opened bios, I disabled XMP so my RAM is now clocked at 2133mhz and I haven't experienced any problems since. Obviously having my RAM clocked at this speed isn't ideal, so I was wondering what could be causing this and if there is anything I can do to fix it?


Thanks.

:)

 

BSOD- memory management

Upon checking the dump file, the issue is being caused by ntoskrnl.exe. Ntoskrnl.exe is the one responsible for memory management that is why you're having the Memory Management error. We suggest that you follow the steps found in the link that we provided
in our last reply to resolve the issue. Please take note that if you're overclocking your processor or video card, kindly reset their settings to default.

Let us know the outcome after performing the provided steps.

 

BSOD Memory Management error while watching You Tube Videos

My System Configuration is as follows

Motherboard: Asus B350-Plus

Processor: AMD Ryzen 7 1700

Ram : 16 GB (8GB x2) DDR4 2400MHz Corsair Vengeance Ram

OS: Windows 10 Pro 64-bit

Additional Info: No Overclocking is enabled

While watching YouTube videos BSOD error stating Memory Management appears. Thought might be a problem with the graphics card and tested with another graphic card but the results were same. Memory Test on my ram also gave positive result stating no error
with my ram. What could be the cause for the problem?. Could anyone suggest methods for diagnosis or solution to the problem.

Thanks in Advance

 

IRQ memory BSODS, device manager, memory range?

The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..