PFN_List_Corrupt Mysterious Problem

[osrk]

So my folding machine has been cranking alone for a week now perfectly fine 24/7. All the sudden it starts developing blue screens with PFN_List_Corrupt or IRQ_NOT_LESS_THEN_OR_EQUAL. Tested the ram with memtest, it passed. I said fuck it, it has to be the RAM bought new RAM. Still occurs. Did a fresh install. Still happens.

The confusing thing is this machine was rock solid for a week before doing this. Could it be a bad hard drive, hard drive cable, or motherboard?

Any help would be appreciated. Currently I'm stress testing the CPU cache and the cpu itself with no problems after 2 hours in prime 95.

Machine stats
Processor: Phenom 9600 no OC
Ram: OCZ Reaper 4 gig
Video Cards: 4 x gtx 250
Motherboard: MSI K9A2
PSU: Corsair 1 kw
OS: Win xp 64

FAHcore_a1 is the core used for CPU folding btw.

Debug dump from the latest crash.
*******************************************************************************
* *
* 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: 0000000000038f36, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000000000, 0

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


BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: FahCore_a1.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80001097fdb to fffff8000102e950

STACK_TEXT:
fffffadf`8c0c45d8 fffff800`01097fdb : 00000000`0000004e 00000000`00000099 00000000`00038f36 00000000`00000000 : nt!CmpDelayCloseWorker+0x1f2
fffffadf`8c0c45e0 00000000`0000004e : 00000000`00000099 00000000`00038f36 00000000`00000000 00000000`00000000 : nt!KeSetSystemTime+0x3ea
fffffadf`8c0c45e8 00000000`00000099 : 00000000`00038f36 00000000`00000000 00000000`00000000 fffffa80`004853b0 : 0x4e
fffffadf`8c0c45f0 00000000`00038f36 : 00000000`00000000 00000000`00000000 fffffa80`004853b0 fffffadf`00000000 : 0x99
fffffadf`8c0c45f8 00000000`00000000 : 00000000`00000000 fffffa80`004853b0 fffffadf`00000000 fffffadf`8c0c4768 : 0x38f36


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpDelayCloseWorker+1f2
fffff800`0102e950 48894c2408 mov qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpDelayCloseWorker+1f2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45d69ab4

FAILURE_BUCKET_ID: X64_0x4E_99_nt!CmpDelayCloseWorker+1f2

BUCKET_ID: X64_0x4E_99_nt!CmpDelayCloseWorker+1f2

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

 

[osrk]

Problem still ongoing. I'm getting memory corruption errors with two different brands of ram both memtest 86 error free. bad motherboard?

 

[silent-circuit]

I'd guess.Possibly dying HDD.

 

[osrk]

I noticed a lot of these threads just end with the problem never "resolved"

I was in the engineering computer lab and by chance asked them if they had a spare hard drive I could use. They had an IDE 20gb (actually about 50 of them)! Loaded windows without a problem and also installed sp2 without a problem (both of which gave me headaches and a ton of bsod's). My sata cd-rom works fine so do you guys think it's just a bad hard drive?

Time will tell the machine is back up to 24/7 production now.