Random BSOD (nvstusb.sys) and reboot when 3D vision usb controller is plugged and enabled
1 / 3
Hello,
Since I'vre upgraded to windows 10 whenever "Stereoscopic 3D" is enabled and an application switches to full screen [color="orange"](it can be Google Chrome when playing a youtube video in full screen or a game such as World of Warcraft)[/color] my computer has 20% chances to crash with a BSOD.
Another symptom is that playing a Youtube video full Screen from chrome switches the system in stereoscopic mode (the USB 3D Controllers lights up and the screens flicker). When it does this I know that the computer has a high chance to crash.
When it does a BSOD Windows Report Center [color="orange"](Control Panel\All Control Panel Items\Security and Maintenance\Problem Details)[/color] always indicates the same problem:
[code]Problem Event Name: BlueScreen
Code: a
Parameter 1: 650000008d
Parameter 2: 2
Parameter 3: 0
Parameter 4: fffff800ea8d1212
OS version: 10_0_10586D vision
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.10586.2.0.0.256.48
Locale ID: 1036
Extra information about the problem
Bucket ID: AV_nvstusb!unknown_function
[/code]
"[b][color="orange"]AV_nvstusb!unknown_function[/color][/b]" being the part that never changes. [b]AV_nvstusb[/b] is the 3D Stereoscopic USB controller driver...
Putting the generated minidump through windows debugger is less interesting as it does not accuse NVIDIA 3d stub driver (probably less evolved than Win10 auto debugging):
[code]BugCheck A, {650000008d, 2, 0, fffff800ea8d1212}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+62 )
Followup: MachineOwner
---------
1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000650000008d, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800ea8d1212, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
000000650000008d
CURRENT_IRQL: 2
FAULTING_IP:
nt!IoCancelIrp+62
fffff800`ea8d1212 488b4928 mov rcx,qword ptr [rcx+28h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: chrome.exe
LAST_CONTROL_TRANSFER: from fffff800ea9652e9 to fffff800ea95a760
STACK_TEXT:
ffffd000`263c5368 fffff800`ea9652e9 : 00000000`0000000a 00000065`0000008d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`263c5370 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!IoCancelIrp+62
fffff800`ea8d1212 488b4928 mov rcx,qword ptr [rcx+28h]
SYMBOL_NAME: nt!IoCancelIrp+62
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 56fa1e56
FAILURE_BUCKET_ID: X64_0xA_nt!IoCancelIrp+62
BUCKET_ID: X64_0xA_nt!IoCancelIrp+62
Followup: MachineOwner
---------
[/code]
I've run a full RAM diagnostic using the latest memtest86 for 8 hours and no memory error where found (the 13 tests passed).
Apart from this specific issue my computer is very stable and never crashes, games run smoothly once launched (The BSOD/reboot always happen at the time the application switches to full screen, if it passes that stage it's OK, alt-tabbing is also fine)
[color="green"][b]Details about my setup:[/b][/color]
I'm using the normal Windows 10 build (see above) and 364.72 nVidia drivers. I have a dual monitor setup (The 3D screen is at 120Hz while the other is at 60Hz).
I use the original NVIDIA 3D kit (1st version of the glasses) with an Acer GD245HQ
I've disabled nVIDIA HDMI sound ouputs as I don't use them. The 3D stereoscopic controller is plugged directly (No hub)
I've updated all my drivers (using iobit driverbooster) and BIOS to the latest possible version when this problem appeared but this did not change anything.
I've searched on the web but could not find anything recent close to this issue.
I've noticed that this issue is more likely to occur if several applications using the video card are running at the same time (such as having chrome open or an active TeamViewer session).
Firefox can also trigger a crash if the nVidia 3d extension is not disabled (it installs automatically with nVidia drivers).
Another (unrelated?) issue I have is that if I don't unplug the 3d vision usb controller new NVIDIA driver [b]express[/b] installation always fails... (I need to choose custom and choose to make a clean install every time)
Any help or suggestions would be greatly appreciated.
Thanks
Since I'vre upgraded to windows 10 whenever "Stereoscopic 3D" is enabled and an application switches to full screen (it can be Google Chrome when playing a youtube video in full screen or a game such as World of Warcraft) my computer has 20% chances to crash with a BSOD.
Another symptom is that playing a Youtube video full Screen from chrome switches the system in stereoscopic mode (the USB 3D Controllers lights up and the screens flicker). When it does this I know that the computer has a high chance to crash.
When it does a BSOD Windows Report Center (Control Panel\All Control Panel Items\Security and Maintenance\Problem Details) always indicates the same problem:
Problem Event Name: BlueScreen
Code: a
Parameter 1: 650000008d
Parameter 2: 2
Parameter 3: 0
Parameter 4: fffff800ea8d1212
OS version: 10_0_10586D vision
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.10586.2.0.0.256.48
Locale ID: 1036
Extra information about the problem
Bucket ID: AV_nvstusb!unknown_function
"AV_nvstusb!unknown_function" being the part that never changes. AV_nvstusb is the 3D Stereoscopic USB controller driver...
Putting the generated minidump through windows debugger is less interesting as it does not accuse NVIDIA 3d stub driver (probably less evolved than Win10 auto debugging):
BugCheck A, {650000008d, 2, 0, fffff800ea8d1212}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+62 )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000650000008d, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800ea8d1212, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
000000650000008d
I've run a full RAM diagnostic using the latest memtest86 for 8 hours and no memory error where found (the 13 tests passed).
Apart from this specific issue my computer is very stable and never crashes, games run smoothly once launched (The BSOD/reboot always happen at the time the application switches to full screen, if it passes that stage it's OK, alt-tabbing is also fine)
Details about my setup:
I'm using the normal Windows 10 build (see above) and 364.72 nVidia drivers. I have a dual monitor setup (The 3D screen is at 120Hz while the other is at 60Hz).
I use the original NVIDIA 3D kit (1st version of the glasses) with an Acer GD245HQ
I've disabled nVIDIA HDMI sound ouputs as I don't use them. The 3D stereoscopic controller is plugged directly (No hub)
I've updated all my drivers (using iobit driverbooster) and BIOS to the latest possible version when this problem appeared but this did not change anything.
I've searched on the web but could not find anything recent close to this issue.
I've noticed that this issue is more likely to occur if several applications using the video card are running at the same time (such as having chrome open or an active TeamViewer session).
Firefox can also trigger a crash if the nVidia 3d extension is not disabled (it installs automatically with nVidia drivers).
Another (unrelated?) issue I have is that if I don't unplug the 3d vision usb controller new NVIDIA driver express installation always fails... (I need to choose custom and choose to make a clean install every time)
Any help or suggestions would be greatly appreciated.
[quote="2072"]Another (unrelated?) issue I have is that if I don't unplug the 3d vision usb controller new NVIDIA driver [b]express[/b] installation always fails... (I need to choose custom and choose to make a clean install every time)[/quote]I've been getting this for over a year. I'm pretty sure it's not actually failed. When it says failed, just press the back button then go forward again and it will say successfully installed and then keep clicking next for the test and finishing of the setup.
P.S. Don't use iobit or whatever. Download the latest version of DDU (Display Driver Uninstaller). Restart Windows in safe mode and run DDU. Make sure to check all the nvidia options. When your PC has restarted, install the nvidia drivers. Always do custom install, always do clean install, and always just choose the bare minimum you need - for me, that's just the 3D Vision drivers (I think there are 2 or 3), PhysX, and the actual display driver if I recall correctly; I always un-check the Miracast thing, HD audio, GeForce experience, and whatever else there is that I don't want. When you're done, make sure to restart the PC even if the driver install doesn't tell you to.
2072 said:Another (unrelated?) issue I have is that if I don't unplug the 3d vision usb controller new NVIDIA driver express installation always fails... (I need to choose custom and choose to make a clean install every time)
I've been getting this for over a year. I'm pretty sure it's not actually failed. When it says failed, just press the back button then go forward again and it will say successfully installed and then keep clicking next for the test and finishing of the setup.
P.S. Don't use iobit or whatever. Download the latest version of DDU (Display Driver Uninstaller). Restart Windows in safe mode and run DDU. Make sure to check all the nvidia options. When your PC has restarted, install the nvidia drivers. Always do custom install, always do clean install, and always just choose the bare minimum you need - for me, that's just the 3D Vision drivers (I think there are 2 or 3), PhysX, and the actual display driver if I recall correctly; I always un-check the Miracast thing, HD audio, GeForce experience, and whatever else there is that I don't want. When you're done, make sure to restart the PC even if the driver install doesn't tell you to.
This just happened again. It seems to happen mostly after Google Chrome "used" stereoscopic vision (by playing some 2D video full screen...) and if I try to launch a game that actually uses stereoscopic vision it gets a very high probability to crash the system with a BSOD accusing nvstusb...
I've updated windows debugger and now it agrees with Windows' auto diagnostic system:
[code]Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051616-36843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
Machine Name:
Kernel base = 0xfffff801`c0e7d000 PsLoadedModuleList = 0xfffff801`c115bcd0
Debug session time: Mon May 16 23:28:26.733 2016 (UTC + 2:00)
System Uptime: 5 days 8:18:54.815
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..................
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {28, 2, 0, fffff801c0f3ca5a}
*** WARNING: Unable to verify timestamp for nvstusb.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstusb.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvstusb.sys ( nvstusb+a57c )
Followup: MachineOwner
---------
7: kd> !analyze -v
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801c0f3ca5a, address which referenced memory
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850
SYSTEM_MANUFACTURER: ASUS
SYSTEM_PRODUCT_NAME: All Series
SYSTEM_SKU: All
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 2103
BIOS_DATE: 08/18/2014
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: SABERTOOTH Z87
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: 28
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff801c0f3ca5a
READ_ADDRESS: fffff801c11fb520: Unable to get MiVisibleState
0000000000000028
CURRENT_IRQL: 2
FAULTING_IP:
nt!IoCancelIrp+62
fffff801`c0f3ca5a 488b4928 mov rcx,qword ptr [rcx+28h]
CPU_COUNT: 8
CPU_MHZ: d48
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: stanley.exe
ANALYSIS_SESSION_HOST: redacted
ANALYSIS_SESSION_TIME: 05-16-2016 23:43:19.0478
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
TRAP_FRAME: ffffd00027c4c4c0 -- (.trap 0xffffd00027c4c4c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffe000294da010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801c0f3ca5a rsp=ffffd00027c4c650 rbp=0000000000000004
r8=fffff801c120f840 r9=fffff780000003b0 r10=fffff78000000008
r11=ffffd00027c4c6c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!IoCancelIrp+0x62:
fffff801`c0f3ca5a 488b4928 mov rcx,qword ptr [rcx+28h] ds:00000000`00000028=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff801c0fca2e9 to fffff801c0fbf780
STACK_TEXT:
ffffd000`27c4c378 fffff801`c0fca2e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`27c4c380 fffff801`c0fc8ac7 : 00000000`00000000 fffffd80`00003e78 00000000`0000000c fffff801`c0eb68aa : nt!KiBugCheckDispatch+0x69
ffffd000`27c4c4c0 fffff801`c0f3ca5a : ffffe000`294da010 00000000`00000000 00000000`00000000 ffffe000`22b0f7b0 : nt!KiPageFault+0x247
ffffd000`27c4c650 fffff801`087fa57c : ffffe000`22b0f800 ffffe000`22b0f7b0 00000000`20000000 fffff801`c0eeff00 : nt!IoCancelIrp+0x62
ffffd000`27c4c690 ffffe000`22b0f800 : ffffe000`22b0f7b0 00000000`20000000 fffff801`c0eeff00 ffffd000`00000001 : nvstusb+0xa57c
ffffd000`27c4c698 ffffe000`22b0f7b0 : 00000000`20000000 fffff801`c0eeff00 ffffd000`00000001 ffffe000`22a49000 : 0xffffe000`22b0f800
ffffd000`27c4c6a0 00000000`20000000 : fffff801`c0eeff00 ffffd000`00000001 ffffe000`22a49000 ffffe000`22b0f7b0 : 0xffffe000`22b0f7b0
ffffd000`27c4c6a8 fffff801`c0eeff00 : ffffd000`00000001 ffffe000`22a49000 ffffe000`22b0f7b0 fffff801`087fa71b : 0x20000000
ffffd000`27c4c6b0 fffff801`093a1c6a : 00000000`00000000 ffffe000`22a48b00 00000000`000000c0 00000000`00000000 : nt!ExpAllocateBigPool+0x30
ffffd000`27c4c7a0 00000000`00000000 : ffffe000`22a48b00 00000000`000000c0 00000000`00000000 ffffe000`2300c000 : nvlddmkm+0x301c6a
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 9ebdb14efecb74b0ab0376296fce50924018f795
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 09c546c0d336f4cd6ff61c33781ea6b5d2cf0265
THREAD_SHA1_HASH_MOD: 9300a294557d552d8a51511467fb017dae1e4ca3
FOLLOWUP_IP:
nvstusb+a57c
fffff801`087fa57c eb47 jmp nvstusb+0xa5c5 (fffff801`087fa5c5)
FAULT_INSTR_CODE: c03347eb
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvstusb+a57c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvstusb
IMAGE_NAME: nvstusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 56d61708
BUCKET_ID_FUNC_OFFSET: a57c
[color="orange"]FAILURE_BUCKET_ID: AV_nvstusb!Unknown_Function
BUCKET_ID: AV_nvstusb!Unknown_Function
PRIMARY_PROBLEM_CLASS: AV_nvstusb!Unknown_Function[/color]
TARGET_TIME: 2016-05-16T21:28:26.000Z
OSBUILD: 10586
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-04-23 06:04:21
BUILDDATESTAMP_STR: 160422-1850
BUILDLAB_STR: th2_release_sec
BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850
ANALYSIS_SESSION_ELAPSED_TIME: 3d80b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_nvstusb!unknown_function
FAILURE_ID_HASH: {269c6f4f-857a-43fc-11b4-7d618f963c57}
Followup: MachineOwner
---------
[/code]
[quote="Spinelli1"][quote="2072"]Another (unrelated?) issue I have is that if I don't unplug the 3d vision usb controller new NVIDIA driver [b]express[/b] installation always fails... (I need to choose custom and choose to make a clean install every time)[/quote]I've been getting this for over a year. I'm pretty sure it's not actually failed. When it says failed, just press the back button then go forward again and it will say successfully installed and then keep clicking next for the test and finishing of the setup.
P.S. Don't use iobit or whatever. Download the latest version of DDU (Display Driver Uninstaller). Restart Windows in safe mode and run DDU. Make sure to check all the nvidia options. When your PC has restarted, install the nvidia drivers. Always do custom install, always do clean install, and always just choose the bare minimum you need - for me, that's just the 3D Vision drivers (I think there are 2 or 3), PhysX, and the actual display driver if I recall correctly; I always un-check the Miracast thing, HD audio, GeForce experience, and whatever else there is that I don't want. When you're done, make sure to restart the PC even if the driver install doesn't tell you to.[/quote]
For me it does fail, the video driver is left in an unusable state, it only works if I check "clean install" *every* time which defeats the purpose of the express installation...
I've tried to use DDU but the problem is that windows 10 keeps reinstalling it's default nVidia driver (even if I remove the package from the system) before or while I try to re-install them manually.
This just happened again. It seems to happen mostly after Google Chrome "used" stereoscopic vision (by playing some 2D video full screen...) and if I try to launch a game that actually uses stereoscopic vision it gets a very high probability to crash the system with a BSOD accusing nvstusb...
I've updated windows debugger and now it agrees with Windows' auto diagnostic system:
Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051616-36843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
Machine Name:
Kernel base = 0xfffff801`c0e7d000 PsLoadedModuleList = 0xfffff801`c115bcd0
Debug session time: Mon May 16 23:28:26.733 2016 (UTC + 2:00)
System Uptime: 5 days 8:18:54.815
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..................
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {28, 2, 0, fffff801c0f3ca5a}
*** WARNING: Unable to verify timestamp for nvstusb.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstusb.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvstusb.sys ( nvstusb+a57c )
Followup: MachineOwner
---------
7: kd> !analyze -v
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801c0f3ca5a, address which referenced memory
TRAP_FRAME: ffffd00027c4c4c0 -- (.trap 0xffffd00027c4c4c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffe000294da010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801c0f3ca5a rsp=ffffd00027c4c650 rbp=0000000000000004
r8=fffff801c120f840 r9=fffff780000003b0 r10=fffff78000000008
r11=ffffd00027c4c6c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!IoCancelIrp+0x62:
fffff801`c0f3ca5a 488b4928 mov rcx,qword ptr [rcx+28h] ds:00000000`00000028=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff801c0fca2e9 to fffff801c0fbf780
2072 said:Another (unrelated?) issue I have is that if I don't unplug the 3d vision usb controller new NVIDIA driver express installation always fails... (I need to choose custom and choose to make a clean install every time)
I've been getting this for over a year. I'm pretty sure it's not actually failed. When it says failed, just press the back button then go forward again and it will say successfully installed and then keep clicking next for the test and finishing of the setup.
P.S. Don't use iobit or whatever. Download the latest version of DDU (Display Driver Uninstaller). Restart Windows in safe mode and run DDU. Make sure to check all the nvidia options. When your PC has restarted, install the nvidia drivers. Always do custom install, always do clean install, and always just choose the bare minimum you need - for me, that's just the 3D Vision drivers (I think there are 2 or 3), PhysX, and the actual display driver if I recall correctly; I always un-check the Miracast thing, HD audio, GeForce experience, and whatever else there is that I don't want. When you're done, make sure to restart the PC even if the driver install doesn't tell you to.
For me it does fail, the video driver is left in an unusable state, it only works if I check "clean install" *every* time which defeats the purpose of the express installation...
I've tried to use DDU but the problem is that windows 10 keeps reinstalling it's default nVidia driver (even if I remove the package from the system) before or while I try to re-install them manually.
I found something interesting, I used DDU again but this time I unplugged the cable so windows could not reinstall anything.
After rebooting from safe mode where DDu did its job I noticed that the USB stereo controller driver was not removed at all by DDU and was still happily running... So I deleted the device from Windows device manager and then I removed the driver package using DriverStore explorer.
i rebooted once more and I launched Nvidia's latest installer in custom mode but somehow it still detected a very old version (280.19) of this damn usb stereo driver being present...
So I launched regedit as the System user and started searching for "nvstusb" in the whole registry. There was plenty of entries left... I deleted them all and then started looking for 'nvidia'. I found an old uninstall entry for the the usb stereo controller (280.19) that didn't show in Windows' control panel... So I manually executed the uninstall string. It uninstalled not without complaining about something but it was successful. (I should have done that before manually deleting nvstusb entries...)
Here is the command I used (directly copy pasted from the registry)
[code]"C:\Program Files (x86)\InstallShield Installation Information\{714B9C6C-70FC-4750-98E2-61520B906C45}\setup.exe" -runfromtemp -l0x0009 -removeonly[/code]
(Note that the uninstaller that launched had a very old look... 280.19 must have been pretty old and the current installer was unable to deal with it properly on it's own.)
I rebooted and launched nvidia installer again and this time it did not detect any old driver at all.
So hopefully this will fix my issues... Only time will tell though. I'll keep this thread updated.
I found something interesting, I used DDU again but this time I unplugged the cable so windows could not reinstall anything.
After rebooting from safe mode where DDu did its job I noticed that the USB stereo controller driver was not removed at all by DDU and was still happily running... So I deleted the device from Windows device manager and then I removed the driver package using DriverStore explorer.
i rebooted once more and I launched Nvidia's latest installer in custom mode but somehow it still detected a very old version (280.19) of this damn usb stereo driver being present...
So I launched regedit as the System user and started searching for "nvstusb" in the whole registry. There was plenty of entries left... I deleted them all and then started looking for 'nvidia'. I found an old uninstall entry for the the usb stereo controller (280.19) that didn't show in Windows' control panel... So I manually executed the uninstall string. It uninstalled not without complaining about something but it was successful. (I should have done that before manually deleting nvstusb entries...)
Here is the command I used (directly copy pasted from the registry)
(Note that the uninstaller that launched had a very old look... 280.19 must have been pretty old and the current installer was unable to deal with it properly on it's own.)
I rebooted and launched nvidia installer again and this time it did not detect any old driver at all.
So hopefully this will fix my issues... Only time will tell though. I'll keep this thread updated.
Starting with driver 275.33, Nvidia packaged the USB driver with the main drivers.
Previously, it was a separate download and you could mix and match driver versions with USB versions.
People were using emulators and 3rd party knock off glasses, so Nvidia changed it to disable the hacks.
Now the USB driver version is required to match the driver version.
If there's a problem with DDU, you can report it in his thread and he will act on it.
https://forums.geforce.com/default/topic/550192/geforce-drivers/wagnard-tools-ddu-gmp-tdr-manipulator-new-cpu-core-analyzer-updated-04-05-2016-/
I hope you have it all sorted now.
unfortunately I didn't have to wait for long... my computer just crashed again upon launching a game, this time without a BSOD, it just restarted. I had to restrain myself from slamming the USB stereo controller on the wall.
I guess the only way to fix this issue is to reinstall win10 from scratch but alas I cannot afford the time to do that. I never had this kind of issue under win7.
One thing I noticed is that the controller turns itself off when not in use, it blinks a few times and stops. During this last crash it was like it failed to turn on, the screen got brighter like it does normally when enabling 3d stereo but the controller stayed off...
unfortunately I didn't have to wait for long... my computer just crashed again upon launching a game, this time without a BSOD, it just restarted. I had to restrain myself from slamming the USB stereo controller on the wall.
I guess the only way to fix this issue is to reinstall win10 from scratch but alas I cannot afford the time to do that. I never had this kind of issue under win7.
One thing I noticed is that the controller turns itself off when not in use, it blinks a few times and stops. During this last crash it was like it failed to turn on, the screen got brighter like it does normally when enabling 3d stereo but the controller stayed off...
Well at least now I know that there are others out there experiencing this too lol. I've been having the same exact issue since I first started using my kit (V2), earlier this year. The BSOD's seem to be less frequent for me now though. Installing the latest 3D vision drivers through GE the other day seems to have helped. But I'm still getting one every now and then (usually the IRQL_Not_Less_Or_Equal one like you). It's funny that you mention Chrome though. Because it seems to me that using Chrome for anything period, and then launching a game, especially while Chrome is still open, definitely seems to increase the chance of a BSOD. Now I just try and leave Chrome the hell alone if I plan on doing any 3D gaming lol.
It is weird though that no one seems to know much about this. I've posted about this twice now and never found out anything useful. At least I'm down to a BSOD every 6th or 8th launch now. And now that I think about it, my avoiding Chrome idea is probably what's really lessening the crashes rather than that new driver. Of course they still eventually happen even if Chrome is completely avoided. Just takes more launches it seems.
Forgot to add that just like you're experiencing, I sometimes get a crash without any BSOD when launching a game with 3D enabled too. Crash dump analysis doesn't seem to pick up on those though. And also, I had the issue back when my system was Windows 7 too. Upgrading to 10 didn't seem to change the frequency of BSOD's for me.
Well at least now I know that there are others out there experiencing this too lol. I've been having the same exact issue since I first started using my kit (V2), earlier this year. The BSOD's seem to be less frequent for me now though. Installing the latest 3D vision drivers through GE the other day seems to have helped. But I'm still getting one every now and then (usually the IRQL_Not_Less_Or_Equal one like you). It's funny that you mention Chrome though. Because it seems to me that using Chrome for anything period, and then launching a game, especially while Chrome is still open, definitely seems to increase the chance of a BSOD. Now I just try and leave Chrome the hell alone if I plan on doing any 3D gaming lol.
It is weird though that no one seems to know much about this. I've posted about this twice now and never found out anything useful. At least I'm down to a BSOD every 6th or 8th launch now. And now that I think about it, my avoiding Chrome idea is probably what's really lessening the crashes rather than that new driver. Of course they still eventually happen even if Chrome is completely avoided. Just takes more launches it seems.
Forgot to add that just like you're experiencing, I sometimes get a crash without any BSOD when launching a game with 3D enabled too. Crash dump analysis doesn't seem to pick up on those though. And also, I had the issue back when my system was Windows 7 too. Upgrading to 10 didn't seem to change the frequency of BSOD's for me.
I'm also having this issue since I bought my new 3D monitor and started using the 3D vision kit again. I've had no problems before but now there's an 80% chance I get a BSOD (most of the time exactly that IRQL one) when launching a game in 3D mode and not one BSOD otherwise. This usually happens after the 3D Vision emitter turns off for some time. I'm using Windows 8.1 and nVidia driver version 368.39 btw.
I'm also having this issue since I bought my new 3D monitor and started using the 3D vision kit again. I've had no problems before but now there's an 80% chance I get a BSOD (most of the time exactly that IRQL one) when launching a game in 3D mode and not one BSOD otherwise. This usually happens after the 3D Vision emitter turns off for some time. I'm using Windows 8.1 and nVidia driver version 368.39 btw.
I have a Gigabyte 970 gtx G1 model and the symptoms are mostly like the ones described in the previous posts so it happens whenever 3D mode is turned on; whether it's a 3D movie or a game the issue is the same. At the moment I'm doing some RAM and file system scans but I doubt there's anything wrong since these BSODs have started to occur right after the 3D vision kit was plugged in again. I'm going to use DDU and reinstall the latest drivers but from I've read I think DDU doesn't delete the 3D vision drivers or not all of them so I'm probably gonna have to manually check for these afterwards.
I have a Gigabyte 970 gtx G1 model and the symptoms are mostly like the ones described in the previous posts so it happens whenever 3D mode is turned on; whether it's a 3D movie or a game the issue is the same. At the moment I'm doing some RAM and file system scans but I doubt there's anything wrong since these BSODs have started to occur right after the 3D vision kit was plugged in again. I'm going to use DDU and reinstall the latest drivers but from I've read I think DDU doesn't delete the 3D vision drivers or not all of them so I'm probably gonna have to manually check for these afterwards.
It's nice to know I'm not the only one experiencing this annoyance. Since my last post I've stopped playing games in stereoscopic mode and my computer is as stable as a rock (I've disabled stereoscopic mode)... So this is definitely an nVidia driver bug.
Do you have a fresh win10 install or was it also an upgrade?
It's nice to know I'm not the only one experiencing this annoyance. Since my last post I've stopped playing games in stereoscopic mode and my computer is as stable as a rock (I've disabled stereoscopic mode)... So this is definitely an nVidia driver bug.
Do you have a fresh win10 install or was it also an upgrade?
I have Windows 8.1 as I've mentioned in one of the posts above and it was a fresh install. I have tested my RAM and system and I did not have any errors or corrupted files but after reinstalling the drivers using DDU I'm glad to say that my system is no longer crashing. Further testing led me closer to the problem and it is indeed the 3D vision emitter causing all of this. After the emitter is off for a while, if I start any game in 3D mode it loads extremely slow to the point that Windows becomes unresponsive. The emitter does not turn on during this and eventually the screen goes black on both of my monitors (one is a 144hz Asus and the other just a generic 60hz monitor) and then the display driver crashes and restores itself. After repeating this several times running different games without restarting the system I've turned off 3D vision from the nVidia CP and any game I load runs fine.
If I had to guess, the emitter is refusing to turn on and the display driver just crashes so my question is [b]does anybody know how to get the emitter to never turn itself off ?[/b] I would like to check if the problem is due to this power saving function. I've already tried several things like turning off usb power saving from Windows Control Panel and Device Manager but the emitter automatically turns off no matter what. Also, the emitter is plugged directly into one of the back usb ports. I would really appreciate any info on this.
Edit:
Changing USB ports fixes this problem but if I exit the application the emitter turns off instantly and the issue is back upon running the application a second time. After trying this it seems that now I'm getting a taskbar pop-up stating that one of my recent usb devices malfunctioned and is no longer recognized by Windows.
Later edit:
Ok so it seems that the problem is indeed the emitter but it's because of this Windows USB Power Saving and I've tried a lot of fixes to disable this nonsense including finding and modifying the Windows registry for the specific USB hub I've plugged the emitter into but nothing works so I guess the only workaround for me at the moment is to just re-plug the usb emitter every time. I have to say that my Windows is up to date and imo this is such a shame since I believe this has caused a ton of issues for so many people and nVidia or Microsoft have yet to fix this after all these years.
I have Windows 8.1 as I've mentioned in one of the posts above and it was a fresh install. I have tested my RAM and system and I did not have any errors or corrupted files but after reinstalling the drivers using DDU I'm glad to say that my system is no longer crashing. Further testing led me closer to the problem and it is indeed the 3D vision emitter causing all of this. After the emitter is off for a while, if I start any game in 3D mode it loads extremely slow to the point that Windows becomes unresponsive. The emitter does not turn on during this and eventually the screen goes black on both of my monitors (one is a 144hz Asus and the other just a generic 60hz monitor) and then the display driver crashes and restores itself. After repeating this several times running different games without restarting the system I've turned off 3D vision from the nVidia CP and any game I load runs fine.
If I had to guess, the emitter is refusing to turn on and the display driver just crashes so my question is does anybody know how to get the emitter to never turn itself off ? I would like to check if the problem is due to this power saving function. I've already tried several things like turning off usb power saving from Windows Control Panel and Device Manager but the emitter automatically turns off no matter what. Also, the emitter is plugged directly into one of the back usb ports. I would really appreciate any info on this.
Edit:
Changing USB ports fixes this problem but if I exit the application the emitter turns off instantly and the issue is back upon running the application a second time. After trying this it seems that now I'm getting a taskbar pop-up stating that one of my recent usb devices malfunctioned and is no longer recognized by Windows.
Later edit:
Ok so it seems that the problem is indeed the emitter but it's because of this Windows USB Power Saving and I've tried a lot of fixes to disable this nonsense including finding and modifying the Windows registry for the specific USB hub I've plugged the emitter into but nothing works so I guess the only workaround for me at the moment is to just re-plug the usb emitter every time. I have to say that my Windows is up to date and imo this is such a shame since I believe this has caused a ton of issues for so many people and nVidia or Microsoft have yet to fix this after all these years.
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.
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
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.
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.
Same thing is happening to me.
I got a 3d capable monitor, and the nvidia 3d vision kit.
Ever since I've been using it, chrome, firefox and a few games will give me a bsod in the same faulting module.
FAULTING_IP:
nt!IoCancelIrp+62
fffff801`c82a4986 488b4928 mov rcx,qword ptr [rcx+28h]
which was called by nvstusb+0xa630
I'm also a programmer, so I have the debug stuff that lets me see where it crashed at.
It was fine the first two days, but now its 1-2 bsod per day.
It happens suddenly, on pretty benign actions like opening a new page in FF/chrome, or opening a menu in a game. I get these bsods in game while the controller is lit, so the last post, i'm not sure if that will help me.
I don't know what else to do.
One other problem that I have is that My monitor has a severe ghosting issue when the monitor is not in 3d mode, or specifically the nvidia lightboost strobing. I used an app to get it to perm be on a month ago that worked fine. But than when my 3d kit arrived, 3d doesnt work, er well more specifically nvidia gives me a red warning box over everything that its not a 3d refresh rate. so after removing that,
So if I open 3d player then close it, it will pop the refresh rate into 3d mode, then ghosting is gone. This may also contribute to my bsod, I'll try not doing that to see if that helps me when not in a 3d game. I got to stop losing work on these bsods.
Is there anything we can do to fix this bsod issue?
Same thing is happening to me.
I got a 3d capable monitor, and the nvidia 3d vision kit.
Ever since I've been using it, chrome, firefox and a few games will give me a bsod in the same faulting module.
FAULTING_IP:
nt!IoCancelIrp+62
fffff801`c82a4986 488b4928 mov rcx,qword ptr [rcx+28h]
which was called by nvstusb+0xa630
I'm also a programmer, so I have the debug stuff that lets me see where it crashed at.
It was fine the first two days, but now its 1-2 bsod per day.
It happens suddenly, on pretty benign actions like opening a new page in FF/chrome, or opening a menu in a game. I get these bsods in game while the controller is lit, so the last post, i'm not sure if that will help me.
I don't know what else to do.
One other problem that I have is that My monitor has a severe ghosting issue when the monitor is not in 3d mode, or specifically the nvidia lightboost strobing. I used an app to get it to perm be on a month ago that worked fine. But than when my 3d kit arrived, 3d doesnt work, er well more specifically nvidia gives me a red warning box over everything that its not a 3d refresh rate. so after removing that,
So if I open 3d player then close it, it will pop the refresh rate into 3d mode, then ghosting is gone. This may also contribute to my bsod, I'll try not doing that to see if that helps me when not in a 3d game. I got to stop losing work on these bsods.
Is there anything we can do to fix this bsod issue?
Since I'vre upgraded to windows 10 whenever "Stereoscopic 3D" is enabled and an application switches to full screen (it can be Google Chrome when playing a youtube video in full screen or a game such as World of Warcraft) my computer has 20% chances to crash with a BSOD.
Another symptom is that playing a Youtube video full Screen from chrome switches the system in stereoscopic mode (the USB 3D Controllers lights up and the screens flicker). When it does this I know that the computer has a high chance to crash.
When it does a BSOD Windows Report Center (Control Panel\All Control Panel Items\Security and Maintenance\Problem Details) always indicates the same problem:
"AV_nvstusb!unknown_function" being the part that never changes. AV_nvstusb is the 3D Stereoscopic USB controller driver...
Putting the generated minidump through windows debugger is less interesting as it does not accuse NVIDIA 3d stub driver (probably less evolved than Win10 auto debugging):
I've run a full RAM diagnostic using the latest memtest86 for 8 hours and no memory error where found (the 13 tests passed).
Apart from this specific issue my computer is very stable and never crashes, games run smoothly once launched (The BSOD/reboot always happen at the time the application switches to full screen, if it passes that stage it's OK, alt-tabbing is also fine)
Details about my setup:
I'm using the normal Windows 10 build (see above) and 364.72 nVidia drivers. I have a dual monitor setup (The 3D screen is at 120Hz while the other is at 60Hz).
I use the original NVIDIA 3D kit (1st version of the glasses) with an Acer GD245HQ
I've disabled nVIDIA HDMI sound ouputs as I don't use them. The 3D stereoscopic controller is plugged directly (No hub)
I've updated all my drivers (using iobit driverbooster) and BIOS to the latest possible version when this problem appeared but this did not change anything.
I've searched on the web but could not find anything recent close to this issue.
I've noticed that this issue is more likely to occur if several applications using the video card are running at the same time (such as having chrome open or an active TeamViewer session).
Firefox can also trigger a crash if the nVidia 3d extension is not disabled (it installs automatically with nVidia drivers).
Another (unrelated?) issue I have is that if I don't unplug the 3d vision usb controller new NVIDIA driver express installation always fails... (I need to choose custom and choose to make a clean install every time)
Any help or suggestions would be greatly appreciated.
Thanks
P.S. Don't use iobit or whatever. Download the latest version of DDU (Display Driver Uninstaller). Restart Windows in safe mode and run DDU. Make sure to check all the nvidia options. When your PC has restarted, install the nvidia drivers. Always do custom install, always do clean install, and always just choose the bare minimum you need - for me, that's just the 3D Vision drivers (I think there are 2 or 3), PhysX, and the actual display driver if I recall correctly; I always un-check the Miracast thing, HD audio, GeForce experience, and whatever else there is that I don't want. When you're done, make sure to restart the PC even if the driver install doesn't tell you to.
I've updated windows debugger and now it agrees with Windows' auto diagnostic system:
For me it does fail, the video driver is left in an unusable state, it only works if I check "clean install" *every* time which defeats the purpose of the express installation...
I've tried to use DDU but the problem is that windows 10 keeps reinstalling it's default nVidia driver (even if I remove the package from the system) before or while I try to re-install them manually.
After rebooting from safe mode where DDu did its job I noticed that the USB stereo controller driver was not removed at all by DDU and was still happily running... So I deleted the device from Windows device manager and then I removed the driver package using DriverStore explorer.
i rebooted once more and I launched Nvidia's latest installer in custom mode but somehow it still detected a very old version (280.19) of this damn usb stereo driver being present...
So I launched regedit as the System user and started searching for "nvstusb" in the whole registry. There was plenty of entries left... I deleted them all and then started looking for 'nvidia'. I found an old uninstall entry for the the usb stereo controller (280.19) that didn't show in Windows' control panel... So I manually executed the uninstall string. It uninstalled not without complaining about something but it was successful. (I should have done that before manually deleting nvstusb entries...)
Here is the command I used (directly copy pasted from the registry)
(Note that the uninstaller that launched had a very old look... 280.19 must have been pretty old and the current installer was unable to deal with it properly on it's own.)
I rebooted and launched nvidia installer again and this time it did not detect any old driver at all.
So hopefully this will fix my issues... Only time will tell though. I'll keep this thread updated.
Previously, it was a separate download and you could mix and match driver versions with USB versions.
People were using emulators and 3rd party knock off glasses, so Nvidia changed it to disable the hacks.
Now the USB driver version is required to match the driver version.
If there's a problem with DDU, you can report it in his thread and he will act on it.
https://forums.geforce.com/default/topic/550192/geforce-drivers/wagnard-tools-ddu-gmp-tdr-manipulator-new-cpu-core-analyzer-updated-04-05-2016-/
I hope you have it all sorted now.
I guess the only way to fix this issue is to reinstall win10 from scratch but alas I cannot afford the time to do that. I never had this kind of issue under win7.
One thing I noticed is that the controller turns itself off when not in use, it blinks a few times and stops. During this last crash it was like it failed to turn on, the screen got brighter like it does normally when enabling 3d stereo but the controller stayed off...
It is weird though that no one seems to know much about this. I've posted about this twice now and never found out anything useful. At least I'm down to a BSOD every 6th or 8th launch now. And now that I think about it, my avoiding Chrome idea is probably what's really lessening the crashes rather than that new driver. Of course they still eventually happen even if Chrome is completely avoided. Just takes more launches it seems.
Forgot to add that just like you're experiencing, I sometimes get a crash without any BSOD when launching a game with 3D enabled too. Crash dump analysis doesn't seem to pick up on those though. And also, I had the issue back when my system was Windows 7 too. Upgrading to 10 didn't seem to change the frequency of BSOD's for me.
Is it certain games? GPU model?
Do you have a fresh win10 install or was it also an upgrade?
If I had to guess, the emitter is refusing to turn on and the display driver just crashes so my question is does anybody know how to get the emitter to never turn itself off ? I would like to check if the problem is due to this power saving function. I've already tried several things like turning off usb power saving from Windows Control Panel and Device Manager but the emitter automatically turns off no matter what. Also, the emitter is plugged directly into one of the back usb ports. I would really appreciate any info on this.
Edit:
Changing USB ports fixes this problem but if I exit the application the emitter turns off instantly and the issue is back upon running the application a second time. After trying this it seems that now I'm getting a taskbar pop-up stating that one of my recent usb devices malfunctioned and is no longer recognized by Windows.
Later edit:
Ok so it seems that the problem is indeed the emitter but it's because of this Windows USB Power Saving and I've tried a lot of fixes to disable this nonsense including finding and modifying the Windows registry for the specific USB hub I've plugged the emitter into but nothing works so I guess the only workaround for me at the moment is to just re-plug the usb emitter every time. I have to say that my Windows is up to date and imo this is such a shame since I believe this has caused a ton of issues for so many people and nVidia or Microsoft have yet to fix this after all these years.
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.
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.
I got a 3d capable monitor, and the nvidia 3d vision kit.
Ever since I've been using it, chrome, firefox and a few games will give me a bsod in the same faulting module.
FAULTING_IP:
nt!IoCancelIrp+62
fffff801`c82a4986 488b4928 mov rcx,qword ptr [rcx+28h]
which was called by nvstusb+0xa630
I'm also a programmer, so I have the debug stuff that lets me see where it crashed at.
It was fine the first two days, but now its 1-2 bsod per day.
It happens suddenly, on pretty benign actions like opening a new page in FF/chrome, or opening a menu in a game. I get these bsods in game while the controller is lit, so the last post, i'm not sure if that will help me.
I don't know what else to do.
One other problem that I have is that My monitor has a severe ghosting issue when the monitor is not in 3d mode, or specifically the nvidia lightboost strobing. I used an app to get it to perm be on a month ago that worked fine. But than when my 3d kit arrived, 3d doesnt work, er well more specifically nvidia gives me a red warning box over everything that its not a 3d refresh rate. so after removing that,
So if I open 3d player then close it, it will pop the refresh rate into 3d mode, then ghosting is gone. This may also contribute to my bsod, I'll try not doing that to see if that helps me when not in a 3d game. I got to stop losing work on these bsods.
Is there anything we can do to fix this bsod issue?