INVALID_WORK_QUEUE_ITEM
Code: 0x96 (150)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0096 (150)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0096 (150)
Parameters
| Parameter | Description |
|---|---|
| 1 | The address of the queue entry whose flink or blink field is NULL. |
| 2 | The address of the queue that is being referenced. Typically, this queue is an ExWorkerQueue. |
| 3 | The base address of the ExWorkerQueue array. (This address helps you determine if the queue in question is indeed an ExWorkerQueue. If the queue is an ExWorkerQueue, the offset from this parameter will isolate the queue.) |
| 4 | Assuming the queue is an ExWorkerQueue, this value is the address of the worker routine that would have been called if the work item had been valid. (You can use this address to isolate the driver that is misusing the work queue.) |
Description
The INVALID_WORK_QUEUE_ITEM bug check has a value of 0x00000096. This bug check indicates that a queue entry was removed that contained a NULL pointer.
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
Cause
The INVALID_WORK_QUEUE_ITEM bug check occurs when KeRemoveQueue removes a queue entry whose flink or blink field is NULL.
Any queue misuse can cause this error. But typically this error occurs because worker thread work items are misused.
An entry on a queue can be inserted on the list only one time. When an item is removed from a queue, its flink field is set to NULL. Then, when this item is removed the second time, this bug check occurs.
In most situations, the queue that is being referenced is an ExWorkerQueue (executive worker queue). To help identify the driver that caused the error, Parameter 4 displays the address of the worker routine that would have been called if this work item had been valid. However, if the queue that is being referenced is not an ExWorkerQueue, this parameter is not useful.
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x96 | 78.11011 | %1 |
| KernelBase.dll | 0x96 | 78.1 | System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed. |
| appmgmts.dll | 0x96 | 8.11011 | A network error occurred accessing software installation data in Active Directory. The error was : %%1 |
| appmgmts.dll | 0x96 | 7 | A network error occurred accessing software installation data in the active directory. The error was : %%1 |
| dsreg.dll | 0x96 | 1011 | The FIDO credential deletion request was successfully sent. UPN: %1 Credential ID: %2 Auth token: %3 Request ID: %4 |
| kernel32.dll | 0x96 | 78.11011 | System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed. |
| nslookup.exe | 0x96 | 78.11011 | refresh = %1 |
| sc.exe | 0x96 | 78.11011 | DESCRIPTION:
Changes the preferred NUMA node for a Win32 service.
This setting is valid only for own process services.
To delete an existing setting, set the node number as -1.
If an invalid preferred node number is supplied, then the
change request will fail.
USAGE:
sc |
| webservices.dll | 0x96 | 78.11011 | Envelope version 'none' may be not be used with this channel. |
| win32k.sys | 0x96 | 78.1 | MinArrange |
| win32kbase.sys | 0x96 | 1011 | MinArrange |
| 11 entries | |||