Problem related with the emitter
Hello to everybody. I have a problem that seems that doesn't occur to other people, or at least to the majority. I wrote about it some months ago, but I have not solved it yet, and my question now is about a perfect clean of every trace of the Nvidia drivers, in order to make a perfect installation to prevent that the previous stuff is originating the problem. The problem itself is that, when I turn on the computer, the Nvidia emitter usually is totally off, with no light, and I need to unplug and plug the USB cord in order to make the emitter be recognized by the computer. Sometimes the emitter is on when I turn on the computer (I don't know why), but the Nvidia 3D Vision driver shows me "3D Vision Discover", and I have to change it for "Samsung LCD 3D 120 Hz" before to play. I can play in 3D, but it is very annoying. The answer I received some weeks ago to solve the problem was to use a shorter usb cord, or to change the usb port, but none of these solutions work. I have tried either with the usb cord included in the bundle and with a 20cm usb cord, and I have tried with 3 different USB ports on my computer (2.1 and 3.0 usb ports). The problem never did happen to me until the release of 3xx Nvidia drivers (I can't remember the version exactly) around 8 or 9 months ago, and it is present with all drivers since then. As I do not read this problem in this forum, I guess it is possible that it is a problem related to my driver traces, maybe colliding with previous drivers, or something like that. My setup: - Windows 7 64bits - Nvidia GTX 660 TI + 314.07 whql drivers - Asus P6X58D-E motherboard - Intel i7 930 CPU - Nvidia 3D Vision V2 - Samsung 2233RZ monitor
Hello to everybody. I have a problem that seems that doesn't occur to other people, or at least to the majority. I wrote about it some months ago, but I have not solved it yet, and my question now is about a perfect clean of every trace of the Nvidia drivers, in order to make a perfect installation to prevent that the previous stuff is originating the problem.

The problem itself is that, when I turn on the computer, the Nvidia emitter usually is totally off, with no light, and I need to unplug and plug the USB cord in order to make the emitter be recognized by the computer. Sometimes the emitter is on when I turn on the computer (I don't know why), but the Nvidia 3D Vision driver shows me "3D Vision Discover", and I have to change it for "Samsung LCD 3D 120 Hz" before to play. I can play in 3D, but it is very annoying.

The answer I received some weeks ago to solve the problem was to use a shorter usb cord, or to change the usb port, but none of these solutions work. I have tried either with the usb cord included in the bundle and with a 20cm usb cord, and I have tried with 3 different USB ports on my computer (2.1 and 3.0 usb ports).

The problem never did happen to me until the release of 3xx Nvidia drivers (I can't remember the version exactly) around 8 or 9 months ago, and it is present with all drivers since then. As I do not read this problem in this forum, I guess it is possible that it is a problem related to my driver traces, maybe colliding with previous drivers, or something like that.

My setup:
- Windows 7 64bits
- Nvidia GTX 660 TI + 314.07 whql drivers
- Asus P6X58D-E motherboard
- Intel i7 930 CPU
- Nvidia 3D Vision V2
- Samsung 2233RZ monitor

- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "MSI GTX 660 TI"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)

#1
Posted 03/16/2013 08:20 AM   
hmm, mines been doing the same. I attributed it to the USB hub I started using, perhaps it isn't. The "select when display is in 3D mode" being greyed out to me, is way more annoying.
hmm, mines been doing the same. I attributed it to the USB hub I started using, perhaps it isn't.

The "select when display is in 3D mode" being greyed out to me, is way more annoying.

#2
Posted 03/16/2013 08:37 AM   
[quote="D-Man11"]hmm, mines been doing the same. I attributed it to the USB hub I started using, perhaps it isn't. The "select when display is in 3D mode" being greyed out to me, is way more annoying.[/quote] I'm sure i have read somewhere else that hubs can cause problems with nvidia 3D. If your not using one, maybe a driver issue, maybe report it in driver section as well (as mods frequent it more often).
D-Man11 said:hmm, mines been doing the same. I attributed it to the USB hub I started using, perhaps it isn't.

The "select when display is in 3D mode" being greyed out to me, is way more annoying.


I'm sure i have read somewhere else that hubs can cause problems with nvidia 3D. If your not using one, maybe a driver issue, maybe report it in driver section as well (as mods frequent it more often).

OS: Win 8 CPU: I7 4770k 3.5GZ GPU: GTX 780ti

#3
Posted 03/16/2013 09:21 AM   
Not many people have them, as motherboards usually have plenty of USB ports, but maybe try using a PCI USB card/adapter? I'm not experiencing the problem so I can't really test it out, I know I have one kicking around somewhere.
Not many people have them, as motherboards usually have plenty of USB ports, but maybe try using a PCI USB card/adapter? I'm not experiencing the problem so I can't really test it out, I know I have one kicking around somewhere.
#4
Posted 03/17/2013 03:28 PM   
Interesting. I've been getting this error recently as well. I'll bet that driver changes made the timing different, and sometimes it loads incorrectly. It seems to be dependent upon timing. Maybe try altering your startup sequence to defer some apps to deliberately alter the timing at boot time. Maybe try making the NVidia Stereoscopic service for the emitter an Automatic Delayed start in the Services panel.
Interesting. I've been getting this error recently as well. I'll bet that driver changes made the timing different, and sometimes it loads incorrectly.


It seems to be dependent upon timing. Maybe try altering your startup sequence to defer some apps to deliberately alter the timing at boot time.

Maybe try making the NVidia Stereoscopic service for the emitter an Automatic Delayed start in the Services panel.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#5
Posted 03/18/2013 07:02 AM   
Scroll To Top