BSOD IRQ problem with Win10

Soldato
Joined
19 May 2005
Posts
5,053
Location
Doncaster
Hi, didn't put this in the software forum because I don't think it's a Win10 issue as such. Also sorry this is long and thanks to anyone that takes the time to read it.

Anyway, getting some BSODs since installing W10, although I also used to get a few with Win7. The error I saw last time was IRQL_NOT_LESS_OR_EQUAL, and when I google that I see talk of IRQ conflicts, so looking in device manager I see these two entries sharing IRQ 16 -

(16) Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
(16) NVIDIA GeForce GTX 970

I've looked in my BIOS and it doesn't seem like you can assign any IRQs manually with my board (MSI Z77A-G43) and I can't change them in device manager either. I honestly don't see any way of changing this :(

It might not even be what's causing the BSODs though. When I look at the crash dump in the Windows SDK debugger it's listing the app that caused the problem as Firefox and the specific file as nvstusb.sys which is the stereoscopic Nvidia stereo 3D driver (I have Nvidia 3D Vision). These drivers include a plug-in for Firefox, which I have disabled, but it's still listed as a plug-in inside Firefox, so it could still be causing issues.

The other thing I noticed in Win10 is that the 3D Vision emitter (a little pyramid shaped IR emitter than sends a sync signal to the 3D glasses) turns itself off when not in 3D mode rather than the light just going dull. It's not supposed to do this and it's possible that could be causing the problem as windows tries to power it back up.

The BSODs, one was watching a twitch stream, one when just web browsing and one when launching Dark Souls (with stereo 3D enabled). The BSODs I used to get in Win7 were mostly while watching twitch streams btw. I always just assumed they were adobe flash being buggy.

Anyone have any ideas, especially with fixing the IRQ sharing? I'd rather the 970 had an IRQ to itself, but I need my USB devices. I have mouse, keyboard, IR emitter, xbox360 pad, and audio interface (low latency soundcard) all connected through USB btw.

Thanks.
 
Last edited:
IRQ conflicts used to be the bane of every PC build (back in DOS, 16 bit windows days) however I do not recall recently any issues. You are right, Windows sets the IRQ sharing and memory address areas for most things nowadays and I do not know if you can allocate resources manually in device manager. It would be in the operating system not the bios.

At one time it was all in the autoexec.bat or config.sys files. :)
 
Back
Top Bottom