Pfn_list_corrupt

[dsavage]

BSOD problem here. Thanks in advance to anyone willing to offer help.

The BSODs typically happen when the hard drives are under heavy load. Error is PFN_LIST_CORRUPT. Transferring HD video from one drive to another will typically cause the BSOD, but it also happens randomly under normal use. I've been sort of "dealing with it" for nearly two years, but I'm finally frustrated to the point of seeking help on the matter.

Here is what I'm working with:
Motherboard: GIGABYTE GA-EP45T-UD3P
Processor: Intel Core2Quad 9550 at 2.83Ghz
RAM: 4 Sticks of 2GB = 8GB OCZ Platinum DDR3
Graphics: GIGABYTE GV-N96GMC-512H GeForce 9600 GSO 512MB
PSU = Silverstone 500W
HDD: WD Black 2x500gig, 3x1TB (2 of these are in a RAID0)

Prerequisite files are attached!
Thank you!!!!!!!

 

[yowanvista]

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.

Do you use Prospect HD? Its process was involved in the last crsah

sptd.sys        fffff880`01073000    fffff880`01199000    0x00126000    0x4ad24632    12/10/2009 00:55:14

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000003e927, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000003e919, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  HDLink.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d6ad7c to fffff80002ce4d00

STACK_TEXT:  
fffff880`09a2e268 fffff800`02d6ad7c : 00000000`0000004e 00000000`00000099 00000000`0003e927 00000000`00000002 : nt!KeBugCheckEx
fffff880`09a2e270 fffff800`02c79aa3 : fffffa80`046363b0 00000000`00000001 00000000`00000000 00000000`00000080 : nt!MiBadShareCount+0x4c
fffff880`09a2e2b0 fffff800`02d3269d : 00000000`00000002 fffff800`00000001 fffffa80`046363b0 fffffa80`04636050 : nt! ?? ::FNODOBFM::`string'+0x11d18
fffff880`09a2e340 fffff800`02d11a1c : 00000000`00000000 00000000`00000000 fffff880`09a2e400 ffffffff`ffffffff : nt!MiRemoveLowestPriorityStandbyPage+0x1d5
fffff880`09a2e3c0 fffff800`02d0de9e : fffff980`0caee000 00000000`02cd82ac fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0xe50
fffff880`09a2e5b0 fffff800`02d0e454 : fffffa80`0730ce00 00000000`02cd82ac fffff880`09a2e6f0 fffff880`00000000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`09a2e6a0 fffff880`014c1c18 : 00000000`1602f6dc fffffa80`06bbe600 fffff880`09a2e790 fffffa80`06bbe670 : nt!CcCopyWrite+0x194
fffff880`09a2e730 fffff880`0122e102 : fffffa80`06bbe670 fffff880`012314f2 00000000`00010000 00000000`00010001 : Ntfs!NtfsCopyWriteA+0x208
fffff880`09a2e930 fffff880`012318ba : fffff880`09a2ea00 fffffa80`06fd6618 00000000`02cc9900 00000000`00010000 : fltmgr!FltpPerformFastIoCall+0xf2
fffff880`09a2e990 fffff880`0124f83e : 00000000`00010000 00000000`00000000 fffffa80`06bbe670 fffff880`09a2eb00 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`09a2e9d0 fffff800`02ff70de : fffffa80`06bbe6e4 fffff880`09a2ea98 00000000`00000000 fffffa80`06bbe6e4 : fltmgr!FltpFastIoWrite+0x1ce
fffff880`09a2ea70 fffff800`02ce3f93 : 00000000`00002501 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x5ad
fffff880`09a2eb70 00000000`73462e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1fe5f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73462e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d6ad7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------

 

[dsavage]

Thanks for looking into this, Yowanvista!

I uninstalled DaemonTools and ran the SPTD uninstaller as you suggested.

I do not use Prospect HD, but a very similar program from Cineform called Neoscene that is used to capture and convert video to Cineform AVI. I was in the middle of converting some video files the last time my computer crashed. The program is pretty essential to me, so I hope it's not the culprit here. And the BSODs began occuring long before I installed Neoscene. Keeping my fingers crossed on this one.

 

[dsavage]

I just got another BSOD! PFN_LIST_CORRUPT once again. I have attached an updated version of the prerequisite zip file. As always, many thanks to anyone willing to help figure this out.

Here's the scenario: I was transferring large HD video files from my RAID-0 drive to another internal drive when it happened. The only program I recall having open was Chrome. This is when these BSODs occur most frequently (when I'm transferring files). And since I edit video and am constantly moving files around, it's become quite an obstacle towards getting things done.

 

[yowanvista]

Latest crash cause by Memory Corruption
Test your RAM to be sure.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000012a6e6, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000098a65, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d1ed7c to fffff80002c98d00

STACK_TEXT:  
fffff880`0cdd4328 fffff800`02d1ed7c : 00000000`0000004e 00000000`00000099 00000000`0012a6e6 00000000`00000002 : nt!KeBugCheckEx
fffff880`0cdd4330 fffff800`02c2daa3 : fffffa80`056b6740 00000000`00000001 00000000`00000000 00000000`00000080 : nt!MiBadShareCount+0x4c
fffff880`0cdd4370 fffff800`02ce669d : 00000000`00000002 4a700001`00000001 fffffa80`056b6740 65b00001`ea369921 : nt! ?? ::FNODOBFM::`string'+0x11d18
fffff880`0cdd4400 fffff800`02c5d28f : fa80072b`b09004c0 fa80072b`b09004c0 fffff880`0cdd44c0 00000000`00000046 : nt!MiRemoveLowestPriorityStandbyPage+0x1d5
fffff880`0cdd4480 fffff800`02f3685a : fffffa80`0702d010 fffffa80`00000001 fffffa80`0702d010 00000000`00000002 : nt!MiPfPutPagesInTransition+0x826
fffff880`0cdd45f0 fffff800`02c87d0d : fffffa80`0702d010 00000000`15400000 00000000`00100000 00000000`00015400 : nt!MmPrefetchForCacheManager+0x8e
fffff880`0cdd4640 fffff800`02f824d0 : fffffa80`00000000 00000000`15400000 fffffa80`07039f20 00000000`05c80040 : nt!CcFetchDataForRead+0x17d
fffff880`0cdd46a0 fffff880`014c0f08 : 00000000`00000000 00000000`00000002 fffff880`00040000 fffffa80`07039f01 : nt!CcCopyRead+0x180
fffff880`0cdd4760 fffff880`01205098 : fffffa80`07039f20 fffffa80`06f77cd8 00000000`00000108 fffffa80`07039f01 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`0cdd4940 fffff880`012088ba : fffff880`0cdd4a10 00000000`05c80003 00000000`05c80000 fffffa80`07039f00 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`0cdd49a0 fffff880`01226630 : fffffa80`07039f20 00000000`00000000 fffff880`0cdd4b00 00000000`00100000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0cdd49e0 fffff800`02f82009 : fffffa80`07039f20 00000000`00000002 fffffa80`06a3c570 fffffa80`07039f20 : fltmgr!FltpFastIoRead+0x1d0
fffff880`0cdd4a80 fffff800`02c97f93 : fffffa80`06bcbb60 00000000`00001270 00000000`00000000 00000000`091a0db8 : nt!NtReadFile+0x417
fffff880`0cdd4b70 00000000`77bd137a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`100cc7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bd137a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d1ed7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------

 

[dsavage]

Will definitely be running Memtest86+. Will post the results here.

Not sure if this is related, but I was going through everything I could find memory-related and saw that the RAM I purchased when I built the system was 1600, whereas my board is 1333. Not sure if this would cause the error. Here are the links to the parts.

Newegg.com - OCZ Platinum 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Dual Channel Kit Desktop Memory Model OCZ3P16004GK
Newegg.com - GIGABYTE GA-EP45T-UD3P LGA 775 Intel P45 ATX Intel Motherboard

I didn't realize this when I purchased everything, and am still a bit of a novice at system-building. But I thought I'd mention this as it does seem to be mismatched.

 

[yowanvista]

Will definitely be running Memtest86+. Will post the results here.

Not sure if this is related, but I was going through everything I could find memory-related and saw that the RAM I purchased when I built the system was 1600, whereas my board is 1333. Not sure if this would cause the error. Here are the links to the parts.

Newegg.com - OCZ Platinum 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Dual Channel Kit Desktop Memory Model OCZ3P16004GK
Newegg.com - GIGABYTE GA-EP45T-UD3P LGA 775 Intel P45 ATX Intel Motherboard

I didn't realize this when I purchased everything, and am still a bit of a novice at system-building. But I thought I'd mention this as it does seem to be mismatched.

Did you check if your board supports this RAM?

 

[dsavage]

The 1GB version was listed on Gigabytes website as being tested compatible. I'm pretty sure that's what I was going on when I bought it.

Here's the model they tested from their website: OET16B1 1GB OCZ OCZ3P1600EB2GK
They also have it listed under "Downgrade to DDR3 1333". I'm not sure how to do this, but I'm hoping the Motherboard is taking care of it automatically.

Late last year, I also added an additional 4GB of RAM (2x2GB) that I thought was the same. Turns out the voltage was slightly different. So now I have two sticks of this:

Newegg.com - OCZ Platinum 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Dual Channel Kit Desktop Memory Model OCZ3P16004GK
and another two sticks of this:
Newegg.com - OCZ Platinum 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model OCZ3P1600LV4GK

The specs are exactly the same except for the voltage. One is listed as 1.65v and the other is 1.7v (although the sticker on the actual RAM lists it as 1.9v)

These are set up on my board as follows:
Slot 1 - 1.9v
Slot 2 - 1.9v
Slot 3 - 1.65v
Slot 4 - 1.65v

Here is the timings table from CPU-Z

JEDEC#1 JEDEC#2 JEDEC#3 JEDEC#4
Frequency: 380mhz 457mhz 533mhz 609mhz
CAS# Latency: 5.0 6.0 7.0 8.0
RAS# to CAS#: 5 6 7 8
RAS# Precharge: 5 6 7 8
tRAS: 12 14 16 19
tRC: 19 23 27 31
Voltage: 1.50v 1.50v 1.50v 1.50v


Not sure what any of this means or if it even helps. I still plan on running Memtest86+ overnight and will report back with the results. Just trying to cover as many bases as possible.

 

[dsavage]

I ran Memtest86+ last night for 8 hours (4 passes) with no errors. No BSODs recently either. Maybe I'll try running it again for a longer amount of time.

 

[dsavage]

Crashed again with PFN_LIST_CORRUPT while I was transferring files from an SD card (via USB reader) to an internal SATA drive. Zip file attached.

I've downloaded quite a few diagnostic tools since this thread started, and have discovered that my CPU is running a bit hot for stock speeds. I'll probably be purchasing an aftermarket cooling solution soon.

I took some screenshots that show the temp and some other info that might be helpful in diagnosing the BSOD issue.

Here's the system at idle:
View attachment 167878


And here it is after running Prime95 for about five minutes:
View attachment 167879

The Tj. Max for my processor is 100C, but the fact that it's hitting 90C at stock is a bit concerning. This may be totally unrelated to the PFN_LIST_CORRUPT errors, but definitely something worth fixing.

Any other advice/ideas/etc would be totally appreciated.

 

[yowanvista]

Crashed again with PFN_LIST_CORRUPT while I was transferring files from an SD card (via USB reader) to an internal SATA drive. Zip file attached.

I've downloaded quite a few diagnostic tools since this thread started, and have discovered that my CPU is running a bit hot for stock speeds. I'll probably be purchasing an aftermarket cooling solution soon.

I took some screenshots that show the temp and some other info that might be helpful in diagnosing the BSOD issue.

Here's the system at idle:
View attachment 167878


And here it is after running Prime95 for about five minutes:
View attachment 167879

The Tj. Max for my processor is 100C, but the fact that it's hitting 90C at stock is a bit concerning. This may be totally unrelated to the PFN_LIST_CORRUPT errors, but definitely something worth fixing.

Any other advice/ideas/etc would be totally appreciated.

90C is way too hot, consider replacing the thermal paste on your CPU

 

[dsavage]

Okay, I may have gone overkill here, but I bought a Thermaltake Frio to take care of the overheating issues. This thing is a BEAST! It's keeping me under 50C, even running Prime95 for 15 minutes plus.

Since I had my overheating issue solved, I decided to try to rule out the memory as a culprit. To do this, I booted windows into safe mode with only one stick of memory and did as much file-transferring and video encoding as possible. It was a bit ridiculous the amount of things I had happening at once, but at this point I was trying to make it crash. No dice.

I repeated the process with all four sticks of memory. Couldn't make it crash.

Okay. I'm thinking, "Great! Maybe it's just a driver issue." So I booted windows normally with all four sticks of RAM installed and threw everything I had at it. Copying hundreds of gigs worth of files. Encoding AVCHD files into Cineform AVI. Transferring to and from external drives. Everything I could think of. Still nothing. This has been going on for the last three hours or so (still copying tons of files), and looking at Core Temp in my toolbar, it's staying at around 40-45C.

I guess the only remaining question is, "Is it possible that the PFN_LIST_CORRUPT problems were due to overheating?".

Other than that, I'm keeping my fingers crossed and if I can't make it crash within the next couple of days of hard testing, I'll consider this issue solved.

Thanks for helping me out on this!

 

[dsavage]

Looks like I spoke too soon. Another BSOD "PFN_LIST_CORRUPT" happened just a few minutes after I posted. Reports attached.

This thing is really throwing me for a loop. What other tests can I run to figure this out?

 

[yowanvista]

Still Memory Corruption but peerblock.exe was involved in the crash, I suggest removing this software
Removeany Gigabyte tuning utilities

GVTDrv64.sys        fffff880`0ae7a000    fffff880`0ae84000    0x0000a000    0x44fd22ca    05/09/2006 11:10:02

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001a46a3, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000000a846f, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  peerblock.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d12d7c to fffff80002c8cd00

STACK_TEXT:  
fffff880`0adfcea8 fffff800`02d12d7c : 00000000`0000004e 00000000`00000099 00000000`001a46a3 00000000`00000002 : nt!KeBugCheckEx
fffff880`0adfceb0 fffff800`02c346e0 : 00000000`00000000 fffff680`009f9538 6da00001`8f355025 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0adfcef0 fffff800`02c5d523 : fffffa80`0a10d420 fffff700`00000814 0000007f`fffffff8 fffff8a0`02ed7b88 : nt! ?? ::FNODOBFM::`string'+0x333b8
fffff880`0adfcf80 fffff800`02c5e606 : fffffa80`0a10d420 fffffa80`00000000 fffff8a0`0000031b fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0adfd830 fffff800`02f6220a : fffff8a0`02ed3060 fffff880`0adfdbe0 00000000`00000000 fffffa80`0a3ef660 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0adfd880 fffff800`02f4751d : 00000000`40010004 00000000`00000001 000007ff`fffdb000 fffffa80`0a0f9b60 : nt!PspExitThread+0x56a
fffff880`0adfd980 fffff800`02c8047a : fffffa80`066a4b30 00000000`00000000 fffffa80`0a3ef660 fffff800`02f83bc4 : nt!PsExitSpecialApc+0x1d
fffff880`0adfd9b0 fffff800`02c807c0 : 00000000`00000000 fffff880`0adfda30 fffff800`02f47490 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0adfda30 fffff800`02c8c037 : fffffa80`0a3ef660 00000000`02a5f908 fffff880`0adfdb88 fffff880`0adfdb00 : nt!KiInitiateUserApc+0x70
fffff880`0adfdb70 00000000`773918ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`02a5f8e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773918ca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d12d7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------