Memory _ Management BSOD

Toggle sidebar Toggle sidebar
MotivatedMuffin

MotivatedMuffin

Commendable
Jul 30, 2016
14
0
1,510
For the past few months, I've been having this Memory Management BSOD happen occasionally. However it only happens when my PC is under heavy load such as playing games like Battlefield or GTA.

I've tried multiple troubleshooting techniques such as using the sfc /scannow command, memory diagnostic tool and I've even tried completely reinstalling Windows 10. None of this has helped.

Furthermore, when playing these intensive games my hard disk is used so much that it makes weird noises and makes my computer freezes up for a short while and then shortly afterwards I usually blue screen.

I'm not very knowledgeable about issues like this and need help.

Specs:
Motherboard - Gigabyte H81M-H
CPU - i5-4670 @ 3.40GHz
GPU - GTX 750 Ti
Memory - 8GB
OS - Windows 10

Cheers
 
Sort by date Sort by votes
Memory management can be caused by drivers, ram or HDD (as memory includes the page file)

Can you download and run the free version of memtest86 on the ram sticks in PC, 1 at a time. It creates a bootable USB. If you get any errors the stick needs to be replaced.

What brand Hard drive do you have? Try running hdtune on it and check its health

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do :)
 
Upvote 0 Downvote


Thanks for taking time to help me.

I have finished using memtest86 and it found no errors in my ram. I have also used hdtune for my hard drive and it says that its health status is "OK". My hard drive is a Seagate ST1000DM003-1CH1.

Below is the summary from Who Crashed:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 03/04/2017 19:20:05 your computer crashed
crash dump file: C:\Windows\Minidump\040317-21718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x3F, 0x10338, 0xD8952CA0, 0x32DCECC0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 03/04/2017 19:20:05 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x3F, 0x10338, 0xD8952CA0, 0x32DCECC0)
Error: MEMORY_MANAGEMENT
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 02/04/2017 15:49:28 your computer crashed
crash dump file: C:\Windows\Minidump\040217-19765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x3F, 0xA149, 0x9F49, 0x6AAADD49)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 29/03/2017 19:03:33 your computer crashed
crash dump file: C:\Windows\Minidump\032917-24437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x7A (0xFFFFCBC604036A50, 0xFFFFFFFFC0000483, 0x188580880, 0xFFFF8C0806D4A2E0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 28/03/2017 18:38:32 your computer crashed
crash dump file: C:\Windows\Minidump\032817-21718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x3F, 0x391, 0x15F07140, 0xBCFEB31A)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Cheers
 
Upvote 0 Downvote
Can run seatools for windows on hdd: http://www.seagate.com/au/en/support/downloads/seatools/

Memory management blaming the kernel, nothing helpful there
KERNEL_DATA_INPAGE_ERROR is page file, it resides on hdd so see how Seatools goes.

if it comes out clean, Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)

dumps will show us more info and maybe a cause.
 
Upvote 0 Downvote


Seatools hasn't found any problems on my drive.

I have made the mini dumps folder and the link below should show the Memory Dumps folder.

https://mega.nz/#F!47QlFAwJ!8lFXqRXI8DPW3gblSQbUXA

 
Upvote 0 Downvote


My ram is definitely locked in place, I've used memtest and it says no errors, and this Hardware Info program doesn't seem to show my power supply output although I could be using a different program.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom