Windows 10: BSOD with tcpip.sys when device is exiting from sleep

Discus and support BSOD with tcpip.sys when device is exiting from sleep in Windows 10 BSOD Crashes and Debugging to solve the problem; A few days ago I built a new PC, and I am seeing that it crashes every time I exit from sleep mode. The code is always the same with tcpip.sys... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by jamjabroni, Jul 6, 2020.

  1. BSOD with tcpip.sys when device is exiting from sleep


    A few days ago I built a new PC, and I am seeing that it crashes every time I exit from sleep mode.


    The code is always the same with tcpip.sys causing the driver version error, so I assume it is related to networking. Odd because I'm not even using wakeup over LAN yet.


    I've tried re-installing my network device drivers both Ethernet and WLAN to no avail.


    The attached dump below shows Spotify.exe as the "cause" but I doubt it's strictly due to that process; if I close Spotify before going to sleep the same exact error occurs with a different process being named.


    So far this is the only BSOD I get from this system but it is getting annoying because I prefer to put my system to sleep rather than booting it down and up between my usages.


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

    * *

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

    Arg2: 0000000000000002, IRQL

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

    Arg4: fffff8071e5428c0, address which referenced memory



    Debugging Details:

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



    *** WARNING: Unable to verify timestamp for win32k.sys



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 3



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on 52BLOOAMD



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 6



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 82



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: d1



    BUGCHECK_P1: 98



    BUGCHECK_P2: 2



    BUGCHECK_P3: 0



    BUGCHECK_P4: fffff8071e5428c0



    READ_ADDRESS: fffff8071aafa388: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    fffff8071aa0f2a8: Unable to get Flags value from nt!KdVersionBlock

    fffff8071aa0f2a8: Unable to get Flags value from nt!KdVersionBlock

    unable to get nt!MmSpecialPagesInUse

    0000000000000098



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: Spotify.exe



    TRAP_FRAME: fffff5035ec8b530 -- .trap 0xfffff5035ec8b530

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000000 rbx=0000000000000000 rcx=ffff860f8422dac8

    rdx=ffff860f8422dac8 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8071e5428c0 rsp=fffff5035ec8b6c0 rbp=ffff860f8422dac8

    r8=fffff5035ec8b7ac r9=0000000000000002 r10=fffff8071e6ca230

    r11=00000000000000bf r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl zr ac po nc

    tcpip!IppCanonicalizeScopeId+0x34:

    fffff807`1e5428c0 498b8698000000 mov rax,qword ptr [r14+98h] ds:00000000`00000098=????????????????

    Resetting default scope



    STACK_TEXT:

    fffff503`5ec8b3e8 fffff807`1a1ef929 : 00000000`0000000a 00000000`00000098 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

    fffff503`5ec8b3f0 fffff807`1a1ebc29 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

    fffff503`5ec8b530 fffff807`1e5428c0 : 00000000`00000000 00000000`00000000 00000000`00000c05 00000000`00000000 : nt!KiPageFault+0x469

    fffff503`5ec8b6c0 fffff807`1e50879a : ffff860f`8422dac8 fffff503`5ec8b800 ffff860f`8422d9e8 00000000`00000000 : tcpip!IppCanonicalizeScopeId+0x34

    fffff503`5ec8b700 fffff807`1e507d20 : 00000000`00000000 ffff860f`8cad2030 fffff807`1e6ca230 00000000`00000000 : tcpip!IppSendDatagramsCommon+0xa5a

    fffff503`5ec8b880 fffff807`1e55fd9e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpNlpSendDatagrams+0x40

    fffff503`5ec8b8c0 fffff807`1e5d1556 : 00000000`00000000 ffff860f`8cad22c8 00000000`00000003 00000000`00000005 : tcpip!InetSendDatagramsAf+0xbe

    fffff503`5ec8b9c0 fffff807`1e58e41c : ffff860f`86785c1c fffff503`5ec8bb80 00000000`00000001 ffff860f`92dff040 : tcpip!TcpResetSend+0x31e

    fffff503`5ec8ba80 fffff807`1e50ed68 : 000000b6`103e5fa0 00000000`00989680 00000000`8196072d 00000000`00000001 : tcpip!TcpMatchReceive+0x7ec5c

    fffff503`5ec8bd30 fffff807`1e50d80e : ffff860f`843b5380 00000000`0000f3fc 00000000`0000000e fffff503`5ec8be00 : tcpip!TcpReceive+0x358

    fffff503`5ec8be20 fffff807`1e50b537 : 00000000`00000006 00000000`00000001 fffff503`5ec8be80 fffff503`5ec8bf10 : tcpip!TcpNlClientReceivePreValidatedDatagrams+0x2e

    fffff503`5ec8be60 fffff807`1e50b2f8 : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IppLbIndicatePackets+0x127

    fffff503`5ec8bf10 fffff807`1a1e12fe : ffff860f`842f9cd0 fffff503`5ec8bfd0 ffff860f`8eebb640 fffff503`64459170 : tcpip!IppLbTransmitStackCallout+0x2a8

    fffff503`5ec8bf80 fffff807`1a1e12bc : fffff503`5ec8bfd0 ffff860f`8eebb640 fffff503`5ec8c000 fffff807`1a03755d : nt!KxSwitchKernelStackCallout+0x2e

    fffff503`64459170 fffff807`1a03755d : fffff503`5ec8bfd0 ffff860f`8eebb640 fffff503`64459218 00000000`00000100 : nt!KiSwitchKernelStackContinue

    fffff503`64459190 fffff807`1a037352 : fffff807`1e50b050 fffff503`64459400 fffff503`00000002 fffff807`00000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x19d

    fffff503`64459230 fffff807`1a0371b3 : fffff503`64459450 ffff860f`842f9cd0 00000000`00000003 00000000`00000000 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xf2

    fffff503`644592a0 fffff807`1a03716d : fffff807`1e50b050 fffff503`64459400 ffff860f`83dff660 ffff860f`8b196b40 : nt!KeExpandKernelStackAndCalloutInternal+0x33

    fffff503`64459310 fffff807`1e50c179 : ffff860f`8422d8a8 ffff860f`83dff660 00000000`00006c02 fffff503`64459680 : nt!KeExpandKernelStackAndCalloutEx+0x1d

    fffff503`64459350 fffff807`1e5587c7 : 00000000`00000007 ffff860f`8422d8a8 ffff860f`92dff040 fffff503`644596b0 : tcpip!IppLoopbackEnqueue+0x729

    fffff503`644595b0 fffff807`1e589a80 : 00000000`00000000 fffff503`00000014 ffff860f`8e9e5010 00000000`0000ad00 : tcpip!IpNlpFastContinueSendLoopbackDatagrams+0x737

    fffff503`644596f0 fffff807`1e504b89 : ffff860f`7c010101 00000000`00000000 fffff807`1e6ca230 ffff860f`9cbbda20 : tcpip!IppSendDatagramsCommon+0x81d40

    fffff503`64459870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpNlpFastSendDatagram+0x349





    SYMBOL_NAME: tcpip!IppCanonicalizeScopeId+34



    MODULE_NAME: tcpip



    IMAGE_NAME: tcpip.sys



    IMAGE_VERSION: 10.0.19041.264



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 34



    FAILURE_BUCKET_ID: AV_tcpip!IppCanonicalizeScopeId



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {e84599e8-d44f-de34-654b-f4462d9b9a60}



    Followup: MachineOwner

    ---------

    :)
     
    jamjabroni, Jul 6, 2020
    #1

  2. BSOD due to netadaptercx.sys after waking the PC from Sleep

    Hi Prakhar,

    The steps you suggested did not solve the problem. I am still experiencing the BSOD when waking the computer from sleep. If you have an other suggestions they'd be greatly appreciated.

    Regards,

    Chris
     
    ChrisBarber2, Jul 6, 2020
    #2
  3. DRIVER_IRQL_NOT_LESS_OR_EQUAL tcpip.sys

    But none of my drivers in the Device Manager tells me they need updating? No exclamation points or anything. Which drivers would I even be updating?

    As another update of the list of BSoD error codes I've received recently, in no particular oder:

    • SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (atikmdag.sys)
    • SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)
    • PAGE_FAULT_IN_NONPAGED_AREA
    • KMODE_EXCEPTION_NOT_HANDLED (NTFS.sys) and (tcpip.sys)
    *^this one comes up pretty often

    • SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
    • IRQL_NOT_LESS_OR_EQUAL
    • DRIVER_IRQL_NOT_LESS_OR_EQUAL (tcpip.sys)
    • DPC_WATCHDOG_VIOLATION
    Minidump files as of late, 5/27-5/29

    https://drive.google.com/open?id=0B7mI1kOkWpn3YlY4XzM4bjJ6U1k

    Sorry that I'm hesitant to be updating drivers via the methods posted. They seem like automated responses that don't feel applicable. My random BSoD's have to do with drivers? Then again, I shouldn't be questioning it since I don't know much.

    EDIT: Is there an easy way out to deal with this? AKA like, hard reset so I don't have to go about doing every single thing manually? Tired of the blue screens.
     
    TheNewDark, Jul 6, 2020
    #3
  4. BSOD with tcpip.sys when device is exiting from sleep

    Audio device unrecognised after waking from sleep


    From time to time I wake my laptop from sleep and find that the audio driver (Conexant Venice) is no longer loaded. The audio hardware is listed in the Device Manager as just "base system device" (or two base system devices, to be precise). Rebooting fixes the problem each time, but it takes a while. Is there a quicker way to make the audio work again than rebooting? I've tried obvious steps like running the troubleshooter and disabling and then re-enabling the devices.
     
    ricecrispies, Jul 6, 2020
    #4
Thema:

BSOD with tcpip.sys when device is exiting from sleep

Loading...
  1. BSOD with tcpip.sys when device is exiting from sleep - Similar Threads - BSOD tcpip sys

  2. Fail to Exit from long Sleep/Hibernate

    in Windows 10 Drivers and Hardware
    Fail to Exit from long Sleep/Hibernate: This has been happening for quite a while to meWinDBG determine the culprit to be tcpip.sys, ['a device object has been blocking an IRP for too long a time'], in another word, the network driverhowever, no matter what i tried except a clean install-power troubleshooting - no...
  3. BSOD when waking from sleep

    in Windows 10 Drivers and Hardware
    BSOD when waking from sleep: Whenever my computer sleeps it gives me a BSOD with a "THREAD STUCK IN DEVICE DRIVER" code Here are my dump files and system info. https://1drv.ms/u/s!ApvOHIqH5IbxgYUnOTNC3F5PHkQ3BQ?e=4b60Ob...
  4. BSOD from netwtw06.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD from netwtw06.sys: I keep getting the BSOD and ive tried many different solutions to no avail https://answers.microsoft.com/en-us/windows/forum/all/bsod-from-netwtw06sys/86cbd32d-44d0-4d46-976c-1079d04c5a0e
  5. BSOD when exiting sleep mode 0x000000d1

    in Windows 10 BSOD Crashes and Debugging
    BSOD when exiting sleep mode 0x000000d1: When I put my computer in sleep mode and after some time try to wake it, my computer shuts off and when rebooting I get the BSOD. The computer then reboots and I can use Windows without any issues, ofcourse it is annoying since I cannot use sleep mode anymore. These...
  6. BSOD when waking from sleep

    in Windows 10 BSOD Crashes and Debugging
    BSOD when waking from sleep: Hi I have had this problem for some months now. While I can put the computer to sleep, each time I wake it up it causes a BSOD. I have followed many threads about this. some suggesting it is video driver problem. So I uninstalled and reinstalled my Nvidia driver but the...
  7. BSODs when resuming from Sleep mode

    in Windows 10 BSOD Crashes and Debugging
    BSODs when resuming from Sleep mode: Hello, Ever since I upgraded to W10 Pro (from W8.1 Pro) my PC has started bluescreening when resuming from Sleep. MEMORY_MANAGEMENT is the most common one, and the only one that has occured so far after upgrade to Build 10586 (upgraded 2015-11-13). BSODs...
  8. BSOD When Waking from Sleep

    in Windows 10 BSOD Crashes and Debugging
    BSOD When Waking from Sleep: Just built a new computer. All of the drives and the Windows installation is the same as in the old system. I don't know if the issue would have occurred in the old system as I never tried to put my computer to sleep. I was getting one BSOD when waking from sleep (something...
  9. BSOD when waking from sleep

    in Windows 10 BSOD Crashes and Debugging
    BSOD when waking from sleep: Greetings forum, Ever since I upgraded to Windows 10, I've been seeing BSODs about once a month when waking my desktop from sleep. I would greatly appreciate any help on this matter. I've never encountered this on Windows 8.1. I've attached the zip file as instructed...
  10. BSOD possibly from TCPIP

    in Windows 10 BSOD Crashes and Debugging
    BSOD possibly from TCPIP: Hi all I am hoping you can help with a BSOD that I am getting. I never have got my windbg symbols to work correctly but my minidumps seem to point to an issue with TCPIP.SYS. Previously it seemed to BSOD when browsing, but this latest one was happened right after I said...