BSOD PFN_LIST_CORRUPT issues Bugcheck code: 0x4E, ntoskrnl.exe (nt+0x7FD00) ntfs.sys (Ntfs+0xA730)

kiryogi

Reputable
Mar 15, 2015
6
0
4,510
This PC was built around 2010. Anyway, so just a few days ago, starting getting various BSODS relating to Driver IRQ Less and Equal and PFN_LIST_CORRUPT, pointing to usbport.sys usually during gaming loads. After some self troubleshooting, I found out I had one bad stick of ram via memtest86. I might have more, I'll run more tests after this. But after that, my drivers were beyond corrupted and I kept getting BSOD. So I decided to start fresh and reformat, and reinstalled Windows. Everythings been smooth again up until now until I started gaming again. I had WTFast, Final Fantasy XIV: A Realm Reborn, and Teamspeak 3 up when it happened. And now it's the same error. I can't seem to pinpoint whats the issue. PFN_LIST_CORRUPT seems to indicate it's a driver issue, but I have no idea what driver it is at this point. I'm also using an Astro A40 headset with Mixamp Pro plugged into the USB. Is it possible my Hard Drive is dying too? Or Could it be the Motherboard? I'm going to try updating to latest radeon drivers and full windows update as well. But any further insight into this will be very much appreciated.

Here's what I have from Whocrashed and bluescreen viewer.

On Sun 3/15/2015 6:30:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031515-26254-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x7, 0x585F9, 0x40000000000, 0x0)
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.



On Sun 3/15/2015 6:30:13 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA730)
Bugcheck code: 0x4E (0x7, 0x585F9, 0x40000000000, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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.

Stop information:

The problem seems to be caused by the following file: ntoskrnl.exe

PFN_LIST_CORRUPT

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000004e (0x0000000000000007, 0x00000000000585f9, 0x0000040000000000,
0x0000000000000000)

*** ntoskrnl.exe - Address 0xfffff80002ad7d00 base at 0xfffff80002a58000 DateStamp
0x4d9fdd5b

Computer Specs:
O/S: Windows 7 Ultimate 64bit
Mother Board; ASUS M4A78T-E
Processor: AMD Phenom II X4 965 Black Edition Deneb Quad-Core 3.4GHz Socket AM3
Ram: CORSAIR XMS3 6GB 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
Graphic Card: SAPPHIRE VAPOR-X 100363VX-2SR Radeon R9 280X 3GB PCI Express 3.0 TRI-X OC w/ Boost Video Card (UEFI)
Power Supply: Antec TruePower New TP-650 650W Continuous Power ATX12V V2.3 / EPS12V V2.91 SLI Certified
HDD: WD Green WD10000CSRTL 1TB 5400 RPM 16MB Cache SATA 3.0Gb/s
Video Card Driver: Radeon 13.10

Thank you.
 
Solution
It could be the motherboard but I am wondering if it could be your hard drive. Try running a check disk on the drive.

http://support.microsoft.com/en-us/kb/2641432

It could be many things. You could also do stress tests to see if it is your CPU or Graphics card. Try Prime95 (for CPU) and Furmark (for GPU).

http://www.mersenne.org/download/
http://www.ozone3d.net/benchmarks/fur/

kiryogi

Reputable
Mar 15, 2015
6
0
4,510
oh I did do checkdsks prior to reformat but havent' done it since. It did find errors but no bad sectors. While the graphics card is relatively new, but I'll bench both the CPU and GPU a bunch and see what happens.
 

kiryogi

Reputable
Mar 15, 2015
6
0
4,510
Ok so video card is fine. Ran prime95 and got a memory management bsod. Does that mean ram or cpu? I'm right now running memtest86 more extensively as we speak and posting from my phone
 

JimF_35

Distinguished
It is looking like it. I would suspect your RAM being that you already had a RAM chip fail. What kind of RAM is this? Does it support XMP profiles and are you using the XMP profile? It could also be the RAM is being under volted. Go into your BIOS and see what the DRAM Voltage is set at and look on the side of the RAM to see if they match. If not bring your DRAM Voltage up to the voltage marked on the side of your RAM.
 

kiryogi

Reputable
Mar 15, 2015
6
0
4,510
So I'm finding more bad sticks. Although running them again. I don't see errors a second time. Usually any errors mean the stick is bad regardless right? I'm also wondering if it's due to heat that they start acting up. But regardless I assume theyre no longer any good.
 

JimF_35

Distinguished


I would double check your voltage setting in your BIOS first. It could be that it is not set to 1.5 volts as required for this RAM. Or, you could try the RAM in another machine just to rule out that it is not something in your computer. It would be a shame to have you buy new RAM only for it not to work too.

 

kiryogi

Reputable
Mar 15, 2015
6
0
4,510
Ah I kind of already did that prior to finding the first bad stick. That said, I did look at the BIOS settings and it's set to auto. I'm currently down to only 1 of the 4 sticks left and seem to be running stable. Although, is there any harm to manually setting it to 1.5v anyway?
 

JimF_35

Distinguished


No. It could have been the auto was under volting the RAM. Set it to 1.5 and try memory test again. It is a shot in the dark and they may be bad but I hate to see someone buy new RAM and still have the same problems.

Also, try your RAM in another computer because it could be a motherboard problem.
 

kiryogi

Reputable
Mar 15, 2015
6
0
4,510
Well the new ram arrived and im at a new odd problem. It won't boot up with more than 8 gigs. *2 sticks of 4. I ended up opting for 16 to replace/upgrae the former ram. I did test it on another pc and yeah, 3 of the original sticks have gone bad. Things are fine otherwise with just 8. Could it be the clocks and needing more voltage than 1.5?

The Ram I got: CORSAIR Vengeance 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Memory Kit Model CMZ8GX3M2A1600C9R x2 for 16

The former ram: CORSAIR XMS3 6GB 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) *was originally 8GB total.

My motherboard: ASUS M4A78T-E
 

Dee Kay

Reputable
Dec 22, 2014
863
0
5,360


Are you sure that all 4 sticks are on the Asus QVL? Some models of ram are supported but others aren't even from the same company and at the same speed because the timings are different. It sounds like 2 sticks may not be on the qualified list which means it COULD give errors or not work. Check Asus for compatibility It may give you an answer that you don't want to hear but would explain why only 8GB seems to work.