cancel
Showing results for 
Search instead for 
Did you mean: 

BSOD: stopcode MEMORY MANAGEMENT

dusank
Level 7
My PC crashes at least once daily and I get a Windows 10 Pro BSOD with the error message stopcode MEMORY MANAGEMENT.

I have run windows memory diagnostics for several hours but no errors were found with my memory.

Any idea how to diagnose the source of this problem and how to solve it?
6,750 Views
8 REPLIES 8

MeanMachine
Level 13
unable to address your issue due to access denial
We owe our existence to the scum of the earth, Cyanobacteria

My System Specs:

MB:ASUS ROG Crosshair VII Hero/WiFi GPU:EVGA GTX 1080 sc PSU:Corsair AX-1200i
CPU:
AMD R7 2700X Cooler: Corsair Hydro H115i Case: Corsair Carbide 780t

Memory:G.Skill TridentZ F4-3200C14D-16GTZR SSD:Samsung 500GB 960 EVO M.2


[/HR]

MeanMachine wrote:
unable to address your issue due to access denial


Not sure what you mean by this.

MeanMachine
Level 13
There is a Forum bug denying access to some threads, Why this is happening, well we don,t know and it's been happening for a while.
I tried to respond with information for you without success. There is a thread Äccess Denial".
We owe our existence to the scum of the earth, Cyanobacteria

My System Specs:

MB:ASUS ROG Crosshair VII Hero/WiFi GPU:EVGA GTX 1080 sc PSU:Corsair AX-1200i
CPU:
AMD R7 2700X Cooler: Corsair Hydro H115i Case: Corsair Carbide 780t

Memory:G.Skill TridentZ F4-3200C14D-16GTZR SSD:Samsung 500GB 960 EVO M.2


[/HR]

raju2529
Level 7
share your memory dump files to online storage and paste the liNk here1. I will analysis the cause of BSOD
Intel i5 7200U_ Nvidia 940MX _Windows_11_Enterprise_64bit_22H2_buildno_22621.754

raju2529 wrote:
share your memory dump files to online storage and paste the liNk here1. I will analysis the cause of BSOD


Thank you very much for your help.

I try to upload the dump file for you but I cant find the file "c:\Windows\MEMORY.DMP".

My startup and recovery options are set to "Automatic memory dump", dump file "%SystemRoot%\MEMORY.DMP".

My "c:\Windows\Minidump" folder is also empty.

I've updated to the latest Crosshair VI Extreme BIOS (7003), loaded Stilts Safe 3200MHz Settings leaving the CPU non-OCed and have run AIDA64 System Stability Test with only "Stress System Memory" turned on.

After very few minutes the SST goes red with the error message "Warning: Hardware Failure Detected! Test Stopped".

Does this imply bad memory sticks? Shall I RMA?

hereric
Level 7
dusank wrote:
My PC crashes at least once daily and I get a Windows 10 Pro BSOD with the error message stopcode MEMORY MANAGEMENT.

I have run windows memory diagnostics for several hours but no errors were found with my memory.

Any idea how to diagnose the source of this problem and how to solve it?


Google "1usmus Dram Calculator"

download version 1.5.1. go to the "memory benchmark" tab, set for max memory and run that to 10000%.

If you have any errors, your memory is not stable. windows memory diagnostic isn't really stressful enough to catch all errors.

hereric wrote:
Google "1usmus Dram Calculator"

download version 1.5.1. go to the "memory benchmark" tab, set for max memory and run that to 10000%.

If you have any errors, your memory is not stable. windows memory diagnostic isn't really stressful enough to catch all errors.


I have downloaded 1usmus 1.5.1 from various sources but when I try to run the benchmark I always get an exception:


************** Exception Text **************
System.MissingMethodException: Method not found: 'UInt64 HCIMemTestController.Controller.GetFreeRam_cut()'.
at Ryzen_DRAM_Calculator_1._5._0.MainForm.MEMbench_Run_BTN(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
Ryzen DRAM Calculator 1.5.0.6
Assembly Version: 1.5.0.6
Win32 Version: 1.5.1.0
CodeBase: file:///C:/Tools/Ryzen%20DRAM%20Calculator%201.5.1/Ryzen%20DRAM%20Calculator%201.5.1.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MetroFramework
Assembly Version: 1.2.0.3
Win32 Version: 1.2.0.3
CodeBase: file:///C:/Tools/Ryzen%20DRAM%20Calculator%201.5.1/MetroFramework.DLL
----------------------------------------
HCIMemTestController
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Tools/Ryzen%20DRAM%20Calculator%201.5.1/HCIMemTestController.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.DataVisualization/v4.0_4.0.0.0__31bf3856ad364e35/System.Windows.Forms.DataVisualization.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3362.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:





When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Any idea how to overcome this?