Windows 10: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) by NDIS!NdisMOidRequestComplete

Discus and support DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) by NDIS!NdisMOidRequestComplete in Windows 10 Drivers and Hardware to solve the problem; 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... Discussion in 'Windows 10 Drivers and Hardware' started by Ligen Xiao (zhong ke, Mar 6, 2019.

  1. 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 fatal error occur by chance.



    Call Function: NDIS!NdisMOidRequestComplete

    Bugcheck Analysis: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    Hardware: IMX6ULL

    Software: Windows 10 IOT Core

    SOC: Freescale



    Would someone take a look at this please?

    Thank you.



    Details of Bugcheck Analysis as below:


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

    * *

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

    Arg2: 00000002, IRQL

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

    Arg4: 936644d3, address which referenced memory

    FOLLOWUP_IP:

    imxnetmini!MpOnPausedStateHandler+f6 [d:\nxp\bsp\driver\net\ndis\imxnetmini\mp_sm.c @ 264]

    96924556 9b04 ldr r3,[sp,#0x10]



    FAULT_INSTR_CODE: f5039b04



    FAULTING_SOURCE_LINE: d:\nxp\bsp\driver\net\ndis\imxnetmini\mp_sm.c



    FAULTING_SOURCE_FILE: d:\nxp\bsp\driver\net\ndis\imxnetmini\mp_sm.c



    FAULTING_SOURCE_LINE_NUMBER: 264



    SYMBOL_STACK_INDEX: 8



    SYMBOL_NAME: imxnetmini!MpOnPausedStateHandler+f6



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: imxnetmini



    IMAGE_NAME: imxnetmini.sys

    STACK_TEXT:

    809b67a0 80eed37a : 810dff88 8107bcc0 809b67d0 80fb24cf : nt!DbgBreakPointWithStatus [minkernel\ntos\rtl\arm\debugstb.asm @ 129]

    ****65ae0e8 : nt!KeBugCheckEx+0x14 [minkernel\ntos\ke\bugcheck.c @ 2204]

    809b6ae0 80eb0b6c : 936644d3 00000000 00000000 00000000 : nt!KiBugCheckDispatch+0x12 [minkernel\ntos\ke\arm\trap.asm @ 2509]

    809b6b18 936644d2 : 8094f530 00000000 00000040 80eb0420 : nt!KiCommonMemoryManagementAbort+0x13c [minkernel\ntos\ke\arm\trap.asm @ 1380]

    809b6cb8 9362d030 : 965ae0e8 00000000 00000000 00000000 : NDIS!ndisMpHookRawOidRequestComplete+0x56 [minio\ndis\mphook\ndismphook.c @ 512]

    ****9247e3 : imxnetmini!MpOnPausedStateHandler+0xf6 [d:\nxp\bsp\driver\net\ndis\imxnetmini\mp_sm.c @ 264]

    ****f1c : NDIS!ndisMTimerObjectDpc+0x9e [minio\ndis\sys\timer.c @ 7****923f2 00000000 : nt!KiTimerExpiration+0x116 [minkernel\ntos\ke\dpcsup.c @ 2626]

    809b6ef0 80eafd8e : 809b6ef8 809b6ef8 00000004 00000000 : nt!KiRetireDpcList+0x146 [minkernel\ntos\ke\dpcsup.c @ 1563]

    ****4ad7128 80c12abf : hal!HalpDispatchSoftwareInterrupt+0x7c [minkernel\hals\lib\interrupts\common\irql.c @ 834]

    94ad7118 80c0f64a : 00000000 9829708d 0000000d 00000000 : hal!HalpInterruptCheckForSoftwareInterrupt+0x2a [minkernel\hals\lib\interrupts\common\irql.c @ 659]

    94ad7130 80efd326 : 00000000 00000058 94ad71c8 80c0f599 : hal!HalEndSystemInterrupt+0xb2 [minkernel\hals\lib\interrupts\common\entry.c @ 285]

    94ad7160 80efd498 : 809be000 0000000d 00000000 80c0f41d : nt!KiSwitchStackAndPlayInterrupt+0x76 [minkernel\ntos\ke\arm\intsupc.c @ 1035]

    94ad71****55e : 00000000 ffffffff 00000000 00000204 : nt!MiWaitForInPageComplete+0x5e2 [minkernel\ntos\mm\pagfault.c @ 13432]

    94ad7400 80f54e16 : c0300d2c 8108f680 00000000 00000000 : nt!MiIssueHardFault+0x2ae [minkernel\ntos\mm\pagfault.c @ 1354]

    94ad745****33636 : 00000000 00000000 00000000 00000000 : Ntfs!NtfsQueryDirectory+0x12b0 [minkernel\fs\ntfs\dirctrl.c @ 1****d0 00000000 : Ntfs!NtfsFsdDirectoryControl+0x7c [minkernel\fs\ntfs\dirctrl.c @ 213]

    94ad7a18 93226c92 : 9701f930 00000000 94ad7a60 93226c93 : nt!IopfCallDriver+0x42 [minkernel\ntos\io\iomgr\iomgr.h @ 3383]

    94ad7a28 93227f24 : 94ad7a60 94ad7a70 00000000 9701f930 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2f6 [minkernel\fs\filtermgr\filter\fltmgr.c @ 3398]

    94ad7a68 93174aa8 : 94ad7a7c 00000003 964bd520 9701f758 : FLTMGR!FltPerformSynchronousIo+0xb0 [minkernel\fs\filtermgr\filter\iosup.c @ 76****4e : 00000000 00000000 00000000 00000000 : FLTMGR!FltpPerformPreCallbacks+0x374 [minkernel\fs\filtermgr\filter\callbacksup.c @ ****57]

    94ad7bf****0 80ed4fd9 : nt!IopfCallDriver+0x42 [minkernel\ntos\io\iomgr\iomgr.h @ 33****7080 : nt!IopCallDriverReference+0x12c [minkernel\ntos\io\iomgr\iomgr.h @ 4214]

    94ad7c68 8116008e : 00000002 00000000 00000001 0303f422 : nt!IopSynchronousServiceTail+0x1ae [minkernel\ntos\io\iomgr\internal.c @ 8608]

    94ad7cb0 80eb146e : 00000001 00000001 00000002 00000003 : nt!NtQueryDirectoryFileEx+0x5a [minkernel\ntos\io\iomgr\dir.c @ 889]

    94ad7d00 80eb11dc : 034ff128 034ff148 00000268 00000003 : nt!KiSystemService+0x10e [minkernel\ntos\ke\arm\trap.asm @ 2390]

    94ad7d40 77d83426 : 8094f4f0 00000000 03000008 00000000 : nt!KiSWIException+0xfc [minkernel\ntos\ke\arm\trap.asm @ 2135]

    034ff0d8 77c11f8c : 034ff128 034ff148 00000268 00000003 : ntdll!ZwQueryDirectoryFileEx+0x6 [minkernel\ntdll\daytona\objfre\arm\usrstubs.asm @ 2711]

    034ff0d8 77c11846 : 034ff128 034ff148 00000268 00000003 : KERNELBASE!FindFirstFileExW+0x2dc [minkernel\kernelbase\filefind.c @ 1011]

    034ff3d8 73812024 : 00000000 00000000 034ff698 73812025 : KERNELBASE!FindFirstFileW+0x16 [minkernel\kernelbase\filefind.c @ 208]

    034ff3e8 73811e3a : 00000000 00000000 00000000 00000000 : fntcache!InstalledFontFileEnumerator::TryConvertFileInfo+0x54 [onecoreuap\windows\core\text\platform\win32\systemfontcollectionloader_win.cpp @ 146]

    034ff6a0 7380f6da : 03019000 027f0200 00000010 00000000 : fntcache!InstalledFontFileEnumerator::GetInstalledFontFiles+0x1ea [onecoreuap\windows\core\text\platform\win32\systemfontcollectionloader_win.cpp @ 119]

    034ff800 7380f412 : 034ff820 736ef44f 030237b0 03020408 : fntcache!FontSetCache::EnumerateAndCreateBuilderIfNeeded+0x4e [onecoreuap\windows\core\text\fontcache\logic\fontsetcache.cpp @ 409]

    034ff8d0 7380f270 : 034ff8f8 00000001 034ff938 00000002 : fntcache!FontSetCache::Update+0x15e [onecoreuap\windows\core\text\fontcache\logic\fontsetcache.cpp @ 327]

    034ff9b8 7380f032 : 00000000 00000000 00000000 00000000 : fntcache!FontSetCache::Initialize+0xb8 [onecoreuap\windows\core\text\fontcache\logic\fontsetcache.cpp @ 277]

    034ffa20 77d9ac62 : fffffffe fffffffe 00000000 7380f011 : fntcache!FontSetCache::MonitorThreadProc+0x22 [onecoreuap\windows\core\text\fontcache\logic\fontsetcache.cpp @ 150]

    034ffa40 00000000 : 00000000 00000000 00000000 00000000 : ntdll!RtlUserThreadStart+0x22 [minkernel\ntdll\rtlstrt.c @ 1162]

    :)
     
    Ligen Xiao (zhong ke, Mar 6, 2019
    #1
  2. Cancrum Win User

    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
     
    Cancrum, Mar 6, 2019
    #2
  3. DRIVER_IRQL_NOT_LESS_OR_EQUAL

    A. Analysis Results

    1. File Name: 120618-39843-01.dmp

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    IMAGE_NAME: tcpip.sys

    *** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

    2. File Name: 120618-42093-01.dmp

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    IMAGE_NAME: tcpip.sys

    *** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

    3. File Name: 120618-40718-01.dmp

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    IMAGE_NAME: tcpip.sys

    *** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

    B. Third Party Drivers

    1. rtwlane.sys - Realtek Wireless Driver

    Driver Date - 23-Jul-2018

    C. Recommendations

    1. Create a system restore point so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    2. Realtek Wireless Driver - Go to computer manufacturer's website and see if any driver is released after 23-Jul-18.
     
    Vijay_Verma, Mar 6, 2019
    #3
  4. DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) by NDIS!NdisMOidRequestComplete

    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, Mar 6, 2019
    #4
Thema:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) by NDIS!NdisMOidRequestComplete

Loading...
  1. DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) by NDIS!NdisMOidRequestComplete - Similar Threads - DRIVER_IRQL_NOT_LESS_OR_EQUAL NDIS NdisMOidRequestComplete

  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. 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...
  4. 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...
  5. 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...
  6. 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 * *...
  7. BSOD error code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

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

    in Windows 10 BSOD Crashes and Debugging
    Windows BSOD D1: Keep getting BSOD on Windows 10 Pro 64 Bit This is the Reliability Details: Problem signature Problem Event Name: BlueScreen Code: d1 Parameter 1: 0 Parameter 2: ff Parameter 3: 0 Parameter 4: 0 OS version: 10_0_17134 Service Pack: 0_0 Product: 256_1 OS...
  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)" -...