How to Fix the Memory Management Error in Windows 10

“Memory_Management” is one of the most unhelpful phrases that Microsoft suggests you search for if you run into a BSOD (Blue Screen of Death) error while running Windows 10. So, how do you fix the memory management issue?

How to Fix the Memory Management Error in Windows 10

The first step in fixing any computer problem is isolating the issue’s source, so you know what to fix. With Window’s ominous errors, such as this one, it may be challenging to know where to begin.

Basic troubleshooting is essential to finding your memory management error. Let’s take a look at what you can do to get this fixed.

Step 1: Run Windows 10 in Safe Mode

The first thing you should do is launch Windows 10 in safe mode with basic drivers. This action allows you to check whether you still receive the BSOD Memory Management error. Essentially, this shuts down any processes the computer doesn’t need. If the memory management error ceases, you’ll know it isn’t hardware but rather something in the software, such as a patch in an update or a driver. If the problem still occurs, you may need to replace some faulty hardware. To boot your system in Safe Mode, follow the steps below.

  1. Use the Win+R keyboard shortcut and type “msconfig without quotes, then hit “enter.”
  2. Tap the “Boot” tab in the upper section of the screen.
  3. Select “Safe Boot.”
  4. Choose “Minimal” from the list of boot options.

Step 2: Run Windows Memory Diagnostic

The Windows Memory Diagnostic tool will test your SDRAM and report any problems it finds—if any at all. This step should use Safe Mode to prevent the BSOD issues you experience. However, this requirement is after affirming that your PC worked correctly in Safe Mode using Step 1 above.

  1. Press the “Windows + R” keyboard combination and type “mdsched” without quotes, then press “Enter” or click “OK.”
  2. Select the option to restart and run a check for SDRAM problems.

Upon restart, you will receive a report letting you know if you’re having a memory issue.

As the name suggests, the memory management error relates to the computer’s memory, which can be a physical problem with the installed RAM. The Windows Memory Diagnostic Tool can help discover if this is the root of the problem.

When Windows restarts, it will tell you if there is something wrong with your memory. If there is, then you’ll have to either replace the RAM yourself or send back your computer if it’s under warranty.

Step 3: Run SFC Scanner

SFC Scanner is a Microsoft tool for detecting various problems with your system, and running it seems to have solved some people’s memory management woes. Once again, this step should also be performed in Safe Mode like Step 1 and Step 2 above.

  1. In the Cortana search bar, type “cmd” without quotes, then click on “Run as administrator” in the right panel for the Command Prompt. You can’t use the right-click Start Menu option anymore since Powershell replaced Command Prompt.
  2. Once the Command Prompt opens, type “sfc/scannow” without quotes and press “Enter.”

SFC Scanner will now run through your system, seeing if it finds any disk errors to fix. Even if it doesn’t find anything, some users have found that their computers play nicer after a full scan.

Note: It is best to perform two or three rounds of scanning since the process doesn’t always detect anything on the first attempt or fixes something else and needs to find more issues.

Step 4: Look for Software Problems

Software problems are a little more challenging to pin down. Still, if the memory management error is a relatively new phenomenon, you could try undoing some of your recent software installations to see if it fixes the problem.

Specific pieces of software often link to memory management errors. You can try disabling and re-enabling newer software to see if that fixes the BSOD, or you can reload Windows 10 entirely (although this is a nuclear option).

Isolating and correcting a software issue or even a corrupted file can take a while, but it’s certainly worth it if you’re not entirely sure you’re experiencing a hardware failure.

Step 5: Update Your Graphics Card Drivers

One of the most common causes of the memory management error in Windows 10 is outdated or broken graphics card drivers. This scenario makes sense, especially since the graphics card has memory too. If you’re not running the latest version, try installing the newest available.

If you already have the latest drivers, try the “uninstall/reinstall” method. Sometimes, a driver is broken or corrupt but goes undetected. The drivers you need will depend on your graphics card, of course. Windows 10 will be able to tell you what you have in your system, but it’s likely to be onboard Intel graphics or something from Nvidia or AMD. External video cards have more memory than onboard graphics, and they are more prone to overheating.

Visit the website of the manufacturer and download any updates to get your system working correctly again.

Step 6: Upgrade Your PC’s Hardware

Depending on the results of your troubleshooting adventures, it may be time to upgrade some of your system’s hardware. As software and PC technology progress, so does hardware requirements.

Before rushing out to buy new hardware, check to ensure that everything in the case is seated correctly. Perhaps you recently moved your machine, and something came loose, or your hardware could use a thorough cleaning.

If it’s a machine that you’ve built or one that is out-of-warranty, it’s time to look for new components to get your computer up and running again. It may be an opportunity for a new graphics card, or you may need more RAM. Whatever the case, if you’ve tried everything above and the issue persists, it’s likely hardware-related.

7 thoughts on “How to Fix the Memory Management Error in Windows 10”

Avatar Larry West says:
Getting repeated (1-2 times per week) BSOD SYSTEM_SERVICE_EXCEPTION errors with repeated references to igdkmdnd64.sys which is a graphics driver. Have performed the steps in this great article, though sometimes with Dell tools rather than the ones suggested. Everything up to date and never any memory or other faults found.

The System Information Hardware | Conflicts/Sharing tool reports one IRQ, one I/O Port, and two memory conflicts and one of these memory conflicts involves the Intel Iris Xe MAX Graphics and this adapter uses the igdkmdnd64.sys driver which is being reported with the BSOD.

Thanks in advance for any insights you can provide and I really appreciate the great resources you provide here.

Avatar John says:
What total Bollocks! The problem comes down to the lowest common denominator as awlays, Microsoft – heres why!

I have a Coffee Lake i5(K) Gaming rig and even at standard clock speed with 32Gb on Ram and running only 2 programs I get freeze ups, memory messages, address messages or App windows that are whited out and frozen! In particular when trying to play games on steam or transcode videos with handbrake I get crashes, memory adressing messages or restarts.. and guess what,,, I also have a second rig.. a Haskell i7(k) and again at standard clock speeds the same crap happens!
Here’s where we get the “ecpert” weighing in… “Check your Graphics card, hardware etc,,,) The i5 has an AMD Radeon RX 5800 on board and the i7 a GTX750Ti… Lowest common denominator again… guess who?

So… Both machines.. recently serviced, re pasted, the i5 is liquid cooled where the 17 has a more than adequate CPU fan and temperatures on both machines are well within safe limits

Ran Memtest x86 on both Machines, passed with flying colours
Ran sfc /scannow again both perfect
ran chkdisk… again no issues
updated the bios and reset optimalto troubleshoot
both machines bang up to date

– now, heres the thing I forgot to mention,,, I run DUAL BOOT HACKINTOSHES on both machines

tried for 3 days to transcode one video on either machine with handbrake… every time failed! tried playing fishing planet on steam or borderlands 3 on the i5 (AMD) machine and it regularly crashes out wo the white app screen mentioned.. or throws up memory access violation messages,,, THis machine remember has 32 GB ram installed and can barely run one program!

On Mac I have NEVER had this issue and can open several apps at one time – currently have around 20 open and no issues whatsoever. I never get the crashes and never get memory access bullshit! Furthermore I am now into my 7th video transcode without so much as a flicker

So… Exact same hardware…. Same Video card (but using macs native amd support drivers). The ONLY difference here is the operating system!

Winblows… TOTAL B-O-L-L-O-C-K-S!!!!

The support is even worse… more often than not some programmed robot from bangalore… with those utterly useless Microsift MVP credentials… about as much use as a tit on a fish!

So.. anyone got a RATIONAL exlanation why this is only happening on windows, regardless of what graphics card and with both Machines in perfect health?

Try updating YOUR drivers and running chkdsk in administrator mode – lol!

I suppose resetting both machines will be the next lightbulb or gem suggestion… and then what?,,, lost time (plenty of), lost apps and dame saves as well as other user files,,, to come cack to the same BS! On mac you can clone perfect copied and restore the lot in a few hours (if that) without losing a single thing!

Avatar abdulwahed says:
I had the same problem, and the solution is to go to device management and check for the PCI memory
control is known to your device if not you need to download the drive from the other places manually
,I used easy drive to do that
Avatar Red Rhino says:
Thanks, it fixes it a bit, doesn’t get the blue screen as much now
Avatar Michael Benjamin R. Baui says:
My device detected that there is no problem but still showing the blue screen.
Steve Larner Steve Larner says:
The article was updated in November and recently in January. Try out the new procedures.
Avatar Ulises Gutierrez says:
Useless advice, cant even boot to do that.
Steve Larner Steve Larner says:
The article was updated back in November and more recently, in January. Try following the new steps.
Avatar KEN WINGER says:
ok tried all the above items, except for uninstall and install video drivers…is this my last option?
Steve Larner Steve Larner says:
The article was updated back in November and now, in January. Try the new steps and procedures, and then let us know how it went. The last option is almost always replacing hardware.

Leave a Reply

Your email address will not be published. Required fields are marked *


Disclaimer: Some pages on this site may include an affiliate link. This does not effect our editorial in any way.

Todays Highlights
How to See Google Search History
how to download photos from google photos