Windows 10: Memory Management Bluescreen

This has been happening every once in a while and it's rather annoying. Nothing points towards RAM corruption though as all my RAM is usable and I did a test on the RAM. Not sure what's going on but maybe you all could help me out? It's beginning to become really annoying. Apparently it's a custom error...

:)

 

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.

 

Out of Memory Bluescreen

Hi,

Thank you for posting your query in Microsoft Community.

As a basic troubleshooting steps try the below steps and check if it helps.

Run Memory Diagnostic Tool.

• 
  Type Memory Diagnostic in the search box.
  
• 
  Select Windows Memory Diagnostics and click on Restart now and check for problems.
  
• 
  Follow the on-screen instructions.
  
  
  

For better assistance in this issue, please post your query in TechNet forum.

Technet forums - Windows 10 IT Pro

Additional Information

Memory Demand in Windows 10

Additional Information

PDC10: Mysteries of Windows Memory Management Revealed: Part Two



Hope it helps.

 

Memory management

Hi Daniel,

Missing/outdated driver and error with your PC memory (RAM) are some of the factors that may cause the blue screen due to Memory Management error. To effectively assist you with your concern, we'd like to ask the following:

• Have you made any recent changes on your device prior to your concern?
• What are other troubleshooting steps have your performed to resolve your concern?

While checking for the dump file that you've sent, we suggest that you run a full scan on your device using the
SFC and DISM command to automatically fix any corrupted files that my possibly trigger the error. The steps can be found on this

Wiki Article created by community MVP ZigZag3143. Once you're done, check if the issue persists.

We'll appreciate if you can send us an update.