Windows 10: Frequent BSOD memory_management

Discus and support Frequent BSOD memory_management in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello I've been suffering with BSOD since I built my system a year ago and have never been able to solve. Please could someone offer some advice?... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by redlum, May 11, 2017.

  1. redlum Win User

    Frequent BSOD memory_management


    Hello

    I've been suffering with BSOD since I built my system a year ago and have never been able to solve. Please could someone offer some advice?


    • I've been running driver verifier for 48hours.
    • I'm not overclocking
    • I have run memtest multiple times (up to 24hours) and it passed each time
    • I believe all my drivers are up to date.
    • I'm running RAID 1 on two HDDs
    • Main drive is an M2 samsung SSD

    After I setup driver verifier the first time I got a BSOD it didn't write a crashdump. After this I configured my pagefile to be system managed (previously there was no pagefile for C: but it always wrote a dump prior to driver verifier). Today I had a memory_management BSOD.

    I'd really like to be methodical about this and figure it out but my own investigations have come up short. I've been using the guides on this site and they have got me this far but I've I'm stuck. Any help offered will be greatly appreciated.

    Many thanks
    George

    edited: To include memtest result and latest minidumps

    Attachment 134622

    :)
     
    redlum, May 11, 2017
    #1

  2. Multiple BSOD on new Ryzen build

    I also got a bunch of BSODs on my new Ryzen build:

    *most frequent* MEMORY_MANAGEMENT

    *second most frequent* IRQL_NOT_LESS_OR_EQUAL

    PAGE_FAULT_IN_NONPAGED_AREA

    ATTEMPTED_WRITE_TO_READONLY_MEMORY

    DPC_WATCHDOG_VIOLATION

    I tried everything I could to troubleshoot. Turns out the culprits are not only Onedrive, but also Dropbox. Enabling either one will send my PC straight to BSOD at Windows startup. Do you think the windows update you mentioned also
    fixes dropbox?
     
    Ichigomiruku, May 11, 2017
    #2
  3. I-Sheng Win User
    Sporadic MEMORY_MANAGEMENT BSOD

    Hi,

    Been encountering sporadic, but frequent, BSOD with identifier MEMORY_MANAGEMENT for the past week or so.

    Three of them resulted in completely Windows failing to load completely (could not even enter safe mode).

    I have noticed that the BSOD is not specific to any application.

    One of the minidumps (second_bsod_070617-5609-01) in the link below reported CRITICAL_PROCESS_DIED instead of MEMORY_MANAGEMENT, with the same crash address. Including it just in case it reveals something the others do not.

    The msinfo output, three most recent minidumps and the full memory dump (the most recent BSOD, with corresponding minidump named third_bsod_070717-9843-01) can be found here:

    Public

    Any pointer on what is causing these crashes is appreciated.
     
    I-Sheng, May 11, 2017
    #3
  4. Plankton Win User

    Frequent BSOD memory_management

    What's your complete hardware configuration? How many (total) drives are you using? What drives go to what? Is this software RAID or hardware RAID?

    Note: using software RAID is not truly a RAID setup. To run a true RAID setup you would need a RAID PCIe card which are a bit expensive. Software RAID is notorious for glitches and erratic behavior.
     
    Plankton, May 11, 2017
    #4
  5. redlum Win User
    Hi there, interesting...yes, in that case it's a software RAID using the motherboard's Intel Controller.

    Primary drive is Samsung SM951 M2 256gb (non RAID)
    The RAID 1 drives are 2x 1tb Western Digital Blue

    Processor: 5820k
    Motherboard: Asus X99-S (latest BIOS)
    Ram: Corasair 16gb DDR 2133MHZ
    PSU: Seasonic SS-650RM
    GPU: Nvidia 950
    OS: Windows 10
    Other: External USB DVD drive.

    Thanks
     
    redlum, May 11, 2017
    #5
  6. Frequent BSOD memory_management [​IMG]
    Diagnostic Test
    Frequent BSOD memory_management [​IMG]
    RAM TEST

    Frequent BSOD memory_management [​IMG]
    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums


    Frequent BSOD memory_management [​IMG]



    Frequent BSOD memory_management [​IMG]
    Note MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

    Make a photo of the result and post it.
     
    BSODHunter, May 14, 2017
    #6
  7. javadth1 Win User
    do u have two graphic processor ? for example invidia and intel ?
     
    javadth1, May 14, 2017
    #7
  8. redlum Win User

    Frequent BSOD memory_management

    I have updated my OP to include the latest dumps plus photo of memtest pass after 19 passes.

    re: Graphics - no there is only the NVIDIA 950; no onboard/integrated graphics.

    Thanks
     
    redlum, May 23, 2017
    #8
  9. There are corruptions on your hard disks. The cause could be the disks itself or a problem with your Raid 1. Please check all the raid settings in the BIOS. Maybe theres a newer BIOS version available. The BSOD dumps show MEMORY_MANAGEMENT memory_corruption at every crash. There are a bunch of errors in the windows eventlog which show u that u have an problem with the disks or the RAID. If u are using software raid then please check all settings in the specific application. U should do also check the harddisks itself.

    Here are the errors from eventlog:
    Code: 2017-05-08T10 18:42.907 Error: The file system structure on volume F: cannot be corrected.Please run the chkdsk utility on the volume F:. 2017-05-08T10 18:42.907 Error: The file system structure on volume F: cannot be corrected.Please run the chkdsk utility on the volume F:. 2017-05-08T10 18:42.907 Error: The file system structure on volume F: cannot be corrected.Please run the chkdsk utility on the volume F:. 2017-05-08T10 18:42.989 Error: The file system structure on volume F: cannot be corrected.Please run the chkdsk utility on the volume F:. 2017-05-08T10 18:42.989 Error: The file system structure on volume F: cannot be corrected.Please run the chkdsk utility on the volume F:. 2017-05-08T10 18:43.656 Error: A corruption was discovered in the file system structure on volume WD. 2017-05-08T10 18:50.128 Error: A corruption was discovered in the file system structure on volume WD. 2017-05-08T10 18:50.268 Error: A corruption was discovered in the file system structure on volume F:. 2017-05-08T10 20:18.570 Error: A corruption was discovered in the file system structure on volume WD. 2017-05-08T10 20:18.733 Error: Volume F: (\Device\HarddiskVolume5) needs to be taken offline for a short time to perform a Spot Fix. Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-08T10 21:06.417 Error: Volume F: (\Device\HarddiskVolume5) needs to be taken offline for a short time to perform a Spot Fix. Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-08T10 23:03.940 Error: A corruption was discovered in the file system structure on volume D:. 2017-05-08T10 24:19.754 Error: Volume D: (\Device\HarddiskVolume5) needs to be taken offline for a short time to perform a Spot Fix. Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-08T10 25:03.537 Error: Volume D: (\Device\HarddiskVolume5) needs to be taken offline for a short time to perform a Spot Fix. Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-08T10 26:46.855 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-08T10 26:46.879 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-08T10 26:46.879 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-08T10 26:46.879 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-08T10 26:46.879 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-08T10 26:49.042 Error: Volume D: (\Device\HarddiskVolume5) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-08T10 26:49.042 Error: A corruption was discovered in the file system structure on volume D:. 2017-05-08T10 27:20.038 Error: A corruption was discovered in the file system structure on volume D:. 2017-05-08T10 28:03.104 Error: Volume D: (\Device\HarddiskVolume5) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-08T10 44:00.006 Error: A corruption was discovered in the file system structure on volume D:. 2017-05-08T12 02:45.168 Error: Volume D: (\Device\HarddiskVolume5) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-11T21 03:47.201 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-11T21 03:47.207 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-11T21 03:47.225 Error: Volume D: (\Device\HarddiskVolume5) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-11T21 03:47.225 Error: The file system structure on volume D: cannot be corrected.Please run the chkdsk utility on the volume D:. 2017-05-11T21 03:47.225 Error: A corruption was discovered in the file system structure on volume D:. 2017-05-12T08 37:15.996 Error: Volume D: (\Device\HarddiskVolume5) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.[/quote]
    As u can see that points to the disks with the partitions D: and F:
    Code: DRIVES INFORMATION ------------------ Windows Dir: C:\WINDOWS Drive: C: Free Space: 89.5 GB Total Space: 243.6 GB Model: SAMSUNG MZHPV256HDGL-00000 Drive: D: Free Space: 318.0 GB Total Space: 500.0 GB Model: Intel Raid 1 Volume Drive: E: Free Space: 111.5 GB Total Space: 250.0 GB Model: Intel Raid 1 Volume Drive: F: Free Space: 54.4 GB Total Space: 203.9 GB Model: Intel Raid 1 Volume[/quote]



    Frequent BSOD memory_management [​IMG]
    Diagnostic Test
    Frequent BSOD memory_management [​IMG]
    HDD TEST

    Frequent BSOD memory_management [​IMG]
    Run HDTune to check health and scan for errors.


    Frequent BSOD memory_management [​IMG]



    Frequent BSOD memory_management [​IMG]
    Note It may take some time, but look for signs of any errors or failure.

    You can also run a disk check using chkdsk. Refer to the tutorial for details of how to do this.
     
    BSODHunter, May 23, 2017
    #9
  10. redlum Win User
    Thanks for the analysis BSODHunter,

    HDTune found no errors, and health is "ok" for all disks.

    Chkdsk did make some repairs, though. However I have run that before and theBSOD still continued.

    I have disabled the raid and will see how things get on with just AHCI.
     
    redlum, May 26, 2017
    #10
  11. redlum Win User
    Unfortunately this hasn't gone away with the RAID switched off.

    I'm attaching two recent dumps. One is a Page Fault on fltmgr.sys and the other is the usual Memory_management.

    Thank you in advance for your help/advice.

    DESKTOP-L224S2J-Thu_01_Jun_213040_35.zip
     
    redlum, May 31, 2017
    #11
  12. ok, now, after u switched to AHCI, the errors in windows eventlog are gone. This is good, but the BSOD analysis shows problems with RAM memory OR disk memory again:
    Code: 0x0000001A: MEMORY_MANAGEMENT (1.06.2017 22:28:46) [Windows 10] CAUSED BY: memory_corruption PROCESS: steamwebhelper Usual causes: Device driver, memory, kernel ============================================================================================================== 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA (28.05.2017 14:54:00) [Windows 10] CAUSED BY: FLTMGR.SYS ***** Invalid * Microsoft Filesystem Filter Manager (Windows System File) PROCESS: System Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS[/quote]
    1. Do u have different RAM modules?

    2. Remove Malwarebytes for testing, MBAM is known for beeing very intrusive

    3. Check if there is a new BIOS version for your Mainboard

    4. Check if theres a firmware update for your SAmsung SSD: Tool & Software | Download | Samsung V-NAND SSD

    5. Perform filesystem check:
    Repair Windows Filesystem:

    1. Open an elevated command prompt.
    2. In the elevated command prompt, type these commands below, and press Enter:

    dism /Online /NoRestart /Cleanup-Image /CheckHealth
    dism /Online /NoRestart /Cleanup-Image /ScanHealth
    dism /Online /NoRestart /Cleanup-Image /RestoreHealth
    dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
    dism /Online /NoRestart /Cleanup-Image /AnalyzeComponentStore

    sfc /scannow

    chkdsk %systemdrive% /F /R /X
    fsutil dirty set %systemdrive%

    SFC:
    The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
    DISM:
    If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
    For example, you would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
    CHKDSK:
    Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...
     
    BSODHunter, Jun 6, 2017
    #12
  13. redlum Win User

    Frequent BSOD memory_management

    Hi, thanks again for your replies.

    1. Ram modules are identical and bought in a pack 4x4gb
    2. Malwarebytes is gone
    3. BIOS is the latest
    4. My Samsung SSD is SM951 M2 ACHI MZHPV256HDGL. Apparently as this is OEM there are no official firmware updates for this although I have seen sites with work around. Not sure what to do about this.
    5. I performed all these checks and the system seemd to pass them all.
    As I was uninstalling Malwarebytes (probably coincidence) the computer suddenly restarted. After this initial restart the machine began to restart more and more frequently to the point where it couldn't even get past the bios screen. After leaving the machine off for a while it would make it to windows but eventually it would restart and the frequency of restarts would increase again. Even if I left it in the BIOS it would eventually restart itself.

    I stripped the machine down and decided to replace the PSU ( a gold rated Seasonic) with another (Super Flower gold rated) and this stopped the restarting.

    I was wondering... could an unstable PSU cause the memory management BSODs? It's too early to tell perhaps but after the PSU replacement I received another BSOD "IRQL_NOT_LESS_OR_EQUAL" - I have attached the minidump for this.

    I feel like maybe we're getting close?

    Many thanks
    George

    IRQL_NOT_LESS_OR_EQUAL BSOD:
    061017-10937-01.zip
     
    redlum, Jun 10, 2017
    #13
  14. Ztruker Win User
    Nothing useful in the dump unfortunately.

    What do you have connected to your computer?
    What mouse, keyboard?
    Any USB devices? If so what are they.
    Do you have a knock off Xbox controller?

    What I suggest is to disconnect everything you can and if possible replace the mouse and keyboard with USB connected ones.

    Try running that way and see what happens.

    Also, run dm_log_collector again and upload the zip file. Want to see the latest e3vent log entries.
     
    Ztruker, Jun 10, 2017
    #14
  15. redlum Win User
    Hi ztrucker.

    Currently I only have a usb mouse (Razer) and keyboard (Dell) connected.

    Prior to replacing the PSU a couple of days ago I had an external dvd drive and a Microsoft Wireless Controller (for official xbox gamepad).

    I also had a USB wifi adaptor/dongle attached but replaced that with a Asus PCI-E card when I swapped the PSU.

    Full log collector below for the past two crashes:
    DESKTOP-L224S2J-Sun_11_Jun_212230_16.zip

    Many thanks
    George
     
    redlum, Jun 10, 2017
    #15
Thema:

Frequent BSOD memory_management

Loading...
  1. Frequent BSOD memory_management - Similar Threads - Frequent BSOD memory_management

  2. Memory_Management BSOD

    in Windows 10 BSOD Crashes and Debugging
    Memory_Management BSOD: Hello, I am uploading my most recent crash dump file in hopes that someone who knows more about this than I do can read it and tell me where I should be looking to solve the issue. I also understand if there is not enough information in this file, I am just desperate for...
  3. MEMORY_MANAGEMENT BSOD

    in Windows 10 BSOD Crashes and Debugging
    MEMORY_MANAGEMENT BSOD: Hello all, I have been getting Memory Management blue screens for the past week. The blue screens have some patterns. Upon my initial boot of the computer, I almost always get a bluescreen right after I type in my password and enter into Windows. However, after the restart...
  4. Frequent BSOD when gaming (MEMORY_MANAGEMENT)

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSOD when gaming (MEMORY_MANAGEMENT): Hello, For the past few months I've been getting frequent BSOD, happens mostly when i am gaming but also happens once in a while when just streaming videos or surfing the web. Things i have tried: Ran Memtest86 and Windows memory diagnostic multiple times on each ram...
  5. BSOD Memory_Management

    in Windows 10 BSOD Crashes and Debugging
    BSOD Memory_Management: Estimados, En algunas ocasiones, mientras estamos trabajando con el notebook, nos tira BSOD Memory_Management *** STOP: 0x0000001A (0x00000000000000403,0FFFFF68000040DD8,0xD410000047F14967,0xFFFFF68000031968) Desconocemos exactamente cual pueda ser la causa. Dejo log...
  6. Bsod memory_management

    in Windows 10 BSOD Crashes and Debugging
    Bsod memory_management: 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. 86632
  7. BSOD Memory_management

    in Windows 10 BSOD Crashes and Debugging
    BSOD Memory_management: 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 assistance. 66574
  8. Memory_management bsod

    in Windows 10 BSOD Crashes and Debugging
    Memory_management bsod: 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. At the sime time, I started...
  9. Frequent BSODs 5-10 min after startup. Often Memory_Management ...

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSODs 5-10 min after startup. Often Memory_Management ...: First time post, I'm running a PC (HP Spectre x360) with Windows-10, and I am recently getting BSODs, 5-10 minutes after booting my PC. I've tried running various programs such as CCleaner (to remove temporary files ...), and whocrashed (quick analysis), but l couldn't...
  10. BSOD Memory_Management

    in Windows 10 BSOD Crashes and Debugging
    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...