Solved "PFN_LIST_CORRUPT" BSOD on new build

x BlueRobot · Nov 22, 2013

Code:

4: kd> [COLOR=SeaGreen]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`0f092000 fffff880`0fd7f000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Thu Nov 07 16:47:15 2013 [/COLOR](527BC413)
    CheckSum:         00CA43A7
    ImageSize:        00CED000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Roll back to the latest WHQL version of the driver, Beta drivers haven't been fully tested for bugs in their code.

http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

WHQL
Release Date: November 18th 2013
Version: 13.10

This driver was causing memory alignment errors too.

agentsmith24 · Nov 22, 2013

Ok, I'll update that and report back a day or two with what's happened! Thanks again.

x BlueRobot · Nov 23, 2013

Welcome, and will look forward for an update

agentsmith24 · Nov 24, 2013

One BSOD just now, saw atikmdag on the screen again... files are attached. It was doing really well too!

Edit: 2nd one, different error code.

x BlueRobot · Nov 25, 2013

Debugging Analysis:

Code:

[COLOR=Red]BugCheck 3B[/COLOR], {[COLOR=SeaGreen]c0000005[/COLOR], [COLOR=Blue]fffff960000d60f7[/COLOR], [COLOR=Orange]fffff880021970f0[/COLOR], 0}

Probably caused by : win32k.sys ( win32k!W32pArgumentTable+2db )

Did you roll back the driver?

Code:

7: kd> [COLOR=SeaGreen]lmvm atikmdag[/COLOR]
Browse full module list
start             end                 module name
fffff880`0f0fd000 fffff880`0fd7d000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red]Thu Sep 12 03:08:03 2013[/COLOR] (52312203)
    CheckSum:         00C34EED
    ImageSize:        00C80000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

fffff880021970f0 -- ([COLOR=SeaGreen].cxr 0xfffff880021970f0[/COLOR])
rax=0000000000000000 rbx=fffffa800cea4160 rcx=0000000000000000
rdx=000000000000002b rsi=000007fefe131010 rdi=0000000000000020
rip=fffff960000d60f7 rsp=fffff88002197ad0 rbp=fffff88002197b60
 r8=0000000000000000  r9=00000000253d28f0 r10=fffff960000d616c
r11=000007ffffee0000 r12=000007fffffd9000 r13=000000001e486710
r14=000007ffffee0000 r15=0000000077a82670
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  [COLOR=Red]ds=002b[/COLOR]  es=002b  fs=0053  gs=002b             efl=00010246
[COLOR=Red]win32k!W32pArgumentTable+0x2db:[/COLOR]
[COLOR=Blue]fffff960`000d60f7[/COLOR] 0000            add     byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope

Code:

7: kd> [COLOR=SeaGreen]dg @ds[/COLOR]
                                                    P Si Gr Pr Lo
Sel        Base              Limit          Type    l ze an es ng Flags
---- ----------------- ----------------- ---------- - -- -- -- -- --------
002B 00000000`00000000 ffffffff`ffffffff Data [COLOR=Red]RW[/COLOR] Ac 0 Bg Pg P  Nl 00000c93

The Data Segment is used to store global and static variables declared by the programmer. Static variables are permanent variables which exist for the lifetime of the program like global variables, and therefore will maintain their value among function calls like passing parameters by reference. However, static variables are local to the the block they are declared in.

Code:

7: kd> [COLOR=SeaGreen]r @al[/COLOR]
Last set context:
al=0

Code:

7: kd> [COLOR=SeaGreen]uf win32k!W32pArgumentTable+0x2db[/COLOR]
win32k!W32pArgumentTable+0x2db:
[COLOR=Blue]fffff960`000d60f7[/COLOR] 0000            [COLOR=Red]add [/COLOR]    byte ptr [rax],al
fffff960`000d60f9 0000            add     byte ptr [rax],al
fffff960`000d60fb 0000            add     byte ptr [rax],al
fffff960`000d60fd 0000            add     byte ptr [rax],al
fffff960`000d60ff 0000            add     byte ptr [rax],al
fffff960`000d6101 0000            add     byte ptr [rax],al
fffff960`000d6103 0000            add     byte ptr [rax],al
fffff960`000d6105 0000            add     byte ptr [rax],al
fffff960`000d6107 0008            add     byte ptr [rax],cl
fffff960`000d6109 0000            add     byte ptr [rax],al
fffff960`000d610b 0000            add     byte ptr [rax],al
fffff960`000d610d 0000            add     byte ptr [rax],al
fffff960`000d610f 0000            add     byte ptr [rax],al
fffff960`000d6111 0000            add     byte ptr [rax],al
fffff960`000d6113 0000            add     byte ptr [rax],al
fffff960`000d6115 0000            add     byte ptr [rax],al
fffff960`000d6117 0000            add     byte ptr [rax],al
fffff960`000d6119 0000            add     byte ptr [rax],al
fffff960`000d611b 0000            add     byte ptr [rax],al

So, the add instruction is being used with a register containing the value of 0, and added to the value stored within the rax register which is used to store integer return values for function calls. The rax register doesn't appear to have a address, and therefore the system may have crashed due to a NULL pointer.

agentsmith24 · Nov 26, 2013

Yes, I rolled the driver back to version 13.10 (WHQL).

Driver Packaging Version---------------13.20-130911a-163984C-ATI

Catalyst Version-----------------------13.10
Provider-------------------------------Advanced Micro Devices, Inc.
2D Driver Version-----------------------8.01.01.1346
2D Driver File Path---------------------/REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/CLASS/{4D36E968-E325-11CE-BFC1-08002BE10318}/0000
Direct3D Version-----------------------9.14.10.0996
OpenGL Version------------------------6.14.10.12458
AMD Catalyst Control Center Version----2013.0911.2154.37488
AMD Audio Driver Version---------------7.12.0.7717

Edit: added new dump file

x BlueRobot · Nov 26, 2013

I would consider testing the card with a graphics card test, do have a onboard graphics card you could switch to? It will save running a graphics card test.

Run Furmark for a few hours (do not let the temperature exceed 90*C) - http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

agentsmith24 · Nov 28, 2013

Ran Furmark, temps eventually leveled off at 80 C, but no artifacts that I could see. It did seem to skip a frame every second or two, but it was running at 30-31 fps so I don't know if that means anything.

agentsmith24 · Nov 28, 2013

Crashed just now, error code I haven't seen before, "unexpected_kernel_mode_trap"?

x BlueRobot · Nov 28, 2013

That is usually caused by stack overflow, again a driver problem. Hopefully there's a TSS on the stack, I can use to rebuild a 'good' stack trace.

x BlueRobot · Nov 28, 2013

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:

[COLOR="SeaGreen"].trap fffff800`044c1e70[/COLOR]
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
[COLOR="Blue"]rip=fffff80002e98698[/COLOR] 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:
[COLOR="Blue"]fffff800`02e98698[/COLOR] 0044898b        add     byte ptr [rcx+rcx*4-75h],al ds:00000000`000000da=??

Code:

0: kd> [COLOR="SeaGreen"]!irql[/COLOR]
Debugger saved IRQL for processor 0x0 -- [COLOR="Red"]12[/COLOR] (SYNCH_LEVEL)

Code:

0: kd> [COLOR="SeaGreen"]!ipi[/COLOR]
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.

agentsmith24 · Nov 28, 2013

Ok, here's the link!

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

x BlueRobot · Nov 29, 2013

Code:

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]411[/COLOR], [COLOR="SeaGreen"]fffff68000019ca0[/COLOR], 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> [COLOR="SeaGreen"]!pte fffff68000019ca0[/COLOR]
                                           VA 0000000003394000
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB400000C8    PTE at [COLOR="Red"]FFFFF68000019CA0[/COLOR]
contains 1530000363B52867  contains 03B0000363B53867  contains 08F0000317CFB867  contains 9450000316CD9884
pfn 363b52    ---DA--UWEV  pfn 363b53    ---DA--UWEV  pfn 317cfb    ---DA--UWEV  [COLOR="Red"]not valid[/COLOR]
                                                                                  Transition: 316cd9
                                                                                  Protect: 4 - ReadWrite

Code:

7: kd> [COLOR="SeaGreen"]knL[/COLOR]
 # 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 [COLOR="Red"]nt!MiResolveTransitionFault[/COLOR]+0x381
03 fffff880`08f6c870 fffff800`02ed5179 nt!MiDispatchFault+0x95f
04 fffff880`08f6c980 fffff800`02ec6cee nt!MmAccessFault+0x359
05 fffff880`08f6cae0 000007fe`ec6110d0 [COLOR="Red"]nt!KiPageFault[/COLOR]+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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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:
test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good
It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good
It is a motherboard issue. The particular slot is bad.

agentsmith24 · Dec 1, 2013

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

x BlueRobot · Dec 2, 2013

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

agentsmith24 · Dec 2, 2013

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

agentsmith24 · Dec 3, 2013

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.

agentsmith24 · Dec 4, 2013

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?

x BlueRobot · Dec 4, 2013

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

agentsmith24 · Dec 4, 2013

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

Solved "PFN_LIST_CORRUPT" BSOD on new build

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request

My Computer My Computer

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request

My Computer My Computer

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer