[quote="TsaebehT"]On my laptop it won't ... but when I [u]uninstall[/u] (or disable it) it from within the Device Manager it turns on, GREEN, and stays on ...[/quote]
Same with my other Win7, non NVIDIA GPU PC, installs and then just shuts off.
[quote="TsaebehT"]I found a key in the registry "DeviceSelectiveSuspended"=dword:00000001[/quote]
The key is the same on my 3Dpc that's working fine.
Odd that on WinXP it stays on and on all the other Win7 (Non N'GPU) PCs that I've tried it shuts off, like it does to you ... well until you un/replug it in.
I removed the work around for now, I haven't heard that it stayed working for anyone even though it should have, makes no sense but I can't really test it to say otherwise.
TsaebehT said:On my laptop it won't ... but when I uninstall (or disable it) it from within the Device Manager it turns on, GREEN, and stays on ...
Same with my other Win7, non NVIDIA GPU PC, installs and then just shuts off.
TsaebehT said:I found a key in the registry "DeviceSelectiveSuspended"=dword:00000001
The key is the same on my 3Dpc that's working fine.
Odd that on WinXP it stays on and on all the other Win7 (Non N'GPU) PCs that I've tried it shuts off, like it does to you ... well until you un/replug it in.
I removed the work around for now, I haven't heard that it stayed working for anyone even though it should have, makes no sense but I can't really test it to say otherwise.
[quote="Spacemoss"]Ok, so since I remembered seeing a mouse behave similarly, I decided to search for info on mouse disconnections. I came across a suggestion and tried it. So far, I've rebooted 3 times and the emitter has worked normally ! Whether it stays that way remains to be seen. Here's what I did.
Go to device manager and expand Universal Serial Bus Controllers.
For each USB root hub right click on it and choose properties. (technically you probably only need the one the emitter is on)
Choose Power Management Tab.
Uncheck / Deselect "Allow Computer to turn off device to save power"
Hit Ok
I'll be interested to see how long it lasts, and if this works for anyone else.
P.S. I'd probably try disabling the script if you're using it, no need to have it unplug/re-plug for no reason, while trying this test.[/quote]
Hi all, I have done all of the suggested workarounds mentioned in this post and I can say that I have still get the turn off issue , although when I leave my PC on "put into sleep mode" after 2hrs, I am getting a better success rate of the emitter staying on when I take the PC out of sleep. I will keep this up for a couple of days just to monitor.
P.S. I disabled the workaround .bat and the power management on that usb to not shut off as per mentioned by Spacemoss
Spacemoss said:Ok, so since I remembered seeing a mouse behave similarly, I decided to search for info on mouse disconnections. I came across a suggestion and tried it. So far, I've rebooted 3 times and the emitter has worked normally ! Whether it stays that way remains to be seen. Here's what I did.
Go to device manager and expand Universal Serial Bus Controllers.
For each USB root hub right click on it and choose properties. (technically you probably only need the one the emitter is on)
Choose Power Management Tab.
Uncheck / Deselect "Allow Computer to turn off device to save power"
Hit Ok
I'll be interested to see how long it lasts, and if this works for anyone else.
P.S. I'd probably try disabling the script if you're using it, no need to have it unplug/re-plug for no reason, while trying this test.
Hi all, I have done all of the suggested workarounds mentioned in this post and I can say that I have still get the turn off issue , although when I leave my PC on "put into sleep mode" after 2hrs, I am getting a better success rate of the emitter staying on when I take the PC out of sleep. I will keep this up for a couple of days just to monitor.
P.S. I disabled the workaround .bat and the power management on that usb to not shut off as per mentioned by Spacemoss
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.
Hi everybody, I started wondering if this might be a hardware issue with the emitter. So I tried hooking up the emitter to a second computer I have with a Gigabyte P45 chipset but no 3D monitor. The 3D setup wizard allowed me to setup the emitter with a Generic CRT selected as monitor although I have a 60hz LCD connected.
First shutdown restart cycle and the emitter failed. It went off at logon and restarted when I unplugged and replugged the emitter. Second and third shutdown restart cycles the emitter worked perfectly. Inconclusive, but so far I'm thinking it looks like a software problem. More data would be better. I'm going to continue moving the emitter over to the other machine for further tests. Is there anyone out there experiencing this problem who has access to a known working 3D setup who could do some testing? I'm actually hoping this is a driver problem and not hardware but I don't think any of us has really looked seriously at this possibility.
The second machine I used has 314.07 whql drivers. I think I've tried these drivers on my 3D machine before but I'll try again just to be sure. In the mean time like Gladjag I have been shutting down with hybrid sleep lately and the emitter has been behaving so far.
Hi everybody, I started wondering if this might be a hardware issue with the emitter. So I tried hooking up the emitter to a second computer I have with a Gigabyte P45 chipset but no 3D monitor. The 3D setup wizard allowed me to setup the emitter with a Generic CRT selected as monitor although I have a 60hz LCD connected.
First shutdown restart cycle and the emitter failed. It went off at logon and restarted when I unplugged and replugged the emitter. Second and third shutdown restart cycles the emitter worked perfectly. Inconclusive, but so far I'm thinking it looks like a software problem. More data would be better. I'm going to continue moving the emitter over to the other machine for further tests. Is there anyone out there experiencing this problem who has access to a known working 3D setup who could do some testing? I'm actually hoping this is a driver problem and not hardware but I don't think any of us has really looked seriously at this possibility.
The second machine I used has 314.07 whql drivers. I think I've tried these drivers on my 3D machine before but I'll try again just to be sure. In the mean time like Gladjag I have been shutting down with hybrid sleep lately and the emitter has been behaving so far.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
It has to be some sort of software issue, be it drivers, firmwares, or settings, because if it wasn't it would never work. But the hardware does work when it's first plugged in, it just seems like it's getting put into a sleep state when windows shuts down and then not waking from it for some reason.
Are there different versions of the emitter for 3D Vision vs 3D Vision 2? I think the model number isn't just P854, there's another number under the S/N, mine is:
942-10701-0005-401 J
Also the J seems like it might be a rev. I guess it's worth a shot posting them to see if there's a pattern. Maybe even Model, Mainboard and USB Host controller. Like this:
[quote]Emitter Model: P854
Sticker #: 942-10701-0005-401 J (Working)
Mainboard: Make/Model/Rev (Placeholder)
USB: Intel(R) ICH9 Family USB Universal Host Controller - 2934 (Placeholder/laptop)[/quote]
It has to be some sort of software issue, be it drivers, firmwares, or settings, because if it wasn't it would never work. But the hardware does work when it's first plugged in, it just seems like it's getting put into a sleep state when windows shuts down and then not waking from it for some reason.
Are there different versions of the emitter for 3D Vision vs 3D Vision 2? I think the model number isn't just P854, there's another number under the S/N, mine is:
942-10701-0005-401 J
Also the J seems like it might be a rev. I guess it's worth a shot posting them to see if there's a pattern. Maybe even Model, Mainboard and USB Host controller. Like this:
ditto ... I don't see any model ID, but this is the number on the sticker under the emitter
Sticker#: 942-11431-0007-001 G
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
[quote="Spacemoss"]
Go to device manager and expand Universal Serial Bus Controllers.
For each USB root hub right click on it and choose properties. (technically you probably only need the one the emitter is on)
Choose Power Management Tab.
Uncheck / Deselect "Allow Computer to turn off device to save power"
Hit Ok
[/quote]
Spacemoss, earlier in this thread I tried disabling "USB selective suspend setting" in the Power Settings for my computer ... this unchecks "Allow Computer to turn off device to save power" for all the USB root hubs, but it didn't work for me. Since you are seeing normal operation I went back and enabled "USB selective suspend setting" in the power settings and cleared "Allow Computer to turn off device to save power" in the Device Manager as you did, just in case there was a difference but I'm still not having any luck with my Emitter. Also, I'm not using any of the startup batch files as you suggested. Is there anything else you might have done? It's good to hear someone's Emitter is operating normally after experiencing this problem.
Spacemoss said:
Go to device manager and expand Universal Serial Bus Controllers.
For each USB root hub right click on it and choose properties. (technically you probably only need the one the emitter is on)
Choose Power Management Tab.
Uncheck / Deselect "Allow Computer to turn off device to save power"
Hit Ok
Spacemoss, earlier in this thread I tried disabling "USB selective suspend setting" in the Power Settings for my computer ... this unchecks "Allow Computer to turn off device to save power" for all the USB root hubs, but it didn't work for me. Since you are seeing normal operation I went back and enabled "USB selective suspend setting" in the power settings and cleared "Allow Computer to turn off device to save power" in the Device Manager as you did, just in case there was a difference but I'm still not having any luck with my Emitter. Also, I'm not using any of the startup batch files as you suggested. Is there anything else you might have done? It's good to hear someone's Emitter is operating normally after experiencing this problem.
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 we had more numbers to go by. So far it looks like you guys have 3D Vision 2 emitters and I have a 1 emitter. 2 of you with possibly the same/newer rev., if that's what the letter is, and 1 with an older rev. that seems to be working.
Wish we had more numbers to go by. So far it looks like you guys have 3D Vision 2 emitters and I have a 1 emitter. 2 of you with possibly the same/newer rev., if that's what the letter is, and 1 with an older rev. that seems to be working.
[quote="GrayMatter"]
Spacemoss, earlier in this thread I tried disabling "USB selective suspend setting" in the Power Settings for my computer ... this unchecks "Allow Computer to turn off device to save power" for all the USB root hubs, but it didn't work for me. Since you are seeing normal operation I went back and enabled "USB selective suspend setting" in the power settings and cleared "Allow Computer to turn off device to save power" in the Device Manager as you did, just in case there was a difference but I'm still not having any luck with my Emitter. Also, I'm not using any of the startup batch files as you suggested. Is there anything else you might have done? It's good to hear someone's Emitter is operating normally after experiencing this problem. [/quote]
Hmmmm, yah it's been another 2 reboots and I'm still working fine. The only things I did were: A)A fresh driver install and I checked the option to do "clean install", (didn't solve problem) B) The original script/task scheduler suggestion on page 4 (didn't solve problem - so I disabled the task and removed devcon folder), C) Did the power cycling once, where I actually unplugged power to the pc after it was shutdown and watched for emitter light blink(compared to just using PSU switch - Didn't solve problem), D)Checked, my BIOS for relevant settings (didn't have any), E)Did the Device Manager thing I suggested with allowing to turn off device.
As a side note, I had investigated my power setting options within the advanced power profiles, but didn't change any related to USB. In fact, my USB selective suspend is enabled, I left it on. From my limited reading and understanding, I'm not 100% sure that using USB selective suspend and Telling the Device manager hardware properties to not allow shutoff are exactly one and the same. I think the power management/selective suspend take advantage of 5 power states between fully-on and fully-off, while the device manager allow option is only referring to one of these states , the fully off one (S0 maybe?). However, that speculation is beyond my current purview.
Spacemoss, earlier in this thread I tried disabling "USB selective suspend setting" in the Power Settings for my computer ... this unchecks "Allow Computer to turn off device to save power" for all the USB root hubs, but it didn't work for me. Since you are seeing normal operation I went back and enabled "USB selective suspend setting" in the power settings and cleared "Allow Computer to turn off device to save power" in the Device Manager as you did, just in case there was a difference but I'm still not having any luck with my Emitter. Also, I'm not using any of the startup batch files as you suggested. Is there anything else you might have done? It's good to hear someone's Emitter is operating normally after experiencing this problem.
Hmmmm, yah it's been another 2 reboots and I'm still working fine. The only things I did were: A)A fresh driver install and I checked the option to do "clean install", (didn't solve problem) B) The original script/task scheduler suggestion on page 4 (didn't solve problem - so I disabled the task and removed devcon folder), C) Did the power cycling once, where I actually unplugged power to the pc after it was shutdown and watched for emitter light blink(compared to just using PSU switch - Didn't solve problem), D)Checked, my BIOS for relevant settings (didn't have any), E)Did the Device Manager thing I suggested with allowing to turn off device.
As a side note, I had investigated my power setting options within the advanced power profiles, but didn't change any related to USB. In fact, my USB selective suspend is enabled, I left it on. From my limited reading and understanding, I'm not 100% sure that using USB selective suspend and Telling the Device manager hardware properties to not allow shutoff are exactly one and the same. I think the power management/selective suspend take advantage of 5 power states between fully-on and fully-off, while the device manager allow option is only referring to one of these states , the fully off one (S0 maybe?). However, that speculation is beyond my current purview.
I know before the numbers used to denote the bundle version/sales location. Like if the kit came with a game it would get new numbers or if you bought the glasses by themselves, they had their own number. There used to be a compehensive list, but I can not find it anywhere.
The closest I can find is http://nvidia.custhelp.com/app/answers/detail/a_id/2617/~/3d-vision-equipment-list
I know before the numbers used to denote the bundle version/sales location. Like if the kit came with a game it would get new numbers or if you bought the glasses by themselves, they had their own number. There used to be a compehensive list, but I can not find it anywhere.
BREAKTHROUGH... I THINK !
So I decided that if changing the power settings in device manager was indeed the fix for me, then undoing the changes should bring back the problem, right... I undid the changes, once again allowing the machine to idle those device, and rebooted, and to my astonishment it was still working fine! However, this means the device manager options were not the problem. This lead me to further review anything at all that I had toggled during all these processes, and then I stumbled on it.
In the NVidia control panel, under the Set Up Stereoscopic 3D page, the first check box says "Enable Stereoscopic 3D". I had been leaving mine disabled, and only enabling it when I was using it. It was DISABLED during all my successful shutdowns/reboots. So I tried shutting down with it enabled and BAM problem was back ! Then I tried, unchecking again, and problem was still here....So, hmmmm, I tried all 4 combinations of having the device manager allowing USB device shutdown/not allowing it with enabled/disabled 3D in NVidia controls. That is, allowed-enabled, allowed-disabled, not allowed-enabled, and not allowed-disabled. I was able to get it working again, and tested it through a few reboots and its working fine ! Here's what you should try.
The Device manager USB power options have no effect on the problem at all so you can turn them back on. Leave the emitter enabled in NVidia controls for the moment.
Do a reboot/fresh boot.
After login the emitter should go black.
Unplug and re-plug the emitter into its USB port, it should be recognized/stay on.
In NVidia control panel uncheck "Enable Stereoscopic 3D" and apply/hit OK.
Reboot
After login it should still be there working fine...all you have to do is then go in and enable it!
Just remember to disable it before shutdown, or you'll need to repeat the above process.
So it seems the culprit for me at least is whether that check box is checked.
Let me know what you find!
So I decided that if changing the power settings in device manager was indeed the fix for me, then undoing the changes should bring back the problem, right... I undid the changes, once again allowing the machine to idle those device, and rebooted, and to my astonishment it was still working fine! However, this means the device manager options were not the problem. This lead me to further review anything at all that I had toggled during all these processes, and then I stumbled on it.
In the NVidia control panel, under the Set Up Stereoscopic 3D page, the first check box says "Enable Stereoscopic 3D". I had been leaving mine disabled, and only enabling it when I was using it. It was DISABLED during all my successful shutdowns/reboots. So I tried shutting down with it enabled and BAM problem was back ! Then I tried, unchecking again, and problem was still here....So, hmmmm, I tried all 4 combinations of having the device manager allowing USB device shutdown/not allowing it with enabled/disabled 3D in NVidia controls. That is, allowed-enabled, allowed-disabled, not allowed-enabled, and not allowed-disabled. I was able to get it working again, and tested it through a few reboots and its working fine ! Here's what you should try.
The Device manager USB power options have no effect on the problem at all so you can turn them back on. Leave the emitter enabled in NVidia controls for the moment.
Do a reboot/fresh boot.
After login the emitter should go black.
Unplug and re-plug the emitter into its USB port, it should be recognized/stay on.
In NVidia control panel uncheck "Enable Stereoscopic 3D" and apply/hit OK.
Reboot
After login it should still be there working fine...all you have to do is then go in and enable it!
Just remember to disable it before shutdown, or you'll need to repeat the above process.
So it seems the culprit for me at least is whether that check box is checked.
Let me know what you find!
Hi Spacemoss,
That sounds like a good path, but to be honest, if I have to remember to disable 3D in Nvidia control panel every time I shut down, it is much faster for me to just unplug and plug back in after boot up.
I think what we are trying to figure out is why it is not functioning like it should and not require our intervention in any way or manner. I have tried all the workarounds mentioned in this post, they work a couple of times and the culprit goes back to shutting down right after windows is fully loaded.
I whish we would get some kind of feed back from Nvidia and it would be even nice if they decided to post here for everyone.
Hi Spacemoss,
That sounds like a good path, but to be honest, if I have to remember to disable 3D in Nvidia control panel every time I shut down, it is much faster for me to just unplug and plug back in after boot up.
I think what we are trying to figure out is why it is not functioning like it should and not require our intervention in any way or manner. I have tried all the workarounds mentioned in this post, they work a couple of times and the culprit goes back to shutting down right after windows is fully loaded.
I whish we would get some kind of feed back from Nvidia and it would be even nice if they decided to post here for everyone.
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.
If it works for everyone maybe I could come up with a script that disables 3D on shutdown, and reenables it on startup. You guys try it out and I'll look into it.
Save as 3Dprompt.bat
[code]@ECHO OFF
ECHO.
:ASK
set /p answer=ENABLE 3D VISION (Y/N)?
if /i "%answer%"=="Y" GOTO ENABLE3D
if /i "%answer%"=="N" GOTO DISABLE3D
GOTO ASK
:ENABLE3D
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /enable
GOTO END
:DISABLE3D
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /disable
GOTO END
:END EXIT[/code]
This saves going into the control panel everytime. :D
If it works for everyone maybe I could come up with a script that disables 3D on shutdown, and reenables it on startup. You guys try it out and I'll look into it.
Save as 3Dprompt.bat
@ECHO OFF
ECHO.
:ASK
set /p answer=ENABLE 3D VISION (Y/N)?
if /i "%answer%"=="Y" GOTO ENABLE3D
if /i "%answer%"=="N" GOTO DISABLE3D
GOTO ASK
:ENABLE3D
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /enable
GOTO END
:DISABLE3D
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /disable
GOTO END
:END EXIT
This saves going into the control panel everytime. :D
[quote="Gladjag"]Hi Spacemoss,
That sounds like a good path, but to be honest, if I have to remember to disable 3D in Nvidia control panel every time I shut down, it is much faster for me to just unplug and plug back in after boot up.
I think what we are trying to figure out is why it is not functioning like it should and not require our intervention in any way or manner.[/quote]
For me, right clicking, choosing NVidia control panel, and unchecking box, is easier/preferred than re-plugging cable, but at that point, it's just a personal preference. At least you would have the cause of the issue, which like you said, is what we were/are trying to determine.
Also, at that point, one could submit something along the lines of an official bug report like "Leaving Enable Stereoscopic 3D Checked Causes Emitter Failure On Subsequent Boots". This it seems, if it is the issue, is something that could easily be fixed in a future driver update, and in the meantime, you could possible just use a script like TsaebehT was offering above.
Gladjag said:Hi Spacemoss,
That sounds like a good path, but to be honest, if I have to remember to disable 3D in Nvidia control panel every time I shut down, it is much faster for me to just unplug and plug back in after boot up.
I think what we are trying to figure out is why it is not functioning like it should and not require our intervention in any way or manner.
For me, right clicking, choosing NVidia control panel, and unchecking box, is easier/preferred than re-plugging cable, but at that point, it's just a personal preference. At least you would have the cause of the issue, which like you said, is what we were/are trying to determine.
Also, at that point, one could submit something along the lines of an official bug report like "Leaving Enable Stereoscopic 3D Checked Causes Emitter Failure On Subsequent Boots". This it seems, if it is the issue, is something that could easily be fixed in a future driver update, and in the meantime, you could possible just use a script like TsaebehT was offering above.
Same with my other Win7, non NVIDIA GPU PC, installs and then just shuts off.
The key is the same on my 3Dpc that's working fine.
Odd that on WinXP it stays on and on all the other Win7 (Non N'GPU) PCs that I've tried it shuts off, like it does to you ... well until you un/replug it in.
I removed the work around for now, I haven't heard that it stayed working for anyone even though it should have, makes no sense but I can't really test it to say otherwise.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Hi all, I have done all of the suggested workarounds mentioned in this post and I can say that I have still get the turn off issue , although when I leave my PC on "put into sleep mode" after 2hrs, I am getting a better success rate of the emitter staying on when I take the PC out of sleep. I will keep this up for a couple of days just to monitor.
P.S. I disabled the workaround .bat and the power management on that usb to not shut off as per mentioned by Spacemoss
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.
First shutdown restart cycle and the emitter failed. It went off at logon and restarted when I unplugged and replugged the emitter. Second and third shutdown restart cycles the emitter worked perfectly. Inconclusive, but so far I'm thinking it looks like a software problem. More data would be better. I'm going to continue moving the emitter over to the other machine for further tests. Is there anyone out there experiencing this problem who has access to a known working 3D setup who could do some testing? I'm actually hoping this is a driver problem and not hardware but I don't think any of us has really looked seriously at this possibility.
The second machine I used has 314.07 whql drivers. I think I've tried these drivers on my 3D machine before but I'll try again just to be sure. In the mean time like Gladjag I have been shutting down with hybrid sleep lately and the emitter has been behaving so far.
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Are there different versions of the emitter for 3D Vision vs 3D Vision 2? I think the model number isn't just P854, there's another number under the S/N, mine is:
942-10701-0005-401 J
Also the J seems like it might be a rev. I guess it's worth a shot posting them to see if there's a pattern. Maybe even Model, Mainboard and USB Host controller. Like this:
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Sticker # 942-11431-0007-001 G
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.
Sticker#: 942-11431-0007-001 G
ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit
Mine is the # 942-11431-0007-001 F.
Spacemoss, earlier in this thread I tried disabling "USB selective suspend setting" in the Power Settings for my computer ... this unchecks "Allow Computer to turn off device to save power" for all the USB root hubs, but it didn't work for me. Since you are seeing normal operation I went back and enabled "USB selective suspend setting" in the power settings and cleared "Allow Computer to turn off device to save power" in the Device Manager as you did, just in case there was a difference but I'm still not having any luck with my Emitter. Also, I'm not using any of the startup batch files as you suggested. Is there anything else you might have done? It's good to hear someone's Emitter is operating normally after experiencing this problem.
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]
Hmmmm, yah it's been another 2 reboots and I'm still working fine. The only things I did were: A)A fresh driver install and I checked the option to do "clean install", (didn't solve problem) B) The original script/task scheduler suggestion on page 4 (didn't solve problem - so I disabled the task and removed devcon folder), C) Did the power cycling once, where I actually unplugged power to the pc after it was shutdown and watched for emitter light blink(compared to just using PSU switch - Didn't solve problem), D)Checked, my BIOS for relevant settings (didn't have any), E)Did the Device Manager thing I suggested with allowing to turn off device.
As a side note, I had investigated my power setting options within the advanced power profiles, but didn't change any related to USB. In fact, my USB selective suspend is enabled, I left it on. From my limited reading and understanding, I'm not 100% sure that using USB selective suspend and Telling the Device manager hardware properties to not allow shutoff are exactly one and the same. I think the power management/selective suspend take advantage of 5 power states between fully-on and fully-off, while the device manager allow option is only referring to one of these states , the fully off one (S0 maybe?). However, that speculation is beyond my current purview.
The closest I can find is http://nvidia.custhelp.com/app/answers/detail/a_id/2617/~/3d-vision-equipment-list
So I decided that if changing the power settings in device manager was indeed the fix for me, then undoing the changes should bring back the problem, right... I undid the changes, once again allowing the machine to idle those device, and rebooted, and to my astonishment it was still working fine! However, this means the device manager options were not the problem. This lead me to further review anything at all that I had toggled during all these processes, and then I stumbled on it.
In the NVidia control panel, under the Set Up Stereoscopic 3D page, the first check box says "Enable Stereoscopic 3D". I had been leaving mine disabled, and only enabling it when I was using it. It was DISABLED during all my successful shutdowns/reboots. So I tried shutting down with it enabled and BAM problem was back ! Then I tried, unchecking again, and problem was still here....So, hmmmm, I tried all 4 combinations of having the device manager allowing USB device shutdown/not allowing it with enabled/disabled 3D in NVidia controls. That is, allowed-enabled, allowed-disabled, not allowed-enabled, and not allowed-disabled. I was able to get it working again, and tested it through a few reboots and its working fine ! Here's what you should try.
The Device manager USB power options have no effect on the problem at all so you can turn them back on. Leave the emitter enabled in NVidia controls for the moment.
Do a reboot/fresh boot.
After login the emitter should go black.
Unplug and re-plug the emitter into its USB port, it should be recognized/stay on.
In NVidia control panel uncheck "Enable Stereoscopic 3D" and apply/hit OK.
Reboot
After login it should still be there working fine...all you have to do is then go in and enable it!
Just remember to disable it before shutdown, or you'll need to repeat the above process.
So it seems the culprit for me at least is whether that check box is checked.
Let me know what you find!
That sounds like a good path, but to be honest, if I have to remember to disable 3D in Nvidia control panel every time I shut down, it is much faster for me to just unplug and plug back in after boot up.
I think what we are trying to figure out is why it is not functioning like it should and not require our intervention in any way or manner. I have tried all the workarounds mentioned in this post, they work a couple of times and the culprit goes back to shutting down right after windows is fully loaded.
I whish we would get some kind of feed back from Nvidia and it would be even nice if they decided to post here for everyone.
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.
Save as 3Dprompt.bat
This saves going into the control panel everytime. :D
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
For me, right clicking, choosing NVidia control panel, and unchecking box, is easier/preferred than re-plugging cable, but at that point, it's just a personal preference. At least you would have the cause of the issue, which like you said, is what we were/are trying to determine.
Also, at that point, one could submit something along the lines of an official bug report like "Leaving Enable Stereoscopic 3D Checked Causes Emitter Failure On Subsequent Boots". This it seems, if it is the issue, is something that could easily be fixed in a future driver update, and in the meantime, you could possible just use a script like TsaebehT was offering above.