Random BSOD (nvstusb.sys) and reboot when 3D vision usb controller is plugged and enabled
2 / 3
Make sure the emitter's light is on when you do anything related to 3D vision (enabling/disabling 3D in CP or in any application) and remove any Power Saving option in Windows. Also, web browsers tend to crash the system when 3D vision is enabled. For more info you might want to check out the last pages of these threads:
https://forums.geforce.com/default/topic/490441/3d-vision/3d-emitter-turns-off
https://forums.geforce.com/default/topic/971868/3d-vision/pc-crash-everytime-i-enable-3d-vision-with-windows-10
One more thing you could try is use DDU (Display Driver Uninstaller) in Safe Mode since you shouldn't be getting any BSOD while in a game. In any case I suggest watching the emitter's light and see if it goes off before a BSOD occurs and maybe do some drive scans for corrupted files although DDU should take care of any nVidia driver corruptions.
One more thing you could try is use DDU (Display Driver Uninstaller) in Safe Mode since you shouldn't be getting any BSOD while in a game. In any case I suggest watching the emitter's light and see if it goes off before a BSOD occurs and maybe do some drive scans for corrupted files although DDU should take care of any nVidia driver corruptions.
[quote="Kaimastah"]Make sure the emitter's light is on when you do anything related to 3D vision (enabling/disabling 3D in CP or in any application) and remove any Power Saving option in Windows. Also, web browsers tend to crash the system when 3D vision is enabled. For more info you might want to check out the last pages of these threads:
https://forums.geforce.com/default/topic/490441/3d-vision/3d-emitter-turns-off
https://forums.geforce.com/default/topic/971868/3d-vision/pc-crash-everytime-i-enable-3d-vision-with-windows-10
One more thing you could try is use DDU (Display Driver Uninstaller) in Safe Mode since you shouldn't be getting any BSOD while in a game. In any case I suggest watching the emitter's light and see if it goes off before a BSOD occurs and maybe do some drive scans for corrupted files although DDU should take care of any nVidia driver corruptions.[/quote]
I got the crash a few times while in game, The light was on and lit, 3d was working as I had the glasses on.
It was WOW, I opened the map, pressing M, immediate bsod. Ive had a bsod while opening the wow map before, usually related to not rebooting often enough and probably a low gpu ram issue due to my insane tabs open.
It also bsod randomly once too while enabling/ disabling 3d in the game because I had reset the driver.
Like I said. I do have 100 chrome tabs open all the time though.
I opened FF thinking, aha chrome you won't bsod me, them boom, immediately as I clicked FF bsod, same crash location from the call in the 3d hub driver. Prolly the hub was not on, though I did have 3d mode on.
I need to keep the 3d mode enabled when browsing as my monitor has a Extreme ghosting issue (to the point unusable) when lightboost is off, and its only on in 3d mode. So I don't know what to do here. I can't keep unplugging my 3d hub every 10 minutes to keep it active if that is the issue.
-
So since my last post, I did a clean install of the nvidia drivers. updated windows, and having some other usb related issue strangely when updating my drivers directly from my mobo's website for windows 10 drivers.
I'll look into writing an app that will query the usb device, hopefully keeping it on.
-update
The w10 wdk has a usb view tool, if you open it and refresh the NVIDIA Stereoscopic 3D USB controller it will stay on. There is source for it, so I think I can modify it to query the device every 4 minutes (mine stays on for 5 minutes before turning off)
One more thing you could try is use DDU (Display Driver Uninstaller) in Safe Mode since you shouldn't be getting any BSOD while in a game. In any case I suggest watching the emitter's light and see if it goes off before a BSOD occurs and maybe do some drive scans for corrupted files although DDU should take care of any nVidia driver corruptions.
I got the crash a few times while in game, The light was on and lit, 3d was working as I had the glasses on.
It was WOW, I opened the map, pressing M, immediate bsod. Ive had a bsod while opening the wow map before, usually related to not rebooting often enough and probably a low gpu ram issue due to my insane tabs open.
It also bsod randomly once too while enabling/ disabling 3d in the game because I had reset the driver.
Like I said. I do have 100 chrome tabs open all the time though.
I opened FF thinking, aha chrome you won't bsod me, them boom, immediately as I clicked FF bsod, same crash location from the call in the 3d hub driver. Prolly the hub was not on, though I did have 3d mode on.
I need to keep the 3d mode enabled when browsing as my monitor has a Extreme ghosting issue (to the point unusable) when lightboost is off, and its only on in 3d mode. So I don't know what to do here. I can't keep unplugging my 3d hub every 10 minutes to keep it active if that is the issue.
-
So since my last post, I did a clean install of the nvidia drivers. updated windows, and having some other usb related issue strangely when updating my drivers directly from my mobo's website for windows 10 drivers.
I'll look into writing an app that will query the usb device, hopefully keeping it on.
-update
The w10 wdk has a usb view tool, if you open it and refresh the NVIDIA Stereoscopic 3D USB controller it will stay on. There is source for it, so I think I can modify it to query the device every 4 minutes (mine stays on for 5 minutes before turning off)
The 3D emitter should never turn itself off when you have 3D enabled in the CP. From what you said I'm pretty sure the BSOD occurs due to the browser being open. I'm not sure how you can fix that but I've seen some people talking about disabling the 3D profile for Chrome or Firefox. If you don't find any solution I guess you'd have to turn off Hardware Acceleration in your browser. Personally I just close the browser when gaming in 3D.
Also what kind of monitor do you have ? The ghosting might be caused by a monitor setting. For example on my Asus monitor I have a setting called Trace Free that reduces ghosting but if you turn it up too much another issue might appear called inverse ghosting which is even worse. So in my case I need to set it at 40-60%.
The 3D emitter should never turn itself off when you have 3D enabled in the CP. From what you said I'm pretty sure the BSOD occurs due to the browser being open. I'm not sure how you can fix that but I've seen some people talking about disabling the 3D profile for Chrome or Firefox. If you don't find any solution I guess you'd have to turn off Hardware Acceleration in your browser. Personally I just close the browser when gaming in 3D.
Also what kind of monitor do you have ? The ghosting might be caused by a monitor setting. For example on my Asus monitor I have a setting called Trace Free that reduces ghosting but if you turn it up too much another issue might appear called inverse ghosting which is even worse. So in my case I need to set it at 40-60%.
Well, the emitter turns its self off after 5 minutes unless the game or movie has [b]active[/b] 3d content.
3d mode can still be on without that content (aka the refresh rate setting enabled by the switch to 3d), which is what I need to get rid of the ghosting.
Its an Acer G246HL. There are no other settings for ghosting, I couldn't afford an expensive asus monitor.
Googleing Acer G246HL ghosting fixe led me to the fact that when lightboost is on, ghosting is 95% gone, and is then a great monitor. I ran some program that added modified refresh rates with the lightboost (strobing) enabled.
I re-read the articles I found, and I managed to create my own 100 & 119hz refresh rate with it enabling lightboost. I have the standard 120 also.
I havent re-enabled 3d on the CP yet since I've been writing that user mode usb driver to keep the hub powered on. But I'll test things out, ideally it will switch out of 119 back to the normal 120hz when the game wants 3d content, as the modified 119hz refresh rate will make nvidia display a red error box over your screen if a game tries 3d content (Something about not being in a 3d refresh rate).
--
So besides, the fact that I had used a bug to keep the monitor in 3d mode might of been contributing to my crashes. I didnt get the crashes when I had the modified refresh rate profiles added to begin with (before I got my 3d kit)
I had to get rid of those when I got my kit, due to the aforementioned error. The app I used removed the normal profiles, so now I have my own profiles I made in the CP, so that should help me, I can switch out to normal for when I want 3d content. The hub might also be the issue, hence me writing something to keep it on, which I am half done with.
I feel like this is bit much to read, but I'll post back with any findings, and a link to the app to keep your hub powered on if I get this to work.
Well, the emitter turns its self off after 5 minutes unless the game or movie has active 3d content.
3d mode can still be on without that content (aka the refresh rate setting enabled by the switch to 3d), which is what I need to get rid of the ghosting.
Its an Acer G246HL. There are no other settings for ghosting, I couldn't afford an expensive asus monitor.
Googleing Acer G246HL ghosting fixe led me to the fact that when lightboost is on, ghosting is 95% gone, and is then a great monitor. I ran some program that added modified refresh rates with the lightboost (strobing) enabled.
I re-read the articles I found, and I managed to create my own 100 & 119hz refresh rate with it enabling lightboost. I have the standard 120 also.
I havent re-enabled 3d on the CP yet since I've been writing that user mode usb driver to keep the hub powered on. But I'll test things out, ideally it will switch out of 119 back to the normal 120hz when the game wants 3d content, as the modified 119hz refresh rate will make nvidia display a red error box over your screen if a game tries 3d content (Something about not being in a 3d refresh rate).
--
So besides, the fact that I had used a bug to keep the monitor in 3d mode might of been contributing to my crashes. I didnt get the crashes when I had the modified refresh rate profiles added to begin with (before I got my 3d kit)
I had to get rid of those when I got my kit, due to the aforementioned error. The app I used removed the normal profiles, so now I have my own profiles I made in the CP, so that should help me, I can switch out to normal for when I want 3d content. The hub might also be the issue, hence me writing something to keep it on, which I am half done with.
I feel like this is bit much to read, but I'll post back with any findings, and a link to the app to keep your hub powered on if I get this to work.
The emitter should turn itself off if you have 3D vision disabled in the CP since it is controlled by an nVidia service and no matter what you do, it will eventually turn itself off.
If it's like you mentioned and the emitter turns off after 5 minutes while having 3D enabled in the CP then that is another issue which I hope you can solve with your workaround although most probably it's a Windows Power Saving setting that you missed.
Regarding the crashes, the thing is that you're not the only one experiencing those and the monitor or refresh rate does not matter from what I've read.
Since there have been many reports about browsers crashing the system while 3D is enabled in the CP, the first thing I would do is check if you're still getting crashes without having Chrome or Firefox in the background. You should eliminate that factor first imo.
Also did you use DDU before installing the nVidia drivers ? The "Perform a clean installation" checkbox in the nVidia installer is not enough to fix any corrupted drivers.
The emitter should turn itself off if you have 3D vision disabled in the CP since it is controlled by an nVidia service and no matter what you do, it will eventually turn itself off.
If it's like you mentioned and the emitter turns off after 5 minutes while having 3D enabled in the CP then that is another issue which I hope you can solve with your workaround although most probably it's a Windows Power Saving setting that you missed.
Regarding the crashes, the thing is that you're not the only one experiencing those and the monitor or refresh rate does not matter from what I've read.
Since there have been many reports about browsers crashing the system while 3D is enabled in the CP, the first thing I would do is check if you're still getting crashes without having Chrome or Firefox in the background. You should eliminate that factor first imo.
Also did you use DDU before installing the nVidia drivers ? The "Perform a clean installation" checkbox in the nVidia installer is not enough to fix any corrupted drivers.
It turns itself off when 3d vision is enabled in the CP. I've checked every power saving feature I could find in windows 10. It just turns itself off if there is no 3d activity. which is the majority of the case since I don't game that often, and closing chrome is not an option. I'm working when ever I'm not spending a little break time on a game or something.
(There are also no named services in Services that relate to 3d vision)
If I got to modify the nvusb driver to walk over the effected call, I can. But thats a bit of work. and installing the modified driver is another issue.
If I can program my way to a crash free system, I'll try, since nvidia doesn't seem to want to bother.
It turns itself off when 3d vision is enabled in the CP. I've checked every power saving feature I could find in windows 10. It just turns itself off if there is no 3d activity. which is the majority of the case since I don't game that often, and closing chrome is not an option. I'm working when ever I'm not spending a little break time on a game or something.
(There are also no named services in Services that relate to 3d vision)
If I got to modify the nvusb driver to walk over the effected call, I can. But thats a bit of work. and installing the modified driver is another issue.
If I can program my way to a crash free system, I'll try, since nvidia doesn't seem to want to bother.
I've been getting the same random nvstusb.sys BSODs on my Win10 rig ever since I got a 3D Vision monitor for it, I've been trying to find a way to replicate it consistently but it really seems random... annoying af.
[I'm also getting the 'no matter what I set the Advanced Power Settings to the emitter goes to sleep after 5mins' issue]
I did notice one thing that seemed a little odd, in the Device Manager under NVIDIA Stereoscopic 3d USB Controller > Properties > Events there was a Device Not Migrated entry... not sure what it means exactly but Googling it seemed to pull up a lot of devices not installing/working properly.
I've been getting the same random nvstusb.sys BSODs on my Win10 rig ever since I got a 3D Vision monitor for it, I've been trying to find a way to replicate it consistently but it really seems random... annoying af.
[I'm also getting the 'no matter what I set the Advanced Power Settings to the emitter goes to sleep after 5mins' issue]
I did notice one thing that seemed a little odd, in the Device Manager under NVIDIA Stereoscopic 3d USB Controller > Properties > Events there was a Device Not Migrated entry... not sure what it means exactly but Googling it seemed to pull up a lot of devices not installing/working properly.
I don't understand why nVidia is not looking into this issue because that's clearly a stupid bug in nvstusb.sys which can't handle itself correctly when the device auto-poweroff has been triggered...
Does anyone know of a procedure to escalate such an issue so that someone at nVidia will look into it?
I've completely stopped 3d gaming to avoid this issue...
I don't understand why nVidia is not looking into this issue because that's clearly a stupid bug in nvstusb.sys which can't handle itself correctly when the device auto-poweroff has been triggered...
Does anyone know of a procedure to escalate such an issue so that someone at nVidia will look into it?
I've completely stopped 3d gaming to avoid this issue...
[quote="2072"]I don't understand why nVidia is not looking into this issue because that's clearly a stupid bug in nvstusb.sys which can't handle itself correctly when the device auto-poweroff has been triggered...
Does anyone know of a procedure to escalate such an issue so that someone at nVidia will look into it?
I've completely stopped 3d gaming to avoid this issue...[/quote]
You need to report this as a bug to NVidia. They won't work on stuff they don't know about, and no one from NVidia monitors these forums.
I'm not clear on whether anyone has filed a bug report for this yet.
2072 said:I don't understand why nVidia is not looking into this issue because that's clearly a stupid bug in nvstusb.sys which can't handle itself correctly when the device auto-poweroff has been triggered...
Does anyone know of a procedure to escalate such an issue so that someone at nVidia will look into it?
I've completely stopped 3d gaming to avoid this issue...
You need to report this as a bug to NVidia. They won't work on stuff they don't know about, and no one from NVidia monitors these forums.
I'm not clear on whether anyone has filed a bug report for this yet.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
Are you guys still having this issue? I haven't had a BSOD in quite awhile... I was also having an issue of the PC not waking from sleep/locking up and I tried the fix for that, not sure if they had anything to do with each other or not but I thought I'd mention it just in case.
The fix was [color="orange"]powercfg -h off[/color] at an elevated Command Prompt, right-click Start and select Command Prompt (Admin). This turns hibernation off and even though it was never enabled and I didn't even have the option on the Start Menu to put it into hibernation, it seems to have fixed the waking from sleep issue... and possibly even the BSOD, I might have had to restart Windows.
Again I'm not sure if this did the trick, watch I'll get one right after I post this... Lol... but the PC and emitter have been sleeping and waking properly for a week or two now... *knocks on wood*
Are you guys still having this issue? I haven't had a BSOD in quite awhile... I was also having an issue of the PC not waking from sleep/locking up and I tried the fix for that, not sure if they had anything to do with each other or not but I thought I'd mention it just in case.
The fix was powercfg -h off at an elevated Command Prompt, right-click Start and select Command Prompt (Admin). This turns hibernation off and even though it was never enabled and I didn't even have the option on the Start Menu to put it into hibernation, it seems to have fixed the waking from sleep issue... and possibly even the BSOD, I might have had to restart Windows.
Again I'm not sure if this did the trick, watch I'll get one right after I post this... Lol... but the PC and emitter have been sleeping and waking properly for a week or two now... *knocks on wood*
I haven't used it in a while. Latest nvidia drivers broke my games, so there would be no change from before. I doubt it's been fixed.
The ultimate cause of the bsod is an invalid handle being passed to IoCancelIRP. It's both m$ and nvidia's fault, for not testing the handle for a null ptr and nvidia for passing it. I sent some message to Microsoft detailing the issue, didnt get a reply. ~~ just checked ntsokrnl, still no check there, so it would still give my bsods. I havent had the time to use it. When I do, I'll just have to make sure to close my important applications in advance so I don't lose my work randomly while trying to game in 3d. I wish I would have known about this before I spent about 300$ specifically for 3d effects in movies, and small part in gaming.
I haven't used it in a while. Latest nvidia drivers broke my games, so there would be no change from before. I doubt it's been fixed.
The ultimate cause of the bsod is an invalid handle being passed to IoCancelIRP. It's both m$ and nvidia's fault, for not testing the handle for a null ptr and nvidia for passing it. I sent some message to Microsoft detailing the issue, didnt get a reply. ~~ just checked ntsokrnl, still no check there, so it would still give my bsods. I havent had the time to use it. When I do, I'll just have to make sure to close my important applications in advance so I don't lose my work randomly while trying to game in 3d. I wish I would have known about this before I spent about 300$ specifically for 3d effects in movies, and small part in gaming.
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.
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.
I am experiencing exactly the same problem here and it seems we are not so few anymore.
I get this random BSOD (often different error messages) just when the 3D stereo would start. Games or even browser displaying videos full screen.
For some unfathomable reason, nVidia in its wisdom makes the emitter turn itself on even when watching non 3D content.
The BSOD are very frequent for me and as annoying as hell.
I am using the latest drivers so obviously they problem has never been fixed nor addressed.
the workaround is here.. if the NVidia emitter turns off and you try and activated a S3D Game the PC will BSOD.. you need to first wake the Emitter either start HWInfo64 or go control panel and open Device and printers to turn on the emitter..
It is a PITA but for now the only workaround..
the workaround is here.. if the NVidia emitter turns off and you try and activated a S3D Game the PC will BSOD.. you need to first wake the Emitter either start HWInfo64 or go control panel and open Device and printers to turn on the emitter..
https://forums.geforce.com/default/topic/490441/3d-vision/3d-emitter-turns-off
https://forums.geforce.com/default/topic/971868/3d-vision/pc-crash-everytime-i-enable-3d-vision-with-windows-10
One more thing you could try is use DDU (Display Driver Uninstaller) in Safe Mode since you shouldn't be getting any BSOD while in a game. In any case I suggest watching the emitter's light and see if it goes off before a BSOD occurs and maybe do some drive scans for corrupted files although DDU should take care of any nVidia driver corruptions.
I got the crash a few times while in game, The light was on and lit, 3d was working as I had the glasses on.
It was WOW, I opened the map, pressing M, immediate bsod. Ive had a bsod while opening the wow map before, usually related to not rebooting often enough and probably a low gpu ram issue due to my insane tabs open.
It also bsod randomly once too while enabling/ disabling 3d in the game because I had reset the driver.
Like I said. I do have 100 chrome tabs open all the time though.
I opened FF thinking, aha chrome you won't bsod me, them boom, immediately as I clicked FF bsod, same crash location from the call in the 3d hub driver. Prolly the hub was not on, though I did have 3d mode on.
I need to keep the 3d mode enabled when browsing as my monitor has a Extreme ghosting issue (to the point unusable) when lightboost is off, and its only on in 3d mode. So I don't know what to do here. I can't keep unplugging my 3d hub every 10 minutes to keep it active if that is the issue.
-
So since my last post, I did a clean install of the nvidia drivers. updated windows, and having some other usb related issue strangely when updating my drivers directly from my mobo's website for windows 10 drivers.
I'll look into writing an app that will query the usb device, hopefully keeping it on.
-update
The w10 wdk has a usb view tool, if you open it and refresh the NVIDIA Stereoscopic 3D USB controller it will stay on. There is source for it, so I think I can modify it to query the device every 4 minutes (mine stays on for 5 minutes before turning off)
Also what kind of monitor do you have ? The ghosting might be caused by a monitor setting. For example on my Asus monitor I have a setting called Trace Free that reduces ghosting but if you turn it up too much another issue might appear called inverse ghosting which is even worse. So in my case I need to set it at 40-60%.
3d mode can still be on without that content (aka the refresh rate setting enabled by the switch to 3d), which is what I need to get rid of the ghosting.
Its an Acer G246HL. There are no other settings for ghosting, I couldn't afford an expensive asus monitor.
Googleing Acer G246HL ghosting fixe led me to the fact that when lightboost is on, ghosting is 95% gone, and is then a great monitor. I ran some program that added modified refresh rates with the lightboost (strobing) enabled.
I re-read the articles I found, and I managed to create my own 100 & 119hz refresh rate with it enabling lightboost. I have the standard 120 also.
I havent re-enabled 3d on the CP yet since I've been writing that user mode usb driver to keep the hub powered on. But I'll test things out, ideally it will switch out of 119 back to the normal 120hz when the game wants 3d content, as the modified 119hz refresh rate will make nvidia display a red error box over your screen if a game tries 3d content (Something about not being in a 3d refresh rate).
--
So besides, the fact that I had used a bug to keep the monitor in 3d mode might of been contributing to my crashes. I didnt get the crashes when I had the modified refresh rate profiles added to begin with (before I got my 3d kit)
I had to get rid of those when I got my kit, due to the aforementioned error. The app I used removed the normal profiles, so now I have my own profiles I made in the CP, so that should help me, I can switch out to normal for when I want 3d content. The hub might also be the issue, hence me writing something to keep it on, which I am half done with.
I feel like this is bit much to read, but I'll post back with any findings, and a link to the app to keep your hub powered on if I get this to work.
If it's like you mentioned and the emitter turns off after 5 minutes while having 3D enabled in the CP then that is another issue which I hope you can solve with your workaround although most probably it's a Windows Power Saving setting that you missed.
Regarding the crashes, the thing is that you're not the only one experiencing those and the monitor or refresh rate does not matter from what I've read.
Since there have been many reports about browsers crashing the system while 3D is enabled in the CP, the first thing I would do is check if you're still getting crashes without having Chrome or Firefox in the background. You should eliminate that factor first imo.
Also did you use DDU before installing the nVidia drivers ? The "Perform a clean installation" checkbox in the nVidia installer is not enough to fix any corrupted drivers.
(There are also no named services in Services that relate to 3d vision)
If I got to modify the nvusb driver to walk over the effected call, I can. But thats a bit of work. and installing the modified driver is another issue.
If I can program my way to a crash free system, I'll try, since nvidia doesn't seem to want to bother.
[I'm also getting the 'no matter what I set the Advanced Power Settings to the emitter goes to sleep after 5mins' issue]
I did notice one thing that seemed a little odd, in the Device Manager under NVIDIA Stereoscopic 3d USB Controller > Properties > Events there was a Device Not Migrated entry... not sure what it means exactly but Googling it seemed to pull up a lot of devices not installing/working properly.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Does anyone know of a procedure to escalate such an issue so that someone at nVidia will look into it?
I've completely stopped 3d gaming to avoid this issue...
You need to report this as a bug to NVidia. They won't work on stuff they don't know about, and no one from NVidia monitors these forums.
I'm not clear on whether anyone has filed a bug report for this yet.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
The fix was powercfg -h off at an elevated Command Prompt, right-click Start and select Command Prompt (Admin). This turns hibernation off and even though it was never enabled and I didn't even have the option on the Start Menu to put it into hibernation, it seems to have fixed the waking from sleep issue... and possibly even the BSOD, I might have had to restart Windows.
Again I'm not sure if this did the trick, watch I'll get one right after I post this... Lol... but the PC and emitter have been sleeping and waking properly for a week or two now... *knocks on wood*
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
The ultimate cause of the bsod is an invalid handle being passed to IoCancelIRP. It's both m$ and nvidia's fault, for not testing the handle for a null ptr and nvidia for passing it. I sent some message to Microsoft detailing the issue, didnt get a reply. ~~ just checked ntsokrnl, still no check there, so it would still give my bsods. I havent had the time to use it. When I do, I'll just have to make sure to close my important applications in advance so I don't lose my work randomly while trying to game in 3d. I wish I would have known about this before I spent about 300$ specifically for 3d effects in movies, and small part in gaming.
I may have moved my emitter to a different slot in this process too.
It was fixed within the last weeks for me.
3D Vision/TRIDEF User
SHIELD portable/tablet/tv
I get this random BSOD (often different error messages) just when the 3D stereo would start. Games or even browser displaying videos full screen.
For some unfathomable reason, nVidia in its wisdom makes the emitter turn itself on even when watching non 3D content.
The BSOD are very frequent for me and as annoying as hell.
I am using the latest drivers so obviously they problem has never been fixed nor addressed.
It is a PITA but for now the only workaround..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
3D Vision/TRIDEF User
SHIELD portable/tablet/tv