BSOD (Driver irql not less or equal) when using mobile hotspot

Page 1 of 2 12 LastLast

  1. OMG
    Posts : 8
    Windows 10 64-bit
       #1

    BSOD (Driver irql not less or equal) when using mobile hotspot


    Before I get into the details, here are my specs:
    CPU: AMD Ryzen 5 2600
    Motherboard: Gigabyte X470 Aorus Gaming 5 WiFi
    GPU: Nvidia GeForce GTX 760 (getting a replacement later)
    RAM: Corsair VENGEANCE LPX 16GB (2 x 8GB) DDR4 DRAM 2666MHz C16
    HDD: WD Black S250G2X0C, Toshiba THNSNJ256GCSU, Toshiba DT01ACA100
    PSU: Owltech Raider 750W Silver
    OS: Windows 10 home


    So the situation is that three days ago, I decided that I am finally saying good bye to my 6-years-old self-built computer. I replaced everything except for a SSD, a HDD, GPU, and the PC case.

    The new motherboard comes with a built-in WiFi, which I intended to use as a hotspot for my mobile phone. The problem is, I get the BSOD with "Driver irql not less or equal" every time my mobile phone is connected to the hotspot and there's some traffic. When it is not connected, the computer will not go BSOD even if the hotspot is turned on. This started immediately after I installed Windows 10 on my new system, and once everything was ready.

    The name of the file in which the error occurs seems to change everytime.

    I am assuming that this must be some driver problems in the WiFi Direct Virtual Adapter, but I do not know what needs to be done.

    I have downloaded and installed the latest driver from the motherboard manufacturer website, but this did not solve the issue.

    I am hoping that someone will be able to help me. I greatly appreciate your time and effort in helping me.
    Thank you very much.


    Here is the Beta Log:
    Attachment 224186
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    The log files are in a foreign (non-English) language and some can not be analyzed. Please change the system language to English and post a new log collector zip. Use the Beta log collector as it collects more information than the standard collector.

    Add, Remove, and Change Display Language in Windows 10
    How To Change Language In Windows 10 Operating System - YouTube

    You can put the language back to normal once done though you may have to do this multiple times if I need you to run the log collector script again in the future. Won't help with data that's already collected but newly generated data will be in English which can help.

    Thanks
      My Computers


  3. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #3

    The 2:13 1:41AM dump shows a problem with e1r65x64.sys.
    Code:
    BugCheck D1, {1c, 2, 0, fffff8014b6884b7}
    *** WARNING: Unable to verify timestamp for e1r65x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1r65x64.sys
    Probably caused by : e1r65x64.sys ( e1r65x64+184b7 )
    Driver Description: Intel Pro/1000 Network Adapter driver
    Driver Update Site: https://downloadcenter.intel.com/

    That agrees with the description you entered about WiFi hotspot use. The driver you have is dated
    Sat Jul 30 00:56:48 2016. See if there is an updated version available to replace it.
      My Computers


  4. OMG
    Posts : 8
    Windows 10 64-bit
    Thread Starter
       #4

    Dear Ztruker,

    I'm sorry that I took some time to reply. Thank you very much for your help.

    1) I apologize that my system was in Japanese. I changed the language settings to English. Hopefully, new BSOD log will be in English now.

    2) Okay. I updated the drivers for the Network adapter, but I have never seen Intel Pro/1000 Network Adapter in the device manager. I decided to go to the intel download center as you suggested, and downloaded the Proset/wireless software, although I was unsure if this is the one I should download. I installed it, and the problem has not occured yet for the past 10 minutes.

    I really really appreciate your help. If the problem happens again, I would like to come back with the new report in English.


    Best regards,
    OMG
      My Computer


  5. OMG
    Posts : 8
    Windows 10 64-bit
    Thread Starter
       #5

    Update

    Okay, so it crashed again with the same error message.

    Here's the beta log.
    Attachment 224376

    thank you
      My Computer


  6. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #6

    Same driver that Ztruker identified is being reported:
    *** WARNING: Unable to verify timestamp for e1r65x64.sys

    There is also:

    Unable to load image \SystemRoot\system32\DRIVERS\Netwtw08.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Netwtw08.sys

    These are all networking drivers. I would update both the LAN and WLAN drivers from the motherboard website making sure you are using the ones they recommend.

    Code:
    0: kd> .load pde;!dpx
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    Start memory scan  : 0xfffff802b526a298 ($csp)
    End memory scan    : 0xfffff802b526c000 (Kernel Stack Base)
    
                   rsp : 0xfffff802b526a298 : 0xfffff802b31c2c69 : nt!KiBugCheckDispatch+0x69
    0xfffff802b526a298 : 0xfffff802b31c2c69 : nt!KiBugCheckDispatch+0x69
    *** WARNING: Unable to verify timestamp for e1r65x64.sys
    0xfffff802b526a378 : 0xfffff804958786df : ndis!NdisFIndicateReceiveNetBufferLists+0x3f
    0xfffff802b526a3d8 : 0xfffff802b31bf8e5 : nt!KiPageFault+0x425
    0xfffff802b526a3e0 : 0xffff9080148517f0 :  Trap @ fffff802b526a3e0
    0xfffff802b526a518 : 0xfffff802b302fbc3 : nt!MiReturnNonPagedPoolPde+0x1f3
    0xfffff802b526a578 : 0xfffff802b33eb8c8 : nt!NonPagedPoolDescriptor+0x8
    0xfffff802b526a598 : 0xfffff802b302f9a8 : nt!MiReturnNonPagedPoolVa+0x44
    0xfffff802b526a628 : 0xfffff804958763bc : ndis!ndisReturnNblWithPowerQueue+0xbc
    0xfffff802b526a638 : 0xfffff80495f41432 : wfplwfs!LwfLowerReturnNetBufferLists+0xf2
    0xfffff802b526a660 : 0xfffff80495876300 : ndis!ndisReturnNblWithPowerQueue
    0xfffff802b526a688 : 0xfffff804958762f3 : ndis!ndisCallReceiveCompleteHandler+0x33
    0xfffff802b526a690 : 0xfffff80495876300 : ndis!ndisReturnNblWithPowerQueue
    0xfffff802b526a6c8 : 0xfffff8049587625d : ndis!NdisReturnNetBufferLists+0x4bd
    0xfffff802b526a6e8 : 0xfffff802b32f3867 : nt!ExFreePoolWithTag+0x807
    0xfffff802b526a7b8 : 0xfffff802b6bb8000 : raspppoe!WPP_GLOBAL_Control
    0xfffff802b526a7c0 : 0xfffff802b6bbe010 : raspppoe!MpReturnNetBufferListChain
    0xfffff802b526a7f0 : 0xfffff802b6bb8000 : raspppoe!WPP_GLOBAL_Control
    0xfffff802b526a7f8 : 0xfffff802b6bb26fc : raspppoe!DerefPppoePacket+0x19c
    0xfffff802b526a838 : 0xfffff802b6bbe08b : raspppoe!MpReturnNetBufferListChain+0x7b
    0xfffff802b526a848 : 0xfffff802b6bb8000 : raspppoe!WPP_GLOBAL_Control
    0xfffff802b526a868 : 0xfffff80495875f5f : ndis!NdisReturnNetBufferLists+0x1bf
    0xfffff802b526a898 : 0xfffff80495d61361 : fwpkclnt!FwppNetBufferListEventNotify+0xe1
    0xfffff802b526a960 : 0xfffff802b6206a80 : ndiswan!MPReturnNetBufferListChain
    0xfffff802b526a968 : 0xfffff802b621a048 : ndiswan!WPP_GLOBAL_Control
    0xfffff802b526a998 : 0xfffff802b6206b35 : ndiswan!MPReturnNetBufferListChain+0xb5
    0xfffff802b526a9c8 : 0xfffff804958762f3 : ndis!ndisCallReceiveCompleteHandler+0x33
    0xfffff802b526a9d0 : 0xfffff802b6206a80 : ndiswan!MPReturnNetBufferListChain
    0xfffff802b526aa08 : 0xfffff8049587625d : ndis!NdisReturnNetBufferLists+0x4bd
    0xfffff802b526aa18 : 0xfffff8049587565c : ndis!NdisFreeCloneNetBufferList+0x24c
    0xfffff802b526aa28 : 0xffff9080187ce600 : 0xfffff802b33ec1e0 : nt!NonPagedPoolDescriptor+0x920
    0xfffff802b526aac8 : 0xfffff804959ccb2c : NETIO!WfpNblInfoDestroyIfUnused+0xec
    0xfffff802b526aad8 : 0xfffff802b32f201b : nt!ExFreePool+0xb
    0xfffff802b526ab38 : 0xfffff804997eb4a5 : wanarp!FlpCompleteNdisNetBufferListChain+0xb5
    0xfffff802b526ab78 : 0xfffff804997eb3b0 : wanarp!FlpReturnNetBufferListChain+0x90
    0xfffff802b526aba8 : 0xfffff804959ccfb6 : NETIO!NetioDereferenceNetBufferList+0x166
    0xfffff802b526abe8 : 0xfffff804959cc883 : NETIO!NetioDereferenceNetBufferListChain+0x2a3
    0xfffff802b526ac18 : 0xfffff80495d61361 : fwpkclnt!FwppNetBufferListEventNotify+0xe1
    0xfffff802b526ac58 : 0xffff908017ad9940 : 0xfffff80495c9ec90 : tcpip!gWfpGlobalTriageBlock
    0xfffff802b526ac68 : 0xfffff80495b17428 : tcpip!FlSendNetBufferListChainComplete+0x58
    0xfffff802b526ac98 : 0xfffff80495871da0 : ndis!ndisMSendCompleteNetBufferListsInternal+0x120
    0xfffff802b526ad20 : 0xffff908017a55520 : 0xfffff80495f62d38 : wfplwfs!gWfpL2Globals+0x18
    0xfffff802b526ad40 : 0xfffff80495871c80 : ndis!ndisMSendCompleteNetBufferListsInternal
    0xfffff802b526ad68 : 0xfffff80495871b8e : ndis!NdisMSendNetBufferListsComplete+0x20e
    0xfffff802b526ade8 : 0xfffff80495d61361 : fwpkclnt!FwppNetBufferListEventNotify+0xe1
    0xfffff802b526adf8 : 0xffff9080187ce600 : 0xfffff802b33ec1e0 : nt!NonPagedPoolDescriptor+0x920
    0xfffff802b526ae38 : 0xffff908017bb3b30 : 0xfffff802b817a100 : vwifimp!GlobalData
    0xfffff802b526ae58 : 0xfffff802b8172a7b : vwifimp!MpSendComplete+0x2b
    0xfffff802b526ae88 : 0xfffff80496576436 : vwififlt!FilterSendNetBufferListsCompleteWDI+0x1b6
    0xfffff802b526aed8 : 0xfffff80496576050 : vwififlt!FilterSendNetBufferListsComplete
    0xfffff802b526aee8 : 0xfffff8049657606b : vwififlt!FilterSendNetBufferListsComplete+0x1b
    0xfffff802b526aef8 : 0xffff9080138ce010 : 0xfffff80496580140 : vwififlt!FilterModuleList
    0xfffff802b526af18 : 0xfffff80495871af9 : ndis!NdisMSendNetBufferListsComplete+0x179
    Unable to load image \SystemRoot\system32\DRIVERS\Netwtw08.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Netwtw08.sys
    0xfffff802b526af58 : 0xffff9080138ce010 : 0xfffff80496580140 : vwififlt!FilterModuleList
    0xfffff802b526afa8 : 0xfffff80499163611 : wdiwifi!CPort::FreeTxWfcFrame+0x1f9
    0xfffff802b526afd0 : 0xfffff804991c0b28 : wdiwifi!WPP_ca23a99a92f335b65d7b8b2f793ec5ad_Traceguids
    0xfffff802b526afd8 : 0xffff908012600000 :  dt wdiwifi!CAdapter
    0xfffff802b526b000 : 0xffff908015b639f0 :  dt wdiwifi!CPort
    0xfffff802b526b008 : 0xfffff8049916375b : wdiwifi!CPort::SendCompleteNetBufferLists+0xef
    0xfffff802b526b040 : 0xfffff802b39bcc20 : hal!MasterAdapterV2
    0xfffff802b526b048 : 0xfffff802b3985800 : hal!HalpDmaReturnToScatterPool+0x60
    0xfffff802b526b058 : 0xfffff80499132578 : wdiwifi!CAdapter::SendCompleteNbl+0x11c
    0xfffff802b526b060 : 0xffff908015b639f0 :  dt wdiwifi!CPort
    0xfffff802b526b088 : 0xfffff80499122fb1 : wdiwifi!CTxMgr::TxTargetDescDeinit+0xa1
    0xfffff802b526b098 : 0xfffff802b39856a1 : hal!HalpDmaReturnPageToOwner+0x55
    0xfffff802b526b0b0 : 0xfffff804991bf410 : wdiwifi!WPP_8b0de58fbb5e32301f1e251f3eb4552d_Traceguids
    0xfffff802b526b0c8 : 0xfffff80499126cea : wdiwifi!CTxMgr::CompleteNdisNbl+0xbe
    0xfffff802b526b128 : 0xfffff80499126953 : wdiwifi!CTxMgr::CompleteNBLs+0x5b
    0xfffff802b526b130 : 0xfffff804991bf400 : wdiwifi!WPP_8af36d4c2a403d6665b176af7cb3ea00_Traceguids
    0xfffff802b526b168 : 0xfffff80499123c3d : wdiwifi!CTxMgr::TxTransferCompleteInd+0x5bd
    0xfffff802b526b170 : 0xfffff804991bf410 : wdiwifi!WPP_8b0de58fbb5e32301f1e251f3eb4552d_Traceguids
    0xfffff802b526b218 : 0xffff908012600000 :  dt wdiwifi!CAdapter
    0xfffff802b526b228 : 0xfffff80499117200 : wdiwifi!AdapterTxTransferCompleteInd+0x10
    0xfffff802b526b230 : 0xfffff804991171f0 : wdiwifi!AdapterTxTransferCompleteInd
    0xfffff802b526b2c0 : 0xffff908012600000 :  dt wdiwifi!CAdapter
    0xfffff802b526b668 : 0xfffff802b304cae5 : nt!PpmUpdatePerformanceFeedback+0x155
    0xfffff802b526b6d8 : 0xfffff802b327aab3 : nt!PpmIdleUpdateConcurrency+0x73
    0xfffff802b526b6e8 : 0xfffff8049a513f44 : amdppm!AcpiCStateIdleExecute+0x24
    Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    0xfffff802b526b7a8 : 0xfffff80495873f05 : ndis!ndisInterruptDpc+0x185
    0xfffff802b526b848 : 0xfffff802b31196bd : nt!KeAndGroupAffinityEx+0x5d
    0xfffff802b526b878 : 0xfffff802b395daf2 : hal!HalRequestIpi+0x212
    0xfffff802b526b8d8 : 0xfffff802b526bb20 : 0xfffff80495873d80 : ndis!ndisInterruptDpc
    0xfffff802b526b908 : 0xfffff802b3047367 : nt!KiExecuteAllDpcs+0x2e7
    0xfffff802b526b960 : 0xfffff80495873d80 : ndis!ndisInterruptDpc
    0xfffff802b526b980 : 0xfffff802b3472400 : nt!KiInitialThread
    0xfffff802b526b9e8 : 0xfffff802b526b960 : 0xfffff80495873d80 : ndis!ndisInterruptDpc
    0xfffff802b526ba20 : 0xfffff802b3472400 : nt!KiInitialThread
    0xfffff802b526ba30 : 0xfffff802b3472400 : nt!KiInitialThread
    0xfffff802b526ba48 : 0xfffff802b30469bb : nt!KiRetireDpcList+0x1db
    0xfffff802b526ba98 : 0xfffff802b395e4e6 : hal!HalPerformEndOfInterrupt+0x16
    0xfffff802b526baa8 : 0xfffff802b3472400 : nt!KiInitialThread
    0xfffff802b526bac8 : 0xfffff802b31b3a15 : nt!KiInterruptDispatch+0x85
    0xfffff802b526bb20 : 0xfffff80495873d80 : ndis!ndisInterruptDpc
    0xfffff802b526bc18 : 0xfffff802b31b9195 : nt!SwapContext+0x165
    0xfffff802b526bc58 : 0xfffff802b31b57fa : nt!KiIdleLoop+0x5a
    0xfffff802b526bc78 : 0xfffff802b3472400 : nt!KiInitialThread
      My Computers


  7. OMG
    Posts : 8
    Windows 10 64-bit
    Thread Starter
       #7

    Actually, updating the network drivers provided by the motherboard manufacturer was the first thing that I did.
    This did not solve the problem.
      My Computer


  8. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #8

    There is always the possibility that you may need to wait for AMD to issue new drivers for your MB. Failing that as Ztruker has suggested use the latest Intel drivers from their download site. It won't hurt to uninstall the drivers from Device Manager and reinstall them.
      My Computers


  9. OMG
    Posts : 8
    Windows 10 64-bit
    Thread Starter
       #9

    Okay, I will try uninstalling and reinstalling drivers.

    I initially updated the drivers from the motherboard manufacturer, but since that did not work, I tried installing Intel drivers as Ztruker suggested. That didn't fix the problem neither.

    Anyhow, thank you very much for the help. I'll come back with the results once I get back (I will be away for a while).
      My Computer


  10. OMG
    Posts : 8
    Windows 10 64-bit
    Thread Starter
       #10

    Okay, so I ran into several problems.

    1) When I uninstalled all network related drivers so that I can reinstall them, the BSOD happened.

    Here's the beat log: Attachment 224481

    2) When I tried to install the drivers (issued by the MB manufacturer website), the setup application said that the latest drivers have alreadly been installed.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:19.
Find Us




Windows 10 Forums