I'm receiving a PFN_LIST_CORRUPT BSOD after a few minutes of using my Dell D600 laptop (running Windows XP). Based on my searches, it seems this is typically related to bad RAM. I haven't had other problems, and nothing has changed on this computer. Could it be that one of the RAM chips has come unseated, or is it just corrupted and I should get a new one?
Does PFN_LIST_CORRUPT error always indicate bad RAM
memory
Related Solutions
I'm running into the same problem.
Trying to do a P2V conversion onto a 64-bit server running Windows Server 2008. Any of the normal file transfer methods for the VMDK file (which is 44GB) cause Windows on the destination server to run out of its 14GB RAM after a few minutes due to the file system caching.
Running the P2V conversion or file copy on a 32-bit server doesn't have this problem and memory usage stays reasonable.
Then trying to copy the VMDK file to the destination VMWare server has the same problem.
This page describe exactly what I'm seeing:
http://blogs.technet.com/askperf/archive/2007/05/08/slow-large-file-copy-issues.aspx
Based on my work this AM ESEUtil seems to be the way to go. It wasn't as fast as I'd expected, but it didn't freak out Windows either.
The Windows FTP client uses a Temp file on C:\ before moving the file to the target destination. Beware! :-)
This is very frustrating.
While I don't have a "here is your problem" answer, I do have a method of helping identify what may be the problem. Based off of what I'm reading here and what I can see on my own servers, Device Manager should be able to help you identify what's going on.
If you open Device Manager, change the view to "Resources by Connection" (not "Devices by connection"). The "Memory" node in there will give you a list of memory reservations by your hardware. Hopefully, the thing that's eating all but 4GB of your RAM will be listed in there. You'll have to convert the hex to RAM sizes, but it can be done.
In this case, the first PCI bus entry is reserving 128KB. The second "Motherboard resources" entry is reserving 64MB. The third PCI Bus is consuming 336MB. And so on.
Once you've identified the device, you're further along than you started.
Best Answer
I can't speak for that error, but there's one way to easily rule it out - run a memory testing application.
Memtest+ does the trick nicely. Download and burn the ISO, boot off it and let it run for 24-48 hours - if it picks up errors, you definitely need new memory. If not, then you can continue troubleshooting with some reasonable evidence that your memory is fine behind you.