PFN_LIST_CORRUPT when hooking up new external drive

[Wrathchild]

Bought a Seagate Backup Plus 3TB USB 3.0 drive and as soon as I plug it in Windows crashes with PFN_LIST_CORRUPT error. Drive states compatible with XP SP3, which is what I have, so I'm guessing something with my system is causing it, but not sure where to start with troubleshooting. I'm gonna hook it up to a friend's XP system, but even if it does work it still really doesn't help me. My system works perfect with no issues, just crashes if I plug the new drive in. Nothing is barking at me in Device Manager, but of course Windows crashes so I can't get to it with the new drive hooked up. Seagate support stated there are no drivers to install. Something must be buggy with my system but where to start looking? Googling shows just posts with people having actual system problems; mine is only with the new device.

 

[goombawaho]

Start with some simple things: a memory test and a BIOS update if available. Then, if no joy.......

If you are getting a DUMP file in the C:\WINDOWS\Minidump then try this procedure to debug it:

Using the Debugging Tools for Windows in procedure.

http://support.microsoft.com/kb/315263/en-us?p=1

It looks harder than it really is.

Basically, once you have the debugging tool installed, launch a command prompt and switch to the debugging tool installation directory, which for me was c:\Program Files\Debugging Tools for Windows (x86)\. Next, launch the graphical debugger by entering the following command (all on one line):
windbg -y srv*C:\symbols*

http://msdl.microsoft.com/download/symbols

-i c:\i386 -z c:\PathToMiniDumpFile__Mini051311-01.dmp

Need to be connected to the internet for the test to work. You'll get information on the module that might be causing the crash or at least the last thing windows did when it puked.

 

[Wrathchild]

Thx for the suggestions - I've used Memtest86 and the memory passed (assume I only need to make one pass as it kept on running) and verified the BIOS is current. Looking for XP disk to install the debugging tool as I did see some .dmp files.

 

[goombawaho]

You can just download the windows debugging tools. Not even sure they're on the CD.

http://msdn.microsoft.com/en-US/windows/hardware/hh852363

 

[Wrathchild]

found my XP disk and installed the Support Tools...ran the dumpchk command and got the following - not sure if this tells me anything?

dumpchk -c C:\WINDOWS\Minidump\mini123006-01.dmp
Loading dump file C:\WINDOWS\Minidump\mini123006-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 16320300
PfnDataBase 81086000
PsLoadedModuleList 805531a0
PsActiveProcessHead 80559258
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 000000ea
BugCheckParameter1 8971dda8
BugCheckParameter2 89a70148
BugCheckParameter3 89889e78
BugCheckParameter4 00000001
PaeEnabled 00000001
KdDebuggerDataBlock 80544ce0
MiniDumpFields 00000cff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00000000
UnloadedDriversOffset 00000000
PrcbOffset 000012f8
ProcessOffset 00001f48
ThreadOffset 000021a8
CallStackOffset 00002400
SizeOfCallStack 00000c44
DriverListOffset 00003048
DriverCount 00000082
StringPoolOffset 000056e0
StringPoolSize 000011e8
BrokenDriverOffset 00000000
TriageOptions 00000000
TopOfStack b36933bc
DebuggerDataOffset 00001068
DebuggerDataSize 00000290
DataBlocksOffset 000068c8
DataBlocksCount 00000001


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Dec 30 19:33:35 2006
System Uptime: 3 days 9:57:07
start end module name
804d7000 806cd280 nt Checksum: 001FB94E Timestamp: Wed Aug 04 01:
58:36 2004 (41107B0C)

Mini Kernel Dump does not contain unloaded driver list
Unable to examine unloaded module list
Finished dump check

 

[Wrathchild]

Still trying to troubleshoot this
I've run Memtest against RAM with no errors (I understand this isn't perfect) and updated several of my drivers using SlimDrivers. SlimDrivers found a new audio driver but BSOD'ed trying to install it. I cannot tell what the most current audio driver is as the one on the Asus site is so old (2003), which I guess could be the latest. I reverted back to the original sound driver. I've now returned the Seagate for a Toshiba 3TB and getting exact same error. Drives work fine on friends XP machine, so obviously something is wrong with mine.

 

[Wrathchild]

My system info:
AMD 64 3000
Asus K8V SE Deluxe
Radeon 9800 card
Windows 32bit

 

[goombawaho]

Can you run the debug once again and press the BLUE text where it says: "!analyze -v to get detailed...."

Then look down the page and then copy and paste THAT info here. Sorry, should have mentioned that the first time. It shows the faulting module which CAN help the diagnosis.



Then, we are approaching time for a nice XP reload I guess. Will save you time in the end.

 

[Wrathchild]

thanks man, I was thinking last night about how I sometimes loose USB connection and need to reboot and if that might be related. So I Googled and found a potential fix for that by adding the DisableSelectiveSuspend setting in the registry. Too early to tell but I did try to reattach the new HD afterwards and now got a different BSOD: BAD_POOL_HEADER so now I'm Googling that and will try some of those fixes. I'll post new dump if this doesn't work.

 

[Wrathchild]

goom, not really sure what you're talking about with "!analyze -v to get detailed...." but I ran the dump the way I did last time and seemed to get more info this time:

dumpchk -c C:\WINDOWS\Minidump\mini020913-03.dmp
Loading dump file C:\WINDOWS\Minidump\mini020913-03.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 003d3000
PfnDataBase 81846000
PsLoadedModuleList 80553fc0
PsActiveProcessHead 8055a158
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000019
BugCheckParameter1 00000020
BugCheckParameter2 8973f350
BugCheckParameter3 8973f4e8
BugCheckParameter4 0a330005
PaeEnabled 00000001
KdDebuggerDataBlock 80545ae0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000300
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000ca4
DriverListOffset 000038b8
DriverCount 00000098
StringPoolOffset 000065d8
StringPoolSize 00001530
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ba4eb35c
DebuggerDataOffset 00003628
DebuggerDataSize 00000290
DataBlocksOffset 00007b08
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Sat Feb 09 19:43:27 2013
System Uptime: 0 days 0:06:23
start end module name
804d7000 806cf580 nt Checksum: 00204E7E Timestamp: Sun Apr 13 14:31:06 2008 (4802516A)

Unloaded modules:
a238f000 a23ba000 kmixer.sys Timestamp: unavailable (00000000)
ba7a5000 ba7a6000 drmkaud.sys Timestamp: unavailable (00000000)
ba1b8000 ba1c5000 DMusic.sys Timestamp: unavailable (00000000)
b96e9000 b96f7000 swmidi.sys Timestamp: unavailable (00000000)
a23ba000 a23dd000 aec.sys Timestamp: unavailable (00000000)
ba5ca000 ba5cc000 splitter.sys Timestamp: unavailable (00000000)
a53c2000 a53d7000 wdmaud.sys Timestamp: unavailable (00000000)
ba380000 ba385000 Cdaudio.SYS Timestamp: unavailable (00000000)
b9cdd000 b9ce0000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

 

[Wrathchild]

Sorry, looks like I gave you a really old (2006!) dump file in the first post, just realized that!

 

[Wrathchild]

I was looking through the prior dumps and noticed some had multiple kmixer.sys entries; not sure if that was a red flag.

dumpchk -c C:\WINDOWS\Minidump\mini020613-01.dmp
Loading dump file C:\WINDOWS\Minidump\mini020613-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 295e0380
PfnDataBase 81846000
PsLoadedModuleList 80553fc0
PsActiveProcessHead 8055a158
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000019
BugCheckParameter1 00000020
BugCheckParameter2 89580000
BugCheckParameter3 89580228
BugCheckParameter4 0a450000
PaeEnabled 00000001
KdDebuggerDataBlock 80545ae0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000300
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00003fff
DriverListOffset 00006c10
DriverCount 00000099
StringPoolOffset 00009980
StringPoolSize 00001550
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack b58c6000
DebuggerDataOffset 00006980
DebuggerDataSize 00000290
DataBlocksOffset 0000aed0
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Wed Feb 06 06:27:39 2013
System Uptime: 0 days 12:52:26
start end module name
804d7000 806cf580 nt Checksum: 00204E7E Timestamp: Sun Apr 13 14:
31:06 2008 (4802516A)

Unloaded modules:
9fe0c000 9fe37000 kmixer.sys Timestamp: unavailable (00000000)
9fed7000 9ff02000 kmixer.sys Timestamp: unavailable (00000000)
9ff77000 9ffa2000 kmixer.sys Timestamp: unavailable (00000000)
a0b62000 a0b8d000 kmixer.sys Timestamp: unavailable (00000000)
ba72a000 ba72b000 drmkaud.sys Timestamp: unavailable (00000000)
ba1b8000 ba1c5000 DMusic.sys Timestamp: unavailable (00000000)
b96a1000 b96af000 swmidi.sys Timestamp: unavailable (00000000)
a0b8d000 a0bb0000 aec.sys Timestamp: unavailable (00000000)
ba5d6000 ba5d8000 splitter.sys Timestamp: unavailable (00000000)
a38f5000 a390a000 wdmaud.sys Timestamp: unavailable (00000000)
b385b000 b3860000 Cdaudio.SYS Timestamp: unavailable (00000000)
b99eb000 b99ee000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

 

[goombawaho]

I'll take a screen shot tomorrow to show what I meant. We really need that to see the faulting module.

 

[Wrathchild]

To document what I've tried so far:

[ul]
[li]Updated most drivers using SlimDrivers[/li]
[li]Ran Memtest for 20hrs (no erros)[/li]
[li]Added DisableSelectiveSuspend to registry (USB)[/li]
[li]Ran ChkDsk[/li]
[li]Disabled Indexing Service from msconfig[/li]
[li]Tried 2 different Externals and they work fine on friends machine[/li]
[li]Tried all USB ports on computer[/li]
[/ul]

To try:
Different Ram configurations

 

[IndianaSkinny]

Not that this helps much, but About 3 years ago I was getting the BSOD - BAD_POOL_HEADER about 3 times a week and couldn't find an issue with the OS. Eventually I assumed a hardware / motherboard issue and swapped the drive with another computer (both identical HP D530s). The problem stayed with the hardware. My system is still running and I scrapped the orignal hardware after multiple hardware diagnostics failed to diagnose an issue.

Do you have the same problem if you use a USB memory stick instead of a portable drive?

 

[Wrathchild]

No problem with jumpdrives or my other external 500gb USB2.0 drive either, they all work just fine. Only new large 3.0 drives are causing issues. What do you mean by "I scrapped the original hardware?" So as of now, based on what I tweaked last before crashing Windows I get one of the following:

[ul]
[li]BAD_POOL_HEADER[/li]
[li]PFN_LIST_CORRUPT[/li]
[li]IRQL_NOT_LESS_OR_EQUAL[/li]
[/ul]

This is ONLY when I plug in the new drive, other than that system is stable.

 

[IndianaSkinny]

<What do you mean by "I scrapped the original hardware?" >

I took the hard disk (with OS and my data) out of one computer and put it in another identical computer. No problems with the new hardware and no more BSDs so I presumed my issue was hardware in the original computer. I've used the memory and dvd drive with no issues so I'm assuming I had a bad motherboard or processor. That's one nice thing about having a few cheap old HP D530s around. Lot's of spare parts and the drivers are the same so there's no problem moving the drives around if you suspect a hardware problem.

 

[Wrathchild]

Gotcha, next step is reconfiguring/swapping out RAM and then after that it's pretty much build a new machine time!

 

[goombawaho]

Please take a look at this PDF document to "finish" the dump analysis as I requested. You need to do the second part to get more info on the faulting module. Please do this and post the extra output from the debugging before fiddling with the memory.

You'll see where I want you to click after the first part is done - "!analyze -v to get detailed debugging information"

Link

 

[Wrathchild]

OK so it looks like I need to install the tool you mentioned in the original post to get that analyze command correct? I was just using the Support Tools installed from the XP disc.