BSOD Memory_Management

  1.    09 Apr 2018 #1

    BSOD Memory_Management


    I don't know what happened. I just built a new PC and did a fresh install of windows, everything was running fine for about a week and all of the sudden google chrome started not being able to load webpages, asking me to reload every page then I just got a random BSOD Memory_management and then I couldnt start up for more than 1 minute without a BSOD.So I ran a windows memory diagnostic which immediately showed that there was a "hardware error call the manufacturer" or whatever so I opened up my case and removed one of the RAM sticks and then started up the computer played around with it and had no google chrome errors anymore and I could actually use the PC without a BSOD. Ran a mem diag on that one stick in the slot it's always been in and it showed no errors - moved the stick to where the other stick was, no errors again. Removed the stick that has remained in the system and put the one I originally removed in the spot the original one was in and I could not boot the system so I don't think it's the slots on the MOBO but the actual stick of ram itself.

    I tried to use the tool in the BSOD instructions post but it didn't work for some reason I think the minidump files are gone. Just wondering what the problem is - because the RAM is relatively new I issued an RMA and got a replacement anyway but I don't want to make any of the same errors or anything that can harm the new RAM cuz the RMA process is a pain.

    My specs are: i7 8700k @ 4.5ghz - Corsair LPX 16gb @ 3000mhz (xmp profile 1), gigabyte z370xp SLI mobo and a gtx 970 g1 gaming edition.

    i was getting memory_management errors - something about a corrupted PTE has been detected.

    I got one ATTEMPTED_TO_WRITE_READONLY

    Apologize for losing the damn dump files, i just read them in WhoCrashed.....any help would be appreciated
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,752
    64bit Win 10 Pro ver 1809 Build 17763.168 and W10 Insider Build 18290
       10 Apr 2018 #2

    Hello wtfnst,

    It does sound as though the one RAM stick was bad. You should get an exact replacement so just try it and see if you are OK.

    If you want to generate some files for us to look at then put the bad RAM back in and wait for the BSOD. Immediately afterwards I suggest you run the beta10 log collector which you will find at the end of the BSOD posting instructions. This file has to be downloaded and extracted to a folder before you can run it. It will then create a zip file on your desktop which you can upload in a new post for us to look at.
      My ComputersSystem Spec


 

Related Threads
Bsod memory_management in BSOD Crashes and Debugging
I've had multiple BSOD's over the past month or so. I've updated all drivers and still had a BSOD today. I've tried using WinDBG but am not smart enough to use it properly. Any assistance would be appreciated.
BSOD Memory_management in BSOD Crashes and Debugging
I have had periodic BSODs on this PC, perhaps every 30 days. Usually irql_not_less_or_equal This is a new cause. I have tested the memory previously with no errors reported. I have (hopefully) attached the report below. Thanks for any...
Solved Memory_management bsod in BSOD Crashes and Debugging
Hello, I've recently started getting MEMORY_MANAGEMENT BSODs. It feels like it happens anytime my PC starts using more RAM (>6gb) which with everything running happens pretty much after starting all programs I normally use. It might...
Solved BSOD Memory_Management in BSOD Crashes and Debugging
Good evening, I've build a new PC with following hardware: i5 6500 AMD R9 380x (PowerColor) AsRock H170 Pro4 Gskill 16 GB Kit F4-240015D Thermaltake 530 W
Solved Memory_management bsod in BSOD Crashes and Debugging
First BSOD after a while of running fine. This is a new build PC with a clean install of Windows 10. It crashed a lot after installation, then settled down. Today, I'm running a download installer for 9.5GBytes of graphics applications and data....
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 20:22.
Find Us