Bluescreen when Hibernating

Hello,

I have regular Bluescreens when Hibernating.

I have analyzed a Dump with WinDBG below.

I have searched for FlpWaitForMiniportToReturnTransmittedPackets without success.

How can I find out, what causes my problem?

Regards,

Hendrik


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff802`2e41b000 PsLoadedModuleList = 0xfffff802`2e782110
Debug session time: Sun Feb 25 20:34:40.643 2018 (UTC + 1:00)
System Uptime: 0 days 6:12:56.379
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................................................
Loading User Symbols

Loading unloaded module list
............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffff910c29691060, ffffac84afe298f0, ffff910c3b076010}

Implicit thread is now ffff910c`312dc700
Probably caused by : tcpip.sys ( tcpip!FlpWaitForMiniportToReturnTransmittedPackets+e )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff910c29691060, Physical Device Object of the stack
Arg3: ffffac84afe298f0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff910c3b076010, The blocked IRP

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

Implicit thread is now ffff910c`312dc700

DUMP_CLASS: 1

DUMP_QUALIFIER: 402

BUILD_VERSION_STRING:  16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  XPS 12-9Q33

SYSTEM_SKU:  XPS 12-9Q33

SYSTEM_VERSION:  A06

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  A06

BIOS_DATE:  04/15/2014

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  XPS 12-9Q33

BASEBOARD_VERSION:  A06

DUMP_TYPE:  0

BUGCHECK_P1: 3

BUGCHECK_P2: ffff910c29691060

BUGCHECK_P3: ffffac84afe298f0

BUGCHECK_P4: ffff910c3b076010

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  312dc700

CPU_COUNT: 4

CPU_MHZ: a22

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 1D'00000000 (cache) 1D'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  LAPTOPHENDRIK

ANALYSIS_SESSION_TIME:  02-25-2018 20:41:31.0241

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8022e4d53e0 to fffff8022e597486

STACK_TEXT:  
ffffac84`b6fbaac0 fffff802`2e4d53e0 : ffff910c`282aa440 00000000`00000000 ffff910c`312dc700 ffffaefc`0210da38 : nt!KiSwapContext+0x76
ffffac84`b6fbac00 fffff802`2e4d4d5e : ffffaed7`7e010868 ffffaefc`0210da38 00000000`00000000 fffff802`2e48d288 : nt!KiSwapThread+0x190
ffffac84`b6fbacc0 fffff802`2e4d4539 : ffff910c`30fd02c0 ffff910c`00000000 ffff7a60`fa55fe00 ffffac84`b6fbae78 : nt!KiCommitThreadWait+0x10e
ffffac84`b6fbad60 fffff802`2e50c5a0 : ffffac84`b6fbae78 fffff802`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x1c9
ffffac84`b6fbae40 fffff804`21b47706 : ffffac84`b6fbb170 00000000`00000001 00000000`00000004 ffffac84`b6fbb178 : nt!ExWaitForRundownProtectionReleaseCacheAware+0xa0
ffffac84`b6fbaeb0 fffff804`219ce529 : 00000000`00000000 fffff802`00000003 00000000`00000000 ffff910c`30fda820 : tcpip!FlpWaitForMiniportToReturnTransmittedPackets+0xe
ffffac84`b6fbaee0 fffff804`2195ff78 : 00000000`00000fff 00000000`00001001 ffffd38e`00000000 00000000`00000000 : tcpip!FlpUninitializePacketProviderInterface+0x55
ffffac84`b6fbaf20 fffff804`2195c58e : ffffffff`5f114500 ffff910c`2b527c10 ffff910c`30fdbc00 ffff910c`30fda820 : tcpip!FlPnpEvent+0x138
ffffac84`b6fbafc0 fffff804`20faa86d : ffffffff`5f114500 ffff910c`2b527c10 ffff910c`000000de ffff910c`30fdbc00 : tcpip!Fl68PnpEvent+0xe
ffffac84`b6fbaff0 fffff804`20ff2151 : ffffac84`0000012b fffff804`2195c580 ffff910c`30fda820 00000000`00000008 : ndis!ndisDeliverNetPnPEventSynchronously+0x211
ffffac84`b6fbb070 fffff804`20fb3da1 : ffffac84`b6fbb2c0 ffffac84`b6fbb339 ffffac84`b6fbb2c0 ffff910c`2f4401a0 : ndis!ndisPnPNotifyBinding+0xe1
ffffac84`b6fbb250 fffff804`20fb3d43 : ffff910c`30fdbc00 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisPnPNotifyBindingUnlocked+0x35
ffffac84`b6fbb2a0 fffff804`20fb3c56 : ffffac84`b6fbb410 ffffd38e`2ec91520 00000000`00000000 ffff910c`00000000 : ndis!ndisPauseProtocolInner+0x7f
ffffac84`b6fbb3a0 fffff804`20fab268 : 00000000`00000004 ffffac84`b6fbb4e0 00000000`00000000 ffff910c`2f441548 : ndis!ndisPauseProtocol+0x66
ffffac84`b6fbb3e0 fffff804`20fab01b : ffff910c`2f4415b0 ffff910c`2f4415b0 ffffac84`b6fbb5a0 ffff910c`2f4415b0 : ndis!Ndis::BindEngine::Iterate+0x198
ffffac84`b6fbb550 fffff804`20faadba : ffff910c`00000000 ffff910c`2f4415c8 00000000`00000000 00000000`00000000 : ndis!Ndis::BindEngine::UpdateBindings+0x57
ffffac84`b6fbb580 fffff804`20f27621 : ffff910c`2f4401a0 00000000`00000020 ffff910c`2f4415b0 00000000`00000004 : ndis!Ndis::BindEngine::ApplyBindChanges+0x86
ffffac84`b6fbb5d0 fffff804`20fb6932 : ffff910c`2f4401a0 00000000`00000004 00000000`00000001 fffff802`2e94f800 : ndis!ndisPrepForLowPower+0x17f1d
ffffac84`b6fbb6a0 fffff804`20fb67e9 : 00000000`00000000 ffff910c`3b076010 00000000`00000004 00000000`00010297 : ndis!ndisSetSystemPower+0x13e
ffffac84`b6fbb720 fffff804`20f0e162 : ffff910c`3b076010 ffff910c`29690c00 ffff910c`3b076170 fffff802`2e537eb1 : ndis!ndisSetPower+0xa9
ffffac84`b6fbb760 fffff802`2ebd8548 : 00000000`00000016 00000000`00000000 ffff910c`2f440050 ffff910c`319942c0 : ndis!ndisPowerDispatch+0x142
ffffac84`b6fbb790 fffff802`2ebd8796 : 00000000`00000000 fffff802`2e597486 00000000`00000002 00000000`00000000 : nt!ViGenericDispatchHandler+0x54
ffffac84`b6fbb7d0 fffff802`2e537d82 : ffff910c`3b076010 00000000`00000000 ffff910c`2f440050 ffff910c`319942c0 : nt!ViGenericPower+0x16
ffffac84`b6fbb800 fffff802`2e5af368 : 00000000`00000000 fffff802`2ebc65f5 ffff910c`3b076010 ffff910c`3b0761b8 : nt!IopPoHandleIrp+0x36
ffffac84`b6fbb830 fffff802`2ebbad5d : ffff910c`3b076010 ffff910c`2f440050 00000000`00000000 00000000`00000000 : nt!IopfCallDriver+0x180594
ffffac84`b6fbb870 fffff802`2e5baf83 : ffffac84`b6fbba70 ffffac84`b6fbba09 ffff910c`3b076010 ffff910c`319942c0 : nt!IovCallDriver+0x275
ffffac84`b6fbb8b0 fffff802`2e540629 : 07400780`078007c0 ffffac84`b6fbb960 00000000`00000004 ffffac84`b6fbb9a1 : nt!IofCallDriver+0x16b973
ffffac84`b6fbb8f0 fffff804`204c7c1d : 00000000`00000008 fffff804`204c04d7 ffff910c`30380000 00000000`00000000 : nt!IoCallDriver+0x9
ffffac84`b6fbb920 fffff804`2049f5bb : ffff910c`2d8d4940 ffffac84`b6fbba70 ffffac84`b6fbba70 ffff910c`2d8d7950 : Wdf01000!FxPkgFdo::_PowerPassDown+0x6d [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 85] 
ffffac84`b6fbb950 fffff804`204b2064 : 00000000`00000002 00006ef3`d272b2f8 ffff910c`2d8d7950 00000000`00000000 : Wdf01000!FxPkgFdo::DispatchSystemSetPower+0x177 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 292] 
ffffac84`b6fbb9a0 fffff804`20497d9e : ffff910c`2d8d4d00 00006ef3`d272b2f8 ffff910c`2d8d7950 00000000`00000000 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x24 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 117] 
ffffac84`b6fbb9d0 fffff804`20497400 : ffff910c`3b076010 ffff910c`2d8d4d00 ffff910c`2d8d7950 fffff804`00000000 : Wdf01000!FxPkgPnp::Dispatch+0xee [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 682] 
ffffac84`b6fbba70 fffff802`2e563186 : ffff910c`3b076010 ffff910c`00000000 ffffac84`00000000 fffff802`2e77d7f0 : Wdf01000!FxDevice::DispatchWithLock+0x150 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430] 
ffffac84`b6fbbb60 fffff802`2e531b87 : ffffffff`fa0a1f00 ffff910c`312dc700 fffff802`2e562f60 00000000`00000000 : nt!PopIrpWorker+0x226
ffffac84`b6fbbc10 fffff802`2e597be6 : ffffc280`397a8180 ffff910c`312dc700 fffff802`2e531b40 fffff8c5`19c11480 : nt!PspSystemThreadStartup+0x47
ffffac84`b6fbbc60 00000000`00000000 : ffffac84`b6fbc000 ffffac84`b6fb6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .thread 0xffff910c312dc700 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  929007854288c598c53d886fe2203a4d29e198af

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ff9f86c894aea9db54f89f3a1b96aeea6ae9d70b

THREAD_SHA1_HASH_MOD:  f8a21147c2ee8a7de77da6297ccb630b905018df

FOLLOWUP_IP: 
tcpip!FlpWaitForMiniportToReturnTransmittedPackets+e
fffff804`21b47706 4883c428        add     rsp,28h

FAULT_INSTR_CODE:  28c48348

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  tcpip!FlpWaitForMiniportToReturnTransmittedPackets+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  6bc13c3

BUCKET_ID_FUNC_OFFSET:  e

FAILURE_BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_tcpip!FlpWaitForMiniportToReturnTransmittedPackets

BUCKET_ID:  0x9F_VRF_3_POWER_DOWN_tcpip!FlpWaitForMiniportToReturnTransmittedPackets

PRIMARY_PROBLEM_CLASS:  0x9F_VRF_3_POWER_DOWN_tcpip!FlpWaitForMiniportToReturnTransmittedPackets

TARGET_TIME:  2018-02-25T19:34:40.000Z

OSBUILD:  16299

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-02-10 05:34:33

BUILDDATESTAMP_STR:  170928-1534

BUILDLAB_STR:  rs3_release

BUILDOSVER_STR:  10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME:  81e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_vrf_3_power_down_tcpip!flpwaitforminiporttoreturntransmittedpackets

FAILURE_ID_HASH:  {6b1eea1b-d668-4f22-7ccc-816287641c18}

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

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Can you run the following utility from Intel and see if it picks up any driver updates :

https://www.intel.com/content/www/us/en/support/detect.html

Also, was there just one Hardware Id?

If more than one was there the following :

PCI\VEN_8086&DEV_9C03&CC_0106

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Just an update, I had upgraded my Intel wifi driver to 18.33.11.2, and had not crashed for a few days, but today I bluescreened again, with km:0x9f_3_power_down_tcpip!flpwaitforminiporttoreturntransmittedpackets again.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello,

thanks for your reply.

In addition there were:

PCI\VEN_8086&DEV_9C03&SUBSYS_05E31028
PCI\VEN_8086&DEV_9C03&CC_010601
PCI\VEN_8086&DEV_9C03&CC_0106

So: Yes!

Regarding the driver assistant: I did run that already. No updates.

Here the Report:

Greetings,

Hendrik

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Based on that Hardware Id you should be able to update the driver using the Device Manager

But first can you provide the minidump file from the latest crash?

And the following file if it got created:

C:\Windows\MEMORY.DMP

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Auggy,

> Based on that Hardware Id you should be able to update the driver using the Device Manager

You mean with the built in Windows function?

> But first can you provide the minidump file from the latest crash?

Sure:

https://1drv.ms/u/s!AvbzKdYzkh6gi02VPWdlJJRwHrkf (full dump)

https://1drv.ms/u/s!AvbzKdYzkh6gi05TRKWkrgLRjxLV (mini)

Greetings,

Hendrik

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The error still points to the Intel wireless driver.

Can you try the very latest driver (18.33.12.2) :

https://downloadcenter.intel.com/download/27615/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10?product=75439

Also, if you want to try updating the Intel SATA driver can you download the f6flpy-x64.zip from the following link :

https://downloadcenter.intel.com/download/26759/Intel-Rapid-Storage-Technology-Intel-RST-User-Interface-and-Driver

Unzip the f6flpy-x64.zip.

Can you locate the iaAHCIC.inf the f6flpy-x64 folder?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello auggy,

for the Wireless Driver, I have already the latest version installed.

The link you provided states:

WiFi_20.40.0_PROSet64_Win10.exe
Driver version = 20.40.0.4 for Windows 10 for 9461,9462, 9560, 9260, 18265, 8265, 18260, 8260 adapters.
Driver version = 19.51.11.2 for Windows 10 for 3168, 3165, 7265 (Rev. D) and 17265 adapters.
Driver version = 18.33.12.2 for Windows 10 for 7265 (Rev. C), 3160, and 7260 adapters.#

So 18.33.12.2 is the latest. When I execute WiFi_20.40.0_PROSet64_Win10.exe the driver remains this version.

For the Storage Driver:

 

your link leads to:
https://downloadcenter.intel.com/download/26759/Intel-Rapid-Storage-Technology-Intel-RST-User-Interface-and-Driver

This is : Version: 14.8.16.1063 (Previously Released) Date: 4/16/2017

And there is a re-direct to the latest driver:
https://downloadcenter.intel.com/download/27681/Intel-Rapid-Storage-Technology-Intel-RST-User-Interface-and-Driver?v=t
Version: 16.0.2.1086 (Latest) Date: 2/21/2018

But this latest driver (16.0.2.x) does not apply to my hardware.

Thus I installed 14.8.16.x. 

Not sure whether there is any driver between the two that works for my hardware and is more recent then 14.8.16.x, but we will see if this one already helped...

Greetings,

Hendrik

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I checked the drivers that were released between the two.

For my hardware, 14.8.16.x.  seems to be the latest driver.

Greetings,

Hendrik

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, that appears to be the latest.

Have you tried updating Windows 10 to the April 2018 update?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello

Jumping into this conversation as I am in similar situation, looking at the error details and description I think it's worth trying to disable power management for the network adapter, I have disabled it now and will see if I get these crashes again.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated January 28, 2021 Views 1,074 Applies to: