STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER (Q293078)

[jjv687]

As some of you may recognize, this is the infamous infinite loop error message. Here's a pretty good background site I've found about it: http://members.home.nl/marf/Infinite%20Loop.html

This error message seems to be a very old problem that seems to be from the same, unfixed problems, some people have it posted on forums as old as 2001

There's really no definite fix for it anywhere so I'm kind of desperate, but any help would be greatly appreciated.

Here's my system:
DFI Lanparty NF4 UT Ultra-d
Opteron 170
Kingston 2x 1024 MB HyperX
Gigabyte 7600GT, fanless
485w Enermax Noisetaker
76GB Raptor
300GB Seagate

Other Info:
Running on Windows Vista Business
Running 100.65 (newest) Nvidia drivers
Running 4.06 (newest) DFI Bios

Up until a few days ago, I ran on a 3000+ Winchester with no problems at all, the very rare random freeze but I think that's about it. I recently installed the Opteron 170 and when I started playing Oblivion, I got this error within 1-25 minutes of playing and continue to get it.

My CPU temperatures sometimes get pretty high when I'm overclocked and have 2x Prime95s running, like 48-50C, but playing Oblivion doesn't get it up that high. When I'm not overlcocked it's still only ever like 44 C and Oblivion still crashes. Oblivion and Jade Empire have also both crashed within just a second of playing, so nothing would be too hot then either.

Also, I used to have a 7600GS with the same system except using the 3000+ still and I would occasionaly get this message.

I know there is no definite fix for this problem so I'm asking anyone who may have had this problem with the same setup as me or same motherboard at least to please let me know of any possible fixes that have worked out. The problem is known to have been fixed with just different BIOS settings or very quarky things like using a divider on your memory.

I've emailed tech support to Nvidia, Gigabyte and DFI and I'm awaiting their response, but not very optimistic.

Things like "get a better power supply" or "cool your junk better" or "use driver cleaner pro" aren't very helpful and that's all I've been seeing on other forums where people post this question.

 

[Cr0nJ0b]

have you loaded up your opteron X2 drivers for mutli-core funtion?

I recently upgraded from a Venice to an Opty 170 and had all sorts of problems...of the type that you are discounting at the bottom of your thread.

1) i didn't have enought power. I forgot that dual core takes a lot more watts than the singles
2) I had a bad drive that I didn't see at the time
3) my system was getting hot (the CPU) because I clocked it so high. It would only happen after playing supreme commander for 30-45 min.

It would be helpful to know which games are giving you trouble.

In my final opinion I would say.

1) double check your power and cooling to make sure they meet the specs for the new setup
2) check your event veiwer logs (not sure if they exist in vista)
3) update the opty drivers
4) re-install the os

 

[jjv687]

I'm positive that my temperatures are fine, the blue screen has come up before I even get a chance to play for 1 second, so nothing would be hot by then. I've also taken off my case door.

I thought that the Opterons didn't take a whole lot of power and my video card isn't as too power hungry either.

Sorry, I should have specified the games, but I'm mostly playing Oblivion right now, which crashes during 1-25 minutes. Jade Empire crashes the couple times I've tried it. I haven't been to inclined to play other games, but I can try them.

Actually, when I first installed Vista, I didn't even use the Nvidia drivers for the longest time and everything was working smooth as silk. Then when I swapped out the 3000+ to the Opteron I got the errors and then installed the newest Nvidia drivers, but that didn't help. So the only display drivers to even be installed are the newest Nvidia drivers.

But what are the Opteron drivers you're talking about? I just saw "Dual Core CPU" and thought everything was fine. haha

Also, as of now, I'm overclocked to 2500 MHz and it's Prime95 stable for 7+ hours, 2 instances of Prime95 of course. This doesn't affect the errors as I get them both before and after overclocking.

 

[Markbnj]

The problem, if it even is the same problem, was common on the 6800 AGP cards. I had it with certain games running a 6800GT AGP on NF3. I have seen a few reports of it on 7600GT cards on PCIe, which is what I run now, so this report makes me cringe. I haven't seen the problem since getting rid of the 6800, and if it recurs with this card I will be an ATI guy for the forseeable future.

Here's the bottom line: nobody knows what causes it; it's extraordinarily difficult to reproduce predictably, and as far as I know nobody has in the five years this has been reported; nVidia has no clue about the source, and certainly no fix, so unless something has changed expect no help from that direction; it often survives a reinstall, leading most to think it is a really low-level hardware issue, and that would be consisten with the class or error caused.

Honestly, I think you have two choices: go ATI, or change to a different combination of card/motherboard.

 

[jjv687]

You're exactly right. I've heard that it has to do with some RX55 memory controller that gets overloaded. People also say that it's just a compatibility issue between your CPU and video card (hence, my system worked with the 3000+ but not the Opteron), but this compatibility issue also ties into that memory controller somehow.

I've heard of some fixes that have to do with closing that memory controller altogether, which causes a 3-5 second lag instead of a blue screen. Some people say they've fixed it by turning off certain BIOS settings.

Also, the problem with the 8800s isn't the same problem at all, and was purely Nvidia's fault. This problem is basically being ignored by Nvidia

So I'm just hoping that someone has had this issue and fixed it with some setting or tool and can help me out.

Oh, and it's not hard to reproduce, I just play a game But I think you mean it's hard to build a system to try to get this error to test it or something.

 

[Markbnj]

Oh, and it's not hard to reproduce, I just play a game But I think you mean it's hard to build a system to try to get this error to test it or something.

Essentially, yes. If you take your system to nVidia and plug it in, and it experiences this error every time you play a certain game, then I'll bet they have the tools to tell you what's happening.

But apparently nobody has ever done that, and the problem has never hit some nVidia person who could make that happen.

 

[jjv687]

Well I guess my best bet is to just simply ask for the Nvidia tech support number, I couldn't find it on their website of course. I'll give them a call when I get home.

Still keep the advice coming though.

 

[jjv687]

I think this turned out to be an Audio Driver problem. I removed all sound drivers(had to physically delete them from System32, Driver Cleaner Pro didn't remove the Nvidia ones) and played Oblivion, with no sound, for an hour+ and no crashes, compared to 10-15 minutes before. I then installed the Realtek Audio drivers and can play fine, with sound, so far.

 

[skatter]

I just recently encountered this problem after upgrading my nvidia drivers to the latest version (not WHQL). I get this problem within 5-10 mins of loading up World of Warcraft, and nothing I have done has been able to resolve the problem.

System overview:
OS: Windows Vista Ultimate 32bit
CPU: AMD 3800+
Mobo: DFI LANPARTY UT nF4 SLI-DR Expert
Video: EVGA 7800GT
Sound: SB X-Fi XtremeMusic
Memory: OCZ DDR PC-4000 EL Gold (2x1024MB)

I've uninstalled my video drivers, and reinstalled the WHQL version.. still no luck.
I've uninstalled every recent app that was installed.. still no luck.

I do find it interesting that you ended up manually deleting your audio drivers for the fix... has this remained true since your last post?

 

[Markbnj]

I can tell you that there were about 2 dozen occasions when I was sure I had it fixed, and it would go 2 weeks, 4 weeks or more, and then bam.

 

[skatter]

Well, I went home and installed my brand spanking new EVGA 8800GTS, loaded up WoW, and ... BSOD!

So, I took the advice here, and went a step further. Instead of just uninstalling the sound drivers, I uninstalled the whole damn card (SB X-Fi). I've been stable in WoW for 20 minutes now (longest since this problem started), and I hope I have pinned down the problem.

Here lies the problem.. why on earth would a sound card lead to an error that the MSKB reports as a graphics driver problem?? Also, if I order a new X-Fi card, what are the chances of the problem remaining? Are there any decent alternatives to an Creative sound card on the market?

Anyways, I'll try and keep this updated w/ my progress..