Bsod memory management error

Toggle sidebar Toggle sidebar
P

Papa

Junior Member
May 14, 2016
22
0
6
The computer reboots, after giving this message, a couple of times a day. Almost always while my son is playing a game on Steam. I say "almost always" because it's happened to me a couple of times in last week or so. I remember I was just opening File Manager when it happened once. Another time, I was just reading a forum and out of the blue, pow, it happened.

I tried a few things - made sure all my drivers were up to date, uninstalled any AV, and ran a couple of memory testers (which found nothing) - but am still getting the error(s) a couple of times a day. <--- I used the plural for "error" because every so often when it happens, it'll say something other than "memory management". I can't remember what though.

The only thing I can think of now is to start randomly replacing parts. I was hoping I could get some advice from you guys before I start to do that.

My system:
i5-4590 Haswell
MSI Z97 PC Mate motherboard
Crucial Ballistix 16GB DDR3 (though we only have 1 stick installed)
EVGA 100-B1-0500-KR 500watt PS
Corsair 480GB SATA 3 hardrive
Gigabyte GeForce GTX 960 4BGB WINDFORCE
Lite-on DVD
CM keyboard/mouse

Thank you,
Mike
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
What operating system are you using?

My son's Haswell based system I built for him was unstable at first and crashing much like yours is doing.

It turned out to be issues with a Windows 10 update.

You might want to run a program like this before replacing hardware.

http://www.resplendence.com/whocrashed
 
P

Papa

Junior Member
May 14, 2016
22
0
6
That was fast and easy. Here's what Whocrashed found..

[FONT=Segoe UI, Arial]System Information (local) [/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-2JMOHBT
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C: \WINDOWS
Hardware: MS-7850, MSI, Z97 PC Mate(MS-7850)
CPU: GenuineIntel Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8536293376 bytes total


[/FONT]
[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C: \WINDOWS\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 7/16/2016 11:55:28 AM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\071616-4343-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0x1A (0x61941, 0x1A06115A46F, 0xD, 0xFFFFD00021AF6B00)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 7/16/2016 11:55:28 AM GMT your computer crashed
crash dump file: C: \WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61941, 0x1A06115A46F, 0xD, 0xFFFFD00021AF6B00)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 6/30/2016 11:54:09 PM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\063016-3734-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x1427A0)
Bugcheck code: 0x1A (0x61941, 0x1C0881847D8, 0xD, 0xFFFFD00024AFFB00)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 6/29/2016 1:54:43 AM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\062816-3671-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x1427A0)
Bugcheck code: 0x1A (0x61941, 0x621844D8, 0xD, 0xFFFFD00022E2DB00)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 6/27/2016 5:37:25 AM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\062716-3718-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x96012)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800216B6012, 0xFFFFD000258C8B40, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 6/24/2016 11:44:04 AM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\062416-9093-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x1427A0)
Bugcheck code: 0x4E (0x99, 0x4105B0, 0x3, 0xC000000000D5889)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 6/23/2016 7:05:41 PM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\062316-8640-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x1427A0)
Bugcheck code: 0xF7 (0x2A8027A7D860, 0x2CCFB9EF1569, 0xFFFFD3304610EA96, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_OVERRAN_STACK_BUFFER[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 6/23/2016 6:04:15 PM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\062316-8500-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x1427A0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680001147B8, 0xC02000021F5A3867, 0xFFFFE0012D1E0AB0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 6/21/2016 10:15:21 PM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\062116-3890-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms2.sys[/FONT] (0xFFFFF8011145ABC8)
Bugcheck code: 0x50 (0xFFFFE00C390BFED8, 0x0, 0xFFFFF8011145ABC8, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 6/19/2016 7:17:34 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061916-3640-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]netio.sys[/FONT] (0xFFFFF80066BB3A16)
Bugcheck code: 0xD1 (0xFFFFE0011E022350, 0x2, 0x0, 0xFFFFF80066BB3A16)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\netio.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]13 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.[FONT=Segoe UI, Arial][/FONT][/FONT]
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
Those look like the errors I experienced. My issues were Windows 10 related crashes. I swapped in a hard drive, RAM, CPU, motherboard, and PSU from other computers, and still had the same crashes. I checked out many different forums, and there were quite a few posts of people experiencing the same issue after a Windows 10 update. None of my Skylake machines were affected.

Are you up to date on Windows updates? Are you running the RAM in XMP (Ovetclocked)? Is the RAM you are using certified to work with your motherboard (by the motherboard manufacturer or RAM manufacturer)?
 
Last edited:
P

Papa

Junior Member
May 14, 2016
22
0
6
I've seen Windows update automatically, so I assume it's up-to-date.

I'm not overclocking the memory at all. I simply popped it in and ran it as-is.

As far as the memory sticks/PSU ...
We've tried both sticks of memory by themselves and have the same issues with both of them. I guess that leaves the PSU to replace first?

Would it do any good to put the memory stick in a different slot?
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
Papa said:
I've seen Windows update automatically, so I assume it's up-to-date.

I'm not overclocking the memory at all. I simply popped it in and ran it as-is.

As far as the memory sticks/PSU ...
We've tried both sticks of memory by themselves and have the same issues with both of them. I guess that leaves the PSU to replace first?

Would it do any good to put the memory stick in a different slot?
Click to expand...

Sometimes. Your motherboard manual will tell what slots to install your RAM in.

List the full model number of your RAM. Maybe you bought a set that isn't on your motherboard's QVL or tested by Crucial to work properly with your motherboard.
 
P

Papa

Junior Member
May 14, 2016
22
0
6
Crucial Ballistix Sport 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model BLS2KIT8G3D1609DS1S00

...from Newegg.




I'm not sure how to find out if these are compatible with the motherboard.
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,545
236
106
A bad driver can you this. Are all drivers certified for Windows 10? Also look at Windows update history and see if it updated a driver recently.

Or your system running the memory at an unsupported speed. CPU-Z will tell you what the system is running the memory at, and what it's rated for. A bad slick of RAM is possible, but rare. Two bad sticks at the same time is almost unheard of. Run memtest once you are sure the sticks are running at a supported speed.

The fact that you are getting almost exactly the same error every time leads me to believe it is a driver. A bad PSU or bad stick of RAM would give you varying issues, including crashes caused by different errors and the occasional crash with no blue screen at all.
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
Papa said:
Crucial Ballistix Sport 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model BLS2KIT8G3D1609DS1S00

...from Newegg.




I'm not sure how to find out if these are compatible with the motherboard.
Click to expand...

I don't see it listed on MSI's QVL list:

https://us.msi.com/Motherboard/support/Z97-PC-Mate.html#support-mem

Crucial's website uses different numbers for their ram so you can't cross-reference and buy it from a retailer's website:

http://www.crucial.com/usa/en/advisor

I would contact Crucial and ask them if the RAM is compatible with the motherboard. They would be able to see if your RAM model number matches their internal product code they display on their advisor site.

Outside of that, is the BIOS flashed to the most current version? That's where they usually add and fix RAM support and issues. Their last version is 4.B released on 2-22-2016.

https://us.msi.com/Motherboard/support/Z97-PC-Mate.html#support_download
 
P

Papa

Junior Member
May 14, 2016
22
0
6
Here's the number off the memory chip ...
bls8g3d1609ds1s00



I.m going to check the bios now.
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,545
236
106
Don't get too caught up on the memory listing. The modules listed means they are the ones MSI has tested, not the only ones that will work. MSI is not going to waste time/money testing every single memory module that enters the market.
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
Papa said:
I just checked the bios...

Version: 4.11
build date 2/16/16
Click to expand...

That is the latest one, even though it called 4.B on their website for some reason. Prior to their last two BIOS releases, they numbered it 4.9

I would contact Crucial or try a stick of ram that has been certified to work on the board. Each memory manufacturer has a memory finder tool on their website that shows which RAM will work on your board. My suggestion would be to go that route first after contacting Crucial for support on your current RAM.

Some people believe all RAM works perfectly fine on all boards. I am not one of those people. All you have to do is look at BIOS updates from the motherboard manufacturers that list things like "Improve RAM compatibility" and "fix XMP compatibility".
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
One thing I forgot to ask you was this a new system that was built that always had these crashes, or was this a system that was updated from Windows 7 or 8, and started having problems with Windows 10?
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
I personally think it is most likely a Windows 10/driver issue or a RAM compatibility issue.

One is easy to rule out by trying certified RAM, or by manually tinkering with the RAM settings/voltage in your BIOS.

Here is just one of the many threads around where people are having the 'memory corruption' crashes. You will notice in the thread people keep entering it with the same issues.

http://www.tomshardware.com/answers/id-1811018/memory-management-bsod-memtest-errors.html

For Windows 10 specifically:

https://www.google.com/search?q=mem...TSYKHfHUBhQQrQIINSgEMAQ&biw=360&bih=518&dpr=4
 
Last edited:
P

Papa

Junior Member
May 14, 2016
22
0
6
Update: Made a couple of changes in the Bios.

I read about someone having a similar problem and the advice given to him was to enable something called 'XMP' (I think that's what it was called). So I enabled it. I have no idea what it is.

Also in the Bios, I changed the Dram frequency from 'auto' to '1600'.

I have no idea if which, if either, did it, but the computer no longer reboots - 3 weeks now.
 
UsandThem

UsandThem

Elite Member
May 4, 2000
16,068
7,380
146
Papa said:
Update: Made a couple of changes in the Bios.

I read about someone having a similar problem and the advice given to him was to enable something called 'XMP' (I think that's what it was called). So I enabled it. I have no idea what it is.

Also in the Bios, I changed the Dram frequency from 'auto' to '1600'.

I have no idea if which, if either, did it, but the computer no longer reboots - 3 weeks now.
Click to expand...

XMP is a automatic memory 'overclocking' setting, or Intel Extreme Memory Profile, so enabling it wouldn't help with your crashes. That would be like experiencing crashes while running a CPU at default settings, but it works when overclocking it.

http://www.intel.com/content/www/us/en/gaming/extreme-memory-profile-xmp.html

Setting the RAM speed from 'auto' to a fixed speed could possibly make a difference if using non QVL RAM.

It's hard to say for sure as there have also been some major Windows 10 updates as well. At least the crashes are now gone.

But just a recommendation for the future: Before changing settings in your BIOS, you might want to know what they do before changing them. Some settings in there can have some very bad results, and can prevent you from even being able to boot into Windows all together.
 
Last edited:
denis280

denis280

Diamond Member
Jan 16, 2011
3,434
9
81
Bingo.Also in the Bios, I changed the Dram frequency from 'auto' to '1600'.
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom