Driver for 9500GT stops responding for a few seconds?

[JohnnyK]

Hey guys, upgraded to Win 7 Pro 64bit and having some severe graphics problems. I'm using an Asus EN9500GT Magic card, on an Asus p5ql Pro mb. The card had no problems before, so it's not hardware (or a 1 in a million coincidence, so let's rule that out, temps are low, as well). If I try to do anything that requires graphics processing, the program shuts off, screen turns black for 2-3 seconds, and turns back on with a little window at the bottom right saying "Video has stopped responding and has been restarted" or some such derivative. I've been searching and noticed tons of people are having this problem, but I can't seem to find a solution. I've tried every driver from 185 to 195 (I beliiiiieve I tried 195, at least). I've installed the latest mobo drivers from asus, and done a bios update. Anyone know the skinny on this problem?

Thanks guys!

 

[torrentg]

Updating the motherboard's chipset drivers should fix this problem for you. A bios update, if available, is always nice too.

If you still have problems, post a crash dump following this and maybe we could find old or conflicting drivers on the system that should be removed.

 

[JohnnyK]

Thanks for the reply. As I said, I have done a bios update, and the chipset is the newest update. I will try that crash dump today and post it up here. Thanks!

 

[torrentg]

lol yeah sorry about that.

Sometimes specific issues cause me to reply in a specific manner as if I didn't read everything carefully.

Posting the crash dump will probably be helpful.

 

[JohnnyK]

Noticed DECA is having a similar problem with an identical card.

2 dumps are in there. 1 happened today when I switched to the newest beta driver.. 195.37 or some such.. This time it went black for a few minutes, came back with a bluescreen, and rebooted, which is different than the "This has stopped responding and has been successfully been restored". The other dump I ASSUME has the other problems in it. Today was while using cad for a minute or two.

Thanks for your help!

 

[torrentg]

Noticed DECA is having a similar problem with an identical card.

2 dumps are in there. 1 happened today when I switched to the newest beta driver.. 195.37 or some such.. This time it went black for a few minutes, came back with a bluescreen, and rebooted, which is different than the "This has stopped responding and has been successfully been restored". The other dump I ASSUME has the other problems in it. Today was while using cad for a minute or two.

Thanks for your help!

Well, you do have the same 0x116 error but also a 0x124 hardware error.

Don't overclock (or so much.) That's the problem. You can see this link for other suggestions on how to fix it.

Here are your old drivers you have to update or remove:

secdrv secdrv.SYS Wed Sep 13 09:18:38 2006
emusba10 emusba10.sys Mon Nov 26 02:12:56 2007
LVUSBS64 LVUSBS64.sys Sat Jul 26 11:06:36 2008
lvrs64 lvrs64.sys Sat Jul 26 11:09:02 2008
lv302a64 lv302a64.sys Sat Jul 26 11:06:31 2008
LV302V64 LV302V64.SYS Sat Jul 26 11:09:08 2008

 

[JohnnyK]

Well that's odd.. So he never did solve his 116 error, correct? Hardware problem I find strange. It was running perfectly before the update, and it's not, nor has it ever been overclocked? Running cool. Doesn't even get a chance to generate heat. Any ideas?

Which dumplog showed what one?

 

[torrentg]

You could always try the latest NVIDIA beta but I don't think that will help. Worth a shot though.

See if there's an update for you bios. And remove those drivers I said!

Here's the 0x124 error:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI04.953\110909-15303-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Mon Nov  9 10:17:28.225 2009 (GMT-5)
System Uptime: 0 days 0:00:07.113
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8002cf67c8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8002cf67c8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fb96f0 fffff800`02cc1a89 : fffffa80`02cf67a0 fffffa80`018d9b60 00000000`00000008 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fb9c10 fffff800`02ba3547 : fffffa80`02cf67a0 fffff800`02c1c5f8 fffffa80`018d9b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fb9c40 fffff800`02b0bb95 : fffff800`02c7e360 fffffa80`02c78208 fffffa80`02c78200 fffffa80`018d9b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fb9c80 fffff800`02a86161 : fffff880`01059e00 fffff800`02b0bb70 fffffa80`018d9b60 00004180`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fb9cb0 fffff800`02d1c166 : 00004300`00000000 fffffa80`018d9b60 00000000`00000080 fffffa80`0184a9e0 : nt!ExpWorkerThread+0x111
fffff880`02fb9d40 fffff800`02a57486 : fffff880`009ea180 fffffa80`018d9b60 fffff880`009f4f40 0000005f`98000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fb9d80 00000000`00000000 : fffff880`02fba000 fffff880`02fb4000 fffff880`037506d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

 

[JohnnyK]

That second smaller dump is with the newest beta. Bios is as updated as it gets. I'll delete those drivers, but otherwise I'm just out of luck if I've tried every driver?

 

[torrentg]

That second smaller dump is with the newest beta. Bios is as updated as it gets. I'll delete those drivers, but otherwise I'm just out of luck if I've tried every driver?

No. Follow the advice in the 0x124 link.

You could also check if your ram timings and voltage (VDimm) are correct for specific modules you're running. Visit RAM manufacturer's site for details on specific RAM.

 

[JohnnyK]

Yeah, I think I will double check that, and then do a ramcheck, although I wonder if I'm chasing my own tail now. Question though, how do you know those drivers aren't in use? I notice that one is for my EMU 0404 and one is for a logitech device, but how do we know they aren't being used at all? I could just not have had them turned on at the time, correct? (EMU is externally turned on, and I only use it when I need sound, and the webcam stays off most of the time as well). Thanks!

 

[JohnnyK]

ALso can't get a screenshot (I mean, I guess I could) but I was browsing around to Advanced TOols and Performance Info and Tools, and there is one warning saying nvlddmkm.sys (Same one that came up on a bluescreen) is causing windows to resume slowly. I downgraded to an nvidia 185.xx at some point today, just to start working backwards through all of them. Time taken: 8 seconds.. so not sure what that means in the grand scheme of things.

 

[Deca]

Did you say you can't do ANYTHING at all graphical? When I had my troubles I could play Wacraft in Windowed mode for up to 30minutes or something without an issue, but never full screen. I had to make sure I had Vertycal Sync enables though as if the frame rate went too high the game would just crash and the same old error would happen.

So all I'm saying is, for now.. until there is a definite fix for it, just try messing around with your settings of things. Don't let the card do too much so to speak. At least you can use it for a little while then ^^

 

[TheMatos]

ALso can't get a screenshot (I mean, I guess I could) but I was browsing around to Advanced TOols and Performance Info and Tools, and there is one warning saying nvlddmkm.sys (Same one that came up on a bluescreen) is causing windows to resume slowly. I downgraded to an nvidia 185.xx at some point today, just to start working backwards through all of them. Time taken: 8 seconds.. so not sure what that means in the grand scheme of things.

Ok, some small things you may have already done. Have you tried uninstalling the drivers and then using driver sweeper to clean them out in safe mode? Try this and then reinstall the drivers.

Second, I have this card and am using it right now (I have the same error as you with my new 5770 and after trying a bunch of stuff I RMA'd it and am going to see if something was wrong with it. And lo and behold, with my 9500 back in system is stable) with the 190.62 drivers. I have had zero stability issues with it and the card can work for long periods of time at around 65 C. I am not using the newer ones because I heard they were having some issues.

I wonder what is causing these drivers to stop responding, I am totally frustrated with my 5770 and I can't figure out what was going on with it.

 

[JohnnyK]

Thanks for the responses. I mean, I can surf the web and stuff, but if I load up a game, crashes almost instantly. If I try to draw a line in CAD, instant crash.

The BSOD, those minilogs I posted, were only with the newer betas.. I tried all the other drivers again last night (YEah, I swept the drivers), and those just result in it exiting the program, waiting a second, then saying "The nvidia driver 1xx.xx stopped responding and has been restarted". But that doesn't create a dump log, so anything else I can post for you guys to check it out?

Also, I'm using rendition ram. I can't find specs for it, but as I said, no hardware issues before win7.

 

[JohnnyK]

Tried the newest released yesterday beta. No BSOD< back to that "Stopped responding". So is there any way to look at whats happening when that happens? Like there is with a minidump?

 

[torrentg]

Tried the newest released yesterday beta. No BSOD< back to that "Stopped responding". So is there any way to look at whats happening when that happens? Like there is with a minidump?

You could check the event logs. Type "event log" in start menu search box, hit enter. Then double click on Windows Logs, then System.