"PFN_LIST_CORRUPT" BSOD on new build

I don't think it's a stack overflow, something has most likely gone wrong with some form of Synchronization. It's difficult to say with the little information provided from a Minidump.

Code:

.trap fffff800`044c1e70
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000007 rbx=0000000000000000 rcx=0000000000000043
rdx=f88008d876500006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e98698 rsp=000000000000d824 rbp=0000000000000000
 r8=0000000000000021  r9=0000000000000007 r10=00000000000000fe
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiIpiSendRequest+0x128:
fffff800`02e98698 0044898b        add     byte ptr [rcx+rcx*4-75h],al ds:00000000`000000da=??

Code:

0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 12 (SYNCH_LEVEL)

Code:

0: kd> !ipi
IPI State for Processor 0
    TargetCount          0  PacketBarrier        0  IpiFrozen     0 [Running]

All I can gather is that Processor 0, sent out a IPI for some reason.

Could you please check this directory:

Code:

C:\Windows\MEMORY.DMP

Compress the file and then place into a zipped folder, and upload to a free file sharing site like Dropbox or Skydrive.

Ok, here's the link!

https://www.dropbox.com/s/cruwp2ucy5u7rd9/MEMORY.zip

Code:

BugCheck 1A, {411, fffff68000019ca0, 9450000316cd9884, fffff6800001a101}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6071 )

This bugcheck indicates that a PTE has become corrupt, parameter 2 contains the address of the corrupt PTE.

Code:

7: kd> !pte fffff68000019ca0
                                           VA 0000000003394000
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB400000C8    PTE at FFFFF68000019CA0
contains 1530000363B52867  contains 03B0000363B53867  contains 08F0000317CFB867  contains 9450000316CD9884
pfn 363b52    ---DA--UWEV  pfn 363b53    ---DA--UWEV  pfn 317cfb    ---DA--UWEV  not valid
                                                                                  Transition: 316cd9
                                                                                  Protect: 4 - ReadWrite

Code:

7: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`08f6c788 fffff800`02ea4c4d nt!KeBugCheckEx
01 fffff880`08f6c790 fffff800`02ef9281 nt! ?? ::FNODOBFM::`string'+0x6071
02 fffff880`08f6c7e0 fffff800`02ee5c8f nt!MiResolveTransitionFault+0x381
03 fffff880`08f6c870 fffff800`02ed5179 nt!MiDispatchFault+0x95f
04 fffff880`08f6c980 fffff800`02ec6cee nt!MmAccessFault+0x359
05 fffff880`08f6cae0 000007fe`ec6110d0 nt!KiPageFault+0x16e
06 00000000`1faaecf8 00000000`00000000 0x000007fe`ec6110d0

Let's establish a few things, the page of paged pool isn't resident in physical memory, thus why the PTE is marked as invalid. A Page Fault happens when this page is referenced and brought into physical memory.

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

This is gonna take a while, about 2 hours per pass...

You could try one stick at a time, instead of doing 16GB all at once.

I am. First stick went 10 passes with no errors, 2nd one is on 6 with no errors so far

Both sticks went 10-11 passes in Slot 1 with 0 errors. Stick #2 in slot 2 just failed with 4 errrors. Attached is a photo of the results. I'm running Stick #1 in slot 2 now.

Stick #1 in slot 2 succeeded through 13 passes with no errors. So the only one that failed was the above post. What does that mean?

It may be acute error in the RAM stick, are all the RAM matched I.e same timings and MHz (clockspeed)?

They were bought as a matched pair so I would think so