Well disappointing news from my side also, after a couple of shutdowns boot-up, the emitter is now doing like Graymatter's is, it turns itself off. Tried running both the USB hub scripts and back to the original uninstall/ re-install emitter ( driver install) and it still shutdown after a couple of seconds.
It works almost like a bad virus lol, just when you think you got it comes back :-(
I still have not heard anything back from Nvidia, I guess it is time to send them the link to this post again.
Well disappointing news from my side also, after a couple of shutdowns boot-up, the emitter is now doing like Graymatter's is, it turns itself off. Tried running both the USB hub scripts and back to the original uninstall/ re-install emitter ( driver install) and it still shutdown after a couple of seconds.
It works almost like a bad virus lol, just when you think you got it comes back :-(
I still have not heard anything back from Nvidia, I guess it is time to send them the link to this post again.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
I'm really at a loss here, these software 'fixes' should work, they do on a system that doesn't have the problem. The thing I don't get is why they work a few times and then stop. I think that's what bugs me the most.
This ...
[quote="GrayMatter"]I'd like to throw out my $0.02. Throughout this process the one thing that has [i]always[/i] worked up to now is unplugging and replugging the emitter into the same USB slot prior to turning on the computer. [u]When I do this the emitter comes up fully functional and configured the same as when I last left it and there is no reinstallation of the Stereoscopic driver.[/u][/quote]
... has me wondering if removing at/before shutdown, might work.
Try this , make a bat with the following, make sure [u]devcon[/u]'s set to run as admin (and not the bat) and run this right before you shutdown, while the emitter's working properly.
[code]cd amd64
devcon.exe remove "USB\VID_0955&PID_0007"[/code]
[quote="GrayMatter"]When next I can tear myself away from Necromorph dismemberment :) I will try your suggested work around.[/quote] I missed this earlier, great game. :D ... well 1 & 2 anyway, haven't bought 3 yet.
I'm really at a loss here, these software 'fixes' should work, they do on a system that doesn't have the problem. The thing I don't get is why they work a few times and then stop. I think that's what bugs me the most.
This ...
GrayMatter said:I'd like to throw out my $0.02. Throughout this process the one thing that has always worked up to now is unplugging and replugging the emitter into the same USB slot prior to turning on the computer. When I do this the emitter comes up fully functional and configured the same as when I last left it and there is no reinstallation of the Stereoscopic driver.
... has me wondering if removing at/before shutdown, might work.
Try this , make a bat with the following, make sure devcon's set to run as admin (and not the bat) and run this right before you shutdown, while the emitter's working properly.
cd amd64
devcon.exe remove "USB\VID_0955&PID_0007"
GrayMatter said:When next I can tear myself away from Necromorph dismemberment :) I will try your suggested work around.
I missed this earlier, great game. :D ... well 1 & 2 anyway, haven't bought 3 yet.
Hi Tsaebeht,
Just finished replaying DS1 & 2 in 3D thanks to Helix and have just started a second go thru of Dead Space 3. The great thing about 3D is my old stuff is new again and I'm having a blast ... except for the flaky hardware issue.
I'll try the "devcon.exe remove ..." next.
As an aside, as Spacemoss suggested I too thought it might be a timing issue ... so I set devcon.exe to execute as admin and ran "devcon.exe restart ..." after bootup failed, but had the same result, i.e. it came on initially then a second or two later shuts down.
The emitter really seems to be messing with us.
Just finished replaying DS1 & 2 in 3D thanks to Helix and have just started a second go thru of Dead Space 3. The great thing about 3D is my old stuff is new again and I'm having a blast ... except for the flaky hardware issue.
I'll try the "devcon.exe remove ..." next.
As an aside, as Spacemoss suggested I too thought it might be a timing issue ... so I set devcon.exe to execute as admin and ran "devcon.exe restart ..." after bootup failed, but had the same result, i.e. it came on initially then a second or two later shuts down.
The emitter really seems to be messing with us.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Hi Guys,
Wish I could provide you with a solutioon to fit all these problems cases with the emitter. What I can say is that my fix for my system stills works fine, numerous reboots and shutdowns and I still have full functionality of my emitter without having to constantly remove the USB cable and reconnnect. As you have all explained within this forum there is more than one way to skin a cat and the reinitialisation of the emitter whilst in windows (script or otherwise) is one option. I chose to look at this problem from a different perspective as my gut feeling is that we have a "Power management" or inherent (something unintensionally built into the system that should'nt be their) problem with the emitter. I'm sorry that some of you were unable to find the solution to this problem - I shall be replying to Nvidia with a link to this forum, identifying my solution for my system only and that perhaps that should be looking at aforementioned suggestions. Best of luck Gents.
Wish I could provide you with a solutioon to fit all these problems cases with the emitter. What I can say is that my fix for my system stills works fine, numerous reboots and shutdowns and I still have full functionality of my emitter without having to constantly remove the USB cable and reconnnect. As you have all explained within this forum there is more than one way to skin a cat and the reinitialisation of the emitter whilst in windows (script or otherwise) is one option. I chose to look at this problem from a different perspective as my gut feeling is that we have a "Power management" or inherent (something unintensionally built into the system that should'nt be their) problem with the emitter. I'm sorry that some of you were unable to find the solution to this problem - I shall be replying to Nvidia with a link to this forum, identifying my solution for my system only and that perhaps that should be looking at aforementioned suggestions. Best of luck Gents.
Hi TsaebehT,
Well I tried "devcon.exe remove", and please note that I just edited the previous reset3d.bat so the HardwareId was not in anyway changed. When executed before shutdown some messages went by that I didn't catch but upon power up I got...
Device Software Installation
USB Root Hub
Generic USB HUB
Merc Stealth USB Human Interface Device
NVIDIA Stereoscopic 3D USB controller
USB Composite Device
Ideazon Merc Stealth MM USB Human Interface Device
or in other words everything USB reinstalled and like so many times before the emitter came on and then went off.
Following your logic I tried the following:
cd amd64
devcon.exe disable "USB\ROOT_HUB20&VID8086&PID3A3A"
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
&
cd amd64
devcon.exe disable "USB\ROOT_HUB20&VID8086&PID3A3A"
devcon.exe enable "USB\ROOT_HUB20&VID8086&PID3A3A"
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
All of which started the emitter but after a few seconds the emitter turned off.
But... I did notice something that had escaped me before.
When I physically unplug and replug the emitter Windows gives an audible confirmation of what I'm doing
Unplug = DeeDah (two sounds with pitch falling)
PlugIn = DahDee (pitch rising)
It has been a while with a lot of water under the bridge but I am as certain as I can be under the circumstances that the first time I used..
cd amd64
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
I heard the above sequence ... pitch falling ... pitch rising ... [u]and it worked[/u].
In all subsequent runnings as well as the above restart,remove, disable, enable etc.
I am hearing ... pitch falling ... pitch falling ... and it no longer works.
As I write this it all seems pretty trivial but it isn't my imagination and there is so little to go on I'm putting it out there just in case this might trigger a thought.
Well I tried "devcon.exe remove", and please note that I just edited the previous reset3d.bat so the HardwareId was not in anyway changed. When executed before shutdown some messages went by that I didn't catch but upon power up I got...
Device Software Installation
USB Root Hub
Generic USB HUB
Merc Stealth USB Human Interface Device
NVIDIA Stereoscopic 3D USB controller
USB Composite Device
Ideazon Merc Stealth MM USB Human Interface Device
or in other words everything USB reinstalled and like so many times before the emitter came on and then went off.
Following your logic I tried the following:
cd amd64
devcon.exe disable "USB\ROOT_HUB20&VID8086&PID3A3A"
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
It has been a while with a lot of water under the bridge but I am as certain as I can be under the circumstances that the first time I used..
cd amd64
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
I heard the above sequence ... pitch falling ... pitch rising ... and it worked.
In all subsequent runnings as well as the above restart,remove, disable, enable etc.
I am hearing ... pitch falling ... pitch falling ... and it no longer works.
As I write this it all seems pretty trivial but it isn't my imagination and there is so little to go on I'm putting it out there just in case this might trigger a thought.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Yeah this was just for the emitter ... you did the hub I think.
[code]cd amd64
devcon.exe remove "USB\VID_0955&PID_0007"[/code]
disable - does just that it only disables the device, it doesn't disconnect it it just doesn't allow it to be used.
I know what you're saying about the sounds, there's the good/positive one and the bad/negative one. If you right-click on your volume icon and then select sounds you'll see them listed in the program events section as, Device Connect, Device Disconnect, and Device Falied to Connect. You can select them and preview them.
When something's restarted you should hear, Device Disconnect and then Device Connect. Are you getting two Device Disconnect sounds or Disconnect and then Failed to Connect? Anything showing up in the device manager when it's blacked out/not working? Is it showing up? Any errors? When you're doing the remove and then rescan you can usually catch the message that pops up on the taskbar and get more details when it's installing, or trying to.
Yeah this was just for the emitter ... you did the hub I think.
cd amd64
devcon.exe remove "USB\VID_0955&PID_0007"
disable - does just that it only disables the device, it doesn't disconnect it it just doesn't allow it to be used.
I know what you're saying about the sounds, there's the good/positive one and the bad/negative one. If you right-click on your volume icon and then select sounds you'll see them listed in the program events section as, Device Connect, Device Disconnect, and Device Falied to Connect. You can select them and preview them.
When something's restarted you should hear, Device Disconnect and then Device Connect. Are you getting two Device Disconnect sounds or Disconnect and then Failed to Connect? Anything showing up in the device manager when it's blacked out/not working? Is it showing up? Any errors? When you're doing the remove and then rescan you can usually catch the message that pops up on the taskbar and get more details when it's installing, or trying to.
After a few more restarts, I've noticed that it's settled into a pattern that was slightly different than in my first post. That is, I don't actually have to run the wizard each time, rather only if I reinstall NVidia driver package. I'm not using the script at the moment. All I do is 1) Start computer - Light comes on. 2) I Login -light stays on a few seconds then goes off. 3) I unplug and re-plug emitter - I hear windows beep, but don't actually see the new hardware found popup, the light then turns green and the emitter is ready to go.
So, I'm wondering what happens by Logging in that specifically starts the "turn off" prompt. Even though you couldn't use it not logged in, I'm thinking it may actually be fine all through boot up until that point.
After a few more restarts, I've noticed that it's settled into a pattern that was slightly different than in my first post. That is, I don't actually have to run the wizard each time, rather only if I reinstall NVidia driver package. I'm not using the script at the moment. All I do is 1) Start computer - Light comes on. 2) I Login -light stays on a few seconds then goes off. 3) I unplug and re-plug emitter - I hear windows beep, but don't actually see the new hardware found popup, the light then turns green and the emitter is ready to go.
So, I'm wondering what happens by Logging in that specifically starts the "turn off" prompt. Even though you couldn't use it not logged in, I'm thinking it may actually be fine all through boot up until that point.
Have you tried logging in as another user or perhaps in safe mode? Just to see if that's any different.
Does anything shut the light off during normal use?
Maybe even try logging off to see if it goes back on.
Tsaebeht,
The sounds I'm hearing are "device connect" and "device disconnect". Until I previewed it I had never heard the "device failed to connect" sound.
The sounds I'm describing above are a pair of "device disconnect" sounds when I should be hearing "device disconnect" followed by "device connect".
The sounds I'm hearing are "device connect" and "device disconnect". Until I previewed it I had never heard the "device failed to connect" sound.
The sounds I'm describing above are a pair of "device disconnect" sounds when I should be hearing "device disconnect" followed by "device connect".
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Ok, now this is bizarre.
With the emitter dark i.e. not working I went to the Device Manager and under
"Univeral Serial Bus controllers"
I selected "NVIDIA Stereoscopic 3D USB controller" ... Properties
"Device status: This device is working properly"
selected Driver Tab everything looks normal
selected Details Tab
and bingo the emitter comes on ... I've done it a bunch of times and it works every time
:( ... but it goes off in a couple of seconds
And if I check the Nvidia control panel while the emitter is on all I see is "3D Vision Discover"
Anyway, to answer your question Tsaebeht, while the emitter is not working nothing looks amiss in the Device Manager Tree.
With the emitter dark i.e. not working I went to the Device Manager and under
"Univeral Serial Bus controllers"
I selected "NVIDIA Stereoscopic 3D USB controller" ... Properties
"Device status: This device is working properly"
selected Driver Tab everything looks normal
selected Details Tab
and bingo the emitter comes on ... I've done it a bunch of times and it works every time
:( ... but it goes off in a couple of seconds
And if I check the Nvidia control panel while the emitter is on all I see is "3D Vision Discover"
Anyway, to answer your question Tsaebeht, while the emitter is not working nothing looks amiss in the Device Manager Tree.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Tsaebeht,
When I go to the device manager and look at the USB Root Hub that has the Stereoscopic 3D controller on it and click ... Properties ... Details ... Hardware Ids, there are three entries:
USB\ROOT_HUB20&VID8086&PID3A3A&REV0000
USB\ROOT_HUB20&VID8086&PID3A3A
USB\ROOT_HUB20
I've been using the second one and although I haven't got the results I desired at least it does do something.
If I use:
USB\VID8086&PID3A3A
which I think is what your are suggesting, well.... nothing happens. I've tried various versions of the batch files that have been suggested, but in every case nada.
Out of curiousity and grasping at anything and everything...
the power tab says the 3D contoller requires 400 mA. Is that what yours reports?
When I go to the device manager and look at the USB Root Hub that has the Stereoscopic 3D controller on it and click ... Properties ... Details ... Hardware Ids, there are three entries:
I've been using the second one and although I haven't got the results I desired at least it does do something.
If I use:
USB\VID8086&PID3A3A
which I think is what your are suggesting, well.... nothing happens. I've tried various versions of the batch files that have been suggested, but in every case nada.
Out of curiousity and grasping at anything and everything...
the power tab says the 3D contoller requires 400 mA. Is that what yours reports?
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
The one I referenced above "USB\VID_0955&PID_0007" is just the emitter itself, not the hub.
You had it right as far as the hub's concerned using the second, could try using the first as well, can't hurt but I doubt it'll change anything. "USB\ROOT_HUB20&VID8086&PID3A3A&REV0000"
Yeah it says that right on the bottom of the emitter also, Model: P854 5V 400mA (I have a pic of it on my phone. Lol) ... besides the serial number I can't see anything that 'marks' it as different from others, like a date code or lot number.
Still really curious about logging off, other users, and safe mode.
Have you done a full clean driver install?
The one I referenced above "USB\VID_0955&PID_0007" is just the emitter itself, not the hub.
You had it right as far as the hub's concerned using the second, could try using the first as well, can't hurt but I doubt it'll change anything. "USB\ROOT_HUB20&VID8086&PID3A3A&REV0000"
Yeah it says that right on the bottom of the emitter also, Model: P854 5V 400mA (I have a pic of it on my phone. Lol) ... besides the serial number I can't see anything that 'marks' it as different from others, like a date code or lot number.
Still really curious about logging off, other users, and safe mode.
Tsaebeht,
When the problems first ocurred I called Nvidia and they had me do a DriveSweep ... Clean install ... attempted various Nvidia driver versions (all done as clean installs) ... tried 3 different usb cables ... and tried every usb connector on the machine ... also tried removing the various other usb devices connected to the machine. A lot of time going around in circles. I hope Nvidia is putting as much thought and energy into this problem as you are. Even though it is still a work in progress, succeed or fail, I can't thank you enough for giving your time to this.
When the problems first ocurred I called Nvidia and they had me do a DriveSweep ... Clean install ... attempted various Nvidia driver versions (all done as clean installs) ... tried 3 different usb cables ... and tried every usb connector on the machine ... also tried removing the various other usb devices connected to the machine. A lot of time going around in circles. I hope Nvidia is putting as much thought and energy into this problem as you are. Even though it is still a work in progress, succeed or fail, I can't thank you enough for giving your time to this.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Hi Guys, well I have been out for a bit and just saw your posts.
Graymatter I have tried same as you with exactly the same results. I tried the disconnect emitter directly from PC prior to boot and re-plug after shutdown of power turn back on as suggested by another poster and that works for a couple of times then goes back turning itself off.
I have resent a link to this post to Nvidia and have not heard anything yet (not surprised)
If it was not for your help in all this TsaebeT I think I would be loosing it with the Nvidia support team, the only consolation is that we know it is not one of isolated problems and others are having the same problem. Hopefully thanks to your input Nvidia support might get an insight and not ask us to go through the standard troubleshooting steps before pushing this to higher level. I am still waiting to hear from a tier 2 support tech.
Once I do I will post the info here.
Again thank you all for supporting this post with detailed info.
Hi Guys, well I have been out for a bit and just saw your posts.
Graymatter I have tried same as you with exactly the same results. I tried the disconnect emitter directly from PC prior to boot and re-plug after shutdown of power turn back on as suggested by another poster and that works for a couple of times then goes back turning itself off.
I have resent a link to this post to Nvidia and have not heard anything yet (not surprised)
If it was not for your help in all this TsaebeT I think I would be loosing it with the Nvidia support team, the only consolation is that we know it is not one of isolated problems and others are having the same problem. Hopefully thanks to your input Nvidia support might get an insight and not ask us to go through the standard troubleshooting steps before pushing this to higher level. I am still waiting to hear from a tier 2 support tech.
Once I do I will post the info here.
Again thank you all for supporting this post with detailed info.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
It works almost like a bad virus lol, just when you think you got it comes back :-(
I still have not heard anything back from Nvidia, I guess it is time to send them the link to this post again.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
This ...
... has me wondering if removing at/before shutdown, might work.
Try this , make a bat with the following, make sure devcon's set to run as admin (and not the bat) and run this right before you shutdown, while the emitter's working properly.
I missed this earlier, great game. :D ... well 1 & 2 anyway, haven't bought 3 yet.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Just finished replaying DS1 & 2 in 3D thanks to Helix and have just started a second go thru of Dead Space 3. The great thing about 3D is my old stuff is new again and I'm having a blast ... except for the flaky hardware issue.
I'll try the "devcon.exe remove ..." next.
As an aside, as Spacemoss suggested I too thought it might be a timing issue ... so I set devcon.exe to execute as admin and ran "devcon.exe restart ..." after bootup failed, but had the same result, i.e. it came on initially then a second or two later shuts down.
The emitter really seems to be messing with us.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Wish I could provide you with a solutioon to fit all these problems cases with the emitter. What I can say is that my fix for my system stills works fine, numerous reboots and shutdowns and I still have full functionality of my emitter without having to constantly remove the USB cable and reconnnect. As you have all explained within this forum there is more than one way to skin a cat and the reinitialisation of the emitter whilst in windows (script or otherwise) is one option. I chose to look at this problem from a different perspective as my gut feeling is that we have a "Power management" or inherent (something unintensionally built into the system that should'nt be their) problem with the emitter. I'm sorry that some of you were unable to find the solution to this problem - I shall be replying to Nvidia with a link to this forum, identifying my solution for my system only and that perhaps that should be looking at aforementioned suggestions. Best of luck Gents.
Well I tried "devcon.exe remove", and please note that I just edited the previous reset3d.bat so the HardwareId was not in anyway changed. When executed before shutdown some messages went by that I didn't catch but upon power up I got...
Device Software Installation
USB Root Hub
Generic USB HUB
Merc Stealth USB Human Interface Device
NVIDIA Stereoscopic 3D USB controller
USB Composite Device
Ideazon Merc Stealth MM USB Human Interface Device
or in other words everything USB reinstalled and like so many times before the emitter came on and then went off.
Following your logic I tried the following:
cd amd64
devcon.exe disable "USB\ROOT_HUB20&VID8086&PID3A3A"
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
&
cd amd64
devcon.exe disable "USB\ROOT_HUB20&VID8086&PID3A3A"
devcon.exe enable "USB\ROOT_HUB20&VID8086&PID3A3A"
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
All of which started the emitter but after a few seconds the emitter turned off.
But... I did notice something that had escaped me before.
When I physically unplug and replug the emitter Windows gives an audible confirmation of what I'm doing
Unplug = DeeDah (two sounds with pitch falling)
PlugIn = DahDee (pitch rising)
It has been a while with a lot of water under the bridge but I am as certain as I can be under the circumstances that the first time I used..
cd amd64
devcon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"
I heard the above sequence ... pitch falling ... pitch rising ... and it worked.
In all subsequent runnings as well as the above restart,remove, disable, enable etc.
I am hearing ... pitch falling ... pitch falling ... and it no longer works.
As I write this it all seems pretty trivial but it isn't my imagination and there is so little to go on I'm putting it out there just in case this might trigger a thought.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
disable - does just that it only disables the device, it doesn't disconnect it it just doesn't allow it to be used.
I know what you're saying about the sounds, there's the good/positive one and the bad/negative one. If you right-click on your volume icon and then select sounds you'll see them listed in the program events section as, Device Connect, Device Disconnect, and Device Falied to Connect. You can select them and preview them.
When something's restarted you should hear, Device Disconnect and then Device Connect. Are you getting two Device Disconnect sounds or Disconnect and then Failed to Connect? Anything showing up in the device manager when it's blacked out/not working? Is it showing up? Any errors? When you're doing the remove and then rescan you can usually catch the message that pops up on the taskbar and get more details when it's installing, or trying to.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
So, I'm wondering what happens by Logging in that specifically starts the "turn off" prompt. Even though you couldn't use it not logged in, I'm thinking it may actually be fine all through boot up until that point.
Does anything shut the light off during normal use?
Maybe even try logging off to see if it goes back on.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
The sounds I'm hearing are "device connect" and "device disconnect". Until I previewed it I had never heard the "device failed to connect" sound.
The sounds I'm describing above are a pair of "device disconnect" sounds when I should be hearing "device disconnect" followed by "device connect".
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
With the emitter dark i.e. not working I went to the Device Manager and under
"Univeral Serial Bus controllers"
I selected "NVIDIA Stereoscopic 3D USB controller" ... Properties
"Device status: This device is working properly"
selected Driver Tab everything looks normal
selected Details Tab
and bingo the emitter comes on ... I've done it a bunch of times and it works every time
:( ... but it goes off in a couple of seconds
And if I check the Nvidia control panel while the emitter is on all I see is "3D Vision Discover"
Anyway, to answer your question Tsaebeht, while the emitter is not working nothing looks amiss in the Device Manager Tree.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
When I go to the device manager and look at the USB Root Hub that has the Stereoscopic 3D controller on it and click ... Properties ... Details ... Hardware Ids, there are three entries:
USB\ROOT_HUB20&VID8086&PID3A3A&REV0000
USB\ROOT_HUB20&VID8086&PID3A3A
USB\ROOT_HUB20
I've been using the second one and although I haven't got the results I desired at least it does do something.
If I use:
USB\VID8086&PID3A3A
which I think is what your are suggesting, well.... nothing happens. I've tried various versions of the batch files that have been suggested, but in every case nada.
Out of curiousity and grasping at anything and everything...
the power tab says the 3D contoller requires 400 mA. Is that what yours reports?
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
You had it right as far as the hub's concerned using the second, could try using the first as well, can't hurt but I doubt it'll change anything. "USB\ROOT_HUB20&VID8086&PID3A3A&REV0000"
Yeah it says that right on the bottom of the emitter also, Model: P854 5V 400mA (I have a pic of it on my phone. Lol) ... besides the serial number I can't see anything that 'marks' it as different from others, like a date code or lot number.
Still really curious about logging off, other users, and safe mode.
Have you done a full clean driver install?
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
When the problems first ocurred I called Nvidia and they had me do a DriveSweep ... Clean install ... attempted various Nvidia driver versions (all done as clean installs) ... tried 3 different usb cables ... and tried every usb connector on the machine ... also tried removing the various other usb devices connected to the machine. A lot of time going around in circles. I hope Nvidia is putting as much thought and energy into this problem as you are. Even though it is still a work in progress, succeed or fail, I can't thank you enough for giving your time to this.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Graymatter I have tried same as you with exactly the same results. I tried the disconnect emitter directly from PC prior to boot and re-plug after shutdown of power turn back on as suggested by another poster and that works for a couple of times then goes back turning itself off.
I have resent a link to this post to Nvidia and have not heard anything yet (not surprised)
If it was not for your help in all this TsaebeT I think I would be loosing it with the Nvidia support team, the only consolation is that we know it is not one of isolated problems and others are having the same problem. Hopefully thanks to your input Nvidia support might get an insight and not ask us to go through the standard troubleshooting steps before pushing this to higher level. I am still waiting to hear from a tier 2 support tech.
Once I do I will post the info here.
Again thank you all for supporting this post with detailed info.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.