Issue with fast startup Windows 10 DRIVER_POWER_STATE_FAILURE

[whatdoesthebsodsays]

I have a Lenovo Y510p Laptop that I upgraded to windows 10, because of the update, everytime I turn on the fast startup feature I would get a BSOD with code: DRIVER_POWER_STATE_FAILURE.
I did some bugcheck on my own and it leads to: UsbHub3.sys
Which lead me to this: https://forums.lenovo.com/t5/Lenovo...te-failure-caused-by-usbhub3-sys/td-p/2046712
I have done the steps mentioned on that forum but that didn't solve my problem, any insights or suggestion would be greatly appreciated.

Here's the bugcheck analysis:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffde85d8c4f750, ffffcd00acdfb960, ffffde85d8df9010}

Probably caused by : UsbHub3.sys

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

7: 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: ffffde85d8c4f750, Physical Device Object of the stack
Arg3: ffffcd00acdfb960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffde85d8df9010, The blocked IRP

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.1715 (rs1_release_inmarket.170906-1810)

SYSTEM_MANUFACTURER: LENOVO

SYSTEM_PRODUCT_NAME: 20217

SYSTEM_SKU: LENOVO_BI_IDEAPAD

SYSTEM_VERSION: Lenovo IdeaPad Y510P

BIOS_VENDOR: LENOVO

BIOS_VERSION: 74CN44WW(V3.05)

BIOS_DATE: 09/18/2013

BASEBOARD_MANUFACTURER: LENOVO

BASEBOARD_PRODUCT: VIQY0Y1

BASEBOARD_VERSION: 31900058STD

DUMP_TYPE: 2

BUGCHECK_P1: 3

BUGCHECK_P2: ffffde85d8c4f750

BUGCHECK_P3: ffffcd00acdfb960

BUGCHECK_P4: ffffde85d8df9010

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5789998e

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80ee4f50000 UsbHub3

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: WINDOWSPC

ANALYSIS_SESSION_TIME: 09-26-2017 20:34:56.0279

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:
ffffcd00`acdfb928 fffff801`4c9ff4bb : 00000000`0000009f 00000000`00000003 ffffde85`d8c4f750 ffffcd00`acdfb960 : nt!KeBugCheckEx
ffffcd00`acdfb930 fffff801`4c9ff3ce : ffffde85`d9ac8900 ffffcd00`acb53180 00000000`00000001 00000000`000000f8 : nt!PopIrpWatchdogBugcheck+0xeb
ffffcd00`acdfb990 fffff801`4c83f361 : ffffde85`d9ac8938 00000000`0023ae28 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22
ffffcd00`acdfb9e0 fffff801`4c95b93a : 00000000`00000000 ffffcd00`acb53180 ffffcd00`acb5fcc0 ffffde85`de0eb080 : nt!KiRetireDpcList+0x701
ffffcd00`acdfbc60 00000000`00000000 : ffffcd00`acdfc000 ffffcd00`acdf6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e33925df3083bf4c2d113365ecd8a7a2b0012493

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 10.0.14393.0

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ibtusb_IMAGE_UsbHub3.sys

BUCKET_ID: 0x9F_3_POWER_DOWN_ibtusb_IMAGE_UsbHub3.sys

PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_ibtusb_IMAGE_UsbHub3.sys

TARGET_TIME: 2017-09-27T02:43:56.000Z

OSBUILD: 14393

OSSERVICEPACK: 1715

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: 2017-09-06 21:54:57

BUILDDATESTAMP_STR: 170906-1810

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.1715

ANALYSIS_SESSION_ELAPSED_TIME: c25

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_ibtusb_image_usbhub3.sys

FAILURE_ID_HASH: {08966383-8cdf-f9dd-b93c-74efb121520b}

Followup: MachineOwner

Minidump can also be found below

 

[Wolfie]

Hi,

apart from removing the offending device from the system using device manager and letting it re-install itself on next boot, I would first try troubleshooting?:

https://www.howtogeek.com/260248/how-to-make-windows-troubleshoot-your-pc-problems-for-you/

See also:

http://ccm.net/faq/43223-open-the-device-manager-in-windows-10

 

[Trouble]

I don't have anything to add, except a question.....
IS there any reason you are still running 14393 and haven't upgraded to 15063

 

[Wolfie]

Well spotted @Trouble.

See also:

https://www.windows10forums.com/threads/how-to-upgrade-windows-10-to-the-latest-version.13015/

 

[whatdoesthebsodsays]

I ran the troubleshooter and it found nothing (well what to expect from microsoft's troubleshooter). Re-installing the device driver doesn't help either. The issue is more with lenovo and windows 10, if I could make it go back to windows 8 I would...

 

[Wolfie]

Do you have a recovery partition on the computer and was it originally furnished with W8?, you can get recovery tools from Lenovo afaik?.

https://support.lenovo.com/de/en/solutions/ht036037