troubleshooting Question

BDSOD Stop Error 0X000000F4

Avatar of alayne
alayneFlag for United States of America asked on
Windows XP
8 Comments1 Solution1312 ViewsLast Modified:
Dell Optiplex E4300 with port replicator.  Seems to happen after undocking laptop.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\aheish\Desktop\Minidumps\Mini122209-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 22 10:02:23.948 2009 (GMT-5)
System Uptime: 0 days 0:11:42.957
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 44, {88982bb0, d64, 0, 0}

*** WARNING: Unable to verify timestamp for hardlock.sys
*** ERROR: Module load completed but symbols could not be loaded for hardlock.sys
Probably caused by : parport.sys ( parport!P4CompleteRequest+1d )

Followup: MachineOwner

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

A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arg1: 88982bb0, Address of the IRP
Arg2: 00000d64
Arg3: 00000000
Arg4: 00000000

Debugging Details:

IRP_ADDRESS:  88982bb0






LOCK_ADDRESS:  8055b4e0 -- (!locks 8055b4e0)

Resource @ nt!PiEngineLock (0x8055b4e0)    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

      Lock address  : 0x8055b4e0
      Thread Count  : 0
      Thread address: 0x00000000
      Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 804f18ec to 804f9f43

ba4fbad0 804f18ec 00000044 88982bb0 00000d64 nt!KeBugCheckEx+0x1b
ba4fbb08 b7b9d0e5 89d4cdcc ba4fbb28 b7b9d105 nt!IopfCompleteRequest+0x2ce
ba4fbb14 b7b9d105 88982bb0 00000000 00000000 parport!P4CompleteRequest+0x1d
ba4fbb28 b7b916ce 88982bb0 00000000 00000000 parport!P4CompleteRequestReleaseRemLock+0x13
ba4fbb48 b7b90a32 89d4cd00 88982bb0 ba4fbba0 parport!PptFdoClose+0x78
ba4fbb58 804ef19f 89d4cd00 88982bb0 88982bb0 parport!PptDispatchClose+0x1a
ba4fbb68 80583af8 88b9fd00 00000000 00000000 nt!IopfCallDriver+0x31
ba4fbba0 805bb474 00b9fd18 00000000 88b9fd00 nt!IopDeleteFile+0x132
ba4fbbbc 805266da 88b9fd18 00000000 88b9c84c nt!ObpRemoveObjectRoutine+0xe0
ba4fbbd4 9c71cb4c 88b9c84c 88b9c800 ba4fbc04 nt!ObfDereferenceObject+0x4c
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4fbbe4 9c786d25 88b9c800 88b95248 ba4fbc9c hardlock+0xfb4c
ba4fbc04 9c722d35 88b9c800 ba4fbc98 8055b700 hardlock+0x79d25
ba4fbc20 80589a11 ba4fbc98 88b9c800 804fb078 hardlock+0x15d35
ba4fbc48 80589f4e 9c7271bb ba4fbc98 88b9c800 nt!PiNotifyDriverCallback+0x6f
ba4fbcb4 8059a3dd 804d8d4c 8a7ff888 00000000 nt!IopNotifyTargetDeviceChange+0xfe
ba4fbd3c 8059a72e ba4fbd78 806e6974 e79fc008 nt!PiProcessQueryRemoveAndEject+0x6dd
ba4fbd58 8059a874 ba4fbd78 89b47a78 8056485c nt!PiProcessTargetDeviceEvent+0x2a
ba4fbd7c 8053877d 89b47a78 00000000 8a85fda8 nt!PiWalkDeviceList+0xea
ba4fbdac 805cff72 89b47a78 00000000 00000000 nt!ExpWorkerThread+0xef
ba4fbddc 805460ee 8053868e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


b7b9d0e5 8bc6            mov     eax,esi


SYMBOL_NAME:  parport!P4CompleteRequest+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: parport

IMAGE_NAME:  parport.sys


FAILURE_BUCKET_ID:  0x44_parport!P4CompleteRequest+1d

BUCKET_ID:  0x44_parport!P4CompleteRequest+1d

Followup: MachineOwner

Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 8 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 8 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros