Bug Check 0xE4: WORKER_INVALID
The WORKER_INVALID bug check has a value of 0x000000E4. This indicates that memory that should not contain an executive work item does contain such an item, or that a currently active work item was queued.
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.
WORKER_INVALID Parameters
Parameter 1 indicates the code position.
| Parameter 1 | Parameter 2 | Parameter 3 | Parameter 4 | Cause of Error |
|---|---|---|---|---|
0x0 |
Address of work item |
Start of pool block |
End of pool block |
An active worker item was freed. |
0x1 |
Address of work item |
Queue number |
0 |
An active worker item was queued. |
0x2 |
Address of work item |
Address of I/O worker routine |
0 |
A queued I/O worker item was freed. |
0x3 |
Address of work item |
Address of invalid object |
0 |
An attempt was made to initialize an I/O worker item with an invalid object. |
0x5 |
Address of work item |
Queue number |
NUMA Node targeted or -1 if all NODES were searched for. |
An attempt was made to queue a work item before Worker Queued was initialized. |
0x6 |
Address of work item |
Queue number |
0 |
Invalid queue type was provided. |
0x7 |
Address of work item |
Queue number |
0 |
An attempt was made to queue a work item with an invalid worker routine address. |
Cause
This is usually caused by a driver freeing memory which still contains an executive work item.