Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PFN_LIST_CORRUPT when hooking up new external drive

Status
Not open for further replies.
Wrathchild

Wrathchild

Technical User
Joined
Aug 24, 2001
Messages
303
Location
US
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.
 
Sort by date Sort by votes
Yeah, that's what I wanted you to do after the first post. There IS a reason why I post what I do - it could be experience or just stupidity, but let's hope it's the former.
 
Upvote 0 Downvote
will do - I didn't realize your method would give more details
 
Upvote 0 Downvote
yeah reason being I didn't want to install the friggin .NET Framework just to debug shit! :) So I've looked at the downloads and of course being MS I can't find what I need for XP 32-bit. Found 64-bit, but no 32. Could you please point me to the proper .NET Framework install so I can then install the debugging tools? thx!
 
Upvote 0 Downvote
Or I could just send you the file, whatevers easier
 
Upvote 0 Downvote
Nevermind, I installed BlueScreenView...much easier :)
So out of 17 crashes ntoskrnl.exe is the most frequent "Caused by Driver" entry with 13 hits, followed by CLASSPNP.SYS with 3 hits.
BlueSreenView shows only ntoskrnl.exe to be present in ALL crashes. I tried to copy the details in but formatting is tough; I included them in HTML if you want to just copy & paste and see the HTML that the program created for the last dmp file.


Crash List

Created by using BlueScreenView

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2
Mini020913-03.dmp 2/9/2013 7:44:31 PM BAD_POOL_HEADER 0x00000019 0x00000020 0x8973f350

Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description
0x8973f4e8 0x0a330005 ntoskrnl.exe ntoskrnl.exe+21cb5 NT Kernel & System

Product Name Company File Version Processor Crash Address Stack Address 1
Microsoft® Windows® Microsoft 5.1.2600.5512
Operating System Corporation (xpsp.080413-2111) 32-bit ntoskrnl.exe+21cb5 ntoskrnl.exe+6da86

Stack Address 2 Stack Address 3 Computer Name Full Path
ntoskrnl.exe+174f8 ntoskrnl.exe+1cdea C:\WINDOWS\Minidump\Mini020913-03.dmp

Processors Count Major Version Minor Version Dump File Size
1 15 2600 94,208

HTML: 
<html><head><title>Crash List</title></head>
<body>
 <h3>Crash List</h3>
<br><h4>Created by using <a href="[URL unfurl="true"]http://www.nirsoft.net/"[/URL] target="newwin">BlueScreenView</a></h4><p><table border="1" cellpadding="5"><tr bgcolor="E0E0E0">
<th>Dump File
<th>Crash Time
<th>Bug Check String
<th>Bug Check Code
<th>Parameter 1
<th>Parameter 2
<th>Parameter 3
<th>Parameter 4
<th>Caused By Driver
<th>Caused By Address
<th>File Description
<th>Product Name
<th>Company
<th>File Version
<th>Processor
<th>Crash Address
<th>Stack Address 1
<th>Stack Address 2
<th>Stack Address 3
<th>Computer Name
<th>Full Path
<th>Processors Count
<th>Major Version
<th>Minor Version
<th>Dump File Size
<tr><td bgcolor=#FFFFFF nowrap>Mini020913-03.dmp<td bgcolor=#FFFFFF nowrap>2/9/2013 7:44:31 PM<td bgcolor=#FFFFFF nowrap>BAD_POOL_HEADER<td bgcolor=#FFFFFF nowrap>0x00000019<td bgcolor=#FFFFFF nowrap>0x00000020<td bgcolor=#FFFFFF nowrap>0x8973f350<td bgcolor=#FFFFFF nowrap>0x8973f4e8<td bgcolor=#FFFFFF nowrap>0x0a330005<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+21cb5<td bgcolor=#FFFFFF nowrap>NT Kernel &amp; System<td bgcolor=#FFFFFF nowrap>Microsoft® Windows® Operating System<td bgcolor=#FFFFFF nowrap>Microsoft Corporation<td bgcolor=#FFFFFF nowrap>5.1.2600.5512 (xpsp.080413-2111)<td bgcolor=#FFFFFF nowrap>32-bit<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+21cb5<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+6da86<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+174f8<td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+1cdea<td bgcolor=#FFFFFF nowrap>&nbsp;<td bgcolor=#FFFFFF nowrap>C:\WINDOWS\Minidump\Mini020913-03.dmp<td bgcolor=#FFFFFF nowrap>1<td bgcolor=#FFFFFF nowrap>15<td bgcolor=#FFFFFF nowrap>2600<td bgcolor=#FFFFFF nowrap>94,208
</table>

</body></html>
 
Upvote 0 Downvote
Well, I'm at the end of being able to help and this article seems to point to needing to run more analysis (!analyze in windows debugger) on the problem which PROBABLY requires MS tools and .NET.

If you're unwilling to install .NET, we're kind of at the end unless someone else has a suggestion.


Have you updated every driver that you can??
Have you tried disabling devices or not allowing the driver to load via Autoruns (sound, wired network, wireless network) one at a time and then inserting the usb cable?
 
Upvote 0 Downvote
No I'm willing if you can point me to the correct installation of .NET Framework for XP 32bit
 
Upvote 0 Downvote
Before wasting more of your time (which I'm grateful for the help) and installing anything else on my computer let me try swapping out the RAM and ruling that out. Should get to that this weekend.
 
Upvote 0 Downvote
If you have extra RAM, go for it though you said you tested the RAM. Not a bad idea at all. Then why don't you check the drivers as I suggested (disable/test, disable test) followed by updates and more testing.
 
Upvote 0 Downvote
RAM tested ok but I checked it with 2 sticks in and it seems you're only supposed to do one at a time...so just swapping it will be easiest at this point.
Good idea with the drivers, I didn't realize you can just load one at a time. I'll read up on Autoruns and try it out if the RAM is fine. thx
 
Upvote 0 Downvote
it seems you're only supposed to do one at a time
Click to expand...
Not if you're using MemTest86+ - you can test the whole lot of ram. 1, 2, 4 sticks.

I didn't realize you can just load one at a time.
Click to expand...
You have to disable the device in BIOS (best way) or Device Manager or manually uncheck the driver in Autoruns.
With Autoruns, be very careful about what you uncheck. If you uncheck a controller driver, windows will not load!

This is the section where you'll find a lot of the sound/network, etc. drivers to disable in Autoruns
HKLM\System\CurrentControlSet\Services
 
Upvote 0 Downvote
OK so is BIOS a 'safer' way meaning less chance of screwing myself for drivers? Memtest86+ is what I used but I'm still gonna start with swapping out RAM to rule out a false negative.
 
Upvote 0 Downvote
Yes - swap the memory first if you have it and see what happens.
Did you try plugging the drive in while in Safe Mode? That would prove that it is something that is NOT running in safe mode that is likely causing the problem in regular mode!!!!!

Everything can't be disabled in the BIOS, so that's why I mentioned multiple methods. To me, the things that would most likely be the culprits are: Video driver, sound driver, wireless network card driver, wired ethernet.

You can't disable the video driver without actually removing it in Device Manager so I'd save that to last. Just update it to the latest and check for any firmware updates too. Wireless and sound could be disabled in AUTORUNS.
 
Upvote 0 Downvote
Latest update:
Tried the new drive in Safe Mode, still crashed
Got RAM from friend just need to actually swap it now
I installed turbotax and that reqd .NET Framework so hopefully I can now install the debugging tools
I borrowed a USB3.0 32gb jumpdrive from a friend and that worked fine
 
Upvote 0 Downvote
Finally got .NET Framework figured out and debugging tools installed; here's the !analyze from last few dumps:

Mini021813-01.dmp
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:
------------------

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c05

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
897524e8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80544a86 to 804f8cb5

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a359f3d8 80544a86 00000019 00000020 897524e8 nt+0x21cb5
a359f428 804ee4f8 897524f0 00000000 00000000 nt+0x6da86
a359f444 804f3dea 897524f0 89752530 89e87020 nt+0x174f8
a359f494 804fdae1 89752530 a359f4e0 a359f4d4 nt+0x1cdea
a359f4e4 806d2c35 00000000 00000000 a359f4fc nt+0x26ae1
a359f4fc 806d2866 badb0d00 00000000 a359f524 hal+0x2c35
a359f58c 804f07d4 89752530 00000000 00000000 hal+0x2866
a359f5c0 ba108bf4 a359f660 ba0f97e2 89607478 nt+0x197d4
a359f5c8 ba0f97e2 89607478 897524f0 00000000 CLASSPNP+0xbf4
a359f660 ba1093ed 89607478 897524f0 8a29a398 disk+0x17e2
a359f67c 8987ccc6 89607478 897524f0 8a29a398 CLASSPNP+0x13ed
a359f69c 804ee119 89607478 897524f0 00000000 0x8987ccc6
a359f6c8 805672db 89607478 89819880 896077f8 nt+0x17119
a359f6e0 805682d3 89607478 a359f6fc 00000000 nt+0x902db
a359f6f4 ba0fdfd1 89607478 a359f71c 896077f8 nt+0x912d3
a359f714 ba0fd724 00000000 00000000 a359f738 disk+0x5fd1
a359f73c ba10f06d 00607478 89607530 00000270 disk+0x5724
a359f754 ba0fbbe7 89607478 0007c058 89607530 CLASSPNP+0x706d
a359f798 ba0f8c5e 89607478 c000000d 89718cd8 disk+0x3be7
a359f82c ba1093ed 89607478 89718cd8 00000000 disk+0xc5e
a359f848 8987ccc6 89607478 89718cd8 00000000 CLASSPNP+0x13ed
a359f868 804ee119 89607478 89718cd8 00000270 0x8987ccc6
a359f8a4 ba332260 89607478 89751000 00000000 nt+0x17119
a359f920 ba333483 89dacca8 89751000 89ffd16c PartMgr+0x2260
a359f95c 804ee119 89dacbf0 89ffd008 89ffd190 PartMgr+0x3483
a359f960 89dacbf0 89ffd008 89ffd190 b9d7ac52 nt+0x17119
a359f964 89ffd008 89ffd190 b9d7ac52 8a28c000 0x89dacbf0
a359f968 89ffd190 b9d7ac52 8a28c000 60000001 0x89ffd008
a359f96c b9d7ac52 8a28c000 60000001 89761df0 0x89ffd190
a359f970 8a28c000 60000001 89761df0 a359fa64 snapman+0xfc52
a359f974 60000001 89761df0 a359fa64 b9d6ba5c 0x8a28c000
a359f978 89761df0 a359fa64 b9d6ba5c 00000000 0x60000001
a359f97c a359fa64 b9d6ba5c 00000000 89edd770 0x89761df0
a359f980 b9d6ba5c 00000000 89edd770 b9d7a31e 0xa359fa64
a359fa64 80588047 89d77f10 a359fa80 00000000 snapman+0xa5c
a359faa8 804f514c 89752388 89ee2c38 00000001 nt+0xb1047
a359fac4 805876f7 89752388 89752301 89ee2c38 nt+0x1e14c
a359fd1c 80587c56 89e95718 00000001 00000000 nt+0xb06f7
a359fd4c 804f58ce 00000003 80552040 8055b0fc nt+0xb0c56
a359fd74 80534c02 00000000 00000000 89e87020 nt+0x1e8ce
a359fdac 805c6160 00000000 00000000 00000000 nt+0x5dc02
a359fddc 80541dd2 80534b02 80000001 00000000 nt+0xef160
00000000 00000000 00000000 00000000 00000000 nt+0x6add2


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP+bf4
ba108bf4 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: CLASSPNP+bf4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

BUCKET_ID: WRONG_SYMBOLS

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

 
Upvote 0 Downvote
Mini021713-01.dmp
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:
------------------

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

BUGCHECK_STR: 0x4E_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80524bfd to 8053380e

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78c65c0 80524bfd 0000004e 00000007 00009e6a nt+0x5c80e
f78c6614 8054a036 8a0fe700 89b59000 805627c0 nt+0x4dbfd
f78c6640 8054b90b 89b59000 89b59000 89bd8ae0 nt+0x73036
f78c6680 80613e59 89b59000 00000000 89b4d678 nt+0x7490b
f78c6708 80614017 0000003f 000000ff 89bd8ae0 nt+0x13ce59
f78c671c 80614df9 89c10120 89bea600 89b4d678 nt+0x13d017
f78c6740 f764d09c 89b4d5c0 89bea600 f78c6798 nt+0x13ddf9
f78c6750 f764abc3 89b4d678 89bea600 0007c058 disk+0x609c
f78c6798 f7647c5e 89b4d5c0 89bea600 89b6ec70 disk+0x3bc3
f78c682c f76583ed 89b4d5c0 89b6ec70 00000000 disk+0xc5e
f78c6848 89d62cc6 89b4d5c0 89b6ec70 00000000 CLASSPNP+0x13ed
f78c6868 804e37f7 89b4d5c0 89b6ec70 00000270 0x89d62cc6
f78c68a4 f7711260 89b4d5c0 89b11000 00000000 nt+0xc7f7
f78c6920 f7712483 89b109d0 89b11000 89be25e4 PartMgr+0x2260
f78c695c 804e37f7 89b10918 89be2480 89be2608 PartMgr+0x3483
f78c6960 89b10918 89be2480 89be2608 f797ec52 nt+0xc7f7
f78c6964 89be2480 89be2608 f797ec52 89eab000 0x89b10918
f78c6968 89be2608 f797ec52 89eab000 60000001 0x89be2480
f78c696c f797ec52 89eab000 60000001 89be40f0 0x89be2608
f78c6970 89eab000 60000001 89be40f0 f78c6a64 snapman+0xfc52
f78c6974 60000001 89be40f0 f78c6a64 f796fa5c 0x89eab000
f78c6978 89be40f0 f78c6a64 f796fa5c 00000000 0x60000001
f78c697c f78c6a64 f796fa5c 00000000 89bec9f0 0x89be40f0
f78c6980 f796fa5c 00000000 89bec9f0 f797e31e 0xf78c6a64
f78c6a64 805b4ed7 89c50730 f78c6a80 00000000 snapman+0xa5c
f78c6aa8 80509638 89b8eab0 89c456e0 00000001 nt+0xdded7
f78c6ac4 805b4d73 89b8eab0 89b8ea01 89c456e0 nt+0x32638
f78c6d1c 8061bc0b 89b798a8 00000001 00000000 nt+0xddd73
f78c6d4c 8050631f 00000003 805592c0 805622fc nt+0x144c0b
f78c6d74 804e426b 00000000 00000000 8a0c0da8 nt+0x2f31f
f78c6dac 8057aeff 00000000 00000000 00000000 nt+0xd26b
f78c6ddc 804f88ea 804e4196 00000001 00000000 nt+0xa3eff
00000000 00000000 00000000 00000000 00000000 nt+0x218ea


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+5c80e
8053380e 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+5c80e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
 
Upvote 0 Downvote
Mini020913-03.dmp
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:
------------------

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c05

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
8973f350

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80544a86 to 804f8cb5

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4eb3d8 80544a86 00000019 00000020 8973f350 nt+0x21cb5
ba4eb428 804ee4f8 8973f358 00000000 00000000 nt+0x6da86
ba4eb444 804f3dea 8973f358 8973f398 8a283da8 nt+0x174f8
ba4eb494 804fdae1 8973f398 ba4eb4e0 ba4eb4d4 nt+0x1cdea
ba4eb4e4 806d2c35 00000000 00000000 ba4eb4fc nt+0x26ae1
ba4eb4fc 806d2866 badb0d00 00000000 ba4eb524 hal+0x2c35
ba4eb58c 804f07d4 8973f398 00000000 00000000 hal+0x2866
ba4eb5c0 ba108bf4 ba4eb660 ba0f97e2 896077c8 nt+0x197d4
ba4eb5c8 ba0f97e2 896077c8 8973f358 00000000 CLASSPNP+0xbf4
ba4eb660 ba1093ed 896077c8 8973f358 8a266868 disk+0x17e2
ba4eb67c 8988dcc6 896077c8 8973f358 8a266868 CLASSPNP+0x13ed
ba4eb69c 804ee119 896077c8 8973f358 00000000 0x8988dcc6
ba4eb6c8 805672db 896077c8 89ebaba0 89607b48 nt+0x17119
ba4eb6e0 805682d3 896077c8 ba4eb6fc 00000000 nt+0x902db
ba4eb6f4 ba0fdfd1 896077c8 ba4eb71c 89607b48 nt+0x912d3
ba4eb714 ba0fd724 00000000 00000000 ba4eb738 disk+0x5fd1
ba4eb73c ba10f06d 006077c8 89607880 00000270 disk+0x5724
ba4eb754 ba0fbbe7 896077c8 0007c058 89607880 CLASSPNP+0x706d
ba4eb798 ba0f8c5e 896077c8 c000000d 8974ac48 disk+0x3be7
ba4eb82c ba1093ed 896077c8 8974ac48 00000000 disk+0xc5e
ba4eb848 8988dcc6 896077c8 8974ac48 00000000 CLASSPNP+0x13ed
ba4eb868 804ee119 896077c8 8974ac48 00000270 0x8988dcc6
ba4eb8a4 ba332260 896077c8 89c7d000 00000000 nt+0x17119
ba4eb920 ba333483 89e3d608 89c7d000 89f9f68c PartMgr+0x2260
ba4eb95c 804ee119 89e3d550 89f9f528 89f9f6b0 PartMgr+0x3483
ba4eb960 89e3d550 89f9f528 89f9f6b0 b9d7ac52 nt+0x17119
ba4eb964 89f9f528 89f9f6b0 b9d7ac52 8a241000 0x89e3d550
ba4eb968 89f9f6b0 b9d7ac52 8a241000 60000001 0x89f9f528
ba4eb96c b9d7ac52 8a241000 60000001 897a3a20 0x89f9f6b0
ba4eb970 8a241000 60000001 897a3a20 ba4eba64 snapman+0xfc52
ba4eb974 60000001 897a3a20 ba4eba64 b9d6ba5c 0x8a241000
ba4eb978 897a3a20 ba4eba64 b9d6ba5c 00000000 0x60000001
ba4eb97c ba4eba64 b9d6ba5c 00000000 89d9e548 0x897a3a20
ba4eb980 b9d6ba5c 00000000 89d9e548 b9d7a31e 0xba4eba64
ba4eba64 80588047 8a022968 ba4eba80 00000000 snapman+0xa5c
ba4ebaa8 804f514c 897f33d8 89611680 00000001 nt+0xb1047
ba4ebac4 805876f7 897f33d8 897f3301 89611680 nt+0x1e14c
ba4ebd1c 80587c56 8a012980 00000001 00000000 nt+0xb06f7
ba4ebd4c 804f58ce 00000003 80552040 8055b0fc nt+0xb0c56
ba4ebd74 80534c02 00000000 00000000 8a283da8 nt+0x1e8ce
ba4ebdac 805c6160 00000000 00000000 00000000 nt+0x5dc02
ba4ebddc 80541dd2 80534b02 00000001 00000000 nt+0xef160
00000000 00000000 00000000 00000000 00000000 nt+0x6add2


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP+bf4
ba108bf4 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: CLASSPNP+bf4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
 
Upvote 0 Downvote
Mini020913-02.dmp
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: 00009615, page frame number
Arg3: 00000002, current share count
Arg4: 00000000, 0

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

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

BUGCHECK_STR: 0x4E_7

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8051f2e3 to 804f8cb5

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4e75b8 8051f2e3 0000004e 00000007 00009615 nt+0x21cb5
ba4e7610 8054380e 8a2c1b10 8a008000 8055b5c0 nt+0x482e3
ba4e7640 8054499d 8a008000 8a008000 89dd2618 nt+0x6c80e
ba4e7680 80565a8b 8a008000 00000000 896579d8 nt+0x6d99d
ba4e7708 80567410 0000003f 000000ff 89dd2618 nt+0x8ea8b
ba4e771c 805682a1 895d79c0 89c22b18 896579d8 nt+0x90410
ba4e7740 ba0fe09c 89657920 89c22b18 ba4e7798 nt+0x912a1
ba4e7750 ba0fbbc3 896579d8 89c22b18 0007c058 disk+0x609c
ba4e7798 ba0f8c5e 89657920 89c22b18 89765e70 disk+0x3bc3
ba4e782c ba1093ed 89657920 89765e70 00000000 disk+0xc5e
ba4e7848 8989dcc6 89657920 89765e70 00000000 CLASSPNP+0x13ed
ba4e7868 804ee119 89657920 89765e70 00000270 0x8989dcc6
ba4e78a4 ba332260 89657920 89614000 00000000 nt+0x17119
ba4e7920 ba333483 896577b0 89614000 8977a52c PartMgr+0x2260
ba4e795c 804ee119 896576f8 8977a3c8 8977a550 PartMgr+0x3483
ba4e7960 896576f8 8977a3c8 8977a550 b9d7ac52 nt+0x17119
ba4e7964 8977a3c8 8977a550 b9d7ac52 8a241000 0x896576f8
ba4e7968 8977a550 b9d7ac52 8a241000 60000001 0x8977a3c8
ba4e796c b9d7ac52 8a241000 60000001 8a00bc60 0x8977a550
ba4e7970 8a241000 60000001 8a00bc60 ba4e7a64 snapman+0xfc52
ba4e7974 60000001 8a00bc60 ba4e7a64 b9d6ba5c 0x8a241000
ba4e7978 8a00bc60 ba4e7a64 b9d6ba5c 00000000 0x60000001
ba4e797c ba4e7a64 b9d6ba5c 00000000 89d12548 0x8a00bc60
ba4e7980 b9d6ba5c 00000000 89d12548 b9d7a31e 0xba4e7a64
ba4e7a64 80588047 89d45c20 ba4e7a80 00000000 snapman+0xa5c
ba4e7aa8 804f514c 89799ea0 897d7698 00000001 nt+0xb1047
ba4e7ac4 805876f7 89799ea0 89799e01 897d7698 nt+0x1e14c
ba4e7d1c 80587c56 89e71520 00000001 00000000 nt+0xb06f7
ba4e7d4c 804f58ce 00000003 80552040 8055b0fc nt+0xb0c56
ba4e7d74 80534c02 00000000 00000000 8a283020 nt+0x1e8ce
ba4e7dac 805c6160 00000000 00000000 00000000 nt+0x5dc02
ba4e7ddc 80541dd2 80534b02 00000001 00000000 nt+0xef160
00000000 00000000 00000000 00000000 00000000 nt+0x6add2


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+21cb5
804f8cb5 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+21cb5

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
 
Upvote 0 Downvote
Mini020913-01.dmp
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 8b946b1a, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80503e62, address which referenced memory

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

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: PartMgr

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 480253b0

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
8b946b1a

CURRENT_IRQL: 2

FAULTING_IP:
nt+2ce62
80503e62 668b480e mov cx,word ptr [eax+0Eh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 8054380e to 80503e62

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4eb7b4 8054380e 8a2c1890 804f0512 8055b5c0 nt+0x2ce62
ba4eb7e4 8054499d 895bd000 804f0512 804f8f22 nt+0x6c80e
ba4eb824 ba33146f 895bd000 00000000 89698658 nt+0x6d99d
ba4eb89c ba3321e2 00698658 8a066948 ca173136 PartMgr+0x146f
ba4eb920 ba333483 89698658 89735000 895ea16c PartMgr+0x21e2
ba4eb95c 804ee119 896985a0 895ea008 895ea190 PartMgr+0x3483
ba4eb960 896985a0 895ea008 895ea190 b9d7ac52 nt+0x17119
ba4eb964 895ea008 895ea190 b9d7ac52 8a241000 0x896985a0
ba4eb968 895ea190 b9d7ac52 8a241000 60000001 0x895ea008
ba4eb96c b9d7ac52 8a241000 60000001 89d3ccb8 0x895ea190
ba4eb970 8a241000 60000001 89d3ccb8 ba4eba64 snapman+0xfc52
ba4eb974 60000001 89d3ccb8 ba4eba64 b9d6ba5c 0x8a241000
ba4eb978 89d3ccb8 ba4eba64 b9d6ba5c 00000000 0x60000001
ba4eb97c ba4eba64 b9d6ba5c 00000000 89d7b6e8 0x89d3ccb8
ba4eb980 b9d6ba5c 00000000 89d7b6e8 b9d7a31e 0xba4eba64
ba4eba64 80588047 89705508 ba4eba80 00000000 snapman+0xa5c
ba4ebaa8 804f514c 89e25990 89c835c8 00000001 nt+0xb1047
ba4ebac4 805876f7 89e25990 89e25901 89c835c8 nt+0x1e14c
ba4ebd1c 80587c56 89750190 00000001 00000000 nt+0xb06f7
ba4ebd4c 804f58ce 00000003 80552040 8055b0fc nt+0xb0c56
ba4ebd74 80534c02 00000000 00000000 8a283da8 nt+0x1e8ce
ba4ebdac 805c6160 00000000 00000000 00000000 nt+0x5dc02
ba4ebddc 80541dd2 80534b02 00000001 00000000 nt+0xef160
00000000 00000000 00000000 00000000 00000000 nt+0x6add2


STACK_COMMAND: kb

FOLLOWUP_IP:
PartMgr+146f
ba33146f ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: PartMgr+146f

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: PartMgr.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Keyboy
  • Locked
  • Question Question
Computer freezing up
Replies
3
Views
2K
Rick998
Rick998
grnzbra
  • Locked
  • Question Question
Formatting Full Hard Drive
Replies
7
Views
986
austinpctech
austinpctech
Sebastian42
  • Locked
  • Question Question
Getting a drive REdetected
Replies
18
Views
2K
Rick998
Rick998
dpellegrini
  • Locked
  • Question Question
Unable to map a drive
Replies
12
Views
1K
dpellegrini
dpellegrini
Flinx
  • Locked
  • Question Question
the SAGA of trying to get a computer to sleep and wake up on a schedule
Replies
1
Views
3K
Flinx
Flinx

Part and Inventory Search

Sponsor

Back
Top