Windows 10 BSOD on a new Lenovo, all drivers and Updates installed

Borizzz

Well-Known Member
Joined
Jun 5, 2018
Brand new Lenovo. Minidumps shows:

Minidump 1:

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BOR

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 12

Key : Analysis.Memory.CommitPeak.Mb
Value: 93

Key : Analysis.System
Value: CreateObject


TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffae88e022f360

BUGCHECK_P3: fffffd06f4ee7ba0

BUGCHECK_P4: ffffae88e5e6b710

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff8043a8a0000 pci

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: regini.exe

DPC_STACK_BASE: FFFFFD06F4EE7FB0

STACK_TEXT:
fffffd06`f4ee7b68 fffff804`36d5ffc7 : 00000000`0000009f 00000000`00000003 ffffae88`e022f360 fffffd06`f4ee7ba0 : nt!KeBugCheckEx
fffffd06`f4ee7b70 fffff804`36d5fee1 : ffffae88`e5f78508 00000000`00000000 ffffae89`182f31f0 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf
fffffd06`f4ee7be0 fffff804`36a81612 : ffffae88`e5f78540 ffff8701`70300180 ffff8701`70300180 ffff8701`00000002 : nt!PopIrpWatchdog+0x31
fffffd06`f4ee7c30 fffff804`36a9991d : ffff8701`70300180 00000080`00000000 00000000`00000008 00000000`00045918 : nt!KiProcessExpiredTimerList+0x172
fffffd06`f4ee7d20 fffff804`36bfe2e5 : b84106eb`00000940 ffff8701`70300180 00000000`00000000 ffffae89`32bcc560 : nt!KiRetireDpcList+0x5dd
fffffd06`f4ee7fb0 fffff804`36bfe0d0 : 00000000`0000fe31 fffffd07`0801dfd0 fffffd07`061c6008 00000000`00000000 : nt!KxRetireDpcList+0x5
fffffd07`0801de10 fffff804`36bfd79e : fffffd07`0801e058 fffff804`36a0c9cc 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
fffffd07`0801de40 fffff804`36a834aa : ffffae88`e0eba9f8 0000000e`009da8fa 00000000`00000000 ffffae89`00000000 : nt!KiDpcInterrupt+0x2ee
fffffd07`0801dfd0 fffff804`36b5fe37 : 00000000`00000000 fffffd07`00000000 00000000`0000004c ffffae88`00000000 : nt!ExpApplyPriorityBoost+0x4ca
fffffd07`0801e060 fffff804`36a0e506 : fffffd07`0801e188 fffff804`0000001b ffffffff`ffffff00 fffffd07`00000000 : nt!ExpApplyRewaitBoost+0x17
fffffd07`0801e090 fffff804`36a0968a : ffffae88`e0eba9f8 fffffd07`0801e170 fffffd07`00010244 fffff804`36b5fe20 : nt!ExpWaitForResource+0xc6
fffffd07`0801e110 fffff804`36a090f4 : 00000000`00000050 ffffae88`e0eba9f8 fffffd07`0801e460 00000000`00000001 : nt!ExpAcquireResourceSharedLite+0x4da
fffffd07`0801e1d0 fffff804`3aee766e : ffff9803`11e00100 ffff9803`12dd2470 ffff9803`11e00340 ffff9803`000000ff : nt!ExAcquireResourceSharedLite+0x44
fffffd07`0801e210 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonQueryInformation+0x53e


IMAGE_VERSION: 10.0.19041.1348

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner




Minidump 2:


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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BOR

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 1

Key : Analysis.Memory.CommitPeak.Mb
Value: 85

Key : Analysis.System
Value: CreateObject

Key : Dump.Attributes.InsufficientDumpfileSize
Value: 1


TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffa90f10d16060

BUGCHECK_P3: fffffe00690cf150

BUGCHECK_P4: ffffa90f20f0f760

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff804446a0000 pci

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffe00`690cf118 fffff804`4035ffc7 : 00000000`0000009f 00000000`00000003 ffffa90f`10d16060 fffffe00`690cf150 : nt!KeBugCheckEx
fffffe00`690cf120 fffff804`4035fee1 : ffffa90f`238b0898 00000000`00000000 ffffa90f`24b5b1f0 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf
fffffe00`690cf190 fffff804`40081612 : ffffa90f`238b08d0 ffffd101`6b400180 ffffd101`6b400180 00000000`00000002 : nt!PopIrpWatchdog+0x31
fffffe00`690cf1e0 fffff804`4009991d : 00000000`00000000 fffff804`400edb55 00000000`00140001 00000000`0067e3e2 : nt!KiProcessExpiredTimerList+0x172
fffffe00`690cf2d0 fffff804`401fae0e : ffffffff`00000000 ffffd101`6b400180 ffffd101`6b40b440 ffffa90f`248d9040 : nt!KiRetireDpcList+0x5dd
fffffe00`690cf560 00000000`00000000 : fffffe00`690d0000 fffffe00`690c9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION: 10.0.19041.1348

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}

Followup: MachineOwner
 
Hi,

is it possible to post the actual dumps?

Often this power tripping can be the gpu not power cycling properly and you can see in the second dump posted that Nvidia is mentioned.

Try updating/reinstalling the gpu driver but make sure you remove the original using DDU or display driver Uninstaller:
Display Driver Uninstaller (DDU) V18.0.4.6 Released. - Wagnardsoft Forum

Check your system files by opening an admin command prompt and typing sfc /scannow, press enter and any corruption should be repaired.

Post back with any new dumps.
 
Back
Top Bottom