Windows 10: BSOD error code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

Discus and support BSOD error code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) in Windows 10 BSOD Crashes and Debugging to solve the problem; I have been geting this error for about 4 times now, it seems like rebooting didn't help. I'm pretty frustrated. if someone can read the minidump file... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by TigerSHe1998, Jan 26, 2019.

  1. BSOD error code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)


    I have been geting this error for about 4 times now, it seems like rebooting didn't help. I'm pretty frustrated. if someone can read the minidump file can you help me identify the problem?





    Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\TigerSHe\Desktop\012619-12000-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17763 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17763.1.amd64fre.rs5_release.180914-1434
    Machine Name:
    Kernel base = 0xfffff804`37a1c000 PsLoadedModuleList = 0xfffff804`37e37ad0
    Debug session time: Sat Jan 26 13:51:32.479 2019 (UTC - 5:00)
    System Uptime: 0 days 1:17:10.236
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..
    Loading User Symbols
    Loading unloaded module list
    .........
    For analysis of this file, run
    !analyze -v
    nt!KeBugCheckEx:
    fffff****e0=000000000000000a
    2: 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: fffff8047fbd66ae, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff8047fbd66ae, address which referenced memory

    Debugging Details:
    ------------------


    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

    SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

    SYSTEM_PRODUCT_NAME: MS-7B43

    SYSTEM_SKU: Default string

    SYSTEM_VERSION: 1.0

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 1.00

    BIOS_DATE: 10/19/2017

    BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

    BASEBOARD_PRODUCT: Z370I GAMING PRO CARBON AC (MS-7B43)

    BASEBOARD_VERSION: 1.0

    DUMP_TYPE: 2

    BUGCHECK_P1: fffff8047fbd66ae

    BUGCHECK_P2: 2

    BUGCHECK_P3: 8

    BUGCHECK_P4: fffff8047fbd66ae

    READ_ADDRESS: GetUlongFromAddress: unable to read from fffff80437ee34c0
    fffff80437f5e390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    fffff8047fbd66ae

    CURRENT_IRQL: 2

    FAULTING_IP:
    +0
    fffff804`7fbd66ae ?? ???

    CPU_COUNT: c

    CPU_MHZ: e70

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

    BLACKBOXBSD: 1 (
    !blackboxbsd)


    BLACKBOXPNP: 1 (
    !blackboxpnp)


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    PROCESS_NAME: 360tray.exe

    ANALYSIS_SESSION_HOST: TIGERSHE-PCGT

    ANALYSIS_SESSION_TIME: 01-26-2019 14:04:20.0579

    ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

    TRAP_FRAME: fffffb0328e86a20 --
    (.trap 0xfffffb0328e86a20)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000e2a000 rbx=0000000000000000 rcx=00000000c0000100
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8047fbd66ae rsp=fffffb0328e86bb0 rbp=000024edbd9bbfff
    r8=ffffd401fe761180 r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po cy
    fffff804`7fbd66ae ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80437be0c69 to fffff80437bcf440

    FAILED_INSTRUCTION_ADDRESS:
    +0
    fffff804`7fbd66ae ?? ???

    STACK_TEXT:
    fffffb03`28e868d8 fffff804`37be0c69 : 00000000`0000000a fffff804`7fbd66ae 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffffb03`28e868e0 fffff804`37bdd08e : 000024ed`bd9bbfff fffffb03`28e86c00 ffff8281`00000001 ffff8281`00000000 : nt!KiBugCheckDispatch+0x69
    fffffb03`28e86a20 fffff804`7fbd66ae : 000024ed`bd9bbfff 00000000`00000000 ffffd401`00000001 00001f80`00000000 : nt!KiPageFault+0x44e
    fffffb03`28e86bb0 000024ed`bd9bbfff : 00000000`00000000 ffffd401`00000001 00001f80`00000000 00000000`00000102 : 0xfffff804`7fbd66ae
    fffffb03`28e86bb8 00000000`00000000 : ffffd401`00000001 00001f80`00000000 00000000`00000102 000051d4`a190e000 : 0x000024ed`bd9bbfff


    THREAD_SHA1_HASH_MOD_FUNC: bf99962f16aee8a6a536cfcc5454c0cd4db15ac9

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2053c9cd60dcbe7f477419e6aee8664b1711298a

    THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:
    nt!KiPageFault+44e
    fffff804`37bdd08e 33c0 xor eax,eax

    FAULT_INSTR_CODE: ffb0c033

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiPageFault+44e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:
    nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION: 10.0.17763.292

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 44e

    FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault

    BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault

    PRIMARY_PROBLEM_CLASS: AV_CODE_AV_BAD_IP_nt!KiPageFault

    TARGET_TIME: 2019-01-26T18:51:32.000Z

    OSBUILD: 17763

    OSSERVICEPACK: 292

    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: unknown_date

    BUILDDATESTAMP_STR: 180914-1434

    BUILDLAB_STR: rs5_release

    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: 1c92

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_code_av_bad_ip_nt!kipagefault

    FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}

    Followup: MachineOwner
    ---------



    :)
     
    TigerSHe1998, Jan 26, 2019
    #1

  2. 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
     
    KoreyKarch, Jan 26, 2019
    #2
  3. 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.
     
    Sangeeta Sarkar, Jan 26, 2019
    #3
  4. Her Vang Win User

    BSOD error code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    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:
    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

    ---------

    Link to Zip File: Dump File.zip
     
    Her Vang, Jan 26, 2019
    #4
Thema:

BSOD error code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

Loading...
  1. BSOD error code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) - Similar Threads - BSOD error code

  2. DRIVER_IRQL_NOT_LESS_OR_EQUAL d1 BSOD, recurring problem

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_IRQL_NOT_LESS_OR_EQUAL d1 BSOD, recurring problem: I have been having a recurring problem, more often now than before. It happened long before when I had an EVGA 1080 installed, but only when playing Overwatch and very infrequently. A couple months ago, I purchased an EVGA 3060ti. I had no problems with it until I installed...
  3. Random BSOD 'Code: d1'

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD 'Code: d1': I haven't experienced a Blue Screen of Death on my current machine before and I'm certain that this event is nothing to worry about; however, I am rather paranoid of BSODs and I'd like to make sure that this singular event is nothing more than an aberration.Here's the...
  4. DRIVER_IRQL_NOT_LESS_OR_EQUAL d1 Help me with this BSOD

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_IRQL_NOT_LESS_OR_EQUAL d1 Help me with this BSOD: Here is the dmp readout 1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis...
  5. DRIVER_IRQL_NOT_LESS_OR_EQUAL d1 crashes

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_IRQL_NOT_LESS_OR_EQUAL d1 crashes: Hi, I've read a bit around the forums and I came to conclusion that the crashes might be related to my network card TL-WN881ND, minidump analysed with WinDbg below. The problem is though that windows states that my driver is newest possible. I tried drivers from the...
  6. DRIVER_IRQL_NOT_LESS_OR_EQUAL d1

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_IRQL_NOT_LESS_OR_EQUAL d1: * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL d1...
  7. win10 blue screen DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    in Windows 10 Drivers and Hardware
    win10 blue screen DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1): ******************************************************************************* * * * Bugcheck Analysis * *...
  8. DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) by NDIS!NdisMOidRequestComplete

    in Windows 10 Drivers and Hardware
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) by NDIS!NdisMOidRequestComplete: Hi, I come across this fatal error downing the window10 IOT core. We can use a USB-Enet hub through USB port, or a network cable by Ethernet port. Added imxnetmini.sys for Ethernet port , but boot with a USB-Ent hub connected. There will be such a...
  9. BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    in Windows 10 BSOD Crashes and Debugging
    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...
  10. driver_irql_not_less_or_equal (d1) (nvlddmkm.sys)

    in Windows 10 BSOD Crashes and Debugging
    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)" -...