Page 1 of 6 123 ... LastLast
  1.    12 May 2017 #1
    Join Date : May 2017
    Posts : 28
    Windows 10

    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
    Attached Thumbnails Attached Thumbnails IMG_0482.jpg  
    Frequent BSOD memory_management Attached Files
    Last edited by redlum; 23 May 2017 at 16:06.
      My ComputerSystem Spec
  2.    12 May 2017 #2
    Join Date : May 2016
    Posts : 736
    Windows 10 Pro

    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.
      My ComputerSystem Spec
  3.    12 May 2017 #3
    Join Date : May 2017
    Posts : 28
    Windows 10
    Thread Starter

    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
      My ComputerSystem Spec
  4.    15 May 2017 #4
    Join Date : Jan 2017
    Karlsruhe
    Posts : 730
    Windows 10 Pro




    Frequent BSOD memory_management Diagnostic Test Frequent BSOD memory_management
     RAM TEST

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums



    Note   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.
      My ComputerSystem Spec
  5.    15 May 2017 #5
    Join Date : May 2017
    Posts : 12
    windows 10 ver 1703 ( os 15063.296 )

    do u have two graphic processor ? for example invidia and intel ?
      My ComputerSystem Spec
  6.    23 May 2017 #6
    Join Date : May 2017
    Posts : 28
    Windows 10
    Thread Starter

    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
      My ComputerSystem Spec
  7.    24 May 2017 #7
    Join Date : Jan 2017
    Karlsruhe
    Posts : 730
    Windows 10 Pro

    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.

    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



    Frequent BSOD memory_management Diagnostic Test Frequent BSOD memory_management
     HDD TEST

    Run HDTune to check health and scan for errors.



    Note   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.
      My ComputerSystem Spec
  8.    27 May 2017 #8
    Join Date : May 2017
    Posts : 28
    Windows 10
    Thread Starter

    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.
      My ComputerSystem Spec
  9.    01 Jun 2017 #9
    Join Date : May 2017
    Posts : 28
    Windows 10
    Thread Starter

    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
      My ComputerSystem Spec
  10.    07 Jun 2017 #10
    Join Date : Jan 2017
    Karlsruhe
    Posts : 730
    Windows 10 Pro

    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

    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...
    Last edited by BSODHunter; 07 Jun 2017 at 03:49.
      My ComputerSystem Spec

 
Page 1 of 6 123 ... LastLast


Similar Threads
Thread Forum
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...
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...
BSOD Crashes and Debugging
Solved Memory_management bsod
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...
BSOD Crashes and Debugging
Solved BSOD Memory_Management
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
BSOD Crashes and Debugging
Solved 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....
BSOD Crashes and Debugging
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 04:47.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums