Random BSOD (nvstusb.sys) and reboot when 3D vision usb controller is plugged and enabled
  3 / 3    
For the longest time my emitter wasn't going into sleep mode, not sure why... and then I had to restart Windows and it started going into sleep mode again and not long after the random BSODs started again... I've disabled 'selective suspend', as well as other power settings... apparently we just don't have control of our PCs anymore. Lol. I had a DevCon script I was using to turn it on before I'd run anything in 3D but after having multiple things open, editing, tinkering with 3D stuff and having it crap out on me randomly in the middle of it because I forgot to run a script made me look into and work on a Logon script that didn't require DevCon... Run gpedit.msc > User Config > Windows Settings > Scripts > Logon > Add > NvStUSB_NoDoz.vbs [img]http://www.computerperformance.co.uk/images/powershell/gpe.jpg[/img] Save as NvStUSB_NoDoz.vbs [code]Set objFS = CreateObject("Scripting.FileSystemObject") Set objFile = objFS.OpenTextFile(Wscript.ScriptFullName,8) Set objShell = CreateObject("WScript.Shell") Do objShell.Run "Powercfg.exe /DeviceEnableWake ""NVIDIA Stereoscopic 3D USB Controller""",0 WScript.Sleep(5*59*1000) Loop[/code] You can run it manually before you Logoff but from here on in it'll run automatically when you Logon... [s]just make sure it's only running once, either manually or at logon... because you can run multiple instances of it...[/s] The only way to stop it is to find it in the Task Manager and End Task, it shows up as Microsoft ® Windows Based Script Host(wscript*exe) or you can disable it using gpedit.msc/Logon and then Logoff/on again... /DeviceEnableWake is kind of a bogus option, it's not supported and errors out but it's hidden and the emitter wakes the ef up... Lol. Then the script sleeps for 5secs shy of 5min and 'nudges' the emitter again... and so on... edit:came up with a way to disable multiple instances...
For the longest time my emitter wasn't going into sleep mode, not sure why... and then I had to restart Windows and it started going into sleep mode again and not long after the random BSODs started again...

I've disabled 'selective suspend', as well as other power settings... apparently we just don't have control of our PCs anymore. Lol.

I had a DevCon script I was using to turn it on before I'd run anything in 3D but after having multiple things open, editing, tinkering with 3D stuff and having it crap out on me randomly in the middle of it because I forgot to run a script made me look into and work on a Logon script that didn't require DevCon...

Run gpedit.msc > User Config > Windows Settings > Scripts > Logon > Add > NvStUSB_NoDoz.vbs

Image

Save as NvStUSB_NoDoz.vbs

Set objFS = CreateObject("Scripting.FileSystemObject")
Set objFile = objFS.OpenTextFile(Wscript.ScriptFullName,8)
Set objShell = CreateObject("WScript.Shell")
Do
objShell.Run "Powercfg.exe /DeviceEnableWake ""NVIDIA Stereoscopic 3D USB Controller""",0
WScript.Sleep(5*59*1000)
Loop

You can run it manually before you Logoff but from here on in it'll run automatically when you Logon... just make sure it's only running once, either manually or at logon... because you can run multiple instances of it...

The only way to stop it is to find it in the Task Manager and End Task, it shows up as Microsoft ® Windows Based Script Host(wscript*exe) or you can disable it using gpedit.msc/Logon and then Logoff/on again...

/DeviceEnableWake is kind of a bogus option, it's not supported and errors out but it's hidden and the emitter wakes the ef up... Lol. Then the script sleeps for 5secs shy of 5min and 'nudges' the emitter again... and so on...

edit:came up with a way to disable multiple instances...
#31
Posted 04/13/2017 12:41 AM   
So it activates the emitter every 5 minutes ? Are you certain that the emitter goes offline only after 5 min ? From my experience it seems that it randomly turns itself off sometimes in 20 seconds, other times after 5 or more minutes and occasionally it doesn't power down at all. Not sure why that happens but I've been struggling to find out how to keep it always on to no avail. Either way, much thanks for this script.
So it activates the emitter every 5 minutes ? Are you certain that the emitter goes offline only after 5 min ? From my experience it seems that it randomly turns itself off sometimes in 20 seconds, other times after 5 or more minutes and occasionally it doesn't power down at all. Not sure why that happens but I've been struggling to find out how to keep it always on to no avail.
Either way, much thanks for this script.

#32
Posted 04/13/2017 03:42 AM   
On mine it's like clockwork every 5min the LED blinks bright a few times and then goes out... I'd give it a try, run it manually and see if it works for you... maybe it'll 'stabilize' whatever's being wonky there? If not, you can edit the time between it firing in line 4, the [color="orange"]*[/color] multiples... [color="orange"]5[/color](Min) x [color="orange"]60[/color](Sec) x [color="orange"]1000[/color](Ms) = 300000 or 5min, it'll accept either an expression([color="orange"]5*59*1000[/color]) or a value in ms([color="orange"]295000[/color])... 4min = 240000, 2min = 120000, 1min = 60000, etc... WScript.Sleep([color="orange"]OnlyEditThis[/color]) Just be careful, with a value too low and/or without that line at all it'll bring your system to it's knees ...and you really wouldn't want that happening at Logon. :)
On mine it's like clockwork every 5min the LED blinks bright a few times and then goes out... I'd give it a try, run it manually and see if it works for you... maybe it'll 'stabilize' whatever's being wonky there?

If not, you can edit the time between it firing in line 4, the * multiples... 5(Min) x 60(Sec) x 1000(Ms) = 300000 or 5min, it'll accept either an expression(5*59*1000) or a value in ms(295000)... 4min = 240000, 2min = 120000, 1min = 60000, etc...

WScript.Sleep(OnlyEditThis)

Just be careful, with a value too low and/or without that line at all it'll bring your system to it's knees ...and you really wouldn't want that happening at Logon. :)
#33
Posted 04/13/2017 02:49 PM   
Thanks for the additional info tho I won't be running the script at Logon for sure. Anwyay it seems like the emitter is no longer turning off but I guess I'll have to check on it more often. Will report back if anything changes :)
Thanks for the additional info tho I won't be running the script at Logon for sure.
Anwyay it seems like the emitter is no longer turning off but I guess I'll have to check on it more often. Will report back if anything changes :)

#34
Posted 04/14/2017 12:41 AM   
[quote="SkySolstice"]I use to have this problem. Between installing a new videocard for physx and reinstalling both videocards and also now using this 378.72 driver, I now do not have that nvst usb crash anymore. I may have moved my emitter to a different slot in this process too. It was fixed within the last weeks for me.[/quote] Going back to this post, I found out if I remove the GTX 670 Physx videocard, the emitter will go into sleep mode after a few minutes. So no specific driver fixed this, it was my configuration that masked the problem. I believe if you have this configuration where you have a secondary videocard to use as physx, this should prevent the emitter from going into standby in the meantime. Does anyone have an extra videocard to check these results? I sent a report to nvidia, so hopefully they can reproduce this.
SkySolstice said:I use to have this problem. Between installing a new videocard for physx and reinstalling both videocards and also now using this 378.72 driver, I now do not have that nvst usb crash anymore.

I may have moved my emitter to a different slot in this process too.

It was fixed within the last weeks for me.


Going back to this post, I found out if I remove the GTX 670 Physx videocard, the emitter will go into sleep mode after a few minutes. So no specific driver fixed this, it was my configuration that masked the problem.

I believe if you have this configuration where you have a secondary videocard to use as physx, this should prevent the emitter from going into standby in the meantime.

Does anyone have an extra videocard to check these results?

I sent a report to nvidia, so hopefully they can reproduce this.

3D Vision/TRIDEF User
SHIELD portable/tablet/tv

#35
Posted 04/20/2017 02:14 PM   
I've had this BSOD issue for over a year now, never thought it was 3D vision related so I only just found this topic. Anyhow I'll try the script to keep the emitter from sleeping and see if that fixes the problem for me. Another thing I've noticed is that my PC takes a long time to shut down when I have 3D vision enabled, when I disable it however it shuts down in a couple of seconds. Anyone else noticing this? Some info about my setup: I had the problem when I upgraded from windows 8 to windows 10 on my old 980 TI card, even when I reinstalled windows 10 a couple of months ago the problem persisted. I did notice that it had something to do with 3D vision as I had it disabled for a while and then I didn't get any BSODs.. However I thought the BSODs were to do with my 980 TI card, maybe an unstable overclock, but a few days ago I upgraded to a 1080 TI and still got BSODs.. And then I found this topic. I've also noticed that the BSODs frequently happen when I start firefox, often after playing a 3D game, but sometimes even when I play a 3D game, then restart the PC and then open firefox... Other times it happens when I start a 3D game as others have reported as well.
I've had this BSOD issue for over a year now, never thought it was 3D vision related so I only just found this topic. Anyhow I'll try the script to keep the emitter from sleeping and see if that fixes the problem for me.

Another thing I've noticed is that my PC takes a long time to shut down when I have 3D vision enabled, when I disable it however it shuts down in a couple of seconds. Anyone else noticing this?

Some info about my setup: I had the problem when I upgraded from windows 8 to windows 10 on my old 980 TI card, even when I reinstalled windows 10 a couple of months ago the problem persisted. I did notice that it had something to do with 3D vision as I had it disabled for a while and then I didn't get any BSODs.. However I thought the BSODs were to do with my 980 TI card, maybe an unstable overclock, but a few days ago I upgraded to a 1080 TI and still got BSODs.. And then I found this topic.

I've also noticed that the BSODs frequently happen when I start firefox, often after playing a 3D game, but sometimes even when I play a 3D game, then restart the PC and then open firefox... Other times it happens when I start a 3D game as others have reported as well.

Nvidia 3D Surround | 3x ASUS VG248QE
Gigabyte AORUS GeForce GTX 1080 Ti
Intel i5-3570K @ 4.3 GHz

#36
Posted 04/30/2017 08:24 PM   
Seems the script fixed it, haven't had a BSOD since I installed it (currently over two weeks). Thanks a lot! :D
Seems the script fixed it, haven't had a BSOD since I installed it (currently over two weeks). Thanks a lot! :D

Nvidia 3D Surround | 3x ASUS VG248QE
Gigabyte AORUS GeForce GTX 1080 Ti
Intel i5-3570K @ 4.3 GHz

#37
Posted 05/17/2017 08:26 PM   
Yeah big up for TsaebehT ! The emitter is no longer powering down and I haven't had any BSOD since. :]
Yeah big up for TsaebehT !

The emitter is no longer powering down and I haven't had any BSOD since. :]

#38
Posted 05/17/2017 08:47 PM   
  3 / 3    
Scroll To Top