Networking: DRIVER_POWER_STATE_FAILURE (9f)

Maybecompletelyw_0 276 Reputation points
2020-12-29T17:26:29.837+00:00

Sporadic crash, when going to sleep S3: 

2: kd> !poaction  
PopAction: fffff80038223360  
  State..........: 3 - Set System State  
  Updates........: 0   
  Action.........: Sleep  
  Lightest State.: Sleeping3  
  Flags..........: 80000004 OverrideApps|Critical  
  Irp minor......: SetPower  
  System State...: Sleeping3  
  Hiber Context..: 0000000000000000

NETWORK DEBUG REPORT shows a 

2: kd> !ndiskd.help STUCK_NBL_DETECTED  
  
FLAG  
  
    STUCK_NBL_DETECTED  
  
  
DESCRIPTION  
  
    NDIS has detected that this miniport has held onto an NBL for an excessive  
    amount of time.  This can indicate that the miniport has an implementation  
    bug that causes NBLs to be "lost", or it may have a design flaw that causes  
    NBLs to be queued for an unreasonable amount of time.

Red rectangle:

52036-netreportpk.jpg
51977-netreport3.jpg

Is it correct, that this could be the failing component?
Some misconfiguration of Hyper-V Virtual Switch perhaps? 

    Hyper-V Virtual Switch Extension Adapter #3  
  
    Ndis handle        ffff9e84553091a0  
    Ndis API version   v6.60  
    Adapter context    ffff9e8455861000  
    Driver             ffff9e84558308b0 - vmsmp  v17.0  
    Network interface  ffff9e8450e61010  
  
    Media type         802.3  
    Physical medium    NdisPhysicalMediumUnspecified  
    Device instance    ROOT\VMS_VSMP\0003  
    Device object      ffff9e8455309050  
    MAC address        [Zero-length address]  
  
STATE  
    Miniport           Running  
    Device PnP         Started  
    Datapath           Normal  
    Interface          Up  
    Media              Connected  
    Power              D0  
    References         3  
    Total resets       0  
    Pending OID        None  
    Flags              NOT_BUS_MASTER, DEFAULT_PORT_ACTIVATED,  
                       SUPPORTS_MEDIA_SENSE, DOES_NOT_DO_LOOPBACK,  
                       MEDIA_CONNECTED  
    PnP flags          VIRTUAL_DEVICE, SYSTEM_SLEEPING, HIDDEN,  
                       NO_HALT_ON_SUSPEND, RECEIVED_START,  
                       CANCELLED_WAKEUP_TIMER  
  
POWER MANAGEMENT  
    Bus Capabilities (IRP_MN_QUERY_CAPABILITIES):  
    SystemWake         PowerSystemUnspecified  
    DeviceWake         PowerDeviceUnspecified  
  
    System state       Device state                                               
    Working            D0  
    S1                 D3  
    S2                 D3  
    S3                 D3  
    S4 (Hibernate)     D3  
    S5 (Shutdown)      D3  
  
    Power management is not enabled  
  
   .....

Just for completeness: 

2: 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: ffff9e84590afb70, Physical Device Object of the stack  
Arg3: ffff8300dc837850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack  
Arg4: ffff9e8455450a60, The blocked IRP  
  
Debugging Details:  
------------------  
  
Implicit thread is now ffff9e84`5037d080  
  
KEY_VALUES_STRING: 1  
  
    Key  : Analysis.CPU.mSec  
    Value: 4187  
  
    Key  : Analysis.DebugAnalysisProvider.CPP  
    Value: Create: 8007007e on WINDOWS7  
  
    Key  : Analysis.DebugData  
    Value: CreateObject  
  
    Key  : Analysis.DebugModel  
    Value: CreateObject  
  
    Key  : Analysis.Elapsed.mSec  
    Value: 25151  
  
    Key  : Analysis.Memory.CommitPeak.Mb  
    Value: 96  
  
    Key  : Analysis.System  
    Value: CreateObject  
  
    Key  : WER.OS.Branch  
    Value: vb_release  
  
    Key  : WER.OS.Timestamp  
    Value: 2019-12-06T14:06:00Z  
  
    Key  : WER.OS.Version  
    Value: 10.0.19041.1  
  
  
ADDITIONAL_XML: 1  
  
OS_BUILD_LAYERS: 1  
  
BUGCHECK_CODE:  9f  
  
BUGCHECK_P1: 3  
  
BUGCHECK_P2: ffff9e84590afb70  
  
BUGCHECK_P3: ffff8300dc837850  
  
BUGCHECK_P4: ffff9e8455450a60  
  
DRVPOWERSTATE_SUBCODE:  3  
  
FAULTING_THREAD:  ffff9e845037d080  
  
BLACKBOXBSD: 1 (!blackboxbsd)  
  
  
BLACKBOXNTFS: 1 (!blackboxntfs)  
  
  
BLACKBOXPNP: 1 (!blackboxpnp)  
  
  
BLACKBOXWINLOGON: 1  
  
PROCESS_NAME:  System  
  
STACK_TEXT:    
ffff8300`dc813cb0 fffff800`37865850     : fffff800`334b3180 00000000`ffffffff 00000000`00000000 ffff9e84`599f6158 : nt!KiSwapContext+0x76  
ffff8300`dc813df0 fffff800`37864d7f     : fdffffff`00000000 ffff9e84`00000003 ffff8300`dc813fb0 ffff8d01`00000000 : nt!KiSwapThread+0x500  
ffff8300`dc813ea0 fffff800`37864623     : fffff800`00000000 fffff800`00000000 00000000`00000000 ffff9e84`5037d1c0 : nt!KiCommitThreadWait+0x14f  
ffff8300`dc813f40 fffff800`3b7a7387     : ffff8300`dc814060 fffff800`00000000 ffff9e84`5920e000 00000000`09226400 : nt!KeWaitForSingleObject+0x233  
ffff8300`dc814030 fffff800`3deb5c3b     : 00000249`0cd9442c 00000000`00000000 00000000`00000000 ffff9e84`5920e000 : ndis!NdisMSleep+0x67  
ffff8300`dc8140b0 fffff800`3b88e519     : ffff9e84`59247220 00000000`00000008 ffff8300`dc00ff00 ffff9e84`55000000 : vmswitch!VmsPtNicNetPnPEvent+0x52acb  
ffff8300`dc8141f0 fffff800`3b88e113     : 00000000`00000000 ffff8300`dc814400 ffff9e84`59245090 ffff8300`dc814400 : ndis!ndisInvokeNetPnPEvent+0x81  
ffff8300`dc814260 fffff800`3b8bbcb1     : 00000000`00000008 ffff8300`dc8143f0 ffff9e84`5582f8a0 ffff9e84`5582f8e8 : ndis!ndisDeliverNetPnPEventSynchronously+0xe7  
ffff8300`dc8142f0 fffff800`3b89a659     : ffff9e84`5924fa00 ffff8300`dc814560 ffff8300`dc814560 ffff9e84`592061a0 : ndis!ndisPnPNotifyBinding+0x13d  
ffff8300`dc8144f0 fffff800`3b8b0495     : ffff9e84`59245090 fffff800`378ebb7d ffff9e84`0a680aa0 ffff8300`dc814610 : ndis!ndisPnPNotifyBindingUnlocked+0x35  
ffff8300`dc814540 fffff800`3b8b036d     : ffffde07`f47077e0 ffffde07`f47077e0 00000000`00000000 ffff8300`dc8147a0 : ndis!ndisPauseProtocolInner+0x79  
ffff8300`dc814640 fffff800`3b8a1c3a     : 00000000`00000000 ffff8300`dc8147a0 00000000`00000000 ffff9e84`59207590 : ndis!ndisPauseProtocol+0xb1  
ffff8300`dc8146a0 fffff800`3b8947f8     : ffff9e84`592061a0 ffff9e84`592061a0 ffff9e84`59207608 ffff9e84`59207590 : ndis!Ndis::BindEngine::Iterate+0xd396  
ffff8300`dc814820 fffff800`3b88de2e     : ffff9e84`59207590 ffff8300`dc814a00 00000000`00000000 00000000`00000000 : ndis!Ndis::BindEngine::UpdateBindings+0x98  
ffff8300`dc814870 fffff800`3b88de94     : ffff9e84`59207590 00000000`00000000 ffff9e84`59207590 fffff800`3b88b917 : ndis!Ndis::BindEngine::DispatchPendingWork+0x76  
ffff8300`dc8148a0 fffff800`3b7d44f2     : ffff9e84`592061a0 ffff8300`dc814a80 ffff9e84`55450a60 ffff9e84`55450a60 : ndis!Ndis::BindEngine::ApplyBindChanges+0x54  
ffff8300`dc8148f0 fffff800`3b7a3e4d     : 00000000`00000000 ffff9e84`592061a0 ffff9e84`592061a0 fffff800`3b88dcd2 : ndis!ndisPrepForLowPowerCommon+0x30676  
ffff8300`dc8149e0 fffff800`3b7a49a9     : 00000000`00000004 ffff9e84`55450a60 ffff9e84`592061a0 fffff800`3b79e0b8 : ndis!ndisPrepForLowPower+0x1d  
ffff8300`dc814a30 fffff800`3b7a524e     : 00000000`00000000 ffff9e84`00000004 ffff9e84`592061a0 ffff9e84`55450b78 : ndis!ndisSetSystemPower+0x191  
ffff8300`dc814ab0 fffff800`3b7a6654     : ffff9e84`55450a60 ffff9e84`590afb70 ffff9e84`55450b78 ffff9e84`592061a0 : ndis!ndisSetPower+0x10a  
ffff8300`dc814b10 fffff800`3799ca09     : ffff9e84`5037d080 ffff8300`dc814bf0 ffff9e84`55450a60 ffff9e84`59206050 : ndis!ndisPowerDispatch+0x114  
ffff8300`dc814b70 fffff800`37917e25     : 00000000`00000000 fffff800`3799c830 00000000`00000000 00000000`00000097 : nt!PopIrpWorker+0x1d9  
ffff8300`dc814c10 fffff800`379fcdd8     : ffff8d01`f5a80180 ffff9e84`5037d080 fffff800`37917dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55  
ffff8300`dc814c60 00000000`00000000     : ffff8300`dc815000 ffff8300`dc80f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28  
  
  
STACK_COMMAND:  .thread 0xffff9e845037d080 ; kb  
  
SYMBOL_NAME:  vmswitch!VmsPtNicNetPnPEvent+52acb  
  
MODULE_NAME: vmswitch  
  
IMAGE_NAME:  vmswitch.sys  
  
BUCKET_ID_FUNC_OFFSET:  52acb  
  
FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_vmswitch!VmsPtNicNetPnPEvent  
  
OS_VERSION:  10.0.19041.1  
  
BUILDLAB_STR:  vb_release  
  
OSPLATFORM_TYPE:  x64  
  
OSNAME:  Windows 10  
  
FAILURE_ID_HASH:  {b25836ba-3b6f-c4d9-fe99-ce9ee5abdff8}  
  
Followup:     MachineOwner  
---------  
  
2: kd> !irp ffff9e8455450a60  
Irp is active with 3 stacks 2 is current (= 0xffff9e8455450b78)  
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.    
     cmd  flg cl Device   File     Completion-Context  
 [N/A(0), N/A(0)]  
            0  0 00000000 00000000 00000000-00000000      
  
			Args: 00000000 00000000 00000000 00000000  
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]  
            0 e1 ffff9e8459206050 00000000 fffff80037f926b0-ffff9e845c7c1930 Success Error Cancel pending  
	       \Driver\NdisImPlatform	nt!PopSystemIrpCompletion  
			Args: 00014400 00000000 00000004 00000002  
 [N/A(0), N/A(0)]  
            0  0 00000000 00000000 00000000-ffff9e845c7c1930      
  
			Args: 00000000 00000000 00000000 00000000
Windows Hardware Performance
Windows Hardware Performance
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Hardware Performance: Delivering / providing hardware or hardware systems or adjusting / adapting hardware or hardware systems.
1,547 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Maybecompletelyw_0 276 Reputation points
    2021-02-11T10:13:14.01+00:00

    Faulting Windows version:
    Windows 10 Kernel Version 19041 MP (4 procs) Free x64

    DRIVER_POWER_STATE_FAILURE (9f) happened sporadically, when explicitely bridging an 'internal' Hyper-V switch to Intel Wifi to get Internet connection.
    Leaving settings alone and using just the 'Default Switch' out of the box for Internet - no bridge in 'Adapter Settings' - with kernel 19042.804 no problems so far.

    1 person found this answer helpful.
    0 comments
  2. Harini Ramakrishnan 1 Reputation point
    2021-02-11T01:40:43.723+00:00

    @Maybecompletelyw_0 Can you give me some details on which build is being used, configuration and repro steps?

    0 comments