DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) BSOD | DUAL MONITORS

Status
Not open for further replies.

koreykarch

Reputable
Sep 23, 2015
3
0
4,510
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
 
Solution
most likely a driver overwrote another drivers data and caused the second driver to try to access a bad memory location= 74

you would have to provide a memory dump from c:\windows\minidump directory and put it on a server like microsoft one drive, mark it for public access and post a link.

or you would have to start cmd.exe as an admin, then run
verifier.exe /standard /all
and reboot, this will force windows to check the driver for corruption of memory. Windows will bugcheck and name the bad driver in the memory dump.
Note: use verifier.exe /reset to turn of verifier when you are done testing.
if the system bugcheck during boot, you might have to boot into safe mode and turn off verifier before you can boot correctly again.
most likely a driver overwrote another drivers data and caused the second driver to try to access a bad memory location= 74

you would have to provide a memory dump from c:\windows\minidump directory and put it on a server like microsoft one drive, mark it for public access and post a link.

or you would have to start cmd.exe as an admin, then run
verifier.exe /standard /all
and reboot, this will force windows to check the driver for corruption of memory. Windows will bugcheck and name the bad driver in the memory dump.
Note: use verifier.exe /reset to turn of verifier when you are done testing.
if the system bugcheck during boot, you might have to boot into safe mode and turn off verifier before you can boot correctly again.
 
Solution
Status
Not open for further replies.