Emitter disconneting on computer boot
  6 / 15    
ok I followed the above suggestions and disappointingly I get the same results, the emitter close back down a bit after the driver installs. Tried all the versions of .bat and no luck
ok I followed the above suggestions and disappointingly I get the same results, the emitter close back down a bit after the driver installs. Tried all the versions of .bat and no luck

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.

#76
Posted 04/28/2013 05:44 PM   
I tried the batch file mods as well, without luck.
I tried the batch file mods as well, without luck.

ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit

#77
Posted 04/28/2013 06:57 PM   
Ok I pulled my emitter out from behind my PC, you know I've never actually seen the thing since I bought it and enabled 3D. Lol. I just use it to enable 3D Vision, DLP-Link. When my PC boots up it flashes white once, then flashes red on and off, goes black for awhile (Windows logo), flashes red on and off a bit more and then goes green and then stays green. Then if I shutdown it goes black, if I restart it goes black and then green the whole time it's booting back up, unlike the initial boot where it flashes and it's black. Then I tried all of these scripts and then some on it and it never once went black, it only went black when I decided to try to 'uninstall' the USB Hub it was under in the Device Manager. The only thing I've come up with that makes my emitter go black, for a second or two, and then back to steady green is restarting the USB hub it's on. The problem is I'm pretty sure it's a different id for other people. I'm pretty sure the following script will restart all USB 2.0 Hubs and devices on them, this is the only thing that makes my emitter go black and then back to green. [quote]cd amd64 devcon.exe restart "USB\ROOT_HUB20"[/quote] If you try this directly from a bat remember DevCon has to be run with admin privileges you'll have to right-click on devcon.exe, select the compatibility tab and check the run this program as an admin box for it to work that way. Otherwise try it from the Task Scheduler. To find the exact id of the USB Hub it's connected to goto Device Manager and click and select Devices by connection. Then start clicking the triangles > to open the views until you find the HUB the emitter is connected to. Here's what mine looked like. [img]http://imageshack.us/a/img259/8548/20130429081856.png[/img] You can copy that id and paste it into the script above. In my case it would look like: [quote]cd amd64 devcon.exe restart "USB\VID_8087&PID_0024"[/quote] This restarts the hub and everything on it, in my case the emitter and my wireless keyboard. Hopefully if it's the HUB, which the emitter going black seems to imply, then this will work.
Ok I pulled my emitter out from behind my PC, you know I've never actually seen the thing since I bought it and enabled 3D. Lol. I just use it to enable 3D Vision, DLP-Link. When my PC boots up it flashes white once, then flashes red on and off, goes black for awhile (Windows logo), flashes red on and off a bit more and then goes green and then stays green. Then if I shutdown it goes black, if I restart it goes black and then green the whole time it's booting back up, unlike the initial boot where it flashes and it's black.

Then I tried all of these scripts and then some on it and it never once went black, it only went black when I decided to try to 'uninstall' the USB Hub it was under in the Device Manager.

The only thing I've come up with that makes my emitter go black, for a second or two, and then back to steady green is restarting the USB hub it's on. The problem is I'm pretty sure it's a different id for other people. I'm pretty sure the following script will restart all USB 2.0 Hubs and devices on them, this is the only thing that makes my emitter go black and then back to green.

cd amd64
devcon.exe restart "USB\ROOT_HUB20"


If you try this directly from a bat remember DevCon has to be run with admin privileges you'll have to right-click on devcon.exe, select the compatibility tab and check the run this program as an admin box for it to work that way. Otherwise try it from the Task Scheduler.

To find the exact id of the USB Hub it's connected to goto Device Manager and click and select Devices by connection. Then start clicking the triangles > to open the views until you find the HUB the emitter is connected to. Here's what mine looked like.

Image

You can copy that id and paste it into the script above. In my case it would look like:

cd amd64
devcon.exe restart "USB\VID_8087&PID_0024"


This restarts the hub and everything on it, in my case the emitter and my wireless keyboard. Hopefully if it's the HUB, which the emitter going black seems to imply, then this will work.
#78
Posted 04/29/2013 04:27 AM   
Hi TsaebehT, i am not on a hub, i have disconnected it from a hub at the start of the post since i beleived that was the culprit, i have it connectede to the back of my PC and even moved it from USB 3 to a USB 2, i have copied and pasted the ID's that we found based on your instructions, so now i am wondering if we are trying to hard to find reason behind your script not working or working sporadically. If others reading this post can comment if it works for them? I know GrayMatter and myself are on the same page and codes are same so notrmal we are both experiencing the emitter not staying on. Food for tought: \Graymatter are you using the Asus graphic tweaker? i am so maybe we have that also in common? Let me know, i might disactivate the boot up at windows log on option and see ( might have done this before, but i am done so many work arounds i cant remeber which i have done in past)
Hi TsaebehT, i am not on a hub, i have disconnected it from a hub at the start of the post since i beleived that was the culprit, i have it connectede to the back of my PC and even moved it from USB 3 to a USB 2, i have copied and pasted the ID's that we found based on your instructions, so now i am wondering if we are trying to hard to find reason behind your script not working or working sporadically. If others reading this post can comment if it works for them?
I know GrayMatter and myself are on the same page and codes are same so notrmal we are both experiencing the emitter not staying on.

Food for tought:
\Graymatter are you using the Asus graphic tweaker? i am so maybe we have that also in common?

Let me know,
i might disactivate the boot up at windows log on option and see ( might have done this before, but i am done so many work arounds i cant remeber which i have done in past)

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.

#79
Posted 04/29/2013 03:14 PM   
They are [i]internal[/i] HUBS not [i]external[/i] HUBS, they're on the motherboard. I'm not grasping at straws here, all your USB devices are connected to HUBS. It works 100% of the time for me, even though I don't need it it's still enabled at log on and still works everytime. The only time my emitter goes black after it's green is when I shutdown/restart windows, or 'restart' the USB HUB using DevCon, like I outlined above.
They are internal HUBS not external HUBS, they're on the motherboard. I'm not grasping at straws here, all your USB devices are connected to HUBS.

It works 100% of the time for me, even though I don't need it it's still enabled at log on and still works everytime.

The only time my emitter goes black after it's green is when I shutdown/restart windows, or 'restart' the USB HUB using DevCon, like I outlined above.
#80
Posted 04/29/2013 04:33 PM   
Ahhh the insanity of it all... Good Morning Tsaebeht, Your tenacity is amazing! Well I followed your instructions, rebooted and the emitter worked like a charm ... but, the reset3D.bat I created looked like this.. cd amd64 [u]devon[/u].exe restart "USB\ROOT_HUB20&VID8086&PID3A3A" Oops! So I fixed the spelling and rebooted. This time during logon I got the windows sound I hear when unplugging and replugging the emitter ... and it worked! (far too many excalmation points I know but I'm feeling exclamated :) Anyway, as you say the motherboard has it's own hubs and for now it's looking good. The fact that I'm getting the auditory feedback of unplugging and replugging [u][i]and[/i][/u] no resinstallation of the stereoscopic 3D driver has me optimistic ... again. I'll report back after awhile whether this keeps working. Thanks TsaebehT. and Gladjag, I am not using the Asus graphic tweaker,but I think this is worth a try ... good luck.
Ahhh the insanity of it all...

Good Morning Tsaebeht,

Your tenacity is amazing!

Well I followed your instructions, rebooted and the emitter worked like a charm ... but,

the reset3D.bat I created looked like this..

cd amd64
devon.exe restart "USB\ROOT_HUB20&VID8086&PID3A3A"

Oops!

So I fixed the spelling and rebooted.

This time during logon I got the windows sound I hear when unplugging and replugging the emitter ... and it worked! (far too many excalmation points I know but I'm feeling exclamated :)

Anyway, as you say the motherboard has it's own hubs and for now it's looking good. The fact that I'm getting the auditory feedback of unplugging and replugging and no resinstallation of the stereoscopic 3D driver has me optimistic ... again.

I'll report back after awhile whether this keeps working.

Thanks TsaebehT.

and Gladjag, I am not using the Asus graphic tweaker,but I think this is worth a try ... good luck.

ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit

#81
Posted 04/29/2013 04:59 PM   
oops me bad, miss-read once again, yes your are correct the USD is connect t o internal hub, noticed when i checked device manager that the emttier shows up in root. Ok will try this when i get home and keep you posted. I really appreciate all your insight and help with this TsaebehT, as Graymetter said it is amazing your tenacity on this even after your set-up works for you to help us out.
oops me bad, miss-read once again, yes your are correct the USD is connect t o internal hub, noticed when i checked device manager that the emttier shows up in root.
Ok will try this when i get home and keep you posted.

I really appreciate all your insight and help with this TsaebehT, as Graymetter said it is amazing your tenacity on this even after your set-up works for you to help us out.

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.

#82
Posted 04/29/2013 05:58 PM   
just had a though, i also have the opertunity to move the Emitter to an intertnal additional USB hub of only 2 slots, that would isolate the Emitter and i should find it under the device manager, thus your script would only disconnect those 2 USB plugs ( will leave only emitter on it since i have more than enought other USD slots) will keep you posted.
just had a though, i also have the opertunity to move the Emitter to an intertnal additional USB hub of only 2 slots, that would isolate the Emitter and i should find it under the device manager, thus your script would only disconnect those 2 USB plugs ( will leave only emitter on it since i have more than enought other USD slots)

will keep you posted.

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.

#83
Posted 04/29/2013 06:18 PM   
Hi Guys, Have been following this forum since I purchased my new BenQ Monitor (XL2411T) and Nvidia Vision 2 kit last week, and have (guess what) received the same problems as yourselves regards the inactivity of the emitter after boot up. I have tried everything suggested on this forum (USB Sleep/Suspend mode, USB Hubs etc)and sometimes the emitter works on boot up, but then it reverts back to NOT working after 2-3 times. Like yourselves I have logged this problem with Nvidia who have yet to get back to me. However gents I have managed to resolve my problem, unsure whether this will help you or not, but here goes: Someone suggested that after powering down your PC, you should try switching the Power Supply off or unplugging the mains cable to you PC, then reconnect and see what effect it has on your emitter. On my system the emitter light powered Red, which beleieve it or not was the same as removing the usb from the PC (whilst powered off) and reconnecting. Needless to say once this had been done my system booted to windows and the 3D emitter was enabled without a hitch. However I don't want to have to disconnect cables everytime I either reboot or shutdown the system. So I looked at the BIOS settings on my "Gigabyte GA-Z68X-UD7-B3" motherboard and made the following changes: a. Under Intergarted Peripherals: 1. USB Storage Function - Detects USB devices during POST (Default enabled) - I set to disabled. 2. USB Turbo - Ensure it remains on Default - disabled. b. Power Management Setup: 1. ErP Support - Determines whether to let the system consume less than 1W power in S5 (shutdown) state - Default is disabled. Note: I have enabled this option. Since I have made these changes, I have rebooted numerous of times and powered down numerous of times and each time has resulted in a successfull boot of my system with the emitter working as it should. Perhaps there is some available options within your BIOS your could try - good luck everyone.
Hi Guys,

Have been following this forum since I purchased my new BenQ Monitor (XL2411T) and Nvidia Vision 2 kit last week, and have (guess what) received the same problems as yourselves regards the inactivity of the emitter after boot up. I have tried everything suggested on this forum (USB Sleep/Suspend mode, USB Hubs etc)and sometimes the emitter works on boot up, but then it reverts back to NOT working after 2-3 times.
Like yourselves I have logged this problem with Nvidia who have yet to get back to me. However gents I have managed to resolve my problem, unsure whether this will help you or not, but here goes:
Someone suggested that after powering down your PC, you should try switching the Power Supply off or unplugging the mains cable to you PC, then reconnect and see what effect it has on your emitter. On my system the emitter light powered Red, which beleieve it or not was the same as removing the usb from the PC (whilst powered off) and reconnecting. Needless to say once this had been done my system booted to windows and the 3D emitter was enabled without a hitch. However I don't want to have to disconnect cables everytime I either reboot or shutdown the system. So I looked at the BIOS settings on my "Gigabyte GA-Z68X-UD7-B3" motherboard and made the following changes:
a. Under Intergarted Peripherals:
1. USB Storage Function - Detects USB devices during POST (Default enabled) - I set to disabled.
2. USB Turbo - Ensure it remains on Default - disabled.
b. Power Management Setup:
1. ErP Support - Determines whether to let the system consume less than 1W power in S5 (shutdown) state - Default is disabled. Note: I have enabled this option.
Since I have made these changes, I have rebooted numerous of times and powered down numerous of times and each time has resulted in a successfull boot of my system with the emitter working as it should.
Perhaps there is some available options within your BIOS your could try - good luck everyone.

#84
Posted 04/29/2013 07:29 PM   
Ok, I did the move of emitter to a different USB, shutdown power on PSU, put in the " restart hub with specific Hardware ID" rebooted my Pc the emitter flashed red at first boot then installed the driver, I then did a full shutdown / restart of PC. The emitter turned on Green and once Windows finished loaded it flashed once ( green) no install of driver and is stable. I will test for a couple of days with this set-up keeping everything crossed that this is the one. Thanks again for all the input it helps. Will keep you all posted. P.S. I did it not disabling Asus GPU Tweak to see if that caused it even with the changes and no effect so I guess that is not affecting emitter.
Ok, I did the move of emitter to a different USB, shutdown power on PSU, put in the " restart hub with specific Hardware ID" rebooted my Pc the emitter flashed red at first boot then installed the driver, I then did a full shutdown / restart of PC. The emitter turned on Green and once Windows finished loaded it flashed once ( green) no install of driver and is stable.
I will test for a couple of days with this set-up keeping everything crossed that this is the one.

Thanks again for all the input it helps.

Will keep you all posted.
P.S. I did it not disabling Asus GPU Tweak to see if that caused it even with the changes and no effect so I guess that is not affecting emitter.

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.

#85
Posted 04/29/2013 09:19 PM   
Thanks for the feedback guys, definitely keep me posted. When I get a chance I'll update the work around, hopefully for the last time. :D I know it's not as universal as I'd like but hopefully I can make it easy to understand so anyone can do it.
Thanks for the feedback guys, definitely keep me posted. When I get a chance I'll update the work around, hopefully for the last time. :D

I know it's not as universal as I'd like but hopefully I can make it easy to understand so anyone can do it.
#86
Posted 04/29/2013 09:29 PM   
Arrgh! ...and other suitably disgusting sounds... The last two boots everything [i]started[/i] OK ... windows made the sound of a USB item uplugging and replugging ... Emitter came on as before ... and then a second later the Emitter went dark and I had nothing but "3D Vision Discover". mannyash, I hope you have better luck with your solution. I have looked at my BIOS and the closest choices I have to yours is to either: Disable "USB Funtions" which "Allows you to enable or disable USB Host Controllers" default [Enabled] or Disable "USB 2.0 Controller" which "Allows you to enable or disable the USB 2.0 controller" default [Enabled] I've never considered disabling either of these before but is it possible that when disabled in the BIOS they are disabled for POST/Boot and then enabled by the operating system? I'm going to have to think about this. Disabling either of these removes the USB speed selection, so I can't replicate your choice there, but then again there isn't a Turbo choice ... just HiSpeed(480 Mbps) and FullSpeed(12 Mbps). Under power options I only have S1 & S3, no S5. Thanks for the input mannyash but it's not looking to good for me. And thank you Tsaebeht for all your efforts ... wish I had something better to report ... I hope Gladjag has better luck.
Arrgh! ...and other suitably disgusting sounds...

The last two boots everything started OK ... windows made the sound of a USB item uplugging and replugging ... Emitter came on as before ... and then a second later the Emitter went dark and I had nothing but "3D Vision Discover".

mannyash, I hope you have better luck with your solution. I have looked at my BIOS and the closest choices I have to yours is to either:

Disable "USB Funtions" which "Allows you to enable or disable USB Host Controllers"
default [Enabled]

or

Disable "USB 2.0 Controller" which "Allows you to enable or disable the USB 2.0 controller"
default [Enabled]

I've never considered disabling either of these before but is it possible that when disabled in the BIOS they are disabled for POST/Boot and then enabled by the operating system? I'm going to have to think about this.

Disabling either of these removes the USB speed selection, so I can't replicate your choice there, but then again there isn't a Turbo choice ... just HiSpeed(480 Mbps) and FullSpeed(12 Mbps).

Under power options I only have S1 & S3, no S5.

Thanks for the input mannyash but it's not looking to good for me.

And thank you Tsaebeht for all your efforts ... wish I had something better to report ... I hope Gladjag has better luck.

ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit

#87
Posted 04/29/2013 11:42 PM   
Have you tried swapping out the USB cable with another one? Try the Intel Update Utility, I upgraded my Asus Rampage Mobo using it for the Intel portions http://www.intel.com/p/en_US/support/detect/
Have you tried swapping out the USB cable with another one?

Try the Intel Update Utility, I upgraded my Asus Rampage Mobo using it for the Intel portions


http://www.intel.com/p/en_US/support/detect/

#88
Posted 04/29/2013 11:57 PM   
... and yet I have another idea. Lol. [s]Do me a favor after the emitter goes black, go into task manager and disable the task, right-click and select disable, then shutdown windows and then start it up again. If the emitter works fine, then enable the task again, until it doesn't work and then repeat.[/s] Try this instead, make a bat with the following, make sure [u]devcon[/u]'s set to run as admin (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] I'll look into a way to 'remove' the emitter when you shutdown/logoff ... maybe it'll be found normally during boot up. If that doesn't work I'm really starting to think that no software methods will work. The only other thing I can think of is update your motherboard's bios and any drivers associated with it, sometimes windows doesn't always supply the best/most current drivers.
... and yet I have another idea. Lol. Do me a favor after the emitter goes black, go into task manager and disable the task, right-click and select disable, then shutdown windows and then start it up again. If the emitter works fine, then enable the task again, until it doesn't work and then repeat. Try this instead, make a bat with the following, make sure devcon's set to run as admin (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"


I'll look into a way to 'remove' the emitter when you shutdown/logoff ... maybe it'll be found normally during boot up.

If that doesn't work I'm really starting to think that no software methods will work.

The only other thing I can think of is update your motherboard's bios and any drivers associated with it, sometimes windows doesn't always supply the best/most current drivers.
#89
Posted 04/30/2013 12:10 AM   
Hello All, I hate to say it, but it seems I'm having the same problem also. I'm running a Biostar TPower X79 motherboard with a 660 Ti card and Windows 7 Prof. 64 bit. It has a fresh setup, and all updated firmware/drivers as far as I can tell, including 314.22 for the card/3d vision. If I unplug and plug the emitter each time, and re-run the wizard, it works. However, on each boot, it seems to pass all the power on tests, and then just goes black. I've tried clean driver installs: nothing. Tried the script/task manager solution on page 4 of thread, and it does run as far as task goes, or serves as an unplug/re-plug, but then still goes black as described in post #73, page 5: so again, nothing. Tried the power cycle/unplug power and change bios settings method, but my bios USB related options were not the same and did not seem to affect the matter: still no go anyway, so nada. Overall, I get the sense that it's related to initializations, hooks, timings, and the likes, and I've seen mice that have had the same problem, albeit more intermittently. Anyway, if my specs can help narrow down the culprit, great, or if I do figure out more I'll post.
Hello All, I hate to say it, but it seems I'm having the same problem also. I'm running a Biostar TPower X79 motherboard with a 660 Ti card and Windows 7 Prof. 64 bit. It has a fresh setup, and all updated firmware/drivers as far as I can tell, including 314.22 for the card/3d vision.

If I unplug and plug the emitter each time, and re-run the wizard, it works. However, on each boot, it seems to pass all the power on tests, and then just goes black. I've tried clean driver installs: nothing. Tried the script/task manager solution on page 4 of thread, and it does run as far as task goes, or serves as an unplug/re-plug, but then still goes black as described in post #73, page 5: so again, nothing. Tried the power cycle/unplug power and change bios settings method, but my bios USB related options were not the same and did not seem to affect the matter: still no go anyway, so nada.

Overall, I get the sense that it's related to initializations, hooks, timings, and the likes, and I've seen mice that have had the same problem, albeit more intermittently. Anyway, if my specs can help narrow down the culprit, great, or if I do figure out more I'll post.

#90
Posted 04/30/2013 04:51 AM   
  6 / 15    
Scroll To Top