Hi all,

I usually use various Linux distributions for common tasks, but recently have been using Windows XP more often as there is a software application which I require for work which will not run under wine on linux.
So, I am not particularly fond of windows, but have learned to live with it.

I recently had a couple of BSOD errors, both while I was asleep. (I rarely switch this computer off, as I run a VNC server 90% for remote access and occasionally a web server)
I have Windows configured to automatically reboot, as I often use the system remotely so cannot do a manual reset if windows crashes. Therefore I have not been able to write down the details, and I cannot re-create the errors so I am restricted to the minidump.

I understand the output from WhoCrashed, and partially the output from DebugWiz, but I am asking this question to see if anybody can shed any more light than me.
Also, hopefully somebody can advise me on whether I should do something to try and fix whatever the cause(s?) was, or simply ignore it and tally it up to my usual dislike for microsoft software.

Here is the output from WhoCrashed:

Code:

On Sun 24/05/2009 10:59:10  your computer crashed
This was likely caused by the following module:  avfwim.sys
Bugcheck code: 0x100000D1 (0xB1D707, 0x2,  0x0, 0xBAF1FC0F)
Error: Unknown
file path:  C:\WINDOWS\system32\drivers\avfwim.sys
product: AntiVir Desktop
company: Avira  GmbH
description: Packet filtering kernel driver ( NDIS IM  )


On Tue 19/05/2009 22:23:53 your computer crashed
This was  likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x89A59DA8,  0x89AFCF60, 0xF78C6CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path:  C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
The crash took place in a standard Microsoft module. Likely the  culprit is another driver on your system which cannot be identified. 

Here is the output from DebugWiz: http://andrewbeveridge.co.uk/misc/debuglog.txt

And here are the actual minidumps, if it makes any difference:
http://andrewbeveridge.co.uk/misc/Mini051909-01.dmp
http://andrewbeveridge.co.uk/misc/Mini052409-01.dmp

Gratefully,
Andrew

Bug Check 0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M

The THREAD_STUCK_IN_DEVICE_DRIVER_M bug check has a value of 0x100000EA. This indicates that a thread in a device driver is endlessly spinning.

I've never seen this error but it seems that windows doesn't know which driver so I recommend that you uninstall all of the drivers (wireless, ethernet, chipset, audio, graphics, etc) and try to reinstall them and see if that helps. On the other hand it seems to think that Avira is the culprit so I would reinstall it first. It might help to know the program that you are running as that might help with determine the driver and it might be causing the problem. Is it that VNC server? Whats that? Also right click on my computer --> manage --> event viewer --> windows logs --> system as well as applications. Look for entries with a red X. Definitely look for entries around the time that you think that it is crashing. If nothing else you could always reinstall windows.

I don't know if this is related but XP is not designed to be a server in fact MS does not want users to use it as a server because they would rather you buy their more expensive server versions. That said I think that they limit the number of simultaneous incoming connections.

Also you might want to turn off automatic restart so that you can witness the BSOD and watch your computer more. Perhaps the screen itself will list the driver.

Likely the culprit is another driver on your system which cannot be identified

That statement is a big help, aint it.

While not being a expert at Windows Operating Systems, I can't say if Anti Virus Software uses a driver or not. I thought drivers were for hardware. Could be wrong though.

Avast is another Free Anti Virus for Windows. On My wifes gear (she is a Vista/XP user) I usually use MBAM for scanning. Spyware Blaster for IE and Firefox Protection. Avast Home Edition for Virus Protection. Avira is good and I haven't seen a problem like yours because Avira was installed. Any New Hardware been plugged or activated in your system before the BSOD?

Have You tried System Restore to a date before the BSODs occured.

Like I said, I am not a Windows expert like Townsbsg. So good Luck.

EDIT: After reading your debug log I found this to be interesting

FAULTING_THREAD: 89a59da8

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

Maybe you should start there?

Originally Posted by rokytnji

That statement is a big help, aint it.

Well the error didn't specify which driver that it is for sure and the article from MS said that with this particular error code Windows doesn't know which driver is at fault.

I thought drivers were for hardware.

Certain software does need drivers for hardware interaction. Off the top of my head I know that zone alarm does have a driver. In the specified folder \windows\system32\drivers on my computer I found 3 drivers for Avira although none of them have exactly the same name but that could be if he has an older version or a different program.

I didn't even see the debug file so I'm glad that you found that. So if I where you I would start with the graphics driver and if that doesn't work move on to Avira.

Thanks for the help guys, I don't really want to uninstall my graphics driver unless it is causing me a large problem, because VESA graphics on a 17" screen looks unbearable.
As for Avira, I am going to assume there must be some bug in the packet filtering network driver, but again, unless it causes me more trouble I shall leave it.
Fortunately there have been no problems since so I am going to assume both were one-offs, albeit coincidental that I got both within a few days.

If I get any more BSODs I will do more narrowing-down by removal of drivers, and I will post here with any extra information I find, just in case.

Thanks for trying =)
-Andrew

Well want to or not if a driver is causing system instability it needs to be reinstalled. I hope you don't think I meant to just uninstall it and not to reinstall it. Well let us know.

Ah ok, though if a driver is buggy reinstalling it will do nothing. Finding a new version would be the only solution.
But to be honest as I haven't had any trouble since, I shall leave the symptom "unstable" out of the picture until I have another BSOD (hopefully that won't happen and it was just a one-off... twice =)

No unless a driver is a beta driver it should'nt be buggy however it can be corrupted which reinstalling should help.

Ok, I guess I see what you are trying to say but I know for sure no hardware driver is perfect.
Anyway, I have had two new BSODs, so I am going to pursue diagnosis again as it is a real problem now.
Here is WhoCrashed's opinion:

Code:

On Fri 29/05/2009 10:53:42  your computer crashed
This was likely caused by the following module:  avfwim.sys
Bugcheck code: 0x100000D1 (0x468B2954,  0x2, 0x0, 0xB2044C8B)
Error: Unknown
file path:  C:\WINDOWS\system32\drivers\avfwim.sys
product: AntiVir Desktop
company: Avira  GmbH
description: Packet filtering kernel driver ( NDIS IM  )

On Wed 27/05/2009 17:32:02 your computer crashed
This was  likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC000001D,  0xBFB8AB97, 0xAFB99A44, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest  that you search on it with Google. 
Click here to do a Google search on hardware

And here are links to the actual minidumps:
http://andrewbeveridge.co.uk/misc/Mini052709-01.dmp
http://andrewbeveridge.co.uk/misc/Mini052909-01.dmp

And the debug log from DebugWiz for both of the above files:
http://andrewbeveridge.co.uk/misc/debuglog2.txt
http://andrewbeveridge.co.uk/misc/debuglog3.txt

It is obvious to me that Avira is causing a problem of some kind, as it is mentioned twice.
The other new one and the one from earlier shed less light though.

Right now, I shall uninstall Avira and re-install my graphics sound and network drivers.
Then I guess it will be a matter of waiting for a week or so to see if I get another BSOD.
In the mean time does anybody here have any more they could tell me based on the new information?

Thanks,
Andrew

You shouldn't have to uninstall all of the drivers. I would start with Avira and then, if that doesn't work, reinstalling graphics drivers. If you uninstall and reinstall all of the drivers at once you won't know for sure what the problem is. Worse case scenario is that windows is corrupted and therefore would need to be reinstalled.