3D Vision controller crashing my computer Bugcheck 9f with nvstusb
Greetings:
I'm having an annoying problem where my computer crashes once in a while. I don't shutdown the computer, but it does go to sleep after about an hour. Sometimes when I wake it up I find that the machine will not wake and I have to manually power it back on. When this happens I find that a minidump has been created. Debugging the minidump seems to point fingers at the 3D Vision controller, more specificially, NVSTUSB.SYS.
This issue has been occurring since September (it's no December), which is about the time I purchased my 3D Vision kit (Asus bundle with the glasses). I would try different drivers, but these latest drivers resolved some of the issues I had with some of the games that I am playing and I would rather not use 3D than go back to the previous drivers. I know that the 3D vision controller has been separated from the video driver, and I'm hoping that this may actually help me get a fix quicker (and easier!!!).
Any recommendations?
The Windbg output is as follows:
[code]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121310-21512-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`0453d500?
Symbol search path is: SRV*E:\Symbols\store*http://msdl.microsoft.com/download/symbols;E:\Symbols\Win7_x64_Retail
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`03086e50
Debug session time: Sun Dec 12 20:46:28.219 2010 (UTC - 5:00)
System Uptime: 2 days 14:47:11.820
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006f68060, Physical Device Object of the stack
Arg3: fffff8000453d518, Functional Device Object of the stack
Arg4: fffffa8007a8c730, The blocked IRP
I'm having an annoying problem where my computer crashes once in a while. I don't shutdown the computer, but it does go to sleep after about an hour. Sometimes when I wake it up I find that the machine will not wake and I have to manually power it back on. When this happens I find that a minidump has been created. Debugging the minidump seems to point fingers at the 3D Vision controller, more specificially, NVSTUSB.SYS.
This issue has been occurring since September (it's no December), which is about the time I purchased my 3D Vision kit (Asus bundle with the glasses). I would try different drivers, but these latest drivers resolved some of the issues I had with some of the games that I am playing and I would rather not use 3D than go back to the previous drivers. I know that the 3D vision controller has been separated from the video driver, and I'm hoping that this may actually help me get a fix quicker (and easier!!!).
Any recommendations?
The Windbg output is as follows:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
1. disable sleep mode in windows
2. If you must run the pc 24/7 with sleep mode on, then do it on another computer (nettop/netbook or second pc or whatever)
The gaming pc (in my sig), which I built recently, [s]also does not recover from sleep mode[/s]. Dont know why. I just turned off sleep mode. And I have an old second pc for internet/work/non-gaming, which by the way, does stay on 24/7 and it sleeps just fine.
[i]oops. It does recover from sleep mode but only if I push the power button[/i]
2. If you must run the pc 24/7 with sleep mode on, then do it on another computer (nettop/netbook or second pc or whatever)
The gaming pc (in my sig), which I built recently, also does not recover from sleep mode. Dont know why. I just turned off sleep mode. And I have an old second pc for internet/work/non-gaming, which by the way, does stay on 24/7 and it sleeps just fine.
oops. It does recover from sleep mode but only if I push the power button
I apologize -- I don't believe I made myself clear. I never have a problem actually waking the PC. The problem is that it crashes on occasion, all with the NVSTUSB driver. I notice it when I go to wake the PC and it doesn't wake because it has been powered off. When I manually power the machine back on, windows informs me that it has recovered and that a crash dump has been saved.
I do appreciate your advice, but I was looking for more technical assistance for trouble shooting the driver. I would like to use sleep mode, and I don't see any reason that I can't, especially if the problem lies within the driver. I don't have another computer to use as I've put all of my money into this one and I use it for everything. I have a feeling I'm going to need to log a support case with nvidia for this one...
I apologize -- I don't believe I made myself clear. I never have a problem actually waking the PC. The problem is that it crashes on occasion, all with the NVSTUSB driver. I notice it when I go to wake the PC and it doesn't wake because it has been powered off. When I manually power the machine back on, windows informs me that it has recovered and that a crash dump has been saved.
I do appreciate your advice, but I was looking for more technical assistance for trouble shooting the driver. I would like to use sleep mode, and I don't see any reason that I can't, especially if the problem lies within the driver. I don't have another computer to use as I've put all of my money into this one and I use it for everything. I have a feeling I'm going to need to log a support case with nvidia for this one...
Suspend is a bit of a crapshoot with random hardware.
It's lot better in Win7, but even if the device handles it properly it might not work in combination with other devices.
USB devices that pull power from the port seem to be the usual issue, I suspect what happens is that windows tries to re-init the device before the device has power or has had a chance to get into a good state.
I have a keyboard that won't come out of suspend, once the machine is back up and running unplugging and replugging the USB cable solves the issue.
I also have an active display port adapter that makes it impossible for my work computer to come out of suspend.
Driver still shouldn't crash though.
About your only option is to go into your bios, and play with the suspend mode settings, and if you have the option to supply 5V to the USB durng suspend that might help.
Suspend is a bit of a crapshoot with random hardware.
It's lot better in Win7, but even if the device handles it properly it might not work in combination with other devices.
USB devices that pull power from the port seem to be the usual issue, I suspect what happens is that windows tries to re-init the device before the device has power or has had a chance to get into a good state.
I have a keyboard that won't come out of suspend, once the machine is back up and running unplugging and replugging the USB cable solves the issue.
I also have an active display port adapter that makes it impossible for my work computer to come out of suspend.
Driver still shouldn't crash though.
About your only option is to go into your bios, and play with the suspend mode settings, and if you have the option to supply 5V to the USB durng suspend that might help.
I had windows crashing on me in 3D games because I had a faulty USB keyboard. Suspend doesn't really work that well with USB as already mentioned, but if you still have problems try removing all your USB devices apart from 3d vision, mouse + keyboard and see if that makes a difference. Personally, I went with a PS/2 keyboard in the end.
I had windows crashing on me in 3D games because I had a faulty USB keyboard. Suspend doesn't really work that well with USB as already mentioned, but if you still have problems try removing all your USB devices apart from 3d vision, mouse + keyboard and see if that makes a difference. Personally, I went with a PS/2 keyboard in the end.
Dell XPS 730 H2C
Chipset : nVidia nForce 790i Ultra SLi SPP
Processor : Intel Core 2 Extreme QX9650 @ 3.67GHz
Physical Memory : 4096MB (4 x 1024 1333MHz DDR3-SDRAM )
Video Card : 2 x NVIDIA GeForce GTX 580 SLI
Hard Disk : NVIDIA STRIPE 931.52GB
Monitor Type : 23" Acer GD245HQ
Operation "Sandy Balls" - in planning phase. "Go balls deep!"
Just found this thread when searching for an issue I'm having.
Having some BSODs with Win10, and from the crash dump the file causing the problem seems to be nvstusb.sys, which is a 3D Vision file, by the looks of it something to do with the emitter. I'm thinking the issue might be connected to the power saving switching the emitter off (as you'll know it switches completely off in W10 rather than the light just going dull), or it might be the 3D Vision plug-in for Firefox (which I have disabled, but it's still listed as a plug-in), since the crash dump seems to be listing the app that crashed as Firefox.
The error on the BSOD page was IRQL_NOT_LESS_OR_EQUAL, and this might have no connection at all, but I notice one of my USB controllers (on the mobo) is sharing IRQ 16 with my GTX970. I can't find a way to change any IRQs in my BIOS. I've had mobos in the past where you could manually set which device uses which IRQ, but it seems this current board (MSI Z77A-G43) doesn't have a way of doing this, and it can't be done in device manager either.
I've disabled power saving on every USB thing that has a power saving option in device manager, but the emitter is still turning off btw.
So 3 possible causes -
1) emitter/USB power saving
2) 3D Vision plug-in for Firefox
3) IRQ conflict/sharing.
Any suggestions for fixing any of these issues? Thanks in advance.
Just found this thread when searching for an issue I'm having.
Having some BSODs with Win10, and from the crash dump the file causing the problem seems to be nvstusb.sys, which is a 3D Vision file, by the looks of it something to do with the emitter. I'm thinking the issue might be connected to the power saving switching the emitter off (as you'll know it switches completely off in W10 rather than the light just going dull), or it might be the 3D Vision plug-in for Firefox (which I have disabled, but it's still listed as a plug-in), since the crash dump seems to be listing the app that crashed as Firefox.
The error on the BSOD page was IRQL_NOT_LESS_OR_EQUAL, and this might have no connection at all, but I notice one of my USB controllers (on the mobo) is sharing IRQ 16 with my GTX970. I can't find a way to change any IRQs in my BIOS. I've had mobos in the past where you could manually set which device uses which IRQ, but it seems this current board (MSI Z77A-G43) doesn't have a way of doing this, and it can't be done in device manager either.
I've disabled power saving on every USB thing that has a power saving option in device manager, but the emitter is still turning off btw.
So 3 possible causes -
1) emitter/USB power saving
2) 3D Vision plug-in for Firefox
3) IRQ conflict/sharing.
Any suggestions for fixing any of these issues? Thanks in advance.
Hello I encounter the same problem under Windows 10 with nvstusb. This is manifested by BSOD. I do not know how to fix this.
Asus Maximus VII Ranger - i7 4790k - Zotac GTX 980 AMP Edition - 16GB DDR3 G.Skill - ASUS VG278HE - Windows 7
My 3D Vision Live Gallery: http://photos.3dvisionlive.com/Torque99 My first 3D Trailer: https://youtu.be/SRF5fNOV-H8 -> Download the video and watch it with a 3D video player
I'm having an annoying problem where my computer crashes once in a while. I don't shutdown the computer, but it does go to sleep after about an hour. Sometimes when I wake it up I find that the machine will not wake and I have to manually power it back on. When this happens I find that a minidump has been created. Debugging the minidump seems to point fingers at the 3D Vision controller, more specificially, NVSTUSB.SYS.
This issue has been occurring since September (it's no December), which is about the time I purchased my 3D Vision kit (Asus bundle with the glasses). I would try different drivers, but these latest drivers resolved some of the issues I had with some of the games that I am playing and I would rather not use 3D than go back to the previous drivers. I know that the 3D vision controller has been separated from the video driver, and I'm hoping that this may actually help me get a fix quicker (and easier!!!).
Any recommendations?
The Windbg output is as follows:
[code]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121310-21512-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`0453d500?
Symbol search path is: SRV*E:\Symbols\store*http://msdl.microsoft.com/download/symbols;E:\Symbols\Win7_x64_Retail
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`03086e50
Debug session time: Sun Dec 12 20:46:28.219 2010 (UTC - 5:00)
System Uptime: 2 days 14:47:11.820
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8006f68060, fffff8000453d518, fffffa8007a8c730}
Probably caused by : usbhub.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006f68060, Physical Device Object of the stack
Arg3: fffff8000453d518, Functional Device Object of the stack
Arg4: fffffa8007a8c730, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc2d
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88005800000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`0453d4c8 fffff800`02f28273 : 00000000`0000009f 00000000`00000003 fffffa80`06f68060 fffff800`0453d518 : nt!KeBugCheckEx
fffff800`0453d4d0 fffff800`02ec529e : fffff800`0453d600 fffff800`0453d600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`0453d570 fffff800`02ec4dd6 : fffffa80`03fd3718 fffffa80`03fd3718 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`0453d5e0 fffff800`02ec54be : 0000020e`4576bc93 fffff800`0453dc58 00000000`00dd1626 fffff800`03036748 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0453dc30 fffff800`02ec4cb7 : 000000ab`d7bf17c6 000000ab`00dd1626 000000ab`d7bf1723 00000000`00000026 : nt!KiTimerExpiration+0x1be
fffff800`0453dcd0 fffff800`02ec1eea : fffff800`03033e80 fffff800`03041c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`0453dd80 00000000`00000000 : fffff800`0453e000 fffff800`04538000 fffff800`0453dd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_nvstusb_IMAGE_usbhub.sys
BUCKET_ID: X64_0x9F_3_nvstusb_IMAGE_usbhub.sys
Followup: MachineOwner
---------
[/code]
I'm having an annoying problem where my computer crashes once in a while. I don't shutdown the computer, but it does go to sleep after about an hour. Sometimes when I wake it up I find that the machine will not wake and I have to manually power it back on. When this happens I find that a minidump has been created. Debugging the minidump seems to point fingers at the 3D Vision controller, more specificially, NVSTUSB.SYS.
This issue has been occurring since September (it's no December), which is about the time I purchased my 3D Vision kit (Asus bundle with the glasses). I would try different drivers, but these latest drivers resolved some of the issues I had with some of the games that I am playing and I would rather not use 3D than go back to the previous drivers. I know that the 3D vision controller has been separated from the video driver, and I'm hoping that this may actually help me get a fix quicker (and easier!!!).
Any recommendations?
The Windbg output is as follows:
2. If you must run the pc 24/7 with sleep mode on, then do it on another computer (nettop/netbook or second pc or whatever)
The gaming pc (in my sig), which I built recently, [s]also does not recover from sleep mode[/s]. Dont know why. I just turned off sleep mode. And I have an old second pc for internet/work/non-gaming, which by the way, does stay on 24/7 and it sleeps just fine.
[i]oops. It does recover from sleep mode but only if I push the power button[/i]
2. If you must run the pc 24/7 with sleep mode on, then do it on another computer (nettop/netbook or second pc or whatever)
The gaming pc (in my sig), which I built recently,
also does not recover from sleep mode. Dont know why. I just turned off sleep mode. And I have an old second pc for internet/work/non-gaming, which by the way, does stay on 24/7 and it sleeps just fine.oops. It does recover from sleep mode but only if I push the power button
Thief 1/2/gold in 3D
https://forums.geforce.com/default/topic/523535/3d-vision/thief-1-2-and-system-shock-2-perfect-3d-with-unofficial-patch-1-19
http://photos.3dvisionlive.com/Partol/album/509eb580a3e067153c000020/
[Acer GD245HQ - 1920x1080 120Hz] [Nvidia 3D Vision]
[MSI H81M-P33 with Pentium G3258 @ 4.4GHz and Zalman CNPS5X}[Transcend 2x2GB DDR3]
[Asus GTX 750 Ti @ 1350MHz] [Intel SSD 330 - 240GB]
[Creative Titanium HD + Beyerdynamic DT 880 (250ohm) headphones] [Windows 7 64bit]
I do appreciate your advice, but I was looking for more technical assistance for trouble shooting the driver. I would like to use sleep mode, and I don't see any reason that I can't, especially if the problem lies within the driver. I don't have another computer to use as I've put all of my money into this one and I use it for everything. I have a feeling I'm going to need to log a support case with nvidia for this one...
I do appreciate your advice, but I was looking for more technical assistance for trouble shooting the driver. I would like to use sleep mode, and I don't see any reason that I can't, especially if the problem lies within the driver. I don't have another computer to use as I've put all of my money into this one and I use it for everything. I have a feeling I'm going to need to log a support case with nvidia for this one...
It's lot better in Win7, but even if the device handles it properly it might not work in combination with other devices.
USB devices that pull power from the port seem to be the usual issue, I suspect what happens is that windows tries to re-init the device before the device has power or has had a chance to get into a good state.
I have a keyboard that won't come out of suspend, once the machine is back up and running unplugging and replugging the USB cable solves the issue.
I also have an active display port adapter that makes it impossible for my work computer to come out of suspend.
Driver still shouldn't crash though.
About your only option is to go into your bios, and play with the suspend mode settings, and if you have the option to supply 5V to the USB durng suspend that might help.
It's lot better in Win7, but even if the device handles it properly it might not work in combination with other devices.
USB devices that pull power from the port seem to be the usual issue, I suspect what happens is that windows tries to re-init the device before the device has power or has had a chance to get into a good state.
I have a keyboard that won't come out of suspend, once the machine is back up and running unplugging and replugging the USB cable solves the issue.
I also have an active display port adapter that makes it impossible for my work computer to come out of suspend.
Driver still shouldn't crash though.
About your only option is to go into your bios, and play with the suspend mode settings, and if you have the option to supply 5V to the USB durng suspend that might help.
My Blog
Dell XPS 730 H2C
Chipset : nVidia nForce 790i Ultra SLi SPP
Processor : Intel Core 2 Extreme QX9650 @ 3.67GHz
Physical Memory : 4096MB (4 x 1024 1333MHz DDR3-SDRAM )
Video Card : 2 x NVIDIA GeForce GTX 580 SLI
Hard Disk : NVIDIA STRIPE 931.52GB
Monitor Type : 23" Acer GD245HQ
Operation "Sandy Balls" - in planning phase. "Go balls deep!"
Having some BSODs with Win10, and from the crash dump the file causing the problem seems to be nvstusb.sys, which is a 3D Vision file, by the looks of it something to do with the emitter. I'm thinking the issue might be connected to the power saving switching the emitter off (as you'll know it switches completely off in W10 rather than the light just going dull), or it might be the 3D Vision plug-in for Firefox (which I have disabled, but it's still listed as a plug-in), since the crash dump seems to be listing the app that crashed as Firefox.
The error on the BSOD page was IRQL_NOT_LESS_OR_EQUAL, and this might have no connection at all, but I notice one of my USB controllers (on the mobo) is sharing IRQ 16 with my GTX970. I can't find a way to change any IRQs in my BIOS. I've had mobos in the past where you could manually set which device uses which IRQ, but it seems this current board (MSI Z77A-G43) doesn't have a way of doing this, and it can't be done in device manager either.
I've disabled power saving on every USB thing that has a power saving option in device manager, but the emitter is still turning off btw.
So 3 possible causes -
1) emitter/USB power saving
2) 3D Vision plug-in for Firefox
3) IRQ conflict/sharing.
Any suggestions for fixing any of these issues? Thanks in advance.
Asus Maximus VII Ranger - i7 4790k - Zotac GTX 980 AMP Edition - 16GB DDR3 G.Skill - ASUS VG278HE - Windows 7
My 3D Vision Live Gallery: http://photos.3dvisionlive.com/Torque99
My first 3D Trailer: https://youtu.be/SRF5fNOV-H8 -> Download the video and watch it with a 3D video player