Vostro 5510 constantly going to BSOD in Windows 11

Dear all,

I have a user with a brand new Vostro 5510 running Windows 11 and constantly getting BSOD. It seems to happen a lot when he is bringing his laptop out of hibernation. I have included the crashdump at the bottom of this message. 

I have used the build-in Dell assistance app to make sure the laptop is up-to-date on Dell drivers. I have ensured the machine is patched up in Windows. I noticed some others were reporting a problem with the Goodix finger scanner driver and I have also manually downloaded from the Dell support site and did the update.

One thing is, he has a Dell U2720Q LCD which he uses it to power his laptop via USB-C port, instead of the power adapter. I am unsure if that will have an effect, although for a test, I have asked him to hook up his power adapter too.

Anyone come across this problem please?

Thanks,

Edmond.

_____________________________________________________________________________________________

1: 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: 0000000000000006, The device did not complete its Directed Power Transition callback successfully.
Arg2: ffffa48229723ae0, The POP_FX_DEVICE object
Arg3: 0000000000000000, If this was a Directed Power Down(1) or Power Up(0) completion
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3921

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3966

Key : Analysis.Init.CPU.mSec
Value: 1671

Key : Analysis.Init.Elapsed.mSec
Value: 17174

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 9f

BUGCHECK_P1: 6

BUGCHECK_P2: ffffa48229723ae0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

DRVPOWERSTATE_SUBCODE: 6

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffca04`5f73f1e8 fffff803`0dfc83dd : 00000000`0000009f 00000000`00000006 ffffa482`29723ae0 00000000`00000000 : nt!KeBugCheckEx
ffffca04`5f73f1f0 fffff803`0dfc7ee3 : ffffa482`29723ae0 00000000`00000000 ffffa482`012b6a00 ffffa482`29723eb0 : nt!PopFxEnforceDirectedPowerTransition+0xc1
ffffca04`5f73f250 fffff803`0dfc859a : 00000000`00000000 00000000`00000000 ffffa482`29723e78 00000000`00000000 : nt!PopFxCompleteDirectedPowerTransition+0x16f
ffffca04`5f73f2a0 fffff803`0dfc81c1 : ffffa482`29723ae0 ffffa482`012b6a20 ffffa482`012b6a20 ffffa482`0129d9a8 : nt!PopFxHandleDirectedPowerTransition+0xa6
ffffca04`5f73f2d0 fffff803`0dd1d35f : ffffa482`012b6a20 ffffa482`2a2dc000 ffffa482`00000000 fffff803`00000000 : nt!PopFxDirectedPowerTransitionWorker+0x11
ffffca04`5f73f300 fffff803`0dc478f5 : ffffa482`2a2dc040 ffffd001`056e0000 ffffa482`2a2dc040 00000000`00000000 : nt!ExpWorkerThread+0x14f
ffffca04`5f73f4f0 fffff803`0de1a2d4 : ffffd001`056d1180 ffffa482`2a2dc040 fffff803`0dc478a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffca04`5f73f540 00000000`00000000 : ffffca04`5f740000 ffffca04`5f739000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nt!PopFxEnforceDirectedPowerTransition+c1

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: c1

FAILURE_BUCKET_ID: 0x9F_nt!PopFxEnforceDirectedPowerTransition

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3a526de2-2a14-c8eb-842b-62f21361ee39}

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