"Thread stuck in device driver" error

[cwsink]

Hello,

I've got a user that has been having blue screens very randomly. He will use his system for several days, then it will crash. Many times he's not even doing anything, or is away. It always crashes when SW is running, but I'm not convinced that it is necessarily a SW problem.

I searched for the error and got varied results, but all pointed to a faulty driver. He has downloaded the latest driver (approved by SW).

He's got Windows XP sp2, SW 2007sp1.1; NVIDIA Quadro4 980XGL.

Any help for diagnosing the problem? I'm not a techie, but neither can we afford one.

Below is an image from the event log:

Craig Sink
Mechanical Engineer
Force Design, Inc.

 

[CorBlimeyLimey]

Try running Hijack This ... available from

http://www.majorgeeks.com/download3155.html

The results can be auto-analysed at

http://hijackthis.de/

You need to see what processes are running when the crash occurs. There are utilities around which will record that info but I don't have any to hand right now.

 

[EEnd]

Excessive heat can also cause problems. Try opening up the computer and checking that it has not become infested with dust bunnies, particularly in the heatsinks and fans for the CPU, video card and chipset.

Eric

 

[CorBlimeyLimey]

Do you have the 'SW search index' thingy running?

 

[smcadman]

Try emptying the SW Backup folder, the default location is: C:\Documents and Settings\User\Local Settings\TempSWBackupDirectory There have been times that I have 1Gb of backups saved.

Then use CCleaner (crap cleaner) to clean up the crap on your computer.

http://www.ccleaner.com/

Finally make a system restore point, then use Registry Mechanic. I've used this with success whenever I run into problems. Try the demo here:

http://www.pctools.com/registry-mechanic/

Try the above suggestions, but like I said, make a system restore point in case you have to undo anything.

SW07 SP1.0

Flores

 

[SBaugh]

When it blue screens it will give the file that caused the crash. Have him write it down... if you reboots automatically then you need to turn that option off under My Computer - RMB and select "Properties"\Advanced\Start up recovery\ - Uncheck "Automatically restart".

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[meintsi]

The blue screen error (stop) codes will be more useful than this event viewer coding.

Remember...
[navy]"If you don't use your head,[/navy]
[navy]your going to have to use your feet."[/navy]

 

[SBaugh]

Sorry forgot to add - with that file you can probably determine what file is causing the error and you can google search it to figure out what applicaiton or what that file belongs too to help determine the problem.

WE had a customer send an actual digital picture in of his blue screen.. .as funny as that is we were able to determine the ATI driver was causing the issue and replacing hte driver with certified drivers fixed his issue (not saying thats your issue, but thats how we found the problem).

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[smcadman]

About the blue screen of death, here is how to "configure Windows to write an event log message with bugcheck information"

http://support.microsoft.com/kb/314084/EN-US/

On a side note, are you bored at the office and want to mess with IT? You can now download the infamous Blue Screen of Death screensaver from Micro$oft: BlueScreen Screen Saver v3.2

Screensaver

Copy the screensaver to the C:\WINDOWS\SYSTEM32 folder in XP.
bsod_jpg

SW07 SP1.0

Flores

 

[cwsink]

Thanks for all the responses! I wasn't able to access this site for awhile???

Corey, he does have "that thingy" running....

Meintsi, I'm not sure if this is what you mean by the stop codes, but he also recorded this:
0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
0x100000EA THREAD_STUCK_IN_DEVICE_DRIVER

The system is already set to "Write an event to the system log". Where exactly do I access that?



Craig Sink
Mechanical Engineer
Force Design, Inc.

 

[smcadman]

It looks like it's a video card issue then:

http://support.microsoft.com/kb/293078

CAUSE
This issue might occur if the display driver is caught in an infinite loop while it waits for the video hardware to become idle. This issue typically indicates a problem with the video hardware or that the display driver cannot program the hardware correctly.

RESOLUTION
To resolve this issue, obtain and install the most current driver for your video adapter, or replace your video card.

(gotta love Google)

SW07 SP1.0

Flores

 

[cwsink]

That was my suspicions. It says that it "typically" indicates a problem with the video hardware. Could it be the drivers causing a problem even though I've downloaded the latest???... which if that's the case, then I don't know what to do....

I really want to avoid a new card if possible.

Thanks,




Craig Sink
Mechanical Engineer
Force Design, Inc.

 

[handleman]

Try opening up the computer and checking that it has not become infested with dust bunnies....

Maybe there's a real thread stuck in there in one of those device drivers - have you tried looking for it with magnifying glass and tweezers?

(Sorry...)

 

[meintsi]

The link from Flores is exactly where I was heading.

The error code 000000d1 in the event viewer isn't searchable. But if you convert it to standard format (0x000000d1), then the same article appears.

The fact that

Many times he's not even doing anything, or is away. It always crashes when SW is running, but I'm not convinced that it is necessarily a SW problem.

... also points to display devices.
Make sure to check the device manager for any virtual display adapters which may also be the source of conflict.

Can you swap video cards to see if the problem travels?

Remember...
[navy]"If you don't use your head,[/navy]
[navy]your going to have to use your feet."[/navy]

 

[rporter]

Being an nvidia grphics card you need to change the driver to a genaric driver and reboot before you upgrade to the new driver. Scott had covered how to to this in another thread. The driver may not be upgrading correctly if you dont.

 

[SBaugh]

Thanks rporter!

Actually I have found that if you don't:

1) uninstall driver
2) Reboot
3) install new driver
4) reboot
5) test

That the drivers are in conflict, even though it says its using XX.XX driver. I have only found this with Nvidia Drivers. If you do a clean install of the driver you can rule that out as the problem. If you continue to see this try switching the card out with another one like it and see if its possibly the card doing this to you.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[cwsink]

Thanks fellas!

I actually did uninstall the driver, re-booted and then re-installed the new driver. During the re-install, it mentioned that the file already existed, so I'm not sure how clean it was. I should probably do it again...

Thank you,

Craig Sink
Mechanical Engineer
Force Design, Inc.

 

[CorBlimeyLimey]

I believe the normal uninstallation of the driver doesn't actually remove it from the system. It just disables it from being used. So if you download & install the driver again, Windows will recognise that it is already on the system and gives you the opportunity of using the existing driver or re-installing the "new" one.

 

[cwsink]

Corey,

I don't think I had an option. Is there a way to completely remove the file(s)?

Also, I checked the box for dust...its clean.



Craig Sink
Mechanical Engineer
Force Design, Inc.

 

[CorBlimeyLimey]

There probably is ... but I have never needed to, and have not bothered to find out the procedure.