5 Replies Latest reply on Nov 19, 2015 11:25 AM by mikec_intel

    NUC5I3RYH: Win 8.1 x64 crashes after entering sleep mode

    nuc5i3-user

      I have been seeing this issue since updating to latest BIOS Version 0350 - RYBDWi35.86A.0350.2015.0812.1722 and/or the latest graphics and/or bluetooth and/or wireless drivers. Following happens approx. once a week:

       

      1. Put NUC into sleep mode and wait at least 10 minutes.

      2. Try to resume (keyboard strike) -> this doesn't work, as Windows has crashed.

      3. Power on NUC and check system event log -> "13.11.2015 20:53:56" (as an example) is the time stamp of entering slep mode (next event is the powering on).

      4. Using WinDbg load and analyze the crash dump file:

       

      Debug session time: Fri Nov 13 20:58:56.147 2015 (Note: This is exactly 5 minutes after entering sleep mode).

      ...

      Bugcheck Analysis

      ...

      BugCheck 9F, {3, ffffe001405cc7f0, fffff80245e4a960, ffffe00141f61af0}

      Probably caused by : UsbHub3.sys

      ...

      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: ffffe001405cc7f0, Physical Device Object of the stack

      Arg3: fffff80245e4a960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

      Arg4: ffffe00141f61af0, The blocked IRP

       

      Debugging Details:

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

      DRVPOWERSTATE_SUBCODE:  3

      DRIVER_OBJECT: ffffe0014071e390

      IMAGE_NAME:  UsbHub3.sys

      ...

      DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

      BUGCHECK_STR:  0x9F

      PROCESS_NAME:  System

      CURRENT_IRQL:  2

      ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

      ...

      FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_UsbHub3.sys

      BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_UsbHub3.sys

      ANALYSIS_SOURCE:  KM

      FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_image_usbhub3.sys

       

      0: kd> lmvm UsbHub3

      start                  end                     module name

      fffff801`97f2a000 fffff801`97fa2000   UsbHub3    (pdb symbols)          c:\program files (x86)\windows kits\8.1\localsymbols\usbhub3.pdb\43723A82F3A14743B93BBD6298DCFBFA2\usbhub3.pdb

          Loaded symbol image file: UsbHub3.sys

          Mapped memory image file: c:\program files (x86)\windows kits\8.1\localsymbols\UsbHub3.sys\5507A0C078000\UsbHub3.sys

          Image path: \SystemRoot\System32\drivers\UsbHub3.sys

          Image name: UsbHub3.sys

          Timestamp:        Tue Mar 17 04:34:24 2015 (5507A0C0)

          CheckSum:         0007A29D

          ImageSize:        00078000

          File version:     6.3.9600.17731

          Product version:  6.3.9600.17731

          File flags:       0 (Mask 3F)

          File OS:          40004 NT Win32

          File type:        3.7 Driver

          File date:        00000000.00000000

          Translations:     0409.04b0

          CompanyName:      Microsoft Corporation

          ProductName:      Microsoft® Windows® Operating System

          InternalName:     usbhub3.sys

          OriginalFilename: usbhub3.sys

          ProductVersion:   6.3.9600.17731

          FileVersion:      6.3.9600.17731 (winblue_r9.150316-1500)

          FileDescription:  USB3 HUB Driver

          LegalCopyright:   © Microsoft Corporation. All rights reserved.

       

      According to Microsoft, the usbhub3.sys driver is not causing the problem. One of the devices connected to the USB3 HUB or its driver is causing the problem.

       

      The only connected external device is a keyboard. I suspect the Intel bluetooth module (part of the wireless card) or its driver (version 17.1.1532.1813) causing the problem. It seems that Windows tries to enter the sleep mode for exactly 5 minutes and then crashes due to A driver has failed to complete a power IRP within a specific time.