3D emitter turns off ?
  1 / 3    
Hi all ...

Well im having a wierd problem with my 3D emitter ...

It just turns itself off when i boot in to windows ?

I can only turn it on by taking the USB out and plug it in again, but then after 15 sec it shuts down again ? (no light or anything)

I reinstalled 3D drivers but no luck there and i changed USB port and still the same ?

I have never experienced this problem before ...

I installed the 270.28 drivers yesterday could that be the problem ?
Hi all ...



Well im having a wierd problem with my 3D emitter ...



It just turns itself off when i boot in to windows ?



I can only turn it on by taking the USB out and plug it in again, but then after 15 sec it shuts down again ? (no light or anything)



I reinstalled 3D drivers but no luck there and i changed USB port and still the same ?



I have never experienced this problem before ...



I installed the 270.28 drivers yesterday could that be the problem ?

#1
Posted 03/26/2011 04:42 PM   
Ok so i found out that the emitter turns off (no light in the Nvidia logo) when i install the 266.21 USB driver ?

When i remove the driver the emitter turns back on ?
Ok so i found out that the emitter turns off (no light in the Nvidia logo) when i install the 266.21 USB driver ?



When i remove the driver the emitter turns back on ?

#2
Posted 03/26/2011 09:28 PM   
You have mismatched emitter and display drivers.
You have mismatched emitter and display drivers.
#3
Posted 03/27/2011 12:11 AM   
[quote name='ERP' date='27 March 2011 - 02:11 AM' timestamp='1301184679' post='1213662']
You have mismatched emitter and display drivers.
[/quote]

The 3D vision "controller" driver for the infared 3D emitter is named 266.21 (I have used that driver since i got my 3D setup ?)

I havent mismatched the drivers, since the driver for the the 3D emitter is not named the same as the Nvidia Graphics driver called 270.28 ...

I think the 3D emitter has gone faulty ...

But it pretty wierd that when i uninstall the 266.21, the light in the Nvidia logo on the emitter turns back on ... ?
[quote name='ERP' date='27 March 2011 - 02:11 AM' timestamp='1301184679' post='1213662']

You have mismatched emitter and display drivers.





The 3D vision "controller" driver for the infared 3D emitter is named 266.21 (I have used that driver since i got my 3D setup ?)



I havent mismatched the drivers, since the driver for the the 3D emitter is not named the same as the Nvidia Graphics driver called 270.28 ...



I think the 3D emitter has gone faulty ...



But it pretty wierd that when i uninstall the 266.21, the light in the Nvidia logo on the emitter turns back on ... ?

#4
Posted 03/27/2011 12:10 PM   
Emitter drivers are updated less frequently than display drivers, but if the two are incompatible you get exactly what you describe.
266.21 works with any of the 26x.xx drivers as far as I've tried.
Since 270.xx aren't officially released even as betas there is a good chance that there is no working emitter driver for them.
Emitter drivers are updated less frequently than display drivers, but if the two are incompatible you get exactly what you describe.

266.21 works with any of the 26x.xx drivers as far as I've tried.

Since 270.xx aren't officially released even as betas there is a good chance that there is no working emitter driver for them.
#5
Posted 03/27/2011 03:56 PM   
[quote name='ERP' date='27 March 2011 - 05:56 PM' timestamp='1301241414' post='1213913']
Emitter drivers are updated less frequently than display drivers, but if the two are incompatible you get exactly what you describe.
266.21 works with any of the 26x.xx drivers as far as I've tried.
Since 270.xx aren't officially released even as betas there is a good chance that there is no working emitter driver for them.
[/quote]

Thanks ... :0)

That did it, now it works ...
[quote name='ERP' date='27 March 2011 - 05:56 PM' timestamp='1301241414' post='1213913']

Emitter drivers are updated less frequently than display drivers, but if the two are incompatible you get exactly what you describe.

266.21 works with any of the 26x.xx drivers as far as I've tried.

Since 270.xx aren't officially released even as betas there is a good chance that there is no working emitter driver for them.





Thanks ... :0)



That did it, now it works ...

#6
Posted 03/28/2011 04:18 PM   
Hi

We have noticed some incompatibility problems with the 266.21 3D Vision Controller (Emitter) driver and using different Release 265 drivers. So as a result of that we will post matching sets of 3D Vision drivers to all Release 265 drivers this week.

There will also be some additional changes with Release 270 with the packaging of the drivers which I will talk more about soon.
Hi



We have noticed some incompatibility problems with the 266.21 3D Vision Controller (Emitter) driver and using different Release 265 drivers. So as a result of that we will post matching sets of 3D Vision drivers to all Release 265 drivers this week.



There will also be some additional changes with Release 270 with the packaging of the drivers which I will talk more about soon.

#7
Posted 03/28/2011 04:37 PM   
Hello, I'm experiencing this problem too. Right today again!

Until a few days ago I had the same above problem happening, I already returned the full 3D vision kit to my retailer for replate, thinking it was broken. After formatting Windows 7 and reinstalling video drivers (285.62) I found it was working fine, then I reinstalled all my programs and games, including driver updates from Windows Update(!).

Now that I was going to play Duke in 3D I discovered that the emitter is turning off again in 15 secs.

I'm now reinstalling the video driver. I don't know if it's related to the NForce drivers (15.56) for my ASUS Crosshair 2 Formula motherboard, but if you have more information about this problem pleeeeeeeease save me another formatting round.

Thank you for any help. I found this topic on Google, better not opening new topics!
Hello, I'm experiencing this problem too. Right today again!



Until a few days ago I had the same above problem happening, I already returned the full 3D vision kit to my retailer for replate, thinking it was broken. After formatting Windows 7 and reinstalling video drivers (285.62) I found it was working fine, then I reinstalled all my programs and games, including driver updates from Windows Update(!).



Now that I was going to play Duke in 3D I discovered that the emitter is turning off again in 15 secs.



I'm now reinstalling the video driver. I don't know if it's related to the NForce drivers (15.56) for my ASUS Crosshair 2 Formula motherboard, but if you have more information about this problem pleeeeeeeease save me another formatting round.



Thank you for any help. I found this topic on Google, better not opening new topics!

#8
Posted 12/09/2011 10:28 PM   
Users have reported having problems when their emitter is plugged into a USB3 port, that corrected themselves when switched to a USB2 port. Post back if this resolves your issue.
Users have reported having problems when their emitter is plugged into a USB3 port, that corrected themselves when switched to a USB2 port. Post back if this resolves your issue.

#9
Posted 12/10/2011 12:50 AM   
My ports are 2.0 only. I also use an external powered hub. Tried all ports (hub, front-case, back-case), but didn't solve.
My ports are 2.0 only. I also use an external powered hub. Tried all ports (hub, front-case, back-case), but didn't solve.

#10
Posted 12/10/2011 07:02 PM   
Hmm, I haven't heard of anyone having such a problem. Make sure your motherboard bios is up to date as well as the Northbridge and Southbridge chip drivers. Be sure to update the bridge drivers from AMD not Asus.

GL, hope this helps.
Hmm, I haven't heard of anyone having such a problem. Make sure your motherboard bios is up to date as well as the Northbridge and Southbridge chip drivers. Be sure to update the bridge drivers from AMD not Asus.



GL, hope this helps.

#11
Posted 12/10/2011 07:35 PM   
[quote name='D-Man11' date='10 December 2011 - 09:35 PM' timestamp='1323545713' post='1340460']
Be sure to update the bridge drivers from AMD not Asus.
[/quote]

What drivers should I download from them? I installed drivers from NVidia for MCP 780a, aren't they enough/better. Can I try the "All 7-series" chipset driver that lead to http://support.amd.com/it/gpudownload/windows/Pages/raid_windows.aspx ?
[quote name='D-Man11' date='10 December 2011 - 09:35 PM' timestamp='1323545713' post='1340460']

Be sure to update the bridge drivers from AMD not Asus.





What drivers should I download from them? I installed drivers from NVidia for MCP 780a, aren't they enough/better. Can I try the "All 7-series" chipset driver that lead to http://support.amd.com/it/gpudownload/windows/Pages/raid_windows.aspx ?

#12
Posted 12/10/2011 07:50 PM   
lol, I saw Asus Crosshair and automatically thought of the newer boards with the 990 or 890 chipset from AMD.

Disregard the mention of AMD.

But what I was trying to point out that the manufacturer often times does not have the most recent drivers available.

You did the right thing, and updated the 780a at Nvidia and not Asus.

Sorry for the confusion.

GL, these are the only things I can think of.
(update all drivers/do not use USB3)
lol, I saw Asus Crosshair and automatically thought of the newer boards with the 990 or 890 chipset from AMD.



Disregard the mention of AMD.



But what I was trying to point out that the manufacturer often times does not have the most recent drivers available.



You did the right thing, and updated the 780a at Nvidia and not Asus.



Sorry for the confusion.



GL, these are the only things I can think of.

(update all drivers/do not use USB3)

#13
Posted 12/10/2011 08:26 PM   
I believe I found the guilt:


[size="6"]USB OVER NETWORK - SERVER[/size], or maybe the client

I installed the server, then, right when the client part began its installation, the emitter turned off.
The client does install a customized USB driver (3DV was already off when Windows asked me for driver confirmation).

Can I just say [b]DAMN[/b]??

It took me months to find out
I believe I found the guilt:





USB OVER NETWORK - SERVER, or maybe the client



I installed the server, then, right when the client part began its installation, the emitter turned off.

The client does install a customized USB driver (3DV was already off when Windows asked me for driver confirmation).



Can I just say DAMN??



It took me months to find out

#14
Posted 12/10/2011 08:56 PM   
I know, this is an old threat, but it's the first one that popped up on google, so I thought I'd leave my solution here. I've had the exact same problem of the emitter turning off shortly after boot or wakeup from standby. Only replugging the device would make it operational again. This was with the currently latest drivers v335.23. I found the culprit to have been Oracle VirtualBox. Since I've uninstalled it, the emitter hasn't turned off once. I presume the issue lies with the USB mirror drivers for VB, so a VB installation without those should be fine. I didn't verify this though, as I didn't use it anymore anyways. Hope these lines save someone some time banging his/her head against the wall. :) Regards, zy.
I know, this is an old threat, but it's the first one that popped up on google, so I thought I'd leave my solution here.

I've had the exact same problem of the emitter turning off shortly after boot or wakeup from standby.
Only replugging the device would make it operational again. This was with the currently latest drivers v335.23.

I found the culprit to have been Oracle VirtualBox. Since I've uninstalled it, the emitter hasn't turned off once.
I presume the issue lies with the USB mirror drivers for VB, so a VB installation without those should be fine. I didn't verify this though, as I didn't use it anymore anyways.

Hope these lines save someone some time banging his/her head against the wall. :)

Regards,
zy.

#15
Posted 04/25/2014 03:01 PM   
  1 / 3    
Scroll To Top