nVidia 163.44 - BAD drivers for me...

TechLarry

RIP [H] Brother - June 1, 2022
Joined
Aug 9, 2005
Messages
30,481
Vista 32. I had to pull these new drivers.

Every 15 min or so, the screen would blank out, stay away for about 10 sec, then come back.

Vista would report something about the driver failing, but it restarted successfully.

After watching this for 2 days I went back to the latest WHQL drivers and the problem went away.

This is a brand spankin' new Vista load on a proven machine.
 
This is the TDR issue, and unfortunately it's a common occurrence with many setups. When this happens, your graphic card driver crashed and has been reset by the OS. The underlying cause of the crash is never reported up front (although a record of it should be held in the Event Viewer,) and two TDRs may not necessarily be caused by the same issue. The frequency of occurrence can vary greatly between setups and over time on the same setup, making it difficult to find a pattern. However, rebooting after it hits often delays it from hitting again.

nVidia has been supposedly working hard to fix this, and Microsoft has released two patches that fix the issue on many machines (look for the performance and compatibility patches--they may not yet be on Windows Update.) However, keep in mind that it's not one issue that's causing this, but a range of remaining instability issues with particular setups and configurations. As a result, each rig can expect a different result regarding TDR occurrences.

If you search around the net, you'll find that the 158.45 drivers eliminated TDR crashes for the most people. 158.45 provides very decent performance, and many users are sticking to them until nVidia releases a new driver update that matches 158.45's stability.

Personally, I've found that 163.11 and 162.22 both bring the issue back, but that 163.44 has been perfect. Again, everyone can expect something different until the underlying causes of the issue have been ironed out.

Mark.
 
This is the TDR issue, and unfortunately it's a common occurrence with many setups. When this happens, your graphic card driver crashed and has been reset by the OS. The underlying cause of the crash is never reported up front (although a record of it should be held in the Event Viewer,) and two TDRs may not necessarily be caused by the same issue. The frequency of occurrence can vary greatly between setups and over time on the same setup, making it difficult to find a pattern. However, rebooting after it hits often delays it from hitting again.

nVidia has been supposedly working hard to fix this, and Microsoft has released two patches that fix the issue on many machines (look for the performance and compatibility patches--they may not yet be on Windows Update.) However, keep in mind that it's not one issue that's causing this, but a range of remaining instability issues with particular setups and configurations. As a result, each rig can expect a different result regarding TDR occurrences.

If you search around the net, you'll find that the 158.45 drivers eliminated TDR crashes for the most people. 158.45 provides very decent performance, and many users are sticking to them until nVidia releases a new driver update that matches 158.45's stability.

Personally, I've found that 163.11 and 162.22 both bring the issue back, but that 163.44 has been perfect. Again, everyone can expect something different until the underlying causes of the issue have been ironed out.

Mark.

I thought I was the only one experiencing this issue. I'm on Vista Ultimate 64 with a Q6600 on 8800 gtx sli'ed and it blacks out intermittenly and reports that nv(something)sys.dll has crashed and successfully recovered. I'm a Maya and 3dMax user and when that black screen occurs, those 2 programs crash and I haven't saved my work. 158.45 fixed those problems for me, but games like BF2 runs like crap with infinitely lag. So far, 163.44 seems to be working fine for me. Hope this helps.
 
I was getting hard crashes with 163.44 betas. Only crashes when playing Bridge Commander. Nothing yet in Bioshock.
 
I'd suggest installing these fixes for Vista if you haven't already done so:

http://support.microsoft.com/?kbid=938194

http://support.microsoft.com/?kbid=938979

938194 especially:

• The screen may go blank when you try to upgrade the video driver. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
932539 (http://support.microsoft.com/kb/932539/) The screen may go blank when you try to upgrade the video driver on a Windows Vista-based computer
• The computer stops responding, and you receive a "Display driver stopped responding and has recovered" error message. You can restart the computer only by pressing the computer's power button.
• The computer stops responding or restarts unexpectedly when you play video games or perform desktop operations.
• The Diagnostic Policy Service (DPS) stops responding when the computer is under heavy load or when very little memory is available. This problem prevents diagnostics from working.
• The screen goes blank after an external display device that is connected to the computer is turned off. For example, this problem may occur when a projector is turned off during a presentation.
• There are stability issues with some graphics processing units (GPUs). These issues could cause GPUs to stop responding (hang).
 
I'd suggest installing these fixes for Vista if you haven't already done so:

http://support.microsoft.com/?kbid=938194

http://support.microsoft.com/?kbid=938979

938194 especially:

• The screen may go blank when you try to upgrade the video driver. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
932539 (http://support.microsoft.com/kb/932539/) The screen may go blank when you try to upgrade the video driver on a Windows Vista-based computer
• The computer stops responding, and you receive a "Display driver stopped responding and has recovered" error message. You can restart the computer only by pressing the computer's power button.
• The computer stops responding or restarts unexpectedly when you play video games or perform desktop operations.
• The Diagnostic Policy Service (DPS) stops responding when the computer is under heavy load or when very little memory is available. This problem prevents diagnostics from working.
• The screen goes blank after an external display device that is connected to the computer is turned off. For example, this problem may occur when a projector is turned off during a presentation.
• There are stability issues with some graphics processing units (GPUs). These issues could cause GPUs to stop responding (hang).

Thank you sir. I'll try these today. :)
 
I have Windows XP-32 bit and just bought a 8800GTX... I play BF2142 for about 10 -15 and screen goes black and then the blue screen memory dump.

Is this the same thing that is happening to you guys??? :confused: I installed the new beta drives and it only has done it once now.
 
You know, I had this happen to me too, but it was with a Quadro NVS 285 :( and old Quadro drivers. Try different drivers if you can and listen to the posters above me.

Good luck! ;)
 
I can't adjust the brightness within Vista on my laptop with these drivers. Other than that, it's been fine.
 
I have Windows XP-32 bit and just bought a 8800GTX... I play BF2142 for about 10 -15 and screen goes black and then the blue screen memory dump.

Is this the same thing that is happening to you guys??? :confused: I installed the new beta drives and it only has done it once now.

Nope. The only game giving me issues is Bioshock.
 
damn it.. I h8 to whine..but wtf?

8800gtx. these new drivers bite. blurry image on my westy.

seriously. nvidia has had plenty of time now to hammer out driver issues, but so far, they go from bad to worse, with Vista 32, anyways.

the hardware may be all that and a cookie too, but either xp or vista, their driver blow.

fricken disappointing
 
My experiences with the NVIDIA drivers have only gotten better with time. These newest ones almost seem like a step back though. I've had issues playing back videos and I've had lockups with BIoshock.
 
Back
Top