Windows 10: BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

Hello Everyone,


This device first had a BSOD: DRIVER_OVERRAN_STACK_BUFFER (f7) error but after performing a Windows Update, it resolved that error.

Now the BSOD Error came back with "DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)" and I've been trying to resolve this issue for the past week now but haven't had much luck with it. I've attempted the troubleshooting steps from this video so far: https://www.youtube.com/watch?v=eCbLI6MHrWs but it didn't find any errors. Any feedback is much appreciated, thank you in advance!! Below is the dump file.


Microsoft (R) Windows Debugger Version 10.0.17763.132 X86

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\her.vang\Desktop\Dump Files 2\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 17134 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 17134.1.amd64fre.rs4_release.180410-1804

Machine Name:

Kernel base = 0xfffff802`3e41a000 PsLoadedModuleList = 0xfffff802`3e7c8170

Debug session time: Thu Dec 6 12:59:40.655 2018 (UTC - 6:00)

System Uptime: 0 days 2:24:20.949

Loading Kernel Symbols

......................................Page 20045a65a too large to be in the dump file.

.........................

................................................................

................................................................

......................................

Loading User Symbols



Loading unloaded module list

.....................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck D1, {fffff802914fc2dd, ff, 86, fffff802914fc2dd}



Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+425 )



Followup: MachineOwner

---------



0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



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: fffff802914fc2dd, memory referenced

Arg2: 00000000000000ff, IRQL

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

Arg4: fffff802914fc2dd, address which referenced memory



Debugging Details:

------------------





KEY_VALUES_STRING: 1





STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 401



BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804



SYSTEM_MANUFACTURER: Microsoft Corporation



SYSTEM_PRODUCT_NAME: Surface Book



SYSTEM_SKU: Surface_Book



SYSTEM_VERSION: D:0B:09F:1C:03P:38



BIOS_VENDOR: Microsoft Corporation



BIOS_VERSION: 91.2327.769



BIOS_DATE: 08/23/2018



BASEBOARD_MANUFACTURER: Microsoft Corporation



BASEBOARD_PRODUCT: Surface Book



DUMP_TYPE: 1



BUGCHECK_P1: fffff802914fc2dd



BUGCHECK_P2: ff



BUGCHECK_P3: 86



BUGCHECK_P4: fffff802914fc2dd



READ_ADDRESS: fffff802914fc2dd



CURRENT_IRQL: 0



FAULTING_IP:

+0

fffff802`914fc2dd ?? ???



ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.



BUGCHECK_STR: DISABLED_INTERRUPT_FAULT



CPU_COUNT: 4



CPU_MHZ: af8



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 4e



CPU_STEPPING: 3



CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXPNP: 1 (!blackboxpnp)





DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: System



ANALYSIS_SESSION_HOST: A0121



ANALYSIS_SESSION_TIME: 12-10-2018 14:28:29.0119



ANALYSIS_VERSION: 10.0.17763.132 x86fre



TRAP_FRAME: fffff8024085e490 -- (.trap 0xfffff8024085e490)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000048

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff802914fc2dd rsp=fffff8024085e620 rbp=fffff8023e32dec8

r8=ffff8c04a77f5390 r9=0000000000000002 r10=ffff8c04a77f5280

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up di ng nz na po nc

fffff802`914fc2dd ?? ???

Resetting default scope



LAST_CONTROL_TRANSFER: from fffff8023e5d4269 to fffff8023e5c3680



FAILED_INSTRUCTION_ADDRESS:

+0

fffff802`914fc2dd ?? ???



STACK_TEXT:

fffff802`4085e348 fffff802`3e5d4269 : 00000000`0000000a fffff802`914fc2dd 00000000`000000ff 00000000`00000086 : nt!KeBugCheckEx

fffff802`4085e350 fffff802`3e5d0ee5 : ffffffff`ffffffff fffff802`3e68ce79 00000000`00000004 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffff802`4085e490 fffff802`914fc2dd : 00000000`91000085 00000000`9100009d fffff802`3d32de0d 00000005`bba1edcd : nt!KiPageFault+0x425

fffff802`4085e620 00000000`91000085 : 00000000`9100009d fffff802`3d32de0d 00000005`bba1edcd ffff8c04`e60000c8 : 0xfffff802`914fc2dd

fffff802`4085e628 00000000`9100009d : fffff802`3d32de0d 00000005`bba1edcd ffff8c04`e60000c8 ffff8c04`f60000c8 : 0x91000085

fffff802`4085e630 fffff802`3d32de0d : 00000005`bba1edcd ffff8c04`e60000c8 ffff8c04`f60000c8 ffff8c04`b6a113e8 : 0x9100009d

fffff802`4085e638 00000005`bba1edcd : ffff8c04`e60000c8 ffff8c04`f60000c8 ffff8c04`b6a113e8 00000008`8900008e : 0xfffff802`3d32de0d

fffff802`4085e640 ffff8c04`e60000c8 : ffff8c04`f60000c8 ffff8c04`b6a113e8 00000008`8900008e 00000001`70010102 : 0x00000005`bba1edcd

fffff802`4085e648 ffff8c04`f60000c8 : ffff8c04`b6a113e8 00000008`8900008e 00000001`70010102 00000002`a900006c : 0xffff8c04`e60000c8

fffff802`4085e650 ffff8c04`b6a113e8 : 00000008`8900008e 00000001`70010102 00000002`a900006c ffff8c04`e9a110ec : 0xffff8c04`f60000c8

fffff802`4085e658 00000008`8900008e : 00000001`70010102 00000002`a900006c ffff8c04`e9a110ec 00000000`d753fbec : 0xffff8c04`b6a113e8

fffff802`4085e660 00000001`70010102 : 00000002`a900006c ffff8c04`e9a110ec 00000000`d753fbec 00000002`00000003 : 0x00000008`8900008e

fffff802`4085e668 00000002`a900006c : ffff8c04`e9a110ec 00000000`d753fbec 00000002`00000003 ffffffff`ffffffff : 0x00000001`70010102

fffff802`4085e670 ffff8c04`e9a110ec : 00000000`d753fbec 00000002`00000003 ffffffff`ffffffff 00000000`00000000 : 0x00000002`a900006c

fffff802`4085e678 00000000`d753fbec : 00000002`00000003 ffffffff`ffffffff 00000000`00000000 ffff8c04`ffffffff : 0xffff8c04`e9a110ec

fffff802`4085e680 00000002`00000003 : ffffffff`ffffffff 00000000`00000000 ffff8c04`ffffffff ffff8c04`a4a1d360 : 0xd753fbec

fffff802`4085e688 ffffffff`ffffffff : 00000000`00000000 ffff8c04`ffffffff ffff8c04`a4a1d360 ffff8c04`a77f5280 : 0x00000002`00000003

fffff802`4085e690 00000000`00000000 : ffff8c04`ffffffff ffff8c04`a4a1d360 ffff8c04`a77f5280 ffff8c04`a6a11520 : 0xffffffff`ffffffff





THREAD_SHA1_HASH_MOD_FUNC: bf99962f16aee8a6a536cfcc5454c0cd4db15ac9



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 79f80cc7f571cb0ec417faf51633559f1df31f0e



THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b



FOLLOWUP_IP:

nt!KiPageFault+425

fffff802`3e5d0ee5 33c0 xor eax,eax



FAULT_INSTR_CODE: ffb0c033



SYMBOL_STACK_INDEX: 2



SYMBOL_NAME: nt!KiPageFault+425



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 5be4eec3



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 425



FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_nt!KiPageFault



BUCKET_ID: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_nt!KiPageFault



PRIMARY_PROBLEM_CLASS: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_nt!KiPageFault



TARGET_TIME: 2018-12-06T18:59:40.000Z



OSBUILD: 17134



OSSERVICEPACK: 0



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: 2018-11-08 20:19:47



BUILDDATESTAMP_STR: 180410-1804



BUILDLAB_STR: rs4_release



BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804



ANALYSIS_SESSION_ELAPSED_TIME: 7a1



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:disabled_interrupt_fault_code_av_bad_ip_nt!kipagefault



FAILURE_ID_HASH: {f2ab72c5-099d-9077-bfcf-ba12aa825b36}



Followup: MachineOwner


---------

:)

 

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:

Black screen after upgrading to Windows 10

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

Thank You.

 

BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL

I have been getting random BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL - Source: nwifi.sys) in the last 3 days. They seem to only appear when playing videos on YouYube, but it might be a coincidence.

What has changed in the last 3 days?

Nothing on the laptop itself. I plugged in a new keyboard and mouse (both USB), and a USB hub (USB-C).
I also installed new drivers for the Intel Graphics and "Intel(R) Dynamic Platform and Thermal Framework Manager" as suggested by Dell Driver Updater, but this was an attempt to fix the BSOD, which already happened before updating these drivers.

What are the laptop info and specs?

• Text version: https://mega.nz/#!w8AGRbDb!_n4JklD702aj7aoC48b-yawUQ69-cko13R9Zt8X_U6c
  
• Speccy version (can be imported into Speccy): https://mega.nz/#!YpQhAYCT!NTfqThbNZ-lqDVMTsKqGTDwKc4GCuUTWzipsDuVVE8c
  
• MsInfo32 Output: https://mega.nz/#!8p4SwTgR!NXJeUPATjAZ6JUUI4-s_-iJGOcDz1FvRmO8JCSniQs8
  

Most recent dump files?

This is the content of C:\Windows\Minidump: (all 3 are the most recent BSOD dumps and match with the date and time of the BSODs)

https://mega.nz/#!40B0TBAA!7n_QUccYUPr80FN0bvhY2evT_0SWbadh1MBFpxqh3Hk
https://mega.nz/#!B0YRUIAZ!XB25NdCVqBFkEleRdFPsKgGssf9PReYKXP5IJIFz1uY
https://mega.nz/#!FtJQmIba!sYXWqG3ayUyaIp7Vf6wnQrhJMYldHwIg8tw46cNp2fo

What have you tried?

I have checked with the Dell System Detect utility to see if all the drivers were up to date; 2 weren't and I updated them (as written above) but that didn't solve the issue.

I have cleaned the system Registry with the CCleaner utility, but that didn't solve the issue.

What can I do?

EDIT:

Upon suggestion, I updated the killer drivers.
All seemes fine of a while, then, after the laptop went to suspended state, I noticed the external mouse stopped working, while the touchpad worked.
After plugging and unplugging, I rebooted.
Laptop stuck to reboot for 6 min (usually takes 6 seconds) then BSOD: DRIVER_POWER_STATE_FAILURE.

Log:

https://mega.nz/#!RxhhyBYJ!7AGY6uAErZnqeE_lGCfk65Webalfc0vNbC_NokwJ-ys