Emitter disconneting on computer boot
  5 / 15    
Hi TsaebehT, I bow before you, this works perfectly, I have shutdown my PC a couple of times and it goes through the process of re-installing the driver for the emitter and it stays on after full windows boot, even keeps my monitor in the Nvidia control panel. I suggest to others having this issue, try out the above and comment back here so others can benefit from your knowledge and work on finding a solution. Once again thank you.
Hi TsaebehT, I bow before you, this works perfectly, I have shutdown my PC a couple of times and it goes through the process of re-installing the driver for the emitter and it stays on after full windows boot, even keeps my monitor in the Nvidia control panel.

I suggest to others having this issue, try out the above and comment back here so others can benefit from your knowledge and work on finding a solution.

Once again thank you.

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.

#61
Posted 04/25/2013 11:08 PM   
You're welcome, glad you got it going. You had me worried for a minute there with the not being able to copy and paste. :D
You're welcome, glad you got it going. You had me worried for a minute there with the not being able to copy and paste. :D
#62
Posted 04/25/2013 11:18 PM   
I updated it with instructions for the 32bit versions, (untested atm but should work just the same just a different location/version for 32bit devcon) I changed the script and it's location, (64bit/32bit versions) and I changed the Actions settings tab to work with both. (64/32) If you're already using the previous one you're fine, keep using it the only reason I changed things was to hopefully make this work around a bit more universal. @Gladjag: You should probably put a link to the 'fix' in the OP, that way if someone finds this thread in a search they'll see it right away. [url]https://forums.geforce.com/default/topic/539264/3d-vision/emitter-disconneting-on-computer-boot/post/3792104/#3792104[/url]
I updated it with instructions for the 32bit versions, (untested atm but should work just the same just a different location/version for 32bit devcon) I changed the script and it's location, (64bit/32bit versions) and I changed the Actions settings tab to work with both. (64/32)

If you're already using the previous one you're fine, keep using it the only reason I changed things was to hopefully make this work around a bit more universal.

@Gladjag: You should probably put a link to the 'fix' in the OP, that way if someone finds this thread in a search they'll see it right away.

https://forums.geforce.com/default/topic/539264/3d-vision/emitter-disconneting-on-computer-boot/post/3792104/#3792104
#63
Posted 04/26/2013 11:55 AM   
I had other people I know running basically same set-up as mine and it did not work for them. I will keep you posted if any changes, I have not done a full shutdown since my last post. Will test over the weekend to make sure nothing changed and it still works. will keep you posted.
I had other people I know running basically same set-up as mine and it did not work for them.
I will keep you posted if any changes, I have not done a full shutdown since my last post. Will test over the weekend to make sure nothing changed and it still works. 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.

#64
Posted 04/26/2013 10:50 PM   
Have them try to do it manually, you remember like I had you do. Uninstall and rescan in the Device Manager. If that works then something else is wrong, either setup wrong, a different hardware id?, or using the wrong version of DevCon. If it doesn't work, or it's not seen by the Device Manager then I'm not sure, I'll have to try to think of something else.
Have them try to do it manually, you remember like I had you do. Uninstall and rescan in the Device Manager.

If that works then something else is wrong, either setup wrong, a different hardware id?, or using the wrong version of DevCon.

If it doesn't work, or it's not seen by the Device Manager then I'm not sure, I'll have to try to think of something else.
#65
Posted 04/26/2013 11:16 PM   
I've been having this problem too. Its annoying.
I've been having this problem too. Its annoying.

#66
Posted 04/27/2013 01:00 PM   
[quote="BababooeyHTJ"]I've been having this problem too. Its annoying. [/quote] And did you try the work around? It's less annoying if you don't have to physically unplug it. [url]https://forums.geforce.com/default/topic/539264/3d-vision/emitter-disconneting-on-computer-boot/post/3792104/#3792104[/url]
BababooeyHTJ said:I've been having this problem too. Its annoying.


And did you try the work around? It's less annoying if you don't have to physically unplug it.

https://forums.geforce.com/default/topic/539264/3d-vision/emitter-disconneting-on-computer-boot/post/3792104/#3792104
#67
Posted 04/27/2013 01:57 PM   
Tsaebeht, your instructions are far better most instruction I have received with hardware I've purchased including the Nvidia 3d kit. Having said that I have to report that unfortunately this is not working for me. I've gone through your instructions carefully twice without luck. When the computer boots, at the end of the startup cycle, when the mouse cursor changes from the animated cirle to a pointer, the emitter does light up like it is going to work but then I get a message at the task bar that Windows is installing a new device driver ... which turns out to be the Nvidia Stereoscopic device ... and the installer says the device has been successfully installed ... but when the "successfully installed" message shows up the emitter goes dark and going to the Nvidia control panel and looking at Stereoscopic 3D shows only 3D Vision Discover, no ASUS monitor and no button to run the 3D wizard setup ... at this point I have tried manually running Reset3D.bat but without luck. The only thing that works at this point is to physically unplug and replug the emitter. Strangely (I think) is the fact that right clicking "Reset3d.Bat" and selecting run as administrator seems to work [i]after[/i] the Emitter is running (i.e.) the batch file runs in a small Cmd window and afterwards the emitter is still running and there is [i]no[/i] reinstall of the Stereoscopic driver.
Tsaebeht, your instructions are far better most instruction I have received with hardware I've purchased including the Nvidia 3d kit. Having said that I have to report that unfortunately this is not working for me. I've gone through your instructions carefully twice without luck.

When the computer boots, at the end of the startup cycle, when the mouse cursor changes from the animated cirle to a pointer, the emitter does light up like it is going to work but then I get a message at the task bar that Windows is installing a new device driver ... which turns out to be the Nvidia Stereoscopic device ... and the installer says the device has been successfully installed ... but when the "successfully installed" message shows up the emitter goes dark and going to the Nvidia control panel and looking at Stereoscopic 3D shows only 3D Vision Discover, no ASUS monitor and no button to run the 3D wizard setup ... at this point I have tried manually running Reset3D.bat but without luck. The only thing that works at this point is to physically unplug and replug the emitter.

Strangely (I think) is the fact that right clicking "Reset3d.Bat" and selecting run as administrator seems to work after the Emitter is running (i.e.) the batch file runs in a small Cmd window and afterwards the emitter is still running and there is no reinstall of the Stereoscopic driver.

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

#68
Posted 04/27/2013 05:05 PM   
[b]Success![/b] (fingers crossed) Tsaebeht, I was just about to remove the Reset3D task from the list when I decided to try altering the "Configure for:" drop down on the "General" Tab. I switched this from "Windows Vista,..." to "Windows 7,..." and now it works :). (Did you do this and forget to include the step?) It still installs the 3D Device driver when I boot up, but now the installation truly is successful ... the Emitter is functional and configured for my 3D Monitor. I'll report back after continued use, but I'm hopeful.
Success! (fingers crossed)

Tsaebeht, I was just about to remove the Reset3D task from the list when I decided to try altering the "Configure for:" drop down on the "General" Tab. I switched this from "Windows Vista,..." to "Windows 7,..." and now it works :). (Did you do this and forget to include the step?)

It still installs the 3D Device driver when I boot up, but now the installation truly is successful ... the Emitter is functional and configured for my 3D Monitor. I'll report back after continued use, but I'm hopeful.

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

#69
Posted 04/27/2013 05:44 PM   
Did manually uninstalling/rescanning it from the Device Manager work for you originally? DevCon has to be run with admin privileges, you're just running the bat as admin, you'd 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.
Did manually uninstalling/rescanning it from the Device Manager work for you originally?

DevCon has to be run with admin privileges, you're just running the bat as admin, you'd 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.
#70
Posted 04/27/2013 05:51 PM   
@GrayMatter Hmm. no mine's set as shown in the guide ... but then again mine was working to begin with. Lol. Thanks for the info, [s]I'll update that section[/s]. Updated thanks again! @Gladjag Could you please have your friends that it wasn't working for try out what worked for GreyMatter? Switching the OS on the general tab in Step 3. Thanks.
@GrayMatter
Hmm. no mine's set as shown in the guide ... but then again mine was working to begin with. Lol. Thanks for the info, I'll update that section. Updated thanks again!

@Gladjag
Could you please have your friends that it wasn't working for try out what worked for GreyMatter? Switching the OS on the general tab in Step 3. Thanks.
#71
Posted 04/27/2013 05:58 PM   
Hi All, Yes I will ask him to try changing OS also, I was having the same problem Graymatter mentioned above after a day or so after a full shutdown of my Pc I even changed to re-try if fail after 1 min but it was only showing the driver install as mentioned by Graymatter. I just changed the OS to Windows 7 to see if that corrected the issue ( fingers crossed ) Will keep you posted.
Hi All,
Yes I will ask him to try changing OS also, I was having the same problem Graymatter mentioned above after a day or so after a full shutdown of my Pc I even changed to re-try if fail after 1 min but it was only showing the driver install as mentioned by Graymatter. I just changed the OS to Windows 7 to see if that corrected the issue ( fingers crossed )

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.

#72
Posted 04/28/2013 02:22 AM   
Well a bit of disappointing news, I made the adjustments as per discussed above and I am still getting the install of driver but the emitter shuts down right after. I did the task manager uninstall and re-scan, it finds the emitter and install driver , emitter connects. Not sure why it stopped working like it was doing for a day or so, I have not installed any new programs or changes to my PC. Graymatter is it working for you now?
Well a bit of disappointing news, I made the adjustments as per discussed above and I am still getting the install of driver but the emitter shuts down right after. I did the task manager uninstall and re-scan, it finds the emitter and install driver , emitter connects.

Not sure why it stopped working like it was doing for a day or so, I have not installed any new programs or changes to my PC.
Graymatter is it working for you now?

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.

#73
Posted 04/28/2013 12:51 PM   
Ok, not sure why this is happening, it [i]should[/i] be working ... then again so should your emitter. After reboot and the emitter shuts down go back into Task Scheduler and check if the task ran, failed, or if it's still running. (Status and Last Run Results) With the emitter in it's shutdown state, find the devcon.exe, right-click > goto properties > on the compatibility tab > check run as admin > click OK. Then find the Reset3d.Bat, right-click > goto edit > select all and then past the following (Ctrl+A then Ctrl+V) and then save as test.bat (File > Save As) and run it. [quote]cd amd64 devcon.exe restart "USB\VID_0955&PID_0007"[/quote] If it works try pasting just this and only this into the Reset3d.Bat and save. (Ctrl+A, Ctrl+V, then Ctrl+S) and restart Windows. Maybe instead or remove it and reinstalling it, just restarting it will work? If that doesn't work try pasting this script into Reset3d.Bat and save and restart Windows. [quote]cd amd64 devcon.exe remove "USB\VID_0955&PID_0007" devcon.exe rescan devcon.exe restart "USB\VID_0955&PID_0007"[/quote] If that doesn't work paste the original script back into Reset3d.Bat and save. [quote]cd amd64 devcon.exe remove "USB\VID_0955&PID_0007" devcon.exe rescan[/quote] I noticed there's a Power section in the conditions tab on the task, for laptops/battery might as well uncheck those. I don't think they apply to you as the task is running just for whatever reason not working but worth mentioning if anyone's trying this on a laptop and it isn't working. I'll update the work around with a note on this. There's also a delay (Delay Task For) in the trigger, on the Triggers tab, the lowest settings are 30 seconds, 1 min., and 30 min. Not sure if setting a delay of 1 min. might keep it from interfering with anything it might be? Try setting it to 1 min. and restarting, if that works after a few reboots/days you could try lowering it to 30 seconds.
Ok, not sure why this is happening, it should be working ... then again so should your emitter. After reboot and the emitter shuts down go back into Task Scheduler and check if the task ran, failed, or if it's still running. (Status and Last Run Results)

With the emitter in it's shutdown state, find the devcon.exe, right-click > goto properties > on the compatibility tab > check run as admin > click OK. Then find the Reset3d.Bat, right-click > goto edit > select all and then past the following (Ctrl+A then Ctrl+V) and then save as test.bat (File > Save As) and run it.

cd amd64
devcon.exe restart "USB\VID_0955&PID_0007"


If it works try pasting just this and only this into the Reset3d.Bat and save. (Ctrl+A, Ctrl+V, then Ctrl+S) and restart Windows. Maybe instead or remove it and reinstalling it, just restarting it will work?


If that doesn't work try pasting this script into Reset3d.Bat and save and restart Windows.

cd amd64
devcon.exe remove "USB\VID_0955&PID_0007"
devcon.exe rescan
devcon.exe restart "USB\VID_0955&PID_0007"


If that doesn't work paste the original script back into Reset3d.Bat and save.

cd amd64
devcon.exe remove "USB\VID_0955&PID_0007"
devcon.exe rescan


I noticed there's a Power section in the conditions tab on the task, for laptops/battery might as well uncheck those. I don't think they apply to you as the task is running just for whatever reason not working but worth mentioning if anyone's trying this on a laptop and it isn't working. I'll update the work around with a note on this.

There's also a delay (Delay Task For) in the trigger, on the Triggers tab, the lowest settings are 30 seconds, 1 min., and 30 min. Not sure if setting a delay of 1 min. might keep it from interfering with anything it might be? Try setting it to 1 min. and restarting, if that works after a few reboots/days you could try lowering it to 30 seconds.
#74
Posted 04/28/2013 02:14 PM   
Hi, no joy here ... after working a couple of times Reset3D.bat now fails most times. As an aside I really like playing in 3D and am pretty frustrated this isn't working as it should since Nvidia has me hooked on the technology, playing games at 100% depth in 3D is outstanding once your brain has adjusted. 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] In other words it works just as I imagine it should. My conjecture is that this suggests Nvidia has inadvertantly built in a device state instability issue in the driver somewhere along the line and they are probably the only ones who can truly solve the issue. That is completely conjecture, but looking at this forum there seems to be a growing list of people having emitter problems. TsaebehT, your tenacity with a problem you aren't even experiencing is truly remarkable. Thank you again. When next I can tear myself away from Necromorph dismemberment :) I will try your suggested work around.
Hi, no joy here ... after working a couple of times Reset3D.bat now fails most times. As an aside I really like playing in 3D and am pretty frustrated this isn't working as it should since Nvidia has me hooked on the technology, playing games at 100% depth in 3D is outstanding once your brain has adjusted.

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. In other words it works just as I imagine it should. My conjecture is that this suggests Nvidia has inadvertantly built in a device state instability issue in the driver somewhere along the line and they are probably the only ones who can truly solve the issue. That is completely conjecture, but looking at this forum there seems to be a growing list of people having emitter problems.

TsaebehT, your tenacity with a problem you aren't even experiencing is truly remarkable. Thank you again. When next I can tear myself away from Necromorph dismemberment :) I will try your suggested work around.

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

#75
Posted 04/28/2013 05:23 PM   
  5 / 15    
Scroll To Top