Random BSOD's
I've been having this problem ever since installing and using the 3D Vision Kit 2. There does not seem to be a specific trigger for these crashes/BSOD's other than launching a game with 3D turned on. Every 3rd or 4th launch, it'll give me a BSOD, no matter what game it is. And the most common one is this IRQL_Not_Less_Or_equal one. I posted about this a while back but never found any solution. Crash dump points directly to this driver for each one "nvstusb.sys (Stereoscopic 3D USB controller driver, NVIDIA Corporation)" and recommends that I update it. This also happened on Win 7 before I updated to 10. Unless there's some super secret update for that driver hidden in the deepest trenches of the internet, i'm convinced that there isn't one. Cause I've damn sure looked lol. And of course I've tried re-installing everything, multiple times. Still happens. Happens when the transmitter is in different ports too, 2.0 and 3.0, doesn't seem to matter. This is honestly why I stopped using it for a while, which is a shame considering how much I paid for it. When it works it's awesome. But it's extremely annoying and difficult to troubleshoot and tweak games for 3D use when I get a BSOD just about every other launch. I've had 5 recent ones trying to get the FFX remaster running in 3D nicely. I'm (about to) attach the crash dump here (screw it, imgur link included, attachment system is not working), and I would greatly appreciate any advice! http://imgur.com/a/iEdGK Additional info if needed: Win 10 Pro AOC Nvidia G-sync monitor AMD FX-6300 CPU EVGA 980 FTW edition Gigabyte UDA-990 MOBO (revision 3)
I've been having this problem ever since installing and using the 3D Vision Kit 2. There does not seem to be a specific trigger for these crashes/BSOD's other than launching a game with 3D turned on. Every 3rd or 4th launch, it'll give me a BSOD, no matter what game it is. And the most common one is this IRQL_Not_Less_Or_equal one. I posted about this a while back but never found any solution.

Crash dump points directly to this driver for each one "nvstusb.sys (Stereoscopic 3D USB controller driver, NVIDIA Corporation)" and recommends that I update it. This also happened on Win 7 before I updated to 10.

Unless there's some super secret update for that driver hidden in the deepest trenches of the internet, i'm convinced that there isn't one. Cause I've damn sure looked lol. And of course I've tried re-installing everything, multiple times. Still happens. Happens when the transmitter is in different ports too, 2.0 and 3.0, doesn't seem to matter.

This is honestly why I stopped using it for a while, which is a shame considering how much I paid for it. When it works it's awesome. But it's extremely annoying and difficult to troubleshoot and tweak games for 3D use when I get a BSOD just about every other launch.

I've had 5 recent ones trying to get the FFX remaster running in 3D nicely. I'm (about to) attach the crash dump here (screw it, imgur link included, attachment system is not working), and I would greatly appreciate any advice!

http://imgur.com/a/iEdGK

Additional info if needed:
Win 10 Pro
AOC Nvidia G-sync monitor
AMD FX-6300 CPU
EVGA 980 FTW edition
Gigabyte UDA-990 MOBO (revision 3)
Attachments

c1.jpg

c2.jpg

c3.jpg

#1
Posted 05/14/2016 08:59 PM   
Hmmm, interesting, I've been getting the same "IRQL_Not_Less_Or_equal" crash upon shut downs and restarts periodically for the past month or so. I kept meaning to investigate it further, but given it would happen upon shutting down I would forget about it by the next time I turned on my computer. It also wasn't as frequent as yours to make it more of a pressing concern. But at least I can confirm it's happening to me too, and our only common factor being Nvidia cards/3D Vision, and Win 10. Please update this post if you find anything. Also, the attach button only appears after you've posted, it'll be on the upper right corner of your message when you put your mouse cursor over your message. Looks like a paper clip.
Hmmm, interesting, I've been getting the same "IRQL_Not_Less_Or_equal" crash upon shut downs and restarts periodically for the past month or so. I kept meaning to investigate it further, but given it would happen upon shutting down I would forget about it by the next time I turned on my computer. It also wasn't as frequent as yours to make it more of a pressing concern. But at least I can confirm it's happening to me too, and our only common factor being Nvidia cards/3D Vision, and Win 10. Please update this post if you find anything.

Also, the attach button only appears after you've posted, it'll be on the upper right corner of your message when you put your mouse cursor over your message. Looks like a paper clip.

3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot

Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king

#2
Posted 05/14/2016 09:04 PM   
It literally only happens when I try to launch a game with 3D Vision turned on. Sometimes on the second launch, sometimes on the 4th launch. It's really strange lol
It literally only happens when I try to launch a game with 3D Vision turned on. Sometimes on the second launch, sometimes on the 4th launch. It's really strange lol

#3
Posted 05/14/2016 09:14 PM   
Windows Insiders Builds have QR codes added to the BSOD that you can take a pic of with your phone, which can then be used to access troubleshooting. It's expected that Microsoft might bring the feature to all Windows 10 users in a future update. http://home.bt.com/tech-gadgets/tech-news/microsoft-windows-10-blues-screen-of-death-qr-code-11364051585167
Windows Insiders Builds have QR codes added to the BSOD that you can take a pic of with your phone, which can then be used to access troubleshooting.

It's expected that Microsoft might bring the feature to all Windows 10 users in a future update.

http://home.bt.com/tech-gadgets/tech-news/microsoft-windows-10-blues-screen-of-death-qr-code-11364051585167

#4
Posted 05/14/2016 10:52 PM   
Scroll To Top