Windows 10: IRQL_NOT_LESS_OR_EQUAL, seems related to Nvidia SLI

Hello, I am new to this forum but not new to computers, but with my recent new build I have been having problems that I just cant seem to fix. This all started when I built my new system, with an Asus Sabertooth x99 motherboard, intel I7-5820k, 32gb corsair vengeance ddr4, corsair tx950 psu, and 2 gtx670 ftw 4gb graphics cards in SLI, running windows 10 pro. everything was going fine until I set up the SLI configuration, now it crashes after about 20 min of gameplay, video playback, or anything that really makes use of SLI. I cannot identify the culprit driver, and I was hoping someone here could analyze my minidump files. Also lately following a crash it has started giving: a required device isnt connected or cant be accessed, Error code 0xc000000e, but if I unplug it for 10 seconds it is fine.

:)

 

PC Starts Hanging and Crashes Randomly (Error Message in Post)

Two errors were reported, IRQL_NOT_LESS_OR_EQUAL (a) and KMODE_EXCEPTION_NOT_HANDLED (1e).

Both errors seemed to be related to the graphics, in particular the NVIDIA.

 

Windows 10 Sli issues since Anniversary update

I am experiencing what appears to be the same issue. It does not seem to occur when SLI is turned off and began with the installation of 1607.

Intel i7-4930K

G.SKILL Ripjaws Z Series 32GB (8 x 4GB) Model F3-17000CL9Q2-32GBZH

SLI NVidia 980

Asus Sabertooth X79

Win 1607 - 14393.222

Nvidia driver 372.90

 

Disable verifier, it is not needed now.

• Open an admin command prompt
• Enter "verifier/reset" (without quotes)

You are missing a driver
Driver Reference Table - IOMap64.sys
Code: *** WARNING: Unable to verify timestamp for IOMap64.sys *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys[/quote]

 

[/quote] I have disabled verifier and updated the driver, but still continue to blue screen in SLI gaming. the new driver in question is ntoskrl.exe. this is another new one from last time, and I am starting to think something else is causing these drivers to malfuction. It seems like the problem could be related directly to SLI as windows and multi-card SLI havent been playing nice together since windows 10. I will upload more dump files next time it crashes.