Windows 10: BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL d1

Can someone help me? This kind of crash happens to me quite often lately, so I decided to check it out by opening and reading the minidumpfile by using WinDbgThis is the text:************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring reposito

:)

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) BSOD | DUAL MONITORS

Ok, so i built my computer just a few weeks ago, and all was completely fine. I never got any BSODs at all. My specs are AMD fx 6300, EVGA gtx 650 ti, and 6 gb RAM. So yesterday I decided to plug in
a second monitor WHILE MY COMPUTER WAS ON, and instantly got a blue screen and then restarted. All was fine for the rest of that day and earlier today. I played a League game, and a CSGO game. No BSOD. Then I decided I would play WoW, while having skype and
chrome open on second monitor. Then suddenly, my headset, mouse, and keyboard quit working for a bout 10 seconds, and then BSOD, saying DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post what the dump file says if thats needed, but for right now here is this.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

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 kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000000000074, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff801114c4d5a, address which referenced memory

ALSO: I AM ON WINDOWS 10, ONE MONITOR IS RUNNING OFF HDMI TO MINI HDMI AND THE OTHER IS RUNNING OFF OF VGA TO DVI both are plugged into gtx 650 ti

EDIT: http://textuploader.com/a2fim Here is the minidump file i got
from Windbg

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) BSOD | DUAL MONITORS

Hi Korey,

Thank you for posting your query on Microsoft Community.

Are you able to boot to your system?

Blue screens (BSOD) is mostly occur due to hardware and sometimes due to incompatible software. In a lot of cases it is a corrupted driver or a driver conflict. The most common causes of blue screens are overheating, faulty RAM,
and video card problem.

I suggest you to update all your drivers. You can update drivers from the Device Manager.

Follow the steps to update drivers from the Device Manager:

• 
  Right click on Start button, type
  Device Manager and Enter.
  
• 
  Find the drivers which needs to be installed and also see if there are any warning symbols. If yes update the drivers.
  
• 
  Right click and click on
  Properties, and go to Driver tab and click on Update driver.
  

If you still face the issue you can check if you need to update the chipset drivers and also load default setting in BIOS.

BIOS DISCLAIMER -

Modifying BIOS/complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting
from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.


I suggest you please go to the below link suggestion provided Sharath Srinivasa
and try the steps. The steps are for Black screen but you may also try the steps and check if it helps:

http://answers.microsoft.com/en-us/...-f0da-4696-91c2-a7f305301d3d?tm=1438892592298

Let us know the status of the issue. We will be glad to assist u further.

Thank You.

 

driver_irql_not_less_or_equal (d1) (nvlddmkm.sys)


Hi


When I play demanding games I can get a bsod, the latest game being Rise of the Tomb Raider. This is the first game that bsods within 10 minutes no matter what. And so far this is what I can read out of the .dmp files : "driver_irql_not_less_or_equal (d1)" - (nvlddmkm.sys).

What happens is: without warning or fps drop the screen goes black (disconnects). Then the sound goes on for a bit, before it's cut goes into a loop. Then the PC restarts, or I have to push the restart button.
I have used the Display Driver Uninstaller 15.7.4.0 and reinstalled the Nvidia driver. Daemon tools have also been removed. Have stopped the Nvidia streamer service through msconfig too, just to see if it helped. No luck with any of the "fixes". I have run Furmark test without any issues, and a "sfc/ scannow". I've been monitoring the CPU and GPU temp before the crash, but no spikes in temperature.
*Side note - If I run Intel extreme tuning utility CPU stress test, the CPU reach almost 100 C in about 3 min. But that's under 100% load. But I guess that's unrelated, since the CPU don't get that load or temp during games. Still a indicator that something is wrong. And the Intel Diagnostic tool tells me there is something wrong with CPU Freq (Module - CPUFreq.exe did not create a results file.) , and it does not pass the stress test there as well. But I can't find anything about that in the .dmp file.


I'm not experienced enough to understand the rest. But so far by comparing similar problems others have had, I understand that Rise of the Tomb Raider are sending an invalid call/path to the Nvidia driver and makes it crash. correct me if i'm wrong.

Any tips on what to do?

---

ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+4d5acf )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000004e7d75, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800133d5acf, address which referenced memory