PC Crash everytime I enable 3d vision with windows 10
  3 / 3    
Well it's really shitty to have to go through these annoying procedures every time. I guess I'm "lucky" that I only need that HWINFO64 program to get 3D vision started without having to replug the emitter lol. I certainly hope nVidia fixes this issue in the future.
Well it's really shitty to have to go through these annoying procedures every time. I guess I'm "lucky" that I only need that HWINFO64 program to get 3D vision started without having to replug the emitter lol. I certainly hope nVidia fixes this issue in the future.

#31
Posted 10/20/2016 12:03 PM   
I'll try just unplugging and repluggin the emitter, without changing hz, screen type, etc. and let's see. If it works that will be a victory for me hahaha xD There is still one thing I'd like to know: Does everybody have this issue in windows 10? I mean, the fact that emitter disconects after a while.
I'll try just unplugging and repluggin the emitter, without changing hz, screen type, etc. and let's see. If it works that will be a victory for me hahaha xD
There is still one thing I'd like to know:
Does everybody have this issue in windows 10? I mean, the fact that emitter disconects after a while.

#32
Posted 10/20/2016 01:31 PM   
Mine goes dark occasionally, but I've never had any crashes because of that. This is on 368.69 without the Anniversary Update.
Mine goes dark occasionally, but I've never had any crashes because of that. This is on 368.69 without the Anniversary Update.

#33
Posted 10/20/2016 03:01 PM   
WORKAROUND AND NOTE TO NVIDIA DEVELOPERS: This workaround REQUIRES the Windows Start Menu to be enabled. 1. Before launching the affected 3D Vision game, visually check if the NVIDIA Stereo Controller is connected and awake (button shows dim green light). If no green light is present then 2. Right click on the Windows Start Button, from the context menu select "Control Panel". Once the Control Panel is shown, from the "Hardware and Sound" section, click on "View devices and printers". This action will ensure all connected USB devices awaken immediately, without the need to physically reattach them. 3. At this point the NVIDIA Stereo Controller will be awaken and the user will see its icon in the Control Panel Window under the "Unspecified" section. The physical NVIDIA Stereo Controller will be lit with a dim green light on its button. 3a. IMPORTANT: Close the Devices and Printers window, to ensure this workaround works the next time you need it. 4. Launch your 3D Vision Enabled game just as it should have been done from the beginning, and enjoy! NVIDIA Developers, please find out what Microsoft coded for this Control Panel view's constructor and make sure the init procedure for 3D Vision calls this code, before whatever the game devs are getting to call now, because all seems to imply that incorrect init sequences that games' code perform when they try to use the still powered down device, are what's causing the BSODs. Hope this helps, Miguel
WORKAROUND AND NOTE TO NVIDIA DEVELOPERS:

This workaround REQUIRES the Windows Start Menu to be enabled.

1. Before launching the affected 3D Vision game, visually check if the NVIDIA Stereo Controller is connected and awake (button shows dim green light). If no green light is present then
2. Right click on the Windows Start Button, from the context menu select "Control Panel". Once the Control Panel is shown, from the "Hardware and Sound" section, click on "View devices and printers". This action will ensure all connected USB devices awaken immediately, without the need to physically reattach them.
3. At this point the NVIDIA Stereo Controller will be awaken and the user will see its icon in the Control Panel Window under the "Unspecified" section. The physical NVIDIA Stereo Controller will be lit with a dim green light on its button.
3a. IMPORTANT: Close the Devices and Printers window, to ensure this workaround works the next time you need it.
4. Launch your 3D Vision Enabled game just as it should have been done from the beginning, and enjoy!

NVIDIA Developers, please find out what Microsoft coded for this Control Panel view's constructor and make sure the init procedure for 3D Vision calls this code, before whatever the game devs are getting to call now, because all seems to imply that incorrect init sequences that games' code perform when they try to use the still powered down device, are what's causing the BSODs.

Hope this helps,

Miguel

ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.

ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.

#34
Posted 10/21/2016 01:22 AM   
[quote="Maegirom"]I'll try just unplugging and repluggin the emitter, without changing hz, screen type, etc. and let's see. If it works that will be a victory for me hahaha xD There is still one thing I'd like to know: Does everybody have this issue in windows 10? I mean, the fact that emitter disconects after a while. [/quote] I had it a few months ago, but installing new drivers solved the problem. :\
Maegirom said:I'll try just unplugging and repluggin the emitter, without changing hz, screen type, etc. and let's see. If it works that will be a victory for me hahaha xD
There is still one thing I'd like to know:
Does everybody have this issue in windows 10? I mean, the fact that emitter disconects after a while.


I had it a few months ago, but installing new drivers solved the problem. :\

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#35
Posted 10/21/2016 12:12 PM   
@Miguel So you're saying that the emitter light turning off for no reason is intended ? I thought that was supposed to be the problem in the first place. But come to think of it after reading what you said, I noticed that sometimes games are turning on the emitter light with no problems but most games will give me a BSOD or a black screen with system hang if the emitter light was off at the time.
@Miguel

So you're saying that the emitter light turning off for no reason is intended ? I thought that was supposed to be the problem in the first place. But come to think of it after reading what you said, I noticed that sometimes games are turning on the emitter light with no problems but most games will give me a BSOD or a black screen with system hang if the emitter light was off at the time.

#36
Posted 10/21/2016 01:27 PM   
Yep, the same as Kaimastah. All my hangs and BSOD were because I was not aware that green light was off. Now that I know it, just ensureing that light is ON has solved all my hangs, black screens and BSOD. By the way, Kaimastah, HWinfo64 indeed lights the emitter up, BUT this doesn't seem to work for me. I need to unplug and replug the USB cord. I'll try the Control Panel Window method. (But I think is the same, just "awake" the devices) The good news is that I don't need to make the ritual (change Hz, set screen type, etc.) anymore. Presently, unplug and replug the usb cord is enough. I have recently installed anniversary update BTW. Don't know if this has to do or not.
Yep, the same as Kaimastah. All my hangs and BSOD were because I was not aware that green light was off. Now that I know it, just ensureing that light is ON has solved all my hangs, black screens and BSOD.
By the way, Kaimastah, HWinfo64 indeed lights the emitter up, BUT this doesn't seem to work for me. I need to unplug and replug the USB cord. I'll try the Control Panel Window method. (But I think is the same, just "awake" the devices)
The good news is that I don't need to make the ritual (change Hz, set screen type, etc.) anymore. Presently, unplug and replug the usb cord is enough.
I have recently installed anniversary update BTW. Don't know if this has to do or not.

#37
Posted 10/21/2016 07:31 PM   
[quote="Kaimastah"]@Miguel So you're saying that the emitter light turning off for no reason is intended ? [/quote] Exactly. That's the new Power Management features in Windows 8 and later, kicking in. The problem is the BSOD happens only when 3D Vision initialization is invoked while the light on the Stereo Controller is off (powered down by Windows). So since this specific Control Panel view has the ability to awake USB devices instantly, I'm suggesting users do invoke it before launching the game in order to avoid the incorrect init sequence that games' code perform when they try to use the still powered down device. I'm guessing this init problem resides within NVIDIA drivers since it didn't happen to me on Win 10 before 364.xx, so maybe that's where they should look in order to fix it. By the way, I'm editing the workaround post now because if you leave the Devices and Printers window open and the light on the Stereo Controller eventually goes off due to Windows PM, the next time Step 2 of the workaround is performed, it won't do anything and the emitter will remain off, so I'm adding step 3a to assure the right workflow to achieve the correct power state for every invocation. Miguel
Kaimastah said:@Miguel
So you're saying that the emitter light turning off for no reason is intended ?

Exactly. That's the new Power Management features in Windows 8 and later, kicking in. The problem is the BSOD happens only when 3D Vision initialization is invoked while the light on the Stereo Controller is off (powered down by Windows). So since this specific Control Panel view has the ability to awake USB devices instantly, I'm suggesting users do invoke it before launching the game in order to avoid the incorrect init sequence that games' code perform when they try to use the still powered down device. I'm guessing this init problem resides within NVIDIA drivers since it didn't happen to me on Win 10 before 364.xx, so maybe that's where they should look in order to fix it.

By the way, I'm editing the workaround post now because if you leave the Devices and Printers window open and the light on the Stereo Controller eventually goes off due to Windows PM, the next time Step 2 of the workaround is performed, it won't do anything and the emitter will remain off, so I'm adding step 3a to assure the right workflow to achieve the correct power state for every invocation.

Miguel

ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.

ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.

#38
Posted 10/21/2016 07:44 PM   
I'm just using HWINFO64 to awake the emitter every time it's off and it always works for me but apparently Maegirom still gets a system hang even when the emitter light is on so he has to replug it each time.
I'm just using HWINFO64 to awake the emitter every time it's off and it always works for me but apparently Maegirom still gets a system hang even when the emitter light is on so he has to replug it each time.

#39
Posted 10/21/2016 07:50 PM   
I'll try HWINFO64 method again. As I said I have just installed anniversary update. Maybe it has fixed something, don't know...
I'll try HWINFO64 method again. As I said I have just installed anniversary update. Maybe it has fixed something, don't know...

#40
Posted 10/21/2016 07:58 PM   
Ok, test done successfully. I have change from g sync mode to 3d vision mode and viceversa and no hang or blackscreen. It seems that now I'm in the same league as Kaimastah, I only need to "wake up" the emitter and go. I sign for this to not change! xD
Ok, test done successfully. I have change from g sync mode to 3d vision mode and viceversa and no hang or blackscreen. It seems that now I'm in the same league as Kaimastah, I only need to "wake up" the emitter and go.
I sign for this to not change! xD

#41
Posted 10/21/2016 08:03 PM   
  3 / 3    
Scroll To Top