Display driver nvlddmkm stopped responding and has successfully recovered.
Display driver nvlddmkm stopped responding and has successfully recovered.
If nVidia and Firefox won't play nice I'm going to have to drop Firefox.
I believe the problem actually is with nVidia, because installing GeForce 275.33 Driver and earlier WHQL drivers eliminates the problem.
But changing video cards costs money, whereas changing web browsers is free.
Hence my statement, "If nVidia and Firefox won't play nice I'm going to have to drop Firefox."
It is not fair, but it is reality.
nVidia is ignoring the issue, because it knows we can cheaply bypass their bugs by switching browsers. (With other people they've pointed fingers at power supplies, mother boards, you name it, anything to pass the buck.)
I am not interested in bypasses. I am only interested in actual fixes.
In other words no jumping through hoops with manual procedures, driver sweeper, unplugging to stop windows update, or stupid actions like deleting all my Windows Restore Checkpoints, etc. Except for deleting all my Windows Restore Checkpoints I've done all that.
That nVidia suggest this suggests to me that the bug is actually in their install or uninstall scripts. The problem with their bypass is it introduces race conditions so it does not work on my system or many other nVidia 400 and 500 series graphics cards.
I've tried all the WHQL nVidia drivers since 275.33 and they all have this problem. So does the latest beta (I seldom ever do betas any more, but I made an exception).
Do a vanilla clean install using the standard install script included with the old 275.33 nVidia drivers and the problem does not occur.
If this is not going to be fixed, if we're going to be left with just bypasses, my bypass will be to change web browsers.
+++ So, can Mozilla somehow please light a fire under nVidia's feet? +++
I really do not want to change browsers, but it is the cheapest solution by far.
ప్రత్యుత్తరాలన్నీ (4)
There are some open bug reports on Nvidia's drivers. We can open a new bug (if you want to go that route, let me know the bug number and I will triage it), but all that Firefox can [usually] do is blacklist the driver so that HWA isn't run on that driver.
Your best bet (for now) is to disable HWA yourself and that should resolve the crashes
http://www.trishtech.com/internet/disable_hardware_acceleration_in_firefox_4.php
I've been battling the same problem for quite some time & have come to the same conclusion as the original poster. I also experience the same driver instability if Thunderbird is running.
I was using both Firefox 9 & Thunderbird 9. My computer is completely stable without the Mozilla software running (never running at all after booting). If I even start Firefox or Thunderbird & close them before having any display issues, it will still eventually crash (display artifacts followed by driver restarts).
I haven't tried disabling hardware acceleration yet for the Mozilla products, but have had zero crashes using Chrome with hardware acceleration enabled.
I have a similar problem as well. Only, the problem only occurs on youtube, and it only occurs while typing in the comments box. I've tried downgrading the flashplayer version and that did not help. I did not try downgrading the video driver version because I didn't want to have complications with other games and programs. So, instead I downgraded firefox to ver. 3, which fixed the problem. But, it also created problems with other video streaming sites as well as performance issues. I've attached a screenshot to show the frequency(in *1* day) of the display driver crashes... all in firefox 9.0.1 and all on youtube.
I have the same problem with AMD's video driver. I first did not see the correlation. CCC (AMD's catalyst control center) did crash on every windows-startup and Win7 had to restore it because Firefox was always was i immediately started. Now after the latest CCC-update Firefox constantly (every few minutes) crashes the video-driver. My PC is brandnew (Athlon X4-3,7GHz, 8GB DDR3, Radeon 6850, SSD) and i did at least (!) 5 clean installs of Windows 7 64bit. I don't blame Firefox for it, but i just have to switch to Chrome now.