NVIDIA Windows Desktop/Internet Browser TDR Troubleshooting Updated 2/24/2012
  1 / 23    
This thread is a continuation of the original [url="http://forums.nvidia.com/index.php?showtopic=215256"]thread[/url] created to address reports by some end users of [url="http://msdn.microsoft.com/en-us/windows/hardware/gg487368"]TDRs[/url] on their PCs when browsing the web using Internet Explorer 9 or Firefox with GPU acceleration enabled. A Windows TDR is a symptom and not a cause. This thread is meant to track a specific type of Windows TDR that is reported to have first appeared in the NVIDIA display driver R280.19 and continued in later drivers. First a brief introduction to what a TDR is.

Microsoft's Windows Vista was the first operating system to introduce TDRs as a way for the system to recover from a graphics card error that in prior operating systems would cause the whole system to crash forcing the user to reboot his/her PC. Since the graphics card is constantly sending a video signal to your PC's display, any system instability could trigger a TDR. If you have ever driven a car and had the check engine light go on while driving, you may have noticed that once you take the car to a mechanic for inspection, in most cases it was not the engine that was the cause for the check engine light to come on. This is similar to Windows TDRs. While a defective graphics card or a bug in the display drivers could trigger a TDR, so could a number of other PC components or software applications. When a TDR is triggered by the operating system, you will see a balloon message like the one below appear on the bottom right hand corner of your screen.

[img]http://nvidiaforums.s3.amazonaws.com/tdr/1.jpg [/img]

Beginning with NVIDIA display driver release 280.19, improvements were made in the drivers which provided better power management and GPU performance. Following the release of this driver, we started receiving some reports of users experiencing TDRs while browsing in Mozilla's Firefox or Microsoft's Internet Explorer 9 with GPU acceleration enabled. Users claim that by downgrading the display driver to version 275.50 or earlier drivers would resolve these issues. By working with our customers, our software team has been able to provide fixes in our more recent driver releases for these browser related TDRs. Some of the most recent reports of TDRs from users have been caused by defective hardware components (motherboard, memory, graphics card, hard drive, etc.) and therefore we would like to both help customers diagnose their issue and also gather further information from those who may still be experiencing browser related TDRs caused by their display driver.

[b]Before submitting your issue, please verify your symptoms as follows:[/b]

-Your PC is experiencing browser related TDRs when display driver 280.19 or later driver is installed
-Verify your issue goes away if you roll back to NVIDIA display driver 275.50:

[b][u]Desktop[/u][/b]
[b]Windows 7 32-bit, Windows Vista 32-bit:[/b]
http://www.nvidia.com/object/win7-winvista-32bit-275.50-beta-driver.html

[b]Windows 7 64-bit, Windows Vista 64-bit:[/b]
http://www.nvidia.com/object/win7-winvista-64bit-275.50-beta-driver.html

[u][b]Notebook[/b][/u]
[b]Windows 7 32-bit, Windows Vista 32-bit:[/b]
http://www.nvidia.com/object/notebook-win7-winvista-275.50-beta-driver.html

[b]Windows 7 64-bit, Windows Vista 64-bit:[/b]
http://www.nvidia.com/object/notebook-win7-winvista-64bit-275.50-beta-driver.html

-If you continue to experience TDRs while browsing the web, you may have a different issue. Please scroll down to the troubleshooting section to help you determine cause of your symptoms

-If the browser related TDRs go away with display driver 275.50, please update your display drivers to the latest version from the URL below and check if our recent drivers fixes resolve your issue:

http://www.geforce.com/drivers

Once you have verified your system is experiencing a desktop/internet browsing related TDR, please fill out the form below so that we may investigate your issue:

http://surveys.nvidia.com/index.jsp?pi=241032f7eb7c9be2b568cb64e9dc9851

Finally, once you have completed the form above, we will also need your Windows dump files which will provide us with further information needed to diagnose your issue. The dump files we need the most are the ones that are located in c:\windows\LiveKernelReports\WatchDog. They are all in the form WD-YYYYMMDD-HHMM-XX.dmp. The other types which includes general crashes are located at c:\windows\minidump and will be in the form of mmddyy-xxxxx-zz.dmp. If you would like to email the files, please send the files to nvidiaforums@yahoo.com. Include your NVIDIA Forums username in the body of the email so that we may match it with the survey you have submitted. While working with some of our customers, we have come to realize that some of the issues are system specific and therefore we ask that you provide as much information as possible so that we can address your specific issue. Thank you.

[u][b]Troubleshooting TDR Issues:[/b][/u]
As previously mentioned, many things can lead to a Windows TDR including the following:

- Overclocking
- Defective/poor quality power supply
- Defective or incorrectly installed memory
- Improper air flow inside of PC that can result in overheating
- Bad driver install
- Defective graphics card
- Over/under voltage to the CPU, memory or graphics card
- Bad motherboard

[b]Overclocking[/b] - Overclocking is never a guaranteed science. As you update your device drivers, your components may become more sensitive to overclocking and thus produce errors. If your PC is overclocked, the first step to troubleshooting PC issues is reduce your PC's CPU and memory speeds to the stock values. Some enthusiast motherboards will leave certain options slightly overclocked in order to appear faster in benchmarks. Check your motherboard BIOS settings to make sure all settings are at the standard values. If your graphics card was factory overclocked, reduce the clock speeds to the same values NVIDIA uses for their reference designs.

[b]Defective/poor quality power supply[/b] - PC's today are becoming smarter in how it manages the amount of power consumption by reducing clock speeds when demand is low and dramatically increasing the same clock speeds when the load increases. As a result, the need for quality power supplies is ever so important to ensure you do not experience system instability as the amount of power increases with load. A defective power supply may appear to be operating normal under light PC usage. Increasing the load on your power supply is often a good indicator of whether it is working properly or not.

[b]Defective or incorrectly installed memory[/b] - While assisting customers with PC stability issues, unstable PC memory is often the culprit. Several 3rd party utilities are available to test your system memory.
One of the most popular free 3rd party memory test utilities is Memtest which is available for download from:

www.memtest.org

The test process is a long. If the memory test fails for any reason, it is likely that one of your memory modules is defective.

[b]Improper air flow inside of PC that can result in overheating[/b] - Always place your PC in an open area where the air may circulate inside of your PC. Check inside of your PC to verify all fans are still operational.

[b]Bad driver install[/b]

End users generally have more than one system monitoring utility running in the background that can sometimes lead to bad driver installs and this can also cause TDRs. When you begin to experience system instability following a driver update, we recommend users perform an NVIDIA Display Driver Clean Installation by following the steps below:

1) Click on the Windows Start Button.

2) Select Control Panel.

3) Select Uninstall a program under Programs or select Programs and Features depending on the control panel view.

4) Double-click on NVIDIA Graphics Driver in the program list and follow the uninstall instructions. Click Restart Now when prompted.

5) After restart, if you have any remaining display drivers stored in your Windows directory, Windows may start to install a different graphics driver. If so, allow it to install the driver and then restart again when prompted.

6) Repeat steps 1 through 5 until the NVIDIA Graphics Driver version is 275.XX or earlier OR until there is no NVIDIA Graphics Driver reported under Programs.

7) Download the latest NVIDIA display driver from:

http://www.geforce.com/Drivers

8) At this point, we recommend you may disable any system monitoring tools or anti-virus software running in the background as they may sometimes prevent driver files or registry keys from being written correctly during the installation process. After a driver installation has completed, you can re-enable your system monitoring or anti-virus software. To begin the driver installation process, Right-click on the NVIDIA display driver package and select "Run as administrator".

9) Continue to the Install Options page. Select Custom install.

10) On the Custom install page, select the checkbox for Perform clean install. Click next.

11) During the clean installation the driver, follow any requests to restart your PC.

12) After the installation is complete, restart your PC one final time.

Further TDR troubleshooting steps may be found in the "NVIDIA Statement on TDR Errors Display driver nvlddmkm stopped.." thread which can be accessed from the URL below:

http://forums.nvidia.com/index.php?showtopic=65161
This thread is a continuation of the original thread created to address reports by some end users of TDRs on their PCs when browsing the web using Internet Explorer 9 or Firefox with GPU acceleration enabled. A Windows TDR is a symptom and not a cause. This thread is meant to track a specific type of Windows TDR that is reported to have first appeared in the NVIDIA display driver R280.19 and continued in later drivers. First a brief introduction to what a TDR is.



Microsoft's Windows Vista was the first operating system to introduce TDRs as a way for the system to recover from a graphics card error that in prior operating systems would cause the whole system to crash forcing the user to reboot his/her PC. Since the graphics card is constantly sending a video signal to your PC's display, any system instability could trigger a TDR. If you have ever driven a car and had the check engine light go on while driving, you may have noticed that once you take the car to a mechanic for inspection, in most cases it was not the engine that was the cause for the check engine light to come on. This is similar to Windows TDRs. While a defective graphics card or a bug in the display drivers could trigger a TDR, so could a number of other PC components or software applications. When a TDR is triggered by the operating system, you will see a balloon message like the one below appear on the bottom right hand corner of your screen.



Image



Beginning with NVIDIA display driver release 280.19, improvements were made in the drivers which provided better power management and GPU performance. Following the release of this driver, we started receiving some reports of users experiencing TDRs while browsing in Mozilla's Firefox or Microsoft's Internet Explorer 9 with GPU acceleration enabled. Users claim that by downgrading the display driver to version 275.50 or earlier drivers would resolve these issues. By working with our customers, our software team has been able to provide fixes in our more recent driver releases for these browser related TDRs. Some of the most recent reports of TDRs from users have been caused by defective hardware components (motherboard, memory, graphics card, hard drive, etc.) and therefore we would like to both help customers diagnose their issue and also gather further information from those who may still be experiencing browser related TDRs caused by their display driver.



Before submitting your issue, please verify your symptoms as follows:



-Your PC is experiencing browser related TDRs when display driver 280.19 or later driver is installed

-Verify your issue goes away if you roll back to NVIDIA display driver 275.50:



Desktop

Windows 7 32-bit, Windows Vista 32-bit:

http://www.nvidia.com/object/win7-winvista-32bit-275.50-beta-driver.html



Windows 7 64-bit, Windows Vista 64-bit:

http://www.nvidia.com/object/win7-winvista-64bit-275.50-beta-driver.html



Notebook

Windows 7 32-bit, Windows Vista 32-bit:

http://www.nvidia.com/object/notebook-win7-winvista-275.50-beta-driver.html



Windows 7 64-bit, Windows Vista 64-bit:

http://www.nvidia.com/object/notebook-win7-winvista-64bit-275.50-beta-driver.html



-If you continue to experience TDRs while browsing the web, you may have a different issue. Please scroll down to the troubleshooting section to help you determine cause of your symptoms



-If the browser related TDRs go away with display driver 275.50, please update your display drivers to the latest version from the URL below and check if our recent drivers fixes resolve your issue:



http://www.geforce.com/drivers



Once you have verified your system is experiencing a desktop/internet browsing related TDR, please fill out the form below so that we may investigate your issue:



http://surveys.nvidia.com/index.jsp?pi=241032f7eb7c9be2b568cb64e9dc9851



Finally, once you have completed the form above, we will also need your Windows dump files which will provide us with further information needed to diagnose your issue. The dump files we need the most are the ones that are located in c:\windows\LiveKernelReports\WatchDog. They are all in the form WD-YYYYMMDD-HHMM-XX.dmp. The other types which includes general crashes are located at c:\windows\minidump and will be in the form of mmddyy-xxxxx-zz.dmp. If you would like to email the files, please send the files to nvidiaforums@yahoo.com. Include your NVIDIA Forums username in the body of the email so that we may match it with the survey you have submitted. While working with some of our customers, we have come to realize that some of the issues are system specific and therefore we ask that you provide as much information as possible so that we can address your specific issue. Thank you.



Troubleshooting TDR Issues:

As previously mentioned, many things can lead to a Windows TDR including the following:



- Overclocking

- Defective/poor quality power supply

- Defective or incorrectly installed memory

- Improper air flow inside of PC that can result in overheating

- Bad driver install

- Defective graphics card

- Over/under voltage to the CPU, memory or graphics card

- Bad motherboard



Overclocking - Overclocking is never a guaranteed science. As you update your device drivers, your components may become more sensitive to overclocking and thus produce errors. If your PC is overclocked, the first step to troubleshooting PC issues is reduce your PC's CPU and memory speeds to the stock values. Some enthusiast motherboards will leave certain options slightly overclocked in order to appear faster in benchmarks. Check your motherboard BIOS settings to make sure all settings are at the standard values. If your graphics card was factory overclocked, reduce the clock speeds to the same values NVIDIA uses for their reference designs.



Defective/poor quality power supply - PC's today are becoming smarter in how it manages the amount of power consumption by reducing clock speeds when demand is low and dramatically increasing the same clock speeds when the load increases. As a result, the need for quality power supplies is ever so important to ensure you do not experience system instability as the amount of power increases with load. A defective power supply may appear to be operating normal under light PC usage. Increasing the load on your power supply is often a good indicator of whether it is working properly or not.



Defective or incorrectly installed memory - While assisting customers with PC stability issues, unstable PC memory is often the culprit. Several 3rd party utilities are available to test your system memory.

One of the most popular free 3rd party memory test utilities is Memtest which is available for download from:



www.memtest.org



The test process is a long. If the memory test fails for any reason, it is likely that one of your memory modules is defective.



Improper air flow inside of PC that can result in overheating - Always place your PC in an open area where the air may circulate inside of your PC. Check inside of your PC to verify all fans are still operational.



Bad driver install



End users generally have more than one system monitoring utility running in the background that can sometimes lead to bad driver installs and this can also cause TDRs. When you begin to experience system instability following a driver update, we recommend users perform an NVIDIA Display Driver Clean Installation by following the steps below:



1) Click on the Windows Start Button.



2) Select Control Panel.



3) Select Uninstall a program under Programs or select Programs and Features depending on the control panel view.



4) Double-click on NVIDIA Graphics Driver in the program list and follow the uninstall instructions. Click Restart Now when prompted.



5) After restart, if you have any remaining display drivers stored in your Windows directory, Windows may start to install a different graphics driver. If so, allow it to install the driver and then restart again when prompted.



6) Repeat steps 1 through 5 until the NVIDIA Graphics Driver version is 275.XX or earlier OR until there is no NVIDIA Graphics Driver reported under Programs.



7) Download the latest NVIDIA display driver from:



http://www.geforce.com/Drivers



8) At this point, we recommend you may disable any system monitoring tools or anti-virus software running in the background as they may sometimes prevent driver files or registry keys from being written correctly during the installation process. After a driver installation has completed, you can re-enable your system monitoring or anti-virus software. To begin the driver installation process, Right-click on the NVIDIA display driver package and select "Run as administrator".



9) Continue to the Install Options page. Select Custom install.



10) On the Custom install page, select the checkbox for Perform clean install. Click next.



11) During the clean installation the driver, follow any requests to restart your PC.



12) After the installation is complete, restart your PC one final time.



Further TDR troubleshooting steps may be found in the "NVIDIA Statement on TDR Errors Display driver nvlddmkm stopped.." thread which can be accessed from the URL below:



http://forums.nvidia.com/index.php?showtopic=65161

Please send me a PM if I fail to keep up on replying in any specific thread or leave a driver feedback: Driver Feedback

#1
Posted 02/24/2012 10:40 AM   
[quote name='ManuelG' date='24 February 2012 - 10:40 AM' timestamp='1330080039' post='1374300']
This thread is a continuation of the original [url="http://forums.nvidia.com/index.php?showtopic=215256"]thread[/url] created to address reports by some end users of [url="http://msdn.microsoft.com/en-us/windows/hardware/gg487368"]TDRs[/url] on their PCs when browsing the web using Internet Explorer 9 or Firefox with [b]GPU acceleration enabled[/b].

Beginning with NVIDIA display driver release 280.19, improvements were made in the drivers which provided better power management and GPU performance. Following the release of this driver, we started receiving some reports of users experiencing TDRs while browsing in Mozilla's Firefox or Microsoft's Internet Explorer 9 [b]with GPU acceleration enabled[/b].
[/quote]
This isn't accurate. All the affected driver revisions also affected users who had browsers with no GPU acceleration. I used 3.6.25 which did not support hardware acceleration. I even tried disabling hardware flash. Additionally other users tried disabling GPU acceleration in browers that supported it and it did not (always?) help. Additionally TDRs were spotted with browsers idle in the background or indeed with no browser running at all. It seems the browser is only relevant because of how it behaves on the hardware, not anything the browser is actually doing.

It should also be mentioned that 290.53 (and newer drivers?) while fixing the issue for a number of users, made it [b]much worse[/b] for some other users. What were once 0x117 bugcheck TDRs became complete system freezes? or 0x116 bugcheck blue screens of death.

Any idea what was causing the TDRs in driver revisions 280.19, 280.26, 280.36, 285.27, 285.38, 285.62, 285.79, 290.36 over a period of about five months yet? Since a fix was included in the aforementioned 290.53, can I get some sort of idea of why I had these broken drivers for ~5 months? Does that seem unreasonable? No one has taken any responsibility yet.
[quote name='ManuelG' date='24 February 2012 - 10:40 AM' timestamp='1330080039' post='1374300']

This thread is a continuation of the original thread created to address reports by some end users of TDRs on their PCs when browsing the web using Internet Explorer 9 or Firefox with GPU acceleration enabled.



Beginning with NVIDIA display driver release 280.19, improvements were made in the drivers which provided better power management and GPU performance. Following the release of this driver, we started receiving some reports of users experiencing TDRs while browsing in Mozilla's Firefox or Microsoft's Internet Explorer 9 with GPU acceleration enabled.



This isn't accurate. All the affected driver revisions also affected users who had browsers with no GPU acceleration. I used 3.6.25 which did not support hardware acceleration. I even tried disabling hardware flash. Additionally other users tried disabling GPU acceleration in browers that supported it and it did not (always?) help. Additionally TDRs were spotted with browsers idle in the background or indeed with no browser running at all. It seems the browser is only relevant because of how it behaves on the hardware, not anything the browser is actually doing.



It should also be mentioned that 290.53 (and newer drivers?) while fixing the issue for a number of users, made it much worse for some other users. What were once 0x117 bugcheck TDRs became complete system freezes? or 0x116 bugcheck blue screens of death.



Any idea what was causing the TDRs in driver revisions 280.19, 280.26, 280.36, 285.27, 285.38, 285.62, 285.79, 290.36 over a period of about five months yet? Since a fix was included in the aforementioned 290.53, can I get some sort of idea of why I had these broken drivers for ~5 months? Does that seem unreasonable? No one has taken any responsibility yet.

GPU: MSI GTX560Ti Twin Frozr II OC 880/4200 (factory overclock)

Monitor: Dell 2312HM 1920x1080@60hz
Monitor/TV: LG32LH5000 1920x1080@50hz

#2
Posted 02/24/2012 11:29 AM   
[quote name='skilak' date='24 February 2012 - 11:29 AM' timestamp='1330082988' post='1374314']
...
[/quote]
I think the interesting information for you, that really 560ti has problems. The change GPU removes the problem.
Quote from Russian forum about bf3
[quote]Personally, I have after replacing PALIT 560Ti ([b]GF114[/b]) 2GB on PALIT 560Ti-448 ([b]GF110[/b]) 1280MB stopped all flights (version firewood (drivers) remained unchanged), for nearly one and a half weeks of play without any problems.[/quote]
[quote name='skilak' date='24 February 2012 - 11:29 AM' timestamp='1330082988' post='1374314']

...



I think the interesting information for you, that really 560ti has problems. The change GPU removes the problem.

Quote from Russian forum about bf3

Personally, I have after replacing PALIT 560Ti (GF114) 2GB on PALIT 560Ti-448 (GF110) 1280MB stopped all flights (version firewood (drivers) remained unchanged), for nearly one and a half weeks of play without any problems.

#3
Posted 02/24/2012 01:52 PM   
Probably a silly suggestion but since all these problems only happen to people when using a single monitor (due to clock speeds etc), has anyone ever tried running their monitor off the second DVI port?
Probably a silly suggestion but since all these problems only happen to people when using a single monitor (due to clock speeds etc), has anyone ever tried running their monitor off the second DVI port?

GPU: MSI GTX560Ti Twin Frozr II OC 880/4200 (factory overclock)

Monitor: Dell 2312HM 1920x1080@60hz
Monitor/TV: LG32LH5000 1920x1080@50hz

#4
Posted 02/24/2012 07:21 PM   
[quote name='skilak' date='24 February 2012 - 07:21 PM' timestamp='1330111272' post='1374541']
Probably a silly suggestion but since all these problems only happen to people when using a single monitor (due to clock speeds etc), has anyone ever tried running their monitor off the second DVI port?
[/quote]

I didnt think the card saw the Dvi ports as port one or two, only if there apparently were two monitors connected. ?

Interesting question mind.
[quote name='skilak' date='24 February 2012 - 07:21 PM' timestamp='1330111272' post='1374541']

Probably a silly suggestion but since all these problems only happen to people when using a single monitor (due to clock speeds etc), has anyone ever tried running their monitor off the second DVI port?





I didnt think the card saw the Dvi ports as port one or two, only if there apparently were two monitors connected. ?



Interesting question mind.

#5
Posted 02/24/2012 08:41 PM   
Faulty hardware. Possibly. But, not likely. I have a Evga Superclocked GTX 560. This random TDR while browsing using Firefox. It has followed me with 2 different systems. Any driver past 275.33 random tdr's while browsing. My second system which is the newest. Got it on Feb. 1st 2012. Since installing the latest whql driver early morning. Nothing at all while using Firefox. It has been the drivers all along. Nvidia changed or fixed something in this latest release. What a complete waste of troubleshooting and possible rma back to Evga. I would have sent back a perfectly working good card. I bought this card back in July 2011. And like I said. Have not been able to upgrade drivers past 275.33. Not only did it stop me from being able to play new games. Now Kepler is practically around the corner. While I am glad it is fixed for some. Like me. I can completely sympathize with other users still having this issue. I will never again buy another Nvidia card because of this. I was so done with this card. I was giving this latest whql its last shot. If they did not work. I was going to sell it.

P.S. I say it is fixed for me. Then again. It has not been 2-4 weeks yet. If no tdr hits for a month or so. I would say it is fixed.
Faulty hardware. Possibly. But, not likely. I have a Evga Superclocked GTX 560. This random TDR while browsing using Firefox. It has followed me with 2 different systems. Any driver past 275.33 random tdr's while browsing. My second system which is the newest. Got it on Feb. 1st 2012. Since installing the latest whql driver early morning. Nothing at all while using Firefox. It has been the drivers all along. Nvidia changed or fixed something in this latest release. What a complete waste of troubleshooting and possible rma back to Evga. I would have sent back a perfectly working good card. I bought this card back in July 2011. And like I said. Have not been able to upgrade drivers past 275.33. Not only did it stop me from being able to play new games. Now Kepler is practically around the corner. While I am glad it is fixed for some. Like me. I can completely sympathize with other users still having this issue. I will never again buy another Nvidia card because of this. I was so done with this card. I was giving this latest whql its last shot. If they did not work. I was going to sell it.



P.S. I say it is fixed for me. Then again. It has not been 2-4 weeks yet. If no tdr hits for a month or so. I would say it is fixed.

#6
Posted 02/24/2012 09:33 PM   
Well, good news: I know it's early, but I haven't had any TDR yet after installing the 295.73 drivers. I'm using Opera and Firefox and with beta 295.51 I had frequent lockups while using both browsers. MSI GTX 560Ti Hawk.
Well, good news: I know it's early, but I haven't had any TDR yet after installing the 295.73 drivers. I'm using Opera and Firefox and with beta 295.51 I had frequent lockups while using both browsers. MSI GTX 560Ti Hawk.

#7
Posted 02/24/2012 09:34 PM   
[quote name='Jay_ombie' date='24 February 2012 - 08:41 PM' timestamp='1330116073' post='1374583']
I didnt think the card saw the Dvi ports as port one or two, only if there apparently were two monitors connected. ?

Interesting question mind.
[/quote]
I usually have two plugged in but the second is usually turned off. I've been having some issues with my monitor, at least I assumed it was the monitor but I've found they seem to have completely gone with the monitor plugged into #2 DVI port. I have not fully troubleshooted (shot?) the problem yet but it has me thinking.
[quote name='Jay_ombie' date='24 February 2012 - 08:41 PM' timestamp='1330116073' post='1374583']

I didnt think the card saw the Dvi ports as port one or two, only if there apparently were two monitors connected. ?



Interesting question mind.



I usually have two plugged in but the second is usually turned off. I've been having some issues with my monitor, at least I assumed it was the monitor but I've found they seem to have completely gone with the monitor plugged into #2 DVI port. I have not fully troubleshooted (shot?) the problem yet but it has me thinking.

GPU: MSI GTX560Ti Twin Frozr II OC 880/4200 (factory overclock)

Monitor: Dell 2312HM 1920x1080@60hz
Monitor/TV: LG32LH5000 1920x1080@50hz

#8
Posted 02/24/2012 09:48 PM   
[quote]Well, good news: I know it's early, but I haven't had any TDR yet after installing the 295.73 drivers...[/quote]

+1

No BSODs and no TDRs so far so good. My system is stable.
I´m waiting for 2/3 weeks for free TDRs and BSODs.

My card ASUS GTX560Ti DirectCU II 1GB
Well, good news: I know it's early, but I haven't had any TDR yet after installing the 295.73 drivers...




+1



No BSODs and no TDRs so far so good. My system is stable.

I´m waiting for 2/3 weeks for free TDRs and BSODs.



My card ASUS GTX560Ti DirectCU II 1GB

#9
Posted 02/24/2012 09:55 PM   
It has been several days after installing 295.73 with NO TDRs yet.

I'm still holding my breath here and I really hope this finally solves it. This problem has been so frustrating.
I was looking at buying a whole new computer for a while since apparently just swapping out the graphics card might not fix it.
And I don't really want to do that.
It has been several days after installing 295.73 with NO TDRs yet.



I'm still holding my breath here and I really hope this finally solves it. This problem has been so frustrating.

I was looking at buying a whole new computer for a while since apparently just swapping out the graphics card might not fix it.

And I don't really want to do that.

#10
Posted 02/25/2012 01:48 PM   
[quote name='skilak' date='24 February 2012 - 07:21 PM' timestamp='1330111272' post='1374541']
Probably a silly suggestion but since all these problems only happen to people when using a single monitor (due to clock speeds etc), has anyone ever tried running their monitor off the second DVI port?
[/quote]
I did - same.
[quote name='skilak' date='24 February 2012 - 07:21 PM' timestamp='1330111272' post='1374541']

Probably a silly suggestion but since all these problems only happen to people when using a single monitor (due to clock speeds etc), has anyone ever tried running their monitor off the second DVI port?



I did - same.

AMD Phenom II x4 965 @3.6GHz | 8GB DDR3 RAM @1333MHz, 9-9-9-24 | Asus M4A79T Deluxe (BIOS v.3503)
Asus GTX670DCII (default clocks) | Zalman 850W PSU | Windows 7 x64 SP1

#11
Posted 02/25/2012 03:32 PM   
I'm still strongly affected by TDR events just as described in initial post with following differencies:

1. TDRs extend to driver 275.50 and below (encountered on driver 275.33) but otherwise express just same as described in 1st post (black screen immediately followed by the alert bubble, sometimes single and sometimes in series followed by BSOD). I observed that the serial TDRs may be timing problem when OS is busy to not be able handle previous TDR in time causing to arise subsequent TDR imediatelly. The crash dumps identify the symptom as TDR.
2. TDRs come up during output to external LCD (not tested with internal display)
3. TDRs extend to all released drivers 295.xx including betas
4. TDRs don't arise at all or only very rare when [url="http://x264.nl/"]video conversion tool[/url] is running in the background. If I know right this tool doesnot activate CUDA but spends all CPU resources and cores available.
5. TDRs mostly arise when CPU is idle or low used and performing action that quickly requests all CPU resources for short time (such a page load in Firefox)
6. TDRs are yet more frequent to come up when running VBoxed OS (Windows XP) in the background on secondary display
7. I already have sumbited several crash dumps achieved mostly with driver version 290.xx beta to NVidias email stated in 1st post but no response.

Therefore due 1st point it's not sure if my problems are the of driver kind or system specific problem. I'd say due to points 5. and 6. that it may be related to undervolting problem of some hardware but don't know how to troubleshoot it. This laptop was twice sent to repair service with successfully passed hardware stress tests, of which once I requested HW diagnostics of GPU, which passed successfully too. Due to listed deviations I'm not sure if I should sumbit another crash reports or look up the problem in HW. Btw. I got another TDR during writing this post.
I'm still strongly affected by TDR events just as described in initial post with following differencies:



1. TDRs extend to driver 275.50 and below (encountered on driver 275.33) but otherwise express just same as described in 1st post (black screen immediately followed by the alert bubble, sometimes single and sometimes in series followed by BSOD). I observed that the serial TDRs may be timing problem when OS is busy to not be able handle previous TDR in time causing to arise subsequent TDR imediatelly. The crash dumps identify the symptom as TDR.

2. TDRs come up during output to external LCD (not tested with internal display)

3. TDRs extend to all released drivers 295.xx including betas

4. TDRs don't arise at all or only very rare when video conversion tool is running in the background. If I know right this tool doesnot activate CUDA but spends all CPU resources and cores available.

5. TDRs mostly arise when CPU is idle or low used and performing action that quickly requests all CPU resources for short time (such a page load in Firefox)

6. TDRs are yet more frequent to come up when running VBoxed OS (Windows XP) in the background on secondary display

7. I already have sumbited several crash dumps achieved mostly with driver version 290.xx beta to NVidias email stated in 1st post but no response.



Therefore due 1st point it's not sure if my problems are the of driver kind or system specific problem. I'd say due to points 5. and 6. that it may be related to undervolting problem of some hardware but don't know how to troubleshoot it. This laptop was twice sent to repair service with successfully passed hardware stress tests, of which once I requested HW diagnostics of GPU, which passed successfully too. Due to listed deviations I'm not sure if I should sumbit another crash reports or look up the problem in HW. Btw. I got another TDR during writing this post.

#12
Posted 02/25/2012 04:47 PM   
[quote name='Anakunda' date='25 February 2012 - 04:47 PM' timestamp='1330188478' post='1374953']
I'm still strongly affected by TDR events just as described in initial post with following differencies:

1. [b]TDRs extend to driver 275.50 and below[/b] (encountered on driver 275.33) but otherwise express just same as described in 1st post (black screen
[/quote]
Are you saying you are getting TDR's with 275.33 and 275.50? If so this thread is dealing with a totally different issue. You may want to create a new thread and request help.
[quote name='Anakunda' date='25 February 2012 - 04:47 PM' timestamp='1330188478' post='1374953']

I'm still strongly affected by TDR events just as described in initial post with following differencies:



1. TDRs extend to driver 275.50 and below (encountered on driver 275.33) but otherwise express just same as described in 1st post (black screen



Are you saying you are getting TDR's with 275.33 and 275.50? If so this thread is dealing with a totally different issue. You may want to create a new thread and request help.

Case: Coolermaster HAF-X

GPU: MSI GTX560Ti TwinFrozr2 (factory OC @ 880MHz)

i7-3770K | ASUS P8Z77-V- PRO| 8GB KINGSTON HYPER-X DDR3 1600MHz | 240GB OCZ Vertex 3 | 1TB WD Caviar Green (Storage) | BenQ V2220H (connected via HDMI) | Corsair TX750W PSU | Noctua NH-D14 | Windows 8.1 Pro | Onboard Sound (Realtek) | Browsers: Firefox (latest version) and occasionally IE 11 | Adobe Flash Player (latest version)

#13
Posted 02/25/2012 06:00 PM   
I've spent the better part of 100 hours trying to resolve the issue of post-275.33 drivers causing the system to crash to bluescreen during web browsing, not including the time it took to exchange the video card or the time it spent in the hands of far more knowledgeable people who also could not solve the problem. I'm a patient guy, and part of me wants to continue to work with Nvidia towards a solution; but the other part is now wondering if the simplest solution may be to spend several hundred dollars to get a new video card from a different company as opposed to waiting for a solution which may or may not materialize months from now.
I was kind of hoping this new 295.73 driver would address the [i]minor[/i] issue of the system being rendered unstable and randomly inoperable during web browsing, but the driver doesn't appear to address the issue and I don't feel like playing Russian Roulette again. Maybe it's classical conditioning. :(
I've spent the better part of 100 hours trying to resolve the issue of post-275.33 drivers causing the system to crash to bluescreen during web browsing, not including the time it took to exchange the video card or the time it spent in the hands of far more knowledgeable people who also could not solve the problem. I'm a patient guy, and part of me wants to continue to work with Nvidia towards a solution; but the other part is now wondering if the simplest solution may be to spend several hundred dollars to get a new video card from a different company as opposed to waiting for a solution which may or may not materialize months from now.

I was kind of hoping this new 295.73 driver would address the minor issue of the system being rendered unstable and randomly inoperable during web browsing, but the driver doesn't appear to address the issue and I don't feel like playing Russian Roulette again. Maybe it's classical conditioning. :(

#14
Posted 02/25/2012 08:23 PM   
[quote name='Anakunda' date='25 February 2012 - 05:47 PM' timestamp='1330188478' post='1374953']
I'm still strongly affected by TDR events just as described in initial post with following differencies:

1. TDRs extend to driver 275.50 and below (encountered on driver 275.33) but otherwise express just same as described in 1st post (black screen immediately followed by the alert bubble, sometimes single and sometimes in series followed by BSOD). I observed that the serial TDRs may be timing problem when OS is busy to not be able handle previous TDR in time causing to arise subsequent TDR imediatelly. The crash dumps identify the symptom as TDR.
2. TDRs come up during output to external LCD (not tested with internal display)
3. TDRs extend to all released drivers 295.xx including betas
4. TDRs don't arise at all or only very rare when [url="http://x264.nl/"]video conversion tool[/url] is running in the background. If I know right this tool doesnot activate CUDA but spends all CPU resources and cores available.
5. TDRs mostly arise when CPU is idle or low used and performing action that quickly requests all CPU resources for short time (such a page load in Firefox)
6. TDRs are yet more frequent to come up when running VBoxed OS (Windows XP) in the background on secondary display
7. I already have sumbited several crash dumps achieved mostly with driver version 290.xx beta to NVidias email stated in 1st post but no response.

Therefore due 1st point it's not sure if my problems are the of driver kind or system specific problem. I'd say due to points 5. and 6. that it may be related to undervolting problem of some hardware but don't know how to troubleshoot it. This laptop was twice sent to repair service with successfully passed hardware stress tests, of which once I requested HW diagnostics of GPU, which passed successfully too. Due to listed deviations I'm not sure if I should sumbit another crash reports or look up the problem in HW. Btw. I got another TDR during writing this post.
[/quote]

^^^This!

[quote name='ABDULH' date='25 February 2012 - 07:00 PM' timestamp='1330192859' post='1374995']
Are you saying you are getting TDR's with 275.33 and 275.50? If so this thread is dealing with a totally different issue. You may want to create a new thread and request help.
[/quote]

I have even encountered TDR's with version 270.xx
BUT before you send me off to create another topic, allow me to add that before a certain date (about a month ago? I didn't write the date down that day...) I NEVER got any TDR's even though I had been using the same card and the same 270.xx drivers for quite some time.

So maybe this is all just one, more complicated problem that affects more versions and relies on more parameters than you might think. I suspect, for instance, a certain Windows update in combination with my video card's hardware may have caused my problems, while someone else's problem may be driver+hardware related, or Wupdate+driver related, or a combination of all three. This does sound quite far-fetched, but how else could you explain this?
By the way, I bought a new 650W CoolerMaster for my <400W consuming PC, so bad power supply should not be the issue here...
[quote name='Anakunda' date='25 February 2012 - 05:47 PM' timestamp='1330188478' post='1374953']

I'm still strongly affected by TDR events just as described in initial post with following differencies:



1. TDRs extend to driver 275.50 and below (encountered on driver 275.33) but otherwise express just same as described in 1st post (black screen immediately followed by the alert bubble, sometimes single and sometimes in series followed by BSOD). I observed that the serial TDRs may be timing problem when OS is busy to not be able handle previous TDR in time causing to arise subsequent TDR imediatelly. The crash dumps identify the symptom as TDR.

2. TDRs come up during output to external LCD (not tested with internal display)

3. TDRs extend to all released drivers 295.xx including betas

4. TDRs don't arise at all or only very rare when video conversion tool is running in the background. If I know right this tool doesnot activate CUDA but spends all CPU resources and cores available.

5. TDRs mostly arise when CPU is idle or low used and performing action that quickly requests all CPU resources for short time (such a page load in Firefox)

6. TDRs are yet more frequent to come up when running VBoxed OS (Windows XP) in the background on secondary display

7. I already have sumbited several crash dumps achieved mostly with driver version 290.xx beta to NVidias email stated in 1st post but no response.



Therefore due 1st point it's not sure if my problems are the of driver kind or system specific problem. I'd say due to points 5. and 6. that it may be related to undervolting problem of some hardware but don't know how to troubleshoot it. This laptop was twice sent to repair service with successfully passed hardware stress tests, of which once I requested HW diagnostics of GPU, which passed successfully too. Due to listed deviations I'm not sure if I should sumbit another crash reports or look up the problem in HW. Btw. I got another TDR during writing this post.





^^^This!



[quote name='ABDULH' date='25 February 2012 - 07:00 PM' timestamp='1330192859' post='1374995']

Are you saying you are getting TDR's with 275.33 and 275.50? If so this thread is dealing with a totally different issue. You may want to create a new thread and request help.





I have even encountered TDR's with version 270.xx

BUT before you send me off to create another topic, allow me to add that before a certain date (about a month ago? I didn't write the date down that day...) I NEVER got any TDR's even though I had been using the same card and the same 270.xx drivers for quite some time.



So maybe this is all just one, more complicated problem that affects more versions and relies on more parameters than you might think. I suspect, for instance, a certain Windows update in combination with my video card's hardware may have caused my problems, while someone else's problem may be driver+hardware related, or Wupdate+driver related, or a combination of all three. This does sound quite far-fetched, but how else could you explain this?

By the way, I bought a new 650W CoolerMaster for my <400W consuming PC, so bad power supply should not be the issue here...

#15
Posted 02/25/2012 08:30 PM   
  1 / 23    
Scroll To Top