Windows 10 BugCheck 9F / DRIVER_POWER_STATE_FAILURE /

[Calby]

Hi,
I did get a BSOD on my brand new laptop, whys that? Can someone please help me thanks in advance.

Setup
Lenovo Thinkpad T470s
Samsung EVO 960 256GB NVMe drive
20GB DDR4 2133MHz
Windows 10 Pro

When did it happen? Can it bee reproduced?
I did run Intel Burn test when the BSOD did happen on the setting "high" and "20" runs but afterwards I have been running Intel Burn test again because I did try to reproduce the issue but I could not do that.
I did run it for "30" runs at "standard", "high" and "very high" but no BSOD that's why I think it's not related to the intel burn test.

Anything connected to the computer?
Yes, my Logitech bluetooth mouse - but it was also connected later on when I did try to reproduce the issue but I could not reproduce it.
And the charger was connected.

Any new configuration?
The only thing that I don't have from "stock" is that I did install the drivers for my external 24" Samsung display but as I did it right from box I don't know if the issue is because of those drivers.

Any more useful information?
I have updated all drivers from Lenovos webbpage and Windows 10 is also up to date.
I have also been running memtest86 for 8h but it did not find any issues with the RAM.

I'm not so good to read the dumpfiles but what I can tell is that it's come kind of driver that did the BSOD right?
I did find this:

Spoiler

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

I'll install a new NVMe disk tomorrow but I don't want to do that until I know if this is a hardware or software issue.

I have tried to analyzed the dump file but my skills regarding that is limited so my question for you guys is - can you see what driver(?) that are causing the issue?

Here is a link to the complete Memory.dmp file, I have rared it so it's only 100MB.
dump_file

Here's a little from the dump file:

Spoiler: Here's a little from the dump file:

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


Loading Dump File [C:\Users\Robin\Downloads\Torrent\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
Machine Name:
Kernel base = 0xfffff801`64e7b000 PsLoadedModuleList = 0xfffff801`6517a000
Debug session time: Mon Mar 27 15:17:59.455 2017 (UTC + 2:00)
System Uptime: 0 days 1:20:49.216
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffff93835f935060, fffff8016761b8e0, ffff9383622c8010}

Implicit thread is now ffff9383`5e876040
Page db1 not present in the dump file. Type ".hh dbgerr004" for details
Page db1 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : pci.sys

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

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

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

Implicit thread is now ffff9383`5e876040

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 14393.953.amd64fre.rs1_release_inmarket.170303-1614

SYSTEM_MANUFACTURER: LENOVO

SYSTEM_PRODUCT_NAME: 20HF0000MX

SYSTEM_SKU: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s

SYSTEM_VERSION: ThinkPad T470s

BIOS_VENDOR: LENOVO

BIOS_VERSION: N1WET28W (1.07 )

BIOS_DATE: 02/13/2017

BASEBOARD_MANUFACTURER: LENOVO

BASEBOARD_PRODUCT: 20HF0000MX

BASEBOARD_VERSION: SDK0J40697 WIN

DUMP_TYPE: 1

BUGCHECK_P1: 3

BUGCHECK_P2: ffff93835f935060

BUGCHECK_P3: fffff8016761b8e0

BUGCHECK_P4: ffff9383622c8010

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: 5e876040

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5850cc6b

MODULE_NAME: pci

FAULTING_MODULE: fffff80591e00000 pci

CPU_COUNT: 4

CPU_MHZ: a98

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8e

CPU_STEPPING: 9

CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 4E'00000000 (cache) 4E'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-0TJK2IM

ANALYSIS_SESSION_TIME: 03-27-2017 19:31:33.0858

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:
ffffe080`9ce86950 fffff801`64eb446c : 00000000`00000000 00000000`00000001 00000000`00000010 00000000`00000282 : nt!KiSwapContext+0x76
ffffe080`9ce86a90 fffff801`64eb3f0f : 00000000`00000000 fffff805`91d35110 00000000`00000000 ffff9383`5e876000 : nt!KiSwapThread+0x17c
ffffe080`9ce86b40 fffff801`64eb5cd7 : ffff9383`00000000 00000000`00000000 ffff9383`6162b010 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffffe080`9ce86be0 fffff805`91d21568 : ffffe080`9ce86cf8 00000000`00000000 00000000`00000000 ffffcc87`00000000 : nt!KeWaitForSingleObject+0x377
ffffe080`9ce86c90 fffff805`91d212bd : ffffe080`00000000 ffffcc87`9221a110 ffff9383`63b67010 00000000`00000004 : ACPI!SyncEvalObject+0x268
ffffe080`9ce86d40 fffff805`91d27900 : 00000000`00000000 fffff805`966b82ce 00000000`00000000 ffffcc87`94bd76e0 : ACPI!AMLIEvalNameSpaceObject+0xad
ffffe080`9ce86da0 fffff805`91d24637 : ffff9383`63b67010 fffff805`00000004 00000000`00000000 ffffcc87`9221a110 : ACPI!ACPIIoctlEvalControlMethod+0x68
ffffe080`9ce86e00 fffff805`91d2420e : ffff9383`5ed8b500 00000000`00000007 ffff9383`63b67170 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0x157
ffffe080`9ce86e40 fffff805`93471752 : 00000000`00000007 00000000`00000000 ffff9383`6074b030 ffff9383`6074b180 : ACPI!ACPIDispatchIrp+0xce
ffffe080`9ce86ec0 fffff805`93594d14 : 00000000`00000000 ffffe080`9ce87059 00000000`00000000 ffff9383`606bb000 : dxgkrnl!DpiDispatchIoctl+0xa2
ffffe080`9ce86fe0 fffff805`964dfc5b : ffff9383`6074b030 ffff9383`60950000 ffffcc87`94cb3740 00000000`0000003c : dxgkrnl!DpEvalAcpiMethod+0x244
ffffe080`9ce870b0 fffff805`964dfeb3 : 00000000`ffffffff 00000000`c0000001 fffff805`96c3b200 00000000`0000003c : igdkmd64+0x4fc5b
ffffe080`9ce870f0 fffff805`9650169c : ffff9383`60950000 00000000`00000007 00000000`00000000 00000000`00000000 : igdkmd64+0x4feb3
ffffe080`9ce87180 fffff805`9669e61a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : igdkmd64+0x7169c
ffffe080`9ce871f0 fffff805`967110de : 00000000`00000002 fffff805`9669f7fd 00000000`00000001 ffff9383`606ce010 : igdkmd64+0x20e61a
ffffe080`9ce87240 fffff805`96718182 : ffff9383`6229f3e0 ffff9383`60686900 00000000`00000000 00000000`00000001 : igdkmd64+0x2810de
ffffe080`9ce872b0 fffff805`9668f8ec : 00000000`00000000 ffffe080`00000001 fffff805`00000000 ffff9383`60682f58 : igdkmd64+0x288182
ffffe080`9ce87300 fffff805`9668f5be : ffffe080`9ce87458 ffff9383`60686960 ffff9383`60682bc0 00000000`00002000 : igdkmd64+0x1ff8ec
ffffe080`9ce87340 fffff805`964de1b1 : ffff9383`00000002 ffff9383`60950000 ffffe080`9ce87458 ffff9383`60950000 : igdkmd64+0x1ff5be
ffffe080`9ce873a0 fffff805`964dea90 : 00000000`00000001 00000000`00000000 ffff9383`60950000 00000000`00000000 : igdkmd64+0x4e1b1
ffffe080`9ce873f0 fffff805`964dd514 : ffff9383`60950000 fffff805`96880e10 ffffe080`9ce87799 00000000`ffffffff : igdkmd64+0x4ea90
ffffe080`9ce87740 fffff805`934d2a31 : 00000000`00000001 00000000`00000001 fffff805`00000000 ffff9383`00000000 : igdkmd64+0x4d514
ffffe080`9ce87800 fffff805`934d2410 : 00000000`00000000 ffffe080`9ce878e1 00000000`00000002 00000000`00000000 : dxgkrnl!DpiDxgkDdiSetPowerState+0x51
ffffe080`9ce87860 fffff805`934d2d7e : ffffe080`9ce87902 ffff9383`6074b030 00000000`00000001 00000000`00000000 : dxgkrnl!DpiFdoSetAdapterPowerState+0x288
ffffe080`9ce87940 fffff805`934d25ab : ffff9383`622c8000 ffff9383`6074b180 ffff9383`622c8010 fffff801`64f99c6e : dxgkrnl!DpiFdoHandleDevicePower+0x2fe
ffffe080`9ce879d0 fffff801`64f997b2 : ffff9383`00000000 ffff9383`5e876040 ffff9383`5e876040 fffff801`65175600 : dxgkrnl!DpiDispatchPower+0x8b
ffffe080`9ce87af0 fffff801`64f312d5 : 91d6a6a5`54ad4188 fffff801`64f995d4 00000000`00000000 00000000`00000053 : nt!PopIrpWorker+0x1de
ffffe080`9ce87b90 fffff801`64fcec86 : ffffe080`9ce91180 ffff9383`5e876040 fffff801`64f31294 73ecfe69`e8e97857 : nt!PspSystemThreadStartup+0x41
ffffe080`9ce87be0 00000000`00000000 : ffffe080`9ce88000 ffffe080`9ce81000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .thread 0xffff93835e876040 ; kb

THREAD_SHA1_HASH_MOD_FUNC: 7922412f45f4bbbce6edcbd074ad4367cde3d4bb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6d6a75dc5cea53371f3714595b5083c3dd6d4f49

THREAD_SHA1_HASH_MOD: 762ccdf9e59d1e2aa3e146f771523440fd22ac01

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 10.0.14393.594

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

PRIMARY_PROBLEM_CLASS: 0x9F_3_ACPI_IMAGE_pci.sys

TARGET_TIME: 2017-03-27T13:17:59.000Z

OSBUILD: 14393

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-03-04 07:09:56

BUILDDATESTAMP_STR: 170303-1614

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.953.amd64fre.rs1_release_inmarket.170303-1614

ANALYSIS_SESSION_ELAPSED_TIME: 5f5

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_acpi_image_pci.sys

FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

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

 

[Calby]

Hi Calby,

to test the drive further you could always create a folder and fill it with anything, books, photo's, music and applications. You could then use this folder to test the drive by transferring filers to and from another drive.
No bsod so far is a really good sign too although I would still update what drivers you can especially chipset..

Hi,
I have done all of the updates that they did have on Lenovo. (No new ones for the chipset or Graphic)
I see today that they did reales a update for "Link Removed" I have been updating the FW now.
Don't know if my issue was fixed in the update or not - I could not tell from the "Readme" file here is the read me file:
https://download.lenovo.com/pccbbs/mobiles/n1qrg11w.txt

I have installed everything and I have been playing around with the laptop so far everything is good, one thing that I have been notice.
I don't have micro lags anymore, with the old NVMe drive when I was typing it could lag and then the text did write it self very fast when the lag was gone, it was only for like 1 sec or less but still.
Don't know if it was because of the old NVMe drive or not.

Edit:
I did run a stresstest for the NVMe for 10 to 20 min and no BSOD this did load read / write to the top of the nvme drive.

Link Removed

 

[kemical]

Hi Calby,
well those Intel management Engine updates are important too and you should always try and be up to date with those. (basically they tell the pc how to run).

Don't know if my issue was fixed in the update or not - I could not tell from the "Readme" file here is the read me file:

WHAT THIS PACKAGE DOES

This package updates the following software.

- Intel Management Engine Firmware

Refer to marketing materials to find out what computer models support Intel
Management Engine.

Updating the software will fix problems, add new functions, or expand
functions as noted below.

This program is language dependent, but can be used with any language system.

Looks like just what you needed..

 

[Calby]

Hi Calby,
well those Intel management Engine updates are important too and you should always try and be up to date with those. (basically they tell the pc how to run).





Looks like just what you needed..

Let's hope so, but if the pcie bus and the nvme drive can handle 20min stress test without any issue I guess that we can rule it out? And say that the issue are not there.
I don't want to run it more then that as the nvme drive have limited read and writes.

Maybe it was my old nvme drive that was defect or maybe the new FW update did solve the issue.
Anyway I have not been seeing any BSOD anymore.

 

[kemical]

Anyway I have not been seeing any BSOD anymore.

Long may it continue..

 

[Calby]

Long may it continue..

Let's hope so, thanks for all of you help.