WHY Frequent BSOD: INVALID_WORK_QUEUE_ITEM 0x96 ntoskrnl.exe

[crashnburn]

This is a X61T fresh from factory restore (XP Tablet PC) machine probably with a few small apps like ZIP tools installed.

It BSODs every 10/15 even if left idle and not doing anything. It was doing this even before the Broadcom Driver got on board.

System Information (local)
--------------------------------------------------------------------------------

computer name: X61T-XP-TABLET
windows version: Windows XP Service Pack 2, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2103660544 total
VM: 2147352576, free: 2047500288



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sat 10/1/2011 9:35:22 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100111-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22EF7)
Bugcheck code: 0x96 (0xFFFFFFFF890518D0, 0xFFFFFFFF80563780, 0xFFFFFFFF80563780, 0xFFFFFFFF8057596C)
Error: INVALID_WORK_QUEUE_ITEM
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a queue entry was removed that contained a null pointer.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 10/1/2011 9:33:26 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100111-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22EF7)
Bugcheck code: 0x96 (0xFFFFFFFF87707408, 0xFFFFFFFF80563780, 0xFFFFFFFF80563780, 0xFFFFFFFF8057596C)
Error: INVALID_WORK_QUEUE_ITEM
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a queue entry was removed that contained a null pointer.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 10/1/2011 9:20:11 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100111-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22EF7)
Bugcheck code: 0x96 (0xFFFFFFFF892B0D70, 0xFFFFFFFF80563780, 0xFFFFFFFF80563780, 0xFFFFFFFF8057596C)
Error: INVALID_WORK_QUEUE_ITEM
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a queue entry was removed that contained a null pointer.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 10/1/2011 8:44:35 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100111-01.dmp
This was probably caused by the following module: btwusb.sys (btwusb+0x7575)
Bugcheck code: 0x1000000A (0x4, 0x1C, 0x1, 0xFFFFFFFF804FC9B9)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\btwusb.sys
product: Bluetooth Software
company: Broadcom Corporation.
description: Driver for Bluetooth USB Devices
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: btwusb.sys (Driver for Bluetooth USB Devices, Broadcom Corporation.).
Google query: btwusb.sys Broadcom Corporation. CUSTOM_ERROR




On Sat 10/1/2011 6:35:35 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini093011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22EF7)
Bugcheck code: 0x96 (0xFFFFFFFF89263D20, 0xFFFFFFFF80563780, 0xFFFFFFFF80563780, 0xFFFFFFFF8057596C)
Error: INVALID_WORK_QUEUE_ITEM
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a queue entry was removed that contained a null pointer.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

btwusb.sys (Driver for Bluetooth USB Devices, Broadcom Corporation.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

[RealBlackStuff]

Install SP3.
And please stop posting the same thing all over the forums!

[crashnburn]

The issue is.. I have an XP installation that was working fine for a long while (even on the Middleton BIOS).
Since it used only 3G of RAM and I wanted to go Windows 7 x64, but wanted to check it out first.
Did that on a second HDD and slowly began migrating Apps and Settings.

Out of the blue with nothing being installed or removed. I just had a freeze up on one of them and from that point on all of a sudden, both started stopping to boot..

So, not knowing what the issue is.. lots of work on repairing and restoring Windows.. finally realized there were some BIOS issues.

I fixed BIOS.
Fixed some drivers. etc.

Now new NTOS kernal issue is happening.
Wondering whats going on.

So did a factory restore in a 3rd Hard Disk (yes have a few spare). Factory install is also causing same NTOS Kernal issue.

Also, WiFi is permanently disabled on Win7 x64 HDD 'Fn F5' key and software app are unable to turn it back on. (Checked Hardware switch).
The WiFi works in Factory Restore XP Tablet HDD, but I havent DARED to disable and enable it via Fn F5.