Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

Truth0r

3 Posts

9315

June 15th, 2006 22:00

BSOD 0x1000000a & ACPI.SYS Latitude D820

I have a user that is running XP SP2 and about once a week gets a BSOD upon reconnecting the laptop to the docking station.  I'm not 100% sure exactly when it comes up but I know it is somehow related to the docking/undocking process.  I asked the user to be sure she is using the Undock button on the Start menu before she disconnects the laptop. 
 
Has anyone else run into this yet?
 
Thanks,
 
Here's the minidump info:

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

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.050622-1524
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jun  7 09:05:17.359 2006 (GMT-5)

...............................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {c, 2, 0, 804ef06b}

Probably caused by : ACPI.sys ( ACPI!ACPIDockIrpRemoveDevice+119 )

Followup: MachineOwner

 

Truth0r

3 Posts

June 15th, 2006 23:00

I forgot to mention that I'm having the user run Prime95 for at least 4 hours to see if there are any calculation errors.  Thanks in advance...

Here's more detailed information:

0: 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: 0000000c, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: 804ef06b, address which referenced memory

Debugging Details:

------------------

 

READ_ADDRESS: 0000000c

CURRENT_IRQL: 2

FAULTING_IP:

nt!IopInsertRemoveDevice+33

804ef06b 3931 cmp [ecx],esi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

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

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

Thread Count : 0

Thread address: 0x00000000

Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 804f4ef5 to 804ef06b

STACK_TEXT:

ba50faec 804f4ef5 89e58a68 8888a588 00000000 nt!IopInsertRemoveDevice+0x33

ba50fb3c 804f176e 89e58a68 00000000 8888a500 nt!IopCompleteUnloadOrDelete+0x127

ba50fb54 b9f89e8f 8888a500 88e250a8 b9f89d76 nt!IoDeleteDevice+0x76

ba50fb74 b9f7fde1 8888a588 00e250a8 88e2513c ACPI!ACPIDockIrpRemoveDevice+0x119

ba50fba4 804eef95 8888a588 b9f94f0c ba50fc30 ACPI!ACPIDispatchIrp+0x129

ba50fbb4 8059183b 8888a588 8888a588 00000002 nt!IopfCallDriver+0x31

ba50fbe0 80591a9d 8888a588 ba50fc0c 00000000 nt!IopSynchronousCall+0xb7

ba50fc34 804f6d72 8888a588 00000002 00000000 nt!IopRemoveDevice+0x93

ba50fc5c 80593466 00000000 00000018 e25104e0 nt!IopRemoveLockedDeviceNode+0x160

ba50fc74 805934cd 888dede0 00000002 e25104e0 nt!IopDeleteLockedDeviceNode+0x34

ba50fca8 8059913b 8888a588 025104e0 00000002 nt!IopDeleteLockedDeviceNodes+0x3f

ba50fd3c 805993fe ba50fd78 806e4974 e3cb2820 nt!PiProcessQueryRemoveAndEject+0x76b

ba50fd58 80599544 ba50fd78 88a590b8 8056375c nt!PiProcessTargetDeviceEvent+0x2a

ba50fd7c 80537851 88a590b8 00000000 89e3bda8 nt!PiWalkDeviceList+0xea

ba50fdac 805ce7d4 88a590b8 00000000 00000000 nt!ExpWorkerThread+0xef

ba50fddc 805451ce 80537762 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

 

STACK_COMMAND: kb

FOLLOWUP_IP:

ACPI!ACPIDockIrpRemoveDevice+119

b9f89e8f 33c0 xor eax,eax

FAULTING_SOURCE_CODE:

 

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ACPI!ACPIDockIrpRemoveDevice+119

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d27

FAILURE_BUCKET_ID: 0xA_ACPI!ACPIDockIrpRemoveDevice+119

BUCKET_ID: 0xA_ACPI!ACPIDockIrpRemoveDevice+119

Followup: MachineOwner

Truth0r

3 Posts

June 21st, 2006 19:00

Do Dell personnel support this forum?  I guess I'm going to have to call.

View More

View All

No Events found!

Top