Windows 10 1803 (17134.112): tcpip.sys BSOD upon sleep: Computer will not sleep/hibernate with active network connections RRS feed

  • Question

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, ffff8403e1482060, fffffa00c36378d0, ffff8403ed953010}
    Implicit thread is now ffff8403`ee21c040
    Probably caused by : tcpip.sys ( tcpip!FlpWaitForMiniportToReturnTransmittedPackets+e )
    Followup:     MachineOwner
    fffff802`a8441680 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffa00`c36378a0=000000000000009f
    2: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    A driver has failed to complete a power IRP within a specific time.
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffff8403e1482060, Physical Device Object of the stack
    Arg3: fffffa00c36378d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffff8403ed953010, The blocked IRP
    Debugging Details:
    Implicit thread is now ffff8403`ee21c040
    BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804
    SYSTEM_MANUFACTURER:  Dell Inc.         
    SYSTEM_PRODUCT_NAME:  Inspiron 7737
    SYSTEM_SKU:  Inspiron 7737
    BIOS_VENDOR:  Dell Inc.         
    BIOS_DATE:  01/29/2018
    BASEBOARD_MANUFACTURER:  Dell Inc.         
    DUMP_TYPE:  2
    BUGCHECK_P1: 3
    BUGCHECK_P2: ffff8403e1482060
    BUGCHECK_P3: fffffa00c36378d0
    BUGCHECK_P4: ffff8403ed953010
    FAULTING_THREAD:  ee21c040
    CPU_COUNT: 4
    CPU_MHZ: 704
    CPU_VENDOR:  GenuineIntel
    CPU_MODEL: 45
    CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 23'00000000 (cache) 23'00000000 (init)
    BLACKBOXBSD: 1 (!blackboxbsd)
    BLACKBOXPNP: 1 (!blackboxpnp)
    PROCESS_NAME:  System
    ANALYSIS_SESSION_TIME:  06-13-2018 12:46:39.0643
    ANALYSIS_VERSION: 10.0.17674.1000 amd64fre
    LAST_CONTROL_TRANSFER:  from fffff802a82fad76 to fffff802a84493b6
    fffffa00`c8a8ab60 fffff802`a82fad76 : 00000000`00000000 ffff8403`ee21c040 fffffa00`c8a8b0a0 ffff8403`e51688c0 : nt!KiSwapContext+0x76
    fffffa00`c8a8aca0 fffff802`a82fa56b : 00000000`00000001 fffff800`032d9cc1 00000000`0000000a ffff8403`00000000 : nt!KiSwapThread+0x2c6
    fffffa00`c8a8ad70 fffff802`a82f9c8f : ffff8403`e514cf80 ffff8403`00000000 ffff8403`e514cf00 ffff8403`ee21c180 : nt!KiCommitThreadWait+0x13b
    fffffa00`c8a8ae10 fffff802`a8356960 : fffffa00`c8a8af28 ffff8403`00000000 fffff800`036a8000 fffff800`03618600 : nt!KeWaitForSingleObject+0x1ff
    fffffa00`c8a8aef0 fffff800`036e1faa : fffffa00`c8a8b220 00000000`00000001 00000000`00000004 fffffa00`c8a8b228 : nt!ExWaitForRundownProtectionReleaseCacheAware+0xa0
    fffffa00`c8a8af60 fffff800`03668305 : ffffb801`05300100 fffff802`00000003 ffff8403`e5151590 fffff802`a839e4dc : tcpip!FlpWaitForMiniportToReturnTransmittedPackets+0xe
    fffffa00`c8a8af90 fffff800`035adb8b : fffffa00`c8a8b220 ffff8403`ec3e8a58 ffff8403`00000000 00000000`00001001 : tcpip!FlpUninitializePacketProviderInterface+0x55
    fffffa00`c8a8afd0 fffff800`035462f2 : ffffffff`5f114500 ffff8403`e1ea7c10 ffff8403`e514fc00 ffff8403`e5151590 : tcpip!FlPnpEvent+0x6786b
    fffffa00`c8a8b070 fffff800`033787a4 : ffffffff`5f114500 ffff8403`e1ea7c10 ffff8403`00000096 ffff8403`e514fc00 : tcpip!Fl68PnpEvent+0x12
    fffffa00`c8a8b0a0 fffff800`033c3641 : 00000000`00041eb0 fffff800`035462e0 ffff8403`e5151590 00000000`00000008 : ndis!ndisDeliverNetPnPEventSynchronously+0x1e8
    fffffa00`c8a8b120 fffff800`03378589 : fffffa00`c8a8b370 fffffa00`c8a8b3e9 fffffa00`c8a8b370 ffff8403`e25b61a0 : ndis!ndisPnPNotifyBinding+0xe1
    fffffa00`c8a8b300 fffff800`033731ab : ffff8403`e514fc00 fffffa00`c8a8b444 fffff211`e4d0263b ffff8403`e25b61a0 : ndis!ndisPnPNotifyBindingUnlocked+0x35
    fffffa00`c8a8b350 fffff800`033730d2 : fffffa00`c8a8b4c0 ffffa088`8dfb4b60 00000000`00000000 ffff8403`00000000 : ndis!ndisPauseProtocolInner+0x7f
    fffffa00`c8a8b450 fffff800`0337c437 : 00000000`00000003 fffffa00`c8a8b590 00000000`00000001 ffff8403`e25b75b0 : ndis!ndisPauseProtocol+0x66
    fffffa00`c8a8b490 fffff800`0337c233 : ffff8403`e25b75b0 ffff8403`e25b75b0 ffff8403`e25b7628 ffff8403`e25b61a0 : ndis!Ndis::BindEngine::Iterate+0x17b
    fffffa00`c8a8b610 fffff800`0337c1a5 : ffff8403`e25b75b0 00000000`00000000 00000000`00000000 fffffa00`c8a8b690 : ndis!Ndis::BindEngine::UpdateBindings+0x7b
    fffffa00`c8a8b640 fffff800`0337bf86 : ffff8403`e25b75c8 00000000`00000000 ffff8403`00000000 00000000`00000000 : ndis!Ndis::BindEngine::DispatchPendingWork+0x69
    fffffa00`c8a8b670 fffff800`032eb7db : ffff8403`e25b61a0 00000000`00000020 ffff8403`e25b75b0 00000000`00000004 : ndis!Ndis::BindEngine::ApplyBindChanges+0x5e
    fffffa00`c8a8b6c0 fffff800`03370ab5 : ffff8403`e25b61a0 00000000`00000004 00000000`00000000 fffff802`a87e3200 : ndis!ndisPrepForLowPower+0x1c19b
    fffffa00`c8a8b790 fffff800`03370982 : 00000000`00000000 fffff802`00000004 ffff8403`ed953010 ffff8403`e25b61a0 : ndis!ndisSetSystemPower+0x129
    fffffa00`c8a8b810 fffff800`032e4145 : ffff8403`ed953010 ffff8403`e1472970 ffff8403`ed953170 fffffa00`c8a8bc10 : ndis!ndisSetPower+0xa6
    fffffa00`c8a8b850 fffff802`a83ff132 : ffff8403`ed953010 fffffa00`c8a8ba09 ffff8403`ed953010 ffff8403`e2691950 : ndis!ndisPowerDispatch+0x135
    fffffa00`c8a8b880 fffff802`a82f2dd0 : ffff8403`00000009 00000000`00000000 00000000`00000000 fffff800`0272d143 : nt!IopPoHandleIrp+0x36
    fffffa00`c8a8b8b0 fffff802`a8404979 : 0a700ab0`0ab00af0 fffffa00`c8a8b9c0 00000000`00000004 fffffa00`c8a8b9a1 : nt!IofCallDriver+0x70
    fffffa00`c8a8b8f0 fffff800`02757bcd : 00000000`00000000 fffff800`0275054f fffffa00`c8a80000 00000000`00000000 : nt!IoCallDriver+0x9
    fffffa00`c8a8b920 fffff800`0272f68b : ffff8403`e268d200 fffffa00`c8a8ba70 fffffa00`c8a8ba70 ffff8403`e2691950 : Wdf01000!FxPkgFdo::_PowerPassDown+0x6d [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 85]
    fffffa00`c8a8b950 fffff800`02742f64 : 00000000`00000002 00007bfc`1d9632f8 ffff8403`e2691950 00000000`00000000 : Wdf01000!FxPkgFdo::DispatchSystemSetPower+0x177 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 292]
    fffffa00`c8a8b9a0 fffff800`02727e00 : ffff8403`e269cd00 00007bfc`1d9632f8 ffff8403`e2691950 00000000`00000000 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x24 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 117]
    fffffa00`c8a8b9d0 fffff800`02727480 : ffff8403`ed953010 ffff8403`e269cd00 ffff8403`e2691950 fffff802`00000000 : Wdf01000!FxPkgPnp::Dispatch+0xf0 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 677]
    fffffa00`c8a8ba70 fffff802`a83fef27 : 00000000`00000000 00000000`00000000 ffff8403`00000000 00000000`00000002 : Wdf01000!FxDevice::DispatchWithLock+0x150 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
    fffffa00`c8a8bb60 fffff802`a838bae7 : ffffffff`fa0a1f00 ffff8403`ee21c040 fffff802`a83fed40 a0888c43`61680400 : nt!PopIrpWorker+0x1e7
    fffffa00`c8a8bc10 fffff802`a8449bc6 : ffffb801`05300180 ffff8403`ee21c040 fffff802`a838baa0 ffff8403`e25fc578 : nt!PspSystemThreadStartup+0x47
    fffffa00`c8a8bc60 00000000`00000000 : fffffa00`c8a8c000 fffffa00`c8a86000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  .thread 0xffff8403ee21c040 ; kb
    THREAD_SHA1_HASH_MOD_FUNC:  5a21e1126bc75f92f1797ab98ae7927f6e55b510
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  21eaaee5c365d3657e63babd448e22cb659a3d22
    THREAD_SHA1_HASH_MOD:  ddb2087af4e914b45a746bf6830abd7ed2f0f361
    fffff800`036e1faa 4883c428        add     rsp,28h
    FAULT_INSTR_CODE:  28c48348
    SYMBOL_NAME:  tcpip!FlpWaitForMiniportToReturnTransmittedPackets+e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: tcpip
    IMAGE_NAME:  tcpip.sys
    IMAGE_VERSION:  10.0.17134.48
    FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_tcpip!FlpWaitForMiniportToReturnTransmittedPackets
    BUCKET_ID:  0x9F_3_POWER_DOWN_tcpip!FlpWaitForMiniportToReturnTransmittedPackets
    PRIMARY_PROBLEM_CLASS:  0x9F_3_POWER_DOWN_tcpip!FlpWaitForMiniportToReturnTransmittedPackets
    TARGET_TIME:  2018-06-12T20:57:23.000Z
    OSBUILD:  17134
    SUITE_MASK:  272
    OSNAME:  Windows 10
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    USER_LCID:  0
    OSBUILD_TIMESTAMP:  2018-05-20 13:23:46
    BUILDDATESTAMP_STR:  180410-1804
    BUILDLAB_STR:  rs4_release
    BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804
    FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_tcpip!flpwaitforminiporttoreturntransmittedpackets
    FAILURE_ID_HASH:  {3a9600b8-5597-3062-7849-e5c3f448bde6}
    Followup:     MachineOwner

    Wednesday, June 13, 2018 10:53 AM


  • I have apparently fixed the issue:

    I disabled both VMWare Bridge Protocol and VirtualBox Bridge Protocol (VirtualBox NDIS6 Bridged Networking Driver) from Intel® Dual Band Wireless-N 7260 and my computer now sleeps wonderfully.

    My computer has successfully passed 5 successive sleep-wake cycles.

    I have to test it a bit more but as I no longer need my virtual machines accessing my physical network devices I can live without this. 

    Tuesday, July 31, 2018 7:46 AM

All replies

  • Hi,

    Do you mean when you wake from sleep, you will encounter BSOD issue, right?

    As tcpip.sys is more related with network driver, please try to disable and enable network driver to check again. 

    If the issue persists, try to download the latest network driver from Dell website.

    By the way, I would recommend to upload all the minidump to One Drive and paste the link here for deep analyze if the issue persists.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 14, 2018 10:10 AM
  • No, it only takes place while shutting down with Fast Boot enabled (hibernation) or sleep. The computer remains on with consistent I/O and screen off until it displays the BSOD. Today I discovered that if I turn off the wireless router which the computer is connected to the computer will instead hibernate or sleep immediately without BSOD. It seems like the computer enters an eternal loop expecting some TCP/IP feedback until it times out and displays the BSOD.

    Thursday, June 14, 2018 2:50 PM
  • Hi, 

    Thank you for your feedback.

    "Today I discovered that if I turn off the wireless router which the computer is connected to the computer will instead hibernate or sleep immediately without BSOD"

    According to your description, I think we have necessary to check and try to troubleshoot on Network driver. Please try my suggestions in the upper post and feedback your action result to us. 

    By the way, the entire minidump is very useful for analyzing the issue deeply. Please upload to One Drive and paste the link here. 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 15, 2018 9:23 AM
  • 1) To evaluate the BSOD please post logs for troubleshooting.

    2) Using administrative command prompt copy and paste this whole command.

    3) Make sure the default language is English so that the logs can be scanned and read.


    4) The command will automatically collect the computer files and place them on the desktop.

    5) Then use one drive or drop box to place share links into the thread for troubleshooting.


    6) This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    7) Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    8) There are two files for you to find manually: 

    a) C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    b) Dxdiag:  In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread




    Please remember to vote and to mark the replies as answers if they help.




    Friday, June 15, 2018 10:47 AM
  • One little question what does the DirectX dump have to do with tcpip.sys??
    Friday, June 15, 2018 11:50 AM
  • Hi. 

    This kind of issues generally are resolved by updating your computer's drivers. By the log you've posted, you should go to this link: http://www.dell.com/support/home/us/en/19/product-support/product/inspiron-17-7737/drivers and download the most recent drivers for your computer. Another thing that could help you is to update your Windows Operating System to the last versions available. 

    If after following all these recommendations you're still facing problems, please, post it here. 

    Thank you...

    Richard Sabino

    • Proposed as answer by Richard Sabino Friday, June 15, 2018 2:08 PM
    • Unproposed as answer by LowEndSilicon Wednesday, July 25, 2018 3:13 PM
    Friday, June 15, 2018 2:08 PM
  • Already on latest drivers. It still happens. Windows 10 will not sleep until the wireless connection is killed by swithching off the router.

    If the computer is left connected while sleeping without interaction it will eventually BSOD and cause data loss.

    Network adapter affected:

    Intel® Dual Band Wireless-N 7260 - Driver version:

    -> VMWare Bridge Protocol Enabled (Used frequently)

    -> VirtualBox Bridge Protocol Enabled (Never used)

    The issue started to happen only after upgrading to Windows 10 1803 17134 and still happens after updating to 17134.167

    Wednesday, July 25, 2018 3:21 PM
  • When available please post one drive or drop box links of the logs for troubleshooting.
    Wednesday, July 25, 2018 3:28 PM
  • Do you really think that it makes sense to provide such a generic answer in this forum?

    It is supposed that you came here looking for FREE HELP! You’re responding to my answer as if you’re my boss or have paid me to look for a deep answer to your question. We came here to look for ideas on how WE can resolve OUR problems, not someone to tell me a step by step on how to resolve it, if someone wants to connect to your computer and do a deep check on it, it is up to the member of this forum. The help here is offered for FREE and you're talking as if you're in a company and as if you have the premium subscription on it.

    Have you tried to update your computer drivers and OS? Did you went to the manufacturer of this wireless network card and look for any drivers updates?

    If you are demanding a solution for your problem just hire someone and pay for it and don’t be stingy.

    If you want a long answer ok, here's your long answer. 

    Based on the log you uploaded I've found the following:

    BIOS version you currently have is from January 29, 2018 and last version from manufacturer is February 24, 2018.

    The Wireless Network driver you have installed is for Win 8, not for Win 10.

    You don't have the last version of Windows 10. 

    You said in a later post that you have Wireless Network Driver, but the latest is ,A00

    So, if you came here to look a step by step solution to your problem for free and complain with me because you think this is a generic answer or because that doesn't follow your style, I suggest you to hire someone that can do the dirty job for you. 

    I have 15 years as a Tech Support and have dealt with thousands of problems like this.

    Have a great day!

    Richard Sabino

    Thursday, July 26, 2018 12:04 AM
  • I have apparently fixed the issue:

    I disabled both VMWare Bridge Protocol and VirtualBox Bridge Protocol (VirtualBox NDIS6 Bridged Networking Driver) from Intel® Dual Band Wireless-N 7260 and my computer now sleeps wonderfully.

    My computer has successfully passed 5 successive sleep-wake cycles.

    I have to test it a bit more but as I no longer need my virtual machines accessing my physical network devices I can live without this. 

    Tuesday, July 31, 2018 7:46 AM
  • Intel driver packages have different driver binaries for different hardware branches as they phase out feature development for each. So, driver package version will probably install an older version as feature development for Intel® Dual Band Wireless-N 7260 has been halted for so long.

    Also the INF file from the driver I use has a Windows 10 section and is WHQL signed. I do not know where these claims you made come from.

    I am sorry if my question offended you in any sense it was not my intention it is just that it seemed to me like a script generated answer and I feared wasting days or months uploading loads of system dumps with lots of personal information with a total lack of focus on the issue.

    My latest technical support experiences have been quite frustrating and in the end it has been me alone solving the issue, maybe because of this I tilted to critic by default.

    Tuesday, July 31, 2018 7:51 AM
  • I have exactly the same issue:

    Windows 10+X79 Gygabyte MB+Intel 7260 AC Wi-Fi

    And yes, I have wifi driver (from Proset 21.10.1 package). Older drivers just do not work well, disconnecting too often, after Windows 1903 update.

    And yes I have VirtualBox. But disabling the bridging driver, does NOT help.

    Worse! When I disconnect from WiFi network, PC goes to hibernate and wakes up safely.
    BUT, the adapter can not find surrounding networks anymore, until WIFI is disabled/enabled.

    60% of attempts to hibernate result in long waiting for dump,and error in power report tool


    System Power State: Hibernate

    94 2019-10-24 19:06:12 0:11:34 Hibernate Button or Lid Abnormal Shutdown -

    OS State Data

    Data obtained from the Event Viewer Logger.

    + Detailed OS State Data

    Name Value
    TargetState 5
    EffectiveState 5

    System Power State: Bugcheck

    95 2019-10-24 19:17:47 0:00:00 Bugcheck Unknown Unknown -

    OS State Data

    Data obtained from the Event Viewer Logger.

    + Detailed OS State Data

    Name Value
    BugcheckCode 0x9f
    BugcheckParameter1 0x3
    BugcheckParameter2 0x0
    BugcheckParameter3 0x0
    BugcheckParameter4 0x0
    BootAppStatus 0x0
    Checkpoint 16
    CheckpointStatus 0
    SystemSleepTransitionsToOn 2
    CsEntryScenarioInstanceId 0

    System Power State: Active

    96 2019-10-24 19:17:47 0:00:46 Active Unknown Unknown -

    OS State Data

    Data obtained from the Event Viewer Logger.


    Checking the dump with KDFE gives

    tcpip.sys ( tcpipFlpWaitForMiniportToReturnTransmittedPackets+14 )

    • Edited by Hale_ru Thursday, October 24, 2019 12:50 PM
    Thursday, October 24, 2019 10:52 AM
  • OK, I got a temporary workaround.(? every temporary thing in Soviet state is permanent...so in MS)
    Seems like...

    MS bundled drivers from 2015 are still working, and allow hibernating after infamous Win10 1903 update.
    But I can not guarantee you the full performance of AC-wifi after that.

    1. Open the web-page from the step 4 on screen, you will need it. Print it out if your browser does not cache it offline.

    2. Disable the internet connection (just disconnect from your WiFi)

    3. Uninstall Intel ProSet drivers completely, using "Add Remove Programs"

    4. Go to device manager and initiate refresh, or just reboot.

     - here windows will install out-of-the-box driver, dated back to year 2015.

    5. Go to device manager again and ensure that drivers are signed by Microsoft, not Intel. If it is still Intel, RMB-click the driver, choose Uninstall with "Delete driver files"; and reboot again, until you get Microsoft signed driver in place.

    6. Follow these steps in order to prevent Windows automatically updating to Intel drivers. The problem is that MS mindlessly included those drivers to update list without beta-testing.


    (you have probably already opened this page in step 1)

    This will disable ANY driver update for selected hardware, including manual update. So you have to remember the change you made. If you look inside policies, you can find an option to make notification, when such update is prevented. Use it for your convenience.

    • Edited by Hale_ru Thursday, October 24, 2019 1:29 PM
    Thursday, October 24, 2019 1:19 PM