BSOD: ntoskrnl.exe ntkrnlmp.exe MEMORY_MANAGEMENT PFN_LIST_CORRUPT

[flymolo93]

Hey guys,

My computer is just getting to be about 6 years old, had rare BSODs in its lifetime, maybe twice, but I've reformatted every year or so to try and keep it fresh, open it and clean it out every other month. I've never replaced the processor but added a better heat sink later on, added on ram and replaced the GPU in the past, otherwise same motherboard and power supply since original build. From my research so far in the past 30 minutes or so, many people with similar dmps are being told its hardware-related, so I thought I'd give that information too.

I haven't reformatted the PC now for a year and a bit (been busy), and it has been sluggish in the past few weeks. In the past couple hours, I've had two bluescreens, and after analyzing the .dmp's with BlueScreenView, I see that the last two crashes were caused by ntoskrnl.exe and the Bug Check String was "MEMORY MANAGEMENT for the most recent, and "PFN_LIST_CORRUPT" for the second most recent.

BlueScreenView Screenshot

However, when I run WhoCrashed to analyze the crashdumps, it finds two separate instances for the most recent crash, both with error "MEMORY_MANAGEMENT" but one caused by the module: ntkrnlmp.exe. Here are the WhoCrashed analyses:


On Mon 08/06/2015 5:31:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060815-28891-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41284, 0xE7F5001, 0xCBAB, 0xFFFFF70001080000)
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.
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 08/06/2015 5:31:54 AM GMT 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 (0x41284, 0xE7F5001, 0xCBAB, 0xFFFFF70001080000)
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.
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 08/06/2015 3:50:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060715-46753-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x4E (0x99, 0x1BEBBC, 0x2, 0x1BEBB6)
Error: PFN_LIST_CORRUPT
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 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.


To be on the safe side, I have been running MBAM while writing this, and have cleaned some unwanted-programs.

So guys, any suggestions or insight would be greatly appreciated!
I'm not averse to replacing any parts here, as this computer is pretty dear to me, I'm just hoping it's nothing as serious as the motherboard or processor, and just ram.
Thanks in advance, sorry for the lengthy post.

 

[onichikun]

Realistically this could be hardware OR software (driver) related... but most likely nothing to do with user-land programs.

To verify that it is driver related, download a live CD such as: http://www.memtest.org/ and run this for a few hours (make sure it does a full pass several times). If there are no errors, I would say that your hardware is likely OK.

A bad driver or root kit could be the cause of your issues.

 

[johnbl]

windows keeps a table that maps between what is stored in memory and its place in the pagefile.sys
something corrupted that list.

I would do the following:
clear windows working set, the best way to do that would be to download and run the microsoft tool rammap.exe https://technet.microsoft.com/en-us/library/ff700229.aspx
(use the menu item called empty)

note: this does not actually fix the problem but can reduce the occurance.

I don't see a IO error listed with your bugchecks but you may also want to disable your virtual memory (pagefile.sys) rename the old file and create a new pagefile.sys incase your drive is getting errors accessing the pagefile. google "how to change virutual memory on windows"
http://windows.microsoft.com/en-us/windows/change-virtual-memory-size#1TC=windows-7

if you continue to get problems, either your drive is having problems and you should look at the drive error info. run crystaldiskinfo.exe
or test the drive run seatools

another cause of this problem is memory corruption caused by another driver. Best to just put the memory dump on a server and post a link.

you might also consider running cmd.exe as an admin then run
sfc.exe /scannow
to check your system for corrupted files.

 

[JBress]

BSOD can be caused by the 'Intel Product Improvement Program' service running in background.
You may want to remove it before anything else.

See this post for more info http://www.tomshardware.co.uk/answers/id-2339268/bsod-driver-verifier.html#19839428