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]

I don't see anything that I can put my finger on in what you gave, but I do keep seeing this:

Kernel symbols are WRONG. Please fix symbols to do analysis.

Are you pointing to the symbols on the internet as in this line?
windbg -y srv*C:\symbols*

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

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

 

[Wrathchild]

Apologies! Forget you said to run it from the command line originally...here are the last few dumps:

Loading Dump File [c:\Windows\MiniDump\Mini021813-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'c:\i386'
Symbol search path is: srv*C:\symbols*

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

Executable search path is: c:\i386
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Mon Feb 18 18:33:57.984 2013 (UTC - 5:00)
System Uptime: 0 days 0:04:19.546
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 897524e8, 89752680, a330032}

*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClassCompleteRequest+11 )

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 897524e8, The pool entry we were looking for within the page.
Arg3: 89752680, The next pool entry.
Arg4: 0a330032, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 897524e8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

IRP_ADDRESS: 897524f0

LOCK_ADDRESS: 80551f60 -- (!locks 80551f60)

Resource @ nt!PiEngineLock (0x80551f60) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x80551f60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80544a86 to 804f8cb5

STACK_TEXT:
a359f3d8 80544a86 00000019 00000020 897524e8 nt!KeBugCheckEx+0x1b
a359f428 804ee4f8 897524f0 00000000 00000000 nt!ExFreePoolWithTag+0x2a0
a359f444 804f3dea 897524f0 89752530 89e87020 nt!IopFreeIrp+0xf2
a359f494 804fdae1 89752530 a359f4e0 a359f4d4 nt!IopCompleteRequest+0x316
a359f4e4 806d2c35 00000000 00000000 a359f4fc nt!KiDeliverApc+0xb3
a359f4e4 806d2866 00000000 00000000 a359f4fc hal!HalpApcInterrupt+0xc5
a359f56c 804faaf3 89752530 897524f0 00000000 hal!KeReleaseInStackQueuedSpinLock+0x16
a359f58c 804f07d4 89752530 00000000 00000000 nt!KeInsertQueueApc+0x4b
a359f5c0 ba108bf4 a359f660 ba0f97e2 89607478 nt!IopfCompleteRequest+0x1d8
a359f5c8 ba0f97e2 89607478 897524f0 00000000 CLASSPNP!ClassCompleteRequest+0x11
a359f660 ba1093ed 89607478 897524f0 8a29a398 disk!DiskDeviceControl+0x11ae
a359f67c 8987ccc6 89607478 897524f0 8a29a398 CLASSPNP!ClassDeviceControlDispatch+0x48
WARNING: Frame IP not in any known module. Following frames may be wrong.
a359f69c 804ee119 89607478 897524f0 00000000 0x8987ccc6
a359f6ac 805671fa 89607530 00000000 89819878 nt!IopfCallDriver+0x31
a359f6c8 805672db 89607478 89819880 896077f8 nt!FstubGetDiskGeometry+0x9a
a359f6e0 805682d3 89607478 a359f6fc 00000000 nt!FstubAllocateDiskInformation+0x85
a359f6f4 ba0fdfd1 89607478 a359f71c 896077f8 nt!IoReadPartitionTableEx+0x13
a359f714 ba0fd724 00000000 00000000 a359f738 disk!DiskReadPartitionTableEx+0x6f
a359f73c ba10f06d 00607478 89607530 00000270 disk!DiskEnumerateDevice+0x32
a359f754 ba0fbbe7 89607478 0007c058 89607530 CLASSPNP!ClassInvalidateBusRelations+0x36
a359f798 ba0f8c5e 89607478 c000000d 89718cd8 disk!DiskIoctlSetDriveLayoutEx+0xfb
a359f82c ba1093ed 89607478 89718cd8 00000000 disk!DiskDeviceControl+0x62a
a359f848 8987ccc6 89607478 89718cd8 00000000 CLASSPNP!ClassDeviceControlDispatch+0x48
a359f868 804ee119 89607478 89718cd8 00000270 0x8987ccc6
a359f878 ba3320cb 89dacca8 e1876180 89751000 nt!IopfCallDriver+0x31
a359f8a4 ba332260 89607478 89751000 00000000 PartMgr!PmWritePartitionTableEx+0x59
a359f920 ba333483 89dacca8 89751000 89ffd16c PartMgr!PmAddSignatures+0x170
a359f95c 804ee119 89dacbf0 89ffd008 89ffd190 PartMgr!PmPnp+0x315
a359f96c b9d7ac52 8a28c000 60000001 89761df0 nt!IopfCallDriver+0x31
a359fa28 804ee119 89d77f10 89ffd008 a359faa4 snapman+0xfc52
a359fa38 80587fc9 a359faa4 89752388 00000000 nt!IopfCallDriver+0x31
a359fa64 80588047 89d77f10 a359fa80 00000000 nt!IopSynchronousCall+0xb7
a359faa8 804f514c 89752388 89ee2c38 00000001 nt!IopStartDevice+0x4d
a359fac4 805876f7 89752388 89752301 89ee2c38 nt!PipProcessStartPhase1+0x4e
a359fd1c 80587c56 89e95718 00000001 00000000 nt!PipProcessDevNodeTree+0x1db
a359fd4c 804f58ce 00000003 80552040 8055b0fc nt!PiRestartDevice+0x80
a359fd74 80534c02 00000000 00000000 89e87020 nt!PipDeviceActionWorker+0x15e
a359fdac 805c6160 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
a359fddc 80541dd2 80534b02 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!ClassCompleteRequest+11
ba108bf4 5d pop ebp

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLASSPNP!ClassCompleteRequest+11

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c05

FAILURE_BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 897524e8, The pool entry we were looking for within the page.
Arg3: 89752680, The next pool entry.
Arg4: 0a330032, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 897524e8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

IRP_ADDRESS: 897524f0

LOCK_ADDRESS: 80551f60 -- (!locks 80551f60)

Resource @ nt!PiEngineLock (0x80551f60) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x80551f60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80544a86 to 804f8cb5

STACK_TEXT:
a359f3d8 80544a86 00000019 00000020 897524e8 nt!KeBugCheckEx+0x1b
a359f428 804ee4f8 897524f0 00000000 00000000 nt!ExFreePoolWithTag+0x2a0
a359f444 804f3dea 897524f0 89752530 89e87020 nt!IopFreeIrp+0xf2
a359f494 804fdae1 89752530 a359f4e0 a359f4d4 nt!IopCompleteRequest+0x316
a359f4e4 806d2c35 00000000 00000000 a359f4fc nt!KiDeliverApc+0xb3
a359f4e4 806d2866 00000000 00000000 a359f4fc hal!HalpApcInterrupt+0xc5
a359f56c 804faaf3 89752530 897524f0 00000000 hal!KeReleaseInStackQueuedSpinLock+0x16
a359f58c 804f07d4 89752530 00000000 00000000 nt!KeInsertQueueApc+0x4b
a359f5c0 ba108bf4 a359f660 ba0f97e2 89607478 nt!IopfCompleteRequest+0x1d8
a359f5c8 ba0f97e2 89607478 897524f0 00000000 CLASSPNP!ClassCompleteRequest+0x11
a359f660 ba1093ed 89607478 897524f0 8a29a398 disk!DiskDeviceControl+0x11ae
a359f67c 8987ccc6 89607478 897524f0 8a29a398 CLASSPNP!ClassDeviceControlDispatch+0x48
WARNING: Frame IP not in any known module. Following frames may be wrong.
a359f69c 804ee119 89607478 897524f0 00000000 0x8987ccc6
a359f6ac 805671fa 89607530 00000000 89819878 nt!IopfCallDriver+0x31
a359f6c8 805672db 89607478 89819880 896077f8 nt!FstubGetDiskGeometry+0x9a
a359f6e0 805682d3 89607478 a359f6fc 00000000 nt!FstubAllocateDiskInformation+0x85
a359f6f4 ba0fdfd1 89607478 a359f71c 896077f8 nt!IoReadPartitionTableEx+0x13
a359f714 ba0fd724 00000000 00000000 a359f738 disk!DiskReadPartitionTableEx+0x6f
a359f73c ba10f06d 00607478 89607530 00000270 disk!DiskEnumerateDevice+0x32
a359f754 ba0fbbe7 89607478 0007c058 89607530 CLASSPNP!ClassInvalidateBusRelations+0x36
a359f798 ba0f8c5e 89607478 c000000d 89718cd8 disk!DiskIoctlSetDriveLayoutEx+0xfb
a359f82c ba1093ed 89607478 89718cd8 00000000 disk!DiskDeviceControl+0x62a
a359f848 8987ccc6 89607478 89718cd8 00000000 CLASSPNP!ClassDeviceControlDispatch+0x48
a359f868 804ee119 89607478 89718cd8 00000270 0x8987ccc6
a359f878 ba3320cb 89dacca8 e1876180 89751000 nt!IopfCallDriver+0x31
a359f8a4 ba332260 89607478 89751000 00000000 PartMgr!PmWritePartitionTableEx+0x59
a359f920 ba333483 89dacca8 89751000 89ffd16c PartMgr!PmAddSignatures+0x170
a359f95c 804ee119 89dacbf0 89ffd008 89ffd190 PartMgr!PmPnp+0x315
a359f96c b9d7ac52 8a28c000 60000001 89761df0 nt!IopfCallDriver+0x31
a359fa28 804ee119 89d77f10 89ffd008 a359faa4 snapman+0xfc52
a359fa38 80587fc9 a359faa4 89752388 00000000 nt!IopfCallDriver+0x31
a359fa64 80588047 89d77f10 a359fa80 00000000 nt!IopSynchronousCall+0xb7
a359faa8 804f514c 89752388 89ee2c38 00000001 nt!IopStartDevice+0x4d
a359fac4 805876f7 89752388 89752301 89ee2c38 nt!PipProcessStartPhase1+0x4e
a359fd1c 80587c56 89e95718 00000001 00000000 nt!PipProcessDevNodeTree+0x1db
a359fd4c 804f58ce 00000003 80552040 8055b0fc nt!PiRestartDevice+0x80
a359fd74 80534c02 00000000 00000000 89e87020 nt!PipDeviceActionWorker+0x15e
a359fdac 805c6160 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
a359fddc 80541dd2 80534b02 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!ClassCompleteRequest+11
ba108bf4 5d pop ebp

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLASSPNP!ClassCompleteRequest+11

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c05

FAILURE_BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 897524e8, The pool entry we were looking for within the page.
Arg3: 89752680, The next pool entry.
Arg4: 0a330032, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 897524e8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

IRP_ADDRESS: 897524f0

LOCK_ADDRESS: 80551f60 -- (!locks 80551f60)

Resource @ nt!PiEngineLock (0x80551f60) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x80551f60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80544a86 to 804f8cb5

STACK_TEXT:
a359f3d8 80544a86 00000019 00000020 897524e8 nt!KeBugCheckEx+0x1b
a359f428 804ee4f8 897524f0 00000000 00000000 nt!ExFreePoolWithTag+0x2a0
a359f444 804f3dea 897524f0 89752530 89e87020 nt!IopFreeIrp+0xf2
a359f494 804fdae1 89752530 a359f4e0 a359f4d4 nt!IopCompleteRequest+0x316
a359f4e4 806d2c35 00000000 00000000 a359f4fc nt!KiDeliverApc+0xb3
a359f4e4 806d2866 00000000 00000000 a359f4fc hal!HalpApcInterrupt+0xc5
a359f56c 804faaf3 89752530 897524f0 00000000 hal!KeReleaseInStackQueuedSpinLock+0x16
a359f58c 804f07d4 89752530 00000000 00000000 nt!KeInsertQueueApc+0x4b
a359f5c0 ba108bf4 a359f660 ba0f97e2 89607478 nt!IopfCompleteRequest+0x1d8
a359f5c8 ba0f97e2 89607478 897524f0 00000000 CLASSPNP!ClassCompleteRequest+0x11
a359f660 ba1093ed 89607478 897524f0 8a29a398 disk!DiskDeviceControl+0x11ae
a359f67c 8987ccc6 89607478 897524f0 8a29a398 CLASSPNP!ClassDeviceControlDispatch+0x48
WARNING: Frame IP not in any known module. Following frames may be wrong.
a359f69c 804ee119 89607478 897524f0 00000000 0x8987ccc6
a359f6ac 805671fa 89607530 00000000 89819878 nt!IopfCallDriver+0x31
a359f6c8 805672db 89607478 89819880 896077f8 nt!FstubGetDiskGeometry+0x9a
a359f6e0 805682d3 89607478 a359f6fc 00000000 nt!FstubAllocateDiskInformation+0x85
a359f6f4 ba0fdfd1 89607478 a359f71c 896077f8 nt!IoReadPartitionTableEx+0x13
a359f714 ba0fd724 00000000 00000000 a359f738 disk!DiskReadPartitionTableEx+0x6f
a359f73c ba10f06d 00607478 89607530 00000270 disk!DiskEnumerateDevice+0x32
a359f754 ba0fbbe7 89607478 0007c058 89607530 CLASSPNP!ClassInvalidateBusRelations+0x36
a359f798 ba0f8c5e 89607478 c000000d 89718cd8 disk!DiskIoctlSetDriveLayoutEx+0xfb
a359f82c ba1093ed 89607478 89718cd8 00000000 disk!DiskDeviceControl+0x62a
a359f848 8987ccc6 89607478 89718cd8 00000000 CLASSPNP!ClassDeviceControlDispatch+0x48
a359f868 804ee119 89607478 89718cd8 00000270 0x8987ccc6
a359f878 ba3320cb 89dacca8 e1876180 89751000 nt!IopfCallDriver+0x31
a359f8a4 ba332260 89607478 89751000 00000000 PartMgr!PmWritePartitionTableEx+0x59
a359f920 ba333483 89dacca8 89751000 89ffd16c PartMgr!PmAddSignatures+0x170
a359f95c 804ee119 89dacbf0 89ffd008 89ffd190 PartMgr!PmPnp+0x315
a359f96c b9d7ac52 8a28c000 60000001 89761df0 nt!IopfCallDriver+0x31
a359fa28 804ee119 89d77f10 89ffd008 a359faa4 snapman+0xfc52
a359fa38 80587fc9 a359faa4 89752388 00000000 nt!IopfCallDriver+0x31
a359fa64 80588047 89d77f10 a359fa80 00000000 nt!IopSynchronousCall+0xb7
a359faa8 804f514c 89752388 89ee2c38 00000001 nt!IopStartDevice+0x4d
a359fac4 805876f7 89752388 89752301 89ee2c38 nt!PipProcessStartPhase1+0x4e
a359fd1c 80587c56 89e95718 00000001 00000000 nt!PipProcessDevNodeTree+0x1db
a359fd4c 804f58ce 00000003 80552040 8055b0fc nt!PiRestartDevice+0x80
a359fd74 80534c02 00000000 00000000 89e87020 nt!PipDeviceActionWorker+0x15e
a359fdac 805c6160 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
a359fddc 80541dd2 80534b02 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!ClassCompleteRequest+11
ba108bf4 5d pop ebp

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLASSPNP!ClassCompleteRequest+11

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c05

FAILURE_BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

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

 

[Wrathchild]

Loading Dump File [c:\Windows\MiniDump\Mini021713-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'c:\i386'
Symbol search path is: srv*C:\symbols*

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

Executable search path is: c:\i386
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Feb 17 05:39:59.343 2013 (UTC - 5:00)
System Uptime: 0 days 0:03:18.843
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 9e6a, 2, 0}

*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : memory_corruption ( nt!MiDeferredUnlockPages+13d )

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

kd> !analyze -v
*******************************************************************************
* *
* 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: 00000007, A driver has unlocked a page more times than it locked it
Arg2: 00009e6a, page frame number
Arg3: 00000002, current share count
Arg4: 00000000, 0

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


BUGCHECK_STR: 0x4E_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)

Resource @ nt!PiEngineLock (0x805591e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80524bfd to 8053380e

STACK_TEXT:
f78c65c0 80524bfd 0000004e 00000007 00009e6a nt!KeBugCheckEx+0x1b
f78c65e0 804ec23d 89b59000 89b59000 805627c0 nt!MiDecrementReferenceCount+0x4e
f78c6614 8054a036 8a0fe700 89b59000 805627c0 nt!MiDeferredUnlockPages+0x13d
f78c6640 8054b90b 89b59000 89b59000 89bd8ae0 nt!MiFreePoolPages+0xac
f78c6680 80613e59 89b59000 00000000 89b4d678 nt!ExFreePoolWithTag+0x1b7
f78c6708 80614017 0000003f 000000ff 89bd8ae0 nt!IoWritePartitionTable+0x389
f78c671c 80614df9 89c10120 89bea600 89b4d678 nt!FstubWritePartitionTableMBR+0x2c
f78c6740 f764d09c 89b4d5c0 89bea600 f78c6798 nt!IoWritePartitionTableEx+0xef
f78c6750 f764abc3 89b4d678 89bea600 0007c058 disk!DiskWritePartitionTableEx+0x34
f78c6798 f7647c5e 89b4d5c0 89bea600 89b6ec70 disk!DiskIoctlSetDriveLayoutEx+0xd7
f78c682c f76583ed 89b4d5c0 89b6ec70 00000000 disk!DiskDeviceControl+0x62a
f78c6848 89d62cc6 89b4d5c0 89b6ec70 00000000 CLASSPNP!ClassDeviceControlDispatch+0x48
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78c6868 804e37f7 89b4d5c0 89b6ec70 00000270 0x89d62cc6
f78c6878 f77110cb 89b109d0 e180cd40 89b11000 nt!IopfCallDriver+0x31
f78c68a4 f7711260 89b4d5c0 89b11000 00000000 PartMgr!PmWritePartitionTableEx+0x59
f78c6920 f7712483 89b109d0 89b11000 89be25e4 PartMgr!PmAddSignatures+0x170
f78c695c 804e37f7 89b10918 89be2480 89be2608 PartMgr!PmPnp+0x315
f78c696c f797ec52 89eab000 60000001 89be40f0 nt!IopfCallDriver+0x31
f78c6a28 804e37f7 89c50730 89be2480 f78c6aa4 snapman+0xfc52
f78c6a38 8059be17 f78c6aa4 89b8eab0 00000000 nt!IopfCallDriver+0x31
f78c6a64 805b4ed7 89c50730 f78c6a80 00000000 nt!IopSynchronousCall+0xb7
f78c6aa8 80509638 89b8eab0 89c456e0 00000001 nt!IopStartDevice+0x4d
f78c6ac4 805b4d73 89b8eab0 89b8ea01 89c456e0 nt!PipProcessStartPhase1+0x4e
f78c6d1c 8061bc0b 89b798a8 00000001 00000000 nt!PipProcessDevNodeTree+0x1db
f78c6d4c 8050631f 00000003 805592c0 805622fc nt!PiRestartDevice+0x80
f78c6d74 804e426b 00000000 00000000 8a0c0da8 nt!PipDeviceActionWorker+0x15e
f78c6dac 8057aeff 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
f78c6ddc 804f88ea 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeferredUnlockPages+13d
804ec23d e982790000 jmp nt!MiDeferredUnlockPages+0x13d (804f3bc4)

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiDeferredUnlockPages+13d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_7_nt!MiDeferredUnlockPages+13d

BUCKET_ID: 0x4E_7_nt!MiDeferredUnlockPages+13d

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

 

[Wrathchild]

Loading Dump File [c:\Windows\MiniDump\Mini020913-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'c:\i386'
Symbol search path is: srv*C:\symbols*

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

Executable search path is: c:\i386
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Sat Feb 9 19:43:27.437 2013 (UTC - 5:00)
System Uptime: 0 days 0:06:23.000
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 8973f350, 8973f4e8, a330005}

*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClassCompleteRequest+11 )

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 8973f350, The pool entry we were looking for within the page.
Arg3: 8973f4e8, The next pool entry.
Arg4: 0a330005, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 8973f350

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

IRP_ADDRESS: 8973f358

LOCK_ADDRESS: 80551f60 -- (!locks 80551f60)

Resource @ nt!PiEngineLock (0x80551f60) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x80551f60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80544a86 to 804f8cb5

STACK_TEXT:
ba4eb3d8 80544a86 00000019 00000020 8973f350 nt!KeBugCheckEx+0x1b
ba4eb428 804ee4f8 8973f358 00000000 00000000 nt!ExFreePoolWithTag+0x2a0
ba4eb444 804f3dea 8973f358 8973f398 8a283da8 nt!IopFreeIrp+0xf2
ba4eb494 804fdae1 8973f398 ba4eb4e0 ba4eb4d4 nt!IopCompleteRequest+0x316
ba4eb4e4 806d2c35 00000000 00000000 ba4eb4fc nt!KiDeliverApc+0xb3
ba4eb4e4 806d2866 00000000 00000000 ba4eb4fc hal!HalpApcInterrupt+0xc5
ba4eb56c 804faaf3 8973f398 8973f358 00000000 hal!KeReleaseInStackQueuedSpinLock+0x16
ba4eb58c 804f07d4 8973f398 00000000 00000000 nt!KeInsertQueueApc+0x4b
ba4eb5c0 ba108bf4 ba4eb660 ba0f97e2 896077c8 nt!IopfCompleteRequest+0x1d8
ba4eb5c8 ba0f97e2 896077c8 8973f358 00000000 CLASSPNP!ClassCompleteRequest+0x11
ba4eb660 ba1093ed 896077c8 8973f358 8a266868 disk!DiskDeviceControl+0x11ae
ba4eb67c 8988dcc6 896077c8 8973f358 8a266868 CLASSPNP!ClassDeviceControlDispatch+0x48
WARNING: Frame IP not in any known module. Following frames may be wrong.
ba4eb69c 804ee119 896077c8 8973f358 00000000 0x8988dcc6
ba4eb6ac 805671fa 89607880 00000000 89ebab98 nt!IopfCallDriver+0x31
ba4eb6c8 805672db 896077c8 89ebaba0 89607b48 nt!FstubGetDiskGeometry+0x9a
ba4eb6e0 805682d3 896077c8 ba4eb6fc 00000000 nt!FstubAllocateDiskInformation+0x85
ba4eb6f4 ba0fdfd1 896077c8 ba4eb71c 89607b48 nt!IoReadPartitionTableEx+0x13
ba4eb714 ba0fd724 00000000 00000000 ba4eb738 disk!DiskReadPartitionTableEx+0x6f
ba4eb73c ba10f06d 006077c8 89607880 00000270 disk!DiskEnumerateDevice+0x32
ba4eb754 ba0fbbe7 896077c8 0007c058 89607880 CLASSPNP!ClassInvalidateBusRelations+0x36
ba4eb798 ba0f8c5e 896077c8 c000000d 8974ac48 disk!DiskIoctlSetDriveLayoutEx+0xfb
ba4eb82c ba1093ed 896077c8 8974ac48 00000000 disk!DiskDeviceControl+0x62a
ba4eb848 8988dcc6 896077c8 8974ac48 00000000 CLASSPNP!ClassDeviceControlDispatch+0x48
ba4eb868 804ee119 896077c8 8974ac48 00000270 0x8988dcc6
ba4eb878 ba3320cb 89e3d608 e1801858 89c7d000 nt!IopfCallDriver+0x31
ba4eb8a4 ba332260 896077c8 89c7d000 00000000 PartMgr!PmWritePartitionTableEx+0x59
ba4eb920 ba333483 89e3d608 89c7d000 89f9f68c PartMgr!PmAddSignatures+0x170
ba4eb95c 804ee119 89e3d550 89f9f528 89f9f6b0 PartMgr!PmPnp+0x315
ba4eb96c b9d7ac52 8a241000 60000001 897a3a20 nt!IopfCallDriver+0x31
ba4eba28 804ee119 8a022968 89f9f528 ba4ebaa4 snapman+0xfc52
ba4eba38 80587fc9 ba4ebaa4 897f33d8 00000000 nt!IopfCallDriver+0x31
ba4eba64 80588047 8a022968 ba4eba80 00000000 nt!IopSynchronousCall+0xb7
ba4ebaa8 804f514c 897f33d8 89611680 00000001 nt!IopStartDevice+0x4d
ba4ebac4 805876f7 897f33d8 897f3301 89611680 nt!PipProcessStartPhase1+0x4e
ba4ebd1c 80587c56 8a012980 00000001 00000000 nt!PipProcessDevNodeTree+0x1db
ba4ebd4c 804f58ce 00000003 80552040 8055b0fc nt!PiRestartDevice+0x80
ba4ebd74 80534c02 00000000 00000000 8a283da8 nt!PipDeviceActionWorker+0x15e
ba4ebdac 805c6160 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
ba4ebddc 80541dd2 80534b02 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!ClassCompleteRequest+11
ba108bf4 5d pop ebp

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLASSPNP!ClassCompleteRequest+11

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c05

FAILURE_BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

BUCKET_ID: 0x19_20_CLASSPNP!ClassCompleteRequest+11

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

 

[Wrathchild]

let me know if you'd like more; not sure why the first one pasted 3x

 

[Wrathchild]

I see "memory corruption" in there so hopefully it's just RAM; still haven't had time to get to that yet

 

[goombawaho]

I think you should (in order) do the following then report back with what happened after doing each thing. Please.
1. Replace the RAM and see what happens. Report back.
2. Extract the CLASSPNP.SYS from the XP SP3 CD and replace it on the system and reboot. See what happens.
3. As I had stated before, either update all drivers that you can OR disable them from starting one at a time and test after each disabling.
4. Remove anti-virus software
5. Change PNP OS setting in BIOS (switch it from whatever it is) ON > OFF or OFF > ON
6. Run CHKDSK on hard drive, run manufacturer's test on hard drive.


You aren't overclocking your memory are you? Set to defaults in BIOS for memory???

BTW - my XP SP3 laptop shows c:\windows\system32\drivers\classpnp.sys 49KB 4/13/2008 11:46 p.m.
Right clicking gives the following "File Version: 5.1.2600.5512 (xpsp.080413-2108)

 

[Wrathchild]

I will do that...classpnp.sys shows the same date/version and no not overclocking. Thx for sticking with me.

 

[goombawaho]

I'll stick with you even if it ends in hand wringing. I'm kind of surprised that you haven't changed the RAM already since it only takes 3 minutes. Most people can't do this because they don't have RAM sitting around.

 

[Wrathchild]

Currently trying to bring my system back from the dead; swapped RAM and got "SYSTEM FAILED CPU TEST" and still getting it after putting my original RAM back in...arghh

 

[goombawaho]

Time to put the old girl down.

 

[Wrathchild]

gonna borrow a PSU and if that doesn't help then maybe reseat the CPU...not much else to try after that. Took the battery & video card out and put back in.

 

[goombawaho]

If you were working for $10/hr, you would probably be at the price of a decent used computer by now. Time is money my brotha.

 

[Wrathchild]

LMAO I know huh! I actually do like to figure things out though...but even I have my cutoff point.