Share via

How to Fix memory_management BSOD On New PC

Anonymous
2020-01-04T19:24:01+00:00

I originally posted here trying to fix this issue on my PC. Since I found a solution that worked for me, I figured I would sum it up for anyone else having the same problem.

If you are having memory_management BSODs on a new PC, I would highly recommend trying these steps before replacing your RAM. It may not actually be because your RAM is faulty, and this will save you a lot of trouble if it works.

  1. (Optional) Update your motherboard's BIOS. I don't think you have to do this step for this solution to work, but I did it before doing the next steps and it may have contributed towards fixing the problem.
  2. Run the Windows Memory Diagnostic Tool. I just did a basic test with one pass. If you get any errors, then updating the BIOS didn't fix the issue.
  3. Reboot your computer and go into EUFI setup (F2 on my motherboard)
  4. Check and change the voltage that is being supplied to your RAM. You will need to look up the recommended voltage for the RAM you have. Mine was supposed to run at 1.35 V, and my motherboard was only supplying 1.2 V. This is what ended up fixing the blue screens for me.
  5. (Recommended) Make sure that your motherboard is running your RAM at the proper MHz. Mine was running at 2400 MHz instead of the 3200 MHz my RAM actually supports. After increasing the voltage, I was getting a lot of lag spikes. Changing the MHz that my RAM was running at fixed that issue.
  6. After doing those steps, run the Memory Diagnostic Tool again. If you don't get any errors, the BSODs should be fixed.
  7. If you are still getting errors when running the Diagnostic Tool after doing the above steps, it is probably because of faulty RAM. I would try getting it replaced and see if that fixes the issue.

Those are all the steps I followed that fixed the memory_management BSOD for me. Hopefully, it also works for you.

Below is my original post:

I just built a new computer the other day. It is my first custom build, so I was very excited to have it done. Everything went well for the first few hours of use, but then I encountered a blue screen. I thought maybe it was just a one-time thing, but over the past few days, they have become more and more common, to the point that they now occur almost every 5 minutes. There are a few different BSODs that I keep getting over and over:

pfn_list_corrupt

irql_not_less_or_equal

system_service_exception

memory_management

Of the four, system_service_exception is by far the most common, and memory_management is a new one that just happened for the first time a few minutes ago. I have tried everything to fix these, including making sure I have all my drivers up to date, making sure I have completely updated windows, factory resetting windows, and even completely wiping the HDD and SSD and reinstalling Windows from scratch, but none of this seems to stop them from happening. The one thing I haven't tried yet is updating my motherboard's BIOS. Would doing that potentially fix these problems or not?

One other thing that might be helpful to know: I am currently running the Windows Memory Diagnostics Tool since I read that I should try it to diagnose these blue screens, and it says "Hardware problems were detected. To identify and repair these problems, you will need to contact the computer manufacturer." Does this mean there could be an issue with my RAM or one of my hard drives?

I would greatly appreciate any help that can be provided since I have no idea what to do at this point to fix it. Nothing I've found online to try seems to have worked.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

21 answers

Sort by: Most helpful
  1. Anonymous
    2020-01-05T23:17:45+00:00

    Andrew, thanks for trying to help. After my previous memory management BSOD, I ran the chkdsk/r command in command prompt since I read online that it was a potential fix for that BSOD. I have since then not gotten any more BSODs after over an hour and a half of use, which is good considering they were happening every 5-10 minutes. Maybe this fixed the problem, but I can't tell for sure yet. If I do get another BSOD though, I will make sure to follow the steps you provided. For now though, I am just going to use the computer normally and see what happens.

    Edit: Also, I have already restored the BIOS to the defaults after I did the BIOS update before. I have also checked several times to make sure I have all the updated drivers installed for all my components, so I don't think that is contributing to the issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. DaveM121 888.7K Reputation points Independent Advisor
    2020-01-04T19:54:54+00:00

    Okay, will be here . . .

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-01-04T19:53:58+00:00

    Okay. I'm in the middle of a motherboard BIOS update right now, but will do that as soon as it finishes.

    Was this answer helpful?

    0 comments No comments
  4. DaveM121 888.7K Reputation points Independent Advisor
    2020-01-04T19:45:42+00:00

    Hi EJP619 to diagnose the underlying issue, I need to analyse your Mini-dump file(s):

    Open Windows File Explorer

    Navigate to C:\Windows\Minidump

    Zip up the contents of that folder

    If you have problems zipping those files, copy them out onto your Desktop and zip them from there

    Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

    Then post a link here to the zip file, so we can take a look for you . . .

    Was this answer helpful?

    0 comments No comments
  5. Neil D 33,235 Reputation points Volunteer Moderator
    2020-01-04T19:36:21+00:00

    I was going to suggest a bios update, check the motherboard manufacturers website and see the reason for the latest update. (or the ones since the version you have)

    If you have more than one memory module then test one at a time. But you could also just try extracting the module/s and re-seating them, then run the test again.

    Was this answer helpful?

    0 comments No comments