[wdmaudiodev] msvad bugcheck 0x96
- From: "James Miles" <liquidl@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Wed, 08 Jun 2005 19:52:26 -0500
Hi All,
I am working with the "multstr" flavor of the msvad included in the DDK. On
one PC, I am getting a 0x96 bugcheck when I run media player. The following is
WinDbg analysis:
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INVALID_WORK_QUEUE_ITEM (96)
This message occurs when KeRemoveQueue removes a queue entry whose flink
or blink field is null. This is almost always called by code misusing
worker thread work items, but any queue misuse can cause this. The rule
is that an entry on a queue may only be inserted on the list once. When an
item is removed from a queue, it's flink field is set to NULL. This bugcheck
occurs when remove queue attempts to remove an entry, but the flink or blink
field is NULL. In order to debug this problem, you need to know the queue being
referenced.
In an attempt to help identify the guilty driver, this bugcheck assumes the
queue is a worker queue (ExWorkerQueue) and prints the worker routine as
parameter 4 below.
Arguments:
Arg1: 812d2b18, The address of the queue entry whose flink/blink field is NULL
Arg2: 80561440, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: 80561440, The base address of the ExWorkerQueue array. This will help
determine
if the queue in question is an ExWorkerQueue and if so, the offset from
this parameter will isolate the queue.
Arg4: 8056377d, If this is an ExWorkerQueue (which it usually is), this is the
address
of the worker routine that would have been called if the work item was
valid. This can be used to isolate the driver that is misusing the work
queue.
Debugging Details:
------------------
[snipped junk]
*************************************************************************
OVERLAPPED_MODULE: rdbss
WORKER_ROUTINE:
nt!IopProcessWorkItem+0
8056377d 8bff mov edi,edi
FAULTING_IP:
nt!IopProcessWorkItem+0
8056377d 8bff mov edi,edi
WORK_ITEM: 812d2b18
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x96
LAST_CONTROL_TRANSFER: from 8053225b to 804e3592
STACK_TEXT:
f96948e0 8053225b 00000003 f9694c3c 00000000 nt!RtlpBreakWithStatusInstruction
f969492c 80532d2e 00000003 81348ba0 81348b30 nt!KiBugCheckDebugBreak+0x19
f9694d0c 8053331e 00000096 812d2b18 80561440 nt!KeBugCheck2+0x574
f9694d2c 8051d1a3 00000096 812d2b18 80561440 nt!KeBugCheckEx+0x1b
f9694d6c 804e423d 00000001 00000001 00000000 nt!KeRemoveQueue+0x2e6
f9694dac 8057be15 812d2b18 00000000 00000000 nt!ExpWorkerThread+0xd6
f9694ddc 804fa4da 804e4196 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!IopProcessWorkItem+0
8056377d 8bff mov edi,edi
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!IopProcessWorkItem+0
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
FAILURE_BUCKET_ID: 0x96_nt!IopProcessWorkItem+0
BUCKET_ID: 0x96_nt!IopProcessWorkItem+0
Followup: MachineOwner
---------
Apparently, the work queue is corrupted. I have not encountered this issue on
other PCs. This PC is an oldish 433 MHz Celeron with Win XP SP1. The only
quirky thing about this PC is that the real time clock is messed up so the time
is waaaayyy to slow. Other than that, it works fine. Has anyone else
encountered this bug??
Regards,
James
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
Other related posts:
- » [wdmaudiodev] msvad bugcheck 0x96
