What is causing my INVALID_WORK_QUEUE_ITEM blue screen?

Unfortunately, we know nothing about your afflicted system(s).

Are any of them Dell computers? 

If you have several systems with the same symptom, I would pick the one that fails the most often and concentrate your efforts on that one,get it working and then see what you can learn to apply to the other systems.

What is a null ptr?

I think it is unlikely the problem has anything to do with ntoskrnl.exe in spite of what the debugger might say.

Did you do some Internet searches with Google to see and read the many other message forum threads in the world where issues like you describe are discussed and can you find one resembling your environment where the message topic thread has a happy ending?

The next time your system crashes, provide more information about what you see.

Here is a BSOD example showing information you need to provide:

http://techrepublic.com.com/i/tr/downloads/images/bsod_a.jpg

Send the information pointed to with the red arrows (3-4 lines total).

Send the entire *** STOP message line since there are clues in the 4 parameters.

If there is a file name listed under the STOP message, be sure to include that information too.

Skip the boring text unless it looks important to you.  We know what a BSOD looks like, we need to know what your BSOD looks like.

Maybe someday the XP forums "Ask a question" dialog will ask these questions automatically when a new thread is started so I do not have to ask them every single time.  It might even be possible to resolve an issue in a single reply when enough information is provided.

Please provide additional information about your system:

What is your system make and model?

What is your XP Version and Service Pack?

Describe your current antivirus and anti malware situation:  McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.

Does the afflicted system have a working CD/DVD drive?

Do you have a genuine bootable XP installation CD (this is not the same as any Recovery CDs that came with your system)?

If the system used to work properly, what do you think might have changed since the last time it did work properly?

Apparently Joselbarra is another MSM or MS wannabe with limited experience, lack of critical thinking capacity and/or analysis skills, who instead gives dumb pointless robotic canned answers, and asks a lot of stupid questions that have sometimes even already been answered.  Then they don't answer back or followup, and leave you hangin'.

I've seen this far too many times on the web.

Let's put a stop to MSM's!!

Who's with me?!

:)

ps- of course he doesn't know what a "null ptr" is, because he and his answers *ARE* null pointers!!

These are not dell machines.  These are custom built machines for consumer based terminal network. 

Yes, I have searched google.  I saw nothing that would fix my problem, thats why I turned here.

We are running XP Embedded with Service pack 3 installed.  No antivirus installed.

The BSOD information is all in the original post.  I included the !analyze -v from windbg on the .dmp file that windows creates following a BSOD.  I assure you, I am beyond just googling the BSOD error.

To restate it in summary:

INVALID_WORK_QUEUE_ITEM

{85f526f8, 805622fc, 805622c0, 805645fd}

Windbg, and the microsoft docs, clearly point to ntoskrnl.exe throwing the bsod.  Another driver is responsible for the null ptr in the queue.

You don't know what a null ptr is?

Thanks, but I've already been there.  I'm hoping to find someone that can say "run xxxx command in windbg to find out exactly which driver caused the null ptr"

Thanks again

This might be hlpful to you:

http://msdn.microsoft.com/en-us/library/ff559300%28v=vs.85%29.aspx

Cheers!