Not sure what is going on but ever since I installed the 301.42 driver my display seems to be changing modes very slowly, the driver keeps frequently crashing and recovering, and 3D on\off responds so slowly sometimes it crashes out. Is this happening to anyone else?
Also ever since I installed the new driver, Andrew's damnable red non 3D display warning comes up all the time for no reason at all. Whoever programmed that thing is an idiot and deserves to be beaten with a rake, covered in tar and chicken feathers, and run out of town on a rail.
I'm on a 22" Mitsubishi Diamond Pro CRT at 1024x768 @ 120hz on a Geforce 460.
The display driver was NOT crashing before, something has changed.
Not sure what is going on but ever since I installed the 301.42 driver my display seems to be changing modes very slowly, the driver keeps frequently crashing and recovering, and 3D on\off responds so slowly sometimes it crashes out. Is this happening to anyone else?
Also ever since I installed the new driver, Andrew's damnable red non 3D display warning comes up all the time for no reason at all. Whoever programmed that thing is an idiot and deserves to be beaten with a rake, covered in tar and chicken feathers, and run out of town on a rail.
I'm on a 22" Mitsubishi Diamond Pro CRT at 1024x768 @ 120hz on a Geforce 460.
The display driver was NOT crashing before, something has changed.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
I had weird problems with 301.42 driver too. Sometimes game graphics had over 200ms latency and looked like antialiasing was missing, framerate was very low (10fps) too. This happened with Tribes: Ascend and Super Street Fighter 4:AE without 3D Vision.
Everything went back to normal after reboot, I also went back to 301.24 beta after second reboot.
I had weird problems with 301.42 driver too. Sometimes game graphics had over 200ms latency and looked like antialiasing was missing, framerate was very low (10fps) too. This happened with Tribes: Ascend and Super Street Fighter 4:AE without 3D Vision.
Everything went back to normal after reboot, I also went back to 301.24 beta after second reboot.
Windows 7 Pro 64-bit, i7 950, ASUS P6X58C-E, GTX 480
I have the same problem with my GTX560TI and an ASUS VG278H monitor. Whenever i switch from and to 3D the system freezes for some seconds. Sometimes it looks like the driver crashes (Windows switches from Aero to Basic theme). The sound plays weird loops when i play TV/music while the mode switches and sometimes my TV-card attached via FireWire cancels recordings! (weak TV signal in Media Center). Looks like there are strange things going on and the whole system gets locked for a timespan which is to long for some attached devices and they crash.
I have the same problem with my GTX560TI and an ASUS VG278H monitor. Whenever i switch from and to 3D the system freezes for some seconds. Sometimes it looks like the driver crashes (Windows switches from Aero to Basic theme). The sound plays weird loops when i play TV/music while the mode switches and sometimes my TV-card attached via FireWire cancels recordings! (weak TV signal in Media Center). Looks like there are strange things going on and the whole system gets locked for a timespan which is to long for some attached devices and they crash.
[quote name='Hoyt Pollard' date='01 June 2012 - 12:39 PM' timestamp='1338572361' post='1416391']
I have the same problem with my GTX560TI and an ASUS VG278H monitor. Whenever i switch from and to 3D the system freezes for some seconds. Sometimes it looks like the driver crashes (Windows switches from Aero to Basic theme). The sound plays weird loops when i play TV/music while the mode switches and sometimes my TV-card attached via FireWire cancels recordings! (weak TV signal in Media Center). Looks like there are strange things going on and the whole system gets locked for a timespan which is to long for some attached devices and they crash.
So the whole 3D-vision stuff is unusable for me.
[/quote]
Fixed it late last night. It was the 3D Vision emitter I think. For some reason unplugging it(it was on a four port hub) and plugging it back in caused the 3d vision usb driver to reinstall. I had originally tried 295.73 thinking it was a driver issue, I even went through a clean install with driver cleaner and all of that crap. But still the problem persisted. The mode change was slow, and the driver kept crashing frequently and recovering. Reverting to an old driver and having the same problem told me that wasn't it. I even swapped my monitor to the other port thinking that maybe one of my ramdacs was bad, and that did nothing.
My clue was that outputting it to my NOT 3D Vizio HD tv over vga caused the nvidia driver to attempt 3D stereo. But the mode change was not lagging. /blarg.gif' class='bbc_emoticon' alt=':/' />
So now I can play 3D again and everything works as before, mind you I have not reinstalled the 301.42 driver. I'm leaning toward the idea that nvidia updated the 3D Vision dongle with a bad driver that causes it to respond at either USB 1.1 speed or slower. Because it only seemed to happen when the emitter was switching on\off. SO when I unplugged the emitter and plugged it back in, it installed the old usb driver instead and it fixed it.
So having ruled everything else out from display to card malfunction to forceware version, my verdict is that it lies in the emitter driver.
I have the same problem with my GTX560TI and an ASUS VG278H monitor. Whenever i switch from and to 3D the system freezes for some seconds. Sometimes it looks like the driver crashes (Windows switches from Aero to Basic theme). The sound plays weird loops when i play TV/music while the mode switches and sometimes my TV-card attached via FireWire cancels recordings! (weak TV signal in Media Center). Looks like there are strange things going on and the whole system gets locked for a timespan which is to long for some attached devices and they crash.
So the whole 3D-vision stuff is unusable for me.
Fixed it late last night. It was the 3D Vision emitter I think. For some reason unplugging it(it was on a four port hub) and plugging it back in caused the 3d vision usb driver to reinstall. I had originally tried 295.73 thinking it was a driver issue, I even went through a clean install with driver cleaner and all of that crap. But still the problem persisted. The mode change was slow, and the driver kept crashing frequently and recovering. Reverting to an old driver and having the same problem told me that wasn't it. I even swapped my monitor to the other port thinking that maybe one of my ramdacs was bad, and that did nothing.
My clue was that outputting it to my NOT 3D Vizio HD tv over vga caused the nvidia driver to attempt 3D stereo. But the mode change was not lagging. /blarg.gif' class='bbc_emoticon' alt=':/' />
So now I can play 3D again and everything works as before, mind you I have not reinstalled the 301.42 driver. I'm leaning toward the idea that nvidia updated the 3D Vision dongle with a bad driver that causes it to respond at either USB 1.1 speed or slower. Because it only seemed to happen when the emitter was switching on\off. SO when I unplugged the emitter and plugged it back in, it installed the old usb driver instead and it fixed it.
So having ruled everything else out from display to card malfunction to forceware version, my verdict is that it lies in the emitter driver.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
[quote name='Hoyt Pollard' date='02 June 2012 - 03:57 AM' timestamp='1338627423' post='1416621']
Glad you found a fix. But my VG278H has an integrated emitter and is only connected via Dual-Link DVI. So your fix doesn't work for me.
[/quote]
Strange, I would send a bug report to Andrew and then point him to this thread. This seems to be a new problem that hasn't cropped up before so its definitely Nvidia's fault.
Glad you found a fix. But my VG278H has an integrated emitter and is only connected via Dual-Link DVI. So your fix doesn't work for me.
Strange, I would send a bug report to Andrew and then point him to this thread. This seems to be a new problem that hasn't cropped up before so its definitely Nvidia's fault.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
Also ever since I installed the new driver, Andrew's damnable red non 3D display warning comes up all the time for no reason at all. Whoever programmed that thing is an idiot and deserves to be beaten with a rake, covered in tar and chicken feathers, and run out of town on a rail.
I'm on a 22" Mitsubishi Diamond Pro CRT at 1024x768 @ 120hz on a Geforce 460.
The display driver was NOT crashing before, something has changed.
Also ever since I installed the new driver, Andrew's damnable red non 3D display warning comes up all the time for no reason at all. Whoever programmed that thing is an idiot and deserves to be beaten with a rake, covered in tar and chicken feathers, and run out of town on a rail.
I'm on a 22" Mitsubishi Diamond Pro CRT at 1024x768 @ 120hz on a Geforce 460.
The display driver was NOT crashing before, something has changed.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
Everything went back to normal after reboot, I also went back to 301.24 beta after second reboot.
Everything went back to normal after reboot, I also went back to 301.24 beta after second reboot.
Windows 7 Pro 64-bit, i7 950, ASUS P6X58C-E, GTX 480
So the whole 3D-vision stuff is unusable for me.
So the whole 3D-vision stuff is unusable for me.
I have the same problem with my GTX560TI and an ASUS VG278H monitor. Whenever i switch from and to 3D the system freezes for some seconds. Sometimes it looks like the driver crashes (Windows switches from Aero to Basic theme). The sound plays weird loops when i play TV/music while the mode switches and sometimes my TV-card attached via FireWire cancels recordings! (weak TV signal in Media Center). Looks like there are strange things going on and the whole system gets locked for a timespan which is to long for some attached devices and they crash.
So the whole 3D-vision stuff is unusable for me.
[/quote]
Fixed it late last night. It was the 3D Vision emitter I think. For some reason unplugging it(it was on a four port hub) and plugging it back in caused the 3d vision usb driver to reinstall. I had originally tried 295.73 thinking it was a driver issue, I even went through a clean install with driver cleaner and all of that crap. But still the problem persisted. The mode change was slow, and the driver kept crashing frequently and recovering. Reverting to an old driver and having the same problem told me that wasn't it. I even swapped my monitor to the other port thinking that maybe one of my ramdacs was bad, and that did nothing.
My clue was that outputting it to my NOT 3D Vizio HD tv over vga caused the nvidia driver to attempt 3D stereo. But the mode change was not lagging.
So now I can play 3D again and everything works as before, mind you I have not reinstalled the 301.42 driver. I'm leaning toward the idea that nvidia updated the 3D Vision dongle with a bad driver that causes it to respond at either USB 1.1 speed or slower. Because it only seemed to happen when the emitter was switching on\off. SO when I unplugged the emitter and plugged it back in, it installed the old usb driver instead and it fixed it.
So having ruled everything else out from display to card malfunction to forceware version, my verdict is that it lies in the emitter driver.
I have the same problem with my GTX560TI and an ASUS VG278H monitor. Whenever i switch from and to 3D the system freezes for some seconds. Sometimes it looks like the driver crashes (Windows switches from Aero to Basic theme). The sound plays weird loops when i play TV/music while the mode switches and sometimes my TV-card attached via FireWire cancels recordings! (weak TV signal in Media Center). Looks like there are strange things going on and the whole system gets locked for a timespan which is to long for some attached devices and they crash.
So the whole 3D-vision stuff is unusable for me.
Fixed it late last night. It was the 3D Vision emitter I think. For some reason unplugging it(it was on a four port hub) and plugging it back in caused the 3d vision usb driver to reinstall. I had originally tried 295.73 thinking it was a driver issue, I even went through a clean install with driver cleaner and all of that crap. But still the problem persisted. The mode change was slow, and the driver kept crashing frequently and recovering. Reverting to an old driver and having the same problem told me that wasn't it. I even swapped my monitor to the other port thinking that maybe one of my ramdacs was bad, and that did nothing.
My clue was that outputting it to my NOT 3D Vizio HD tv over vga caused the nvidia driver to attempt 3D stereo. But the mode change was not lagging.
So now I can play 3D again and everything works as before, mind you I have not reinstalled the 301.42 driver. I'm leaning toward the idea that nvidia updated the 3D Vision dongle with a bad driver that causes it to respond at either USB 1.1 speed or slower. Because it only seemed to happen when the emitter was switching on\off. SO when I unplugged the emitter and plugged it back in, it installed the old usb driver instead and it fixed it.
So having ruled everything else out from display to card malfunction to forceware version, my verdict is that it lies in the emitter driver.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
Glad you found a fix. But my VG278H has an integrated emitter and is only connected via Dual-Link DVI. So your fix doesn't work for me.
[/quote]
Strange, I would send a bug report to Andrew and then point him to this thread. This seems to be a new problem that hasn't cropped up before so its definitely Nvidia's fault.
Glad you found a fix. But my VG278H has an integrated emitter and is only connected via Dual-Link DVI. So your fix doesn't work for me.
Strange, I would send a bug report to Andrew and then point him to this thread. This seems to be a new problem that hasn't cropped up before so its definitely Nvidia's fault.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision