• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Locked

‎09-14-2022 03:20 AM

HP Recommended

Hi Ub6424,

This Notebook was purchased in September 2021 and the thermal paste has not been replaced.

Thank you.

Was this reply helpful? Yes No

‎09-14-2022 03:23 AM - edited ‎09-14-2022 03:25 AM

HP Recommended

Hello @ArserHsieh 

 

(1) Repeat to monitor cpu and gpu temperatures

--->>> take screenshot after a few minutes <gaming>

 

(2) Please report your results

Was this reply helpful? Yes No

‎09-14-2022 03:30 AM

HP Recommended

Hi Ub6424,

Here is the new screenshot:

Performance2.png

 

I think the design of this Dragonfly Max is bad because its vents are so close to the desktop that even if I add a pad, still feels like the notebook is running hot.

PS: My work environment is air-conditioned.

Thank you.

Was this reply helpful? Yes No

‎09-14-2022 04:15 AM

HP Recommended

Hello @ArserHsieh 

 

Test performance and stability ...

 

(1) Choose what you like and test

 10+ BEST GPU Benchmark Software for PC (Free/Paid) in 2022

 

(2) Does your notebook freezes and crashes ?

 

(3) Please report your results...

Was this reply helpful? Yes No

‎09-14-2022 08:48 PM

HP Recommended

Hi Ub6424,

Stability testing for six hours without a crash.

stabilitytest.png

 

My system crashes frequently when AC and battery are used interchangeably, but less than five times in two years.

The most recent crash occurred on September 13, and the dump file records that it was caused by mslldp.sys:

DumpFile 

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

Debugging Details:
------------------
Implicit thread is now ffffcc0f`d86ef040
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4124
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4451
Key : Analysis.Init.CPU.mSec
Value: 3092
Key : Analysis.Init.Elapsed.mSec
Value: 20919
Key : Analysis.Memory.CommitPeak.Mb
Value: 121
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

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1800
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffcc0fde8aed80
BUGCHECK_P3: fffff8030846a0d0
BUGCHECK_P4: ffffcc0fd9aaa010
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffcc0fd86ef040
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System

STACK_TEXT:
ffffcb0d`c8ee66d0 fffff803`0cc80c17 : ffffe201`524cf180 ffffcb0d`ffffffff ffffcb0d`00000000 00000000`00000000 : nt!KiSwapContext+0x76
ffffcb0d`c8ee6810 fffff803`0cc82ac9 : ffffffff`00000001 fffff803`00000007 00000000`00000000 00000083`00000000 : nt!KiSwapThread+0x3a7
ffffcb0d`c8ee68f0 fffff803`0cc86786 : 00000000`00000000 00000000`00000000 00000000`000000a7 0000006c`0c306d91 : nt!KiCommitThreadWait+0x159
ffffcb0d`c8ee6990 fffff803`598ff88a : ffffcc0f`dff44260 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KeDelayExecutionThread+0x416
ffffcb0d`c8ee6a20 fffff803`598ff4c5 : 00000000`00000000 ffffffff`ff63c000 00000000`00000000 00000000`0000000d : mslldp!lldpWaitForValueToZero+0x36
ffffcb0d`c8ee6a50 fffff803`598fd037 : ffffcc0f`c6fd5000 ffffcb0d`c8ee6f00 ffffcc0f`ddaeb1c0 ffffcc0f`ddaeb1c0 : mslldp!lldpWaitForTxCompletion+0x69
ffffcb0d`c8ee6a90 fffff803`598fcf36 : 00000000`00000008 ffffcb0d`c8ee6b28 00000000`00000004 00000000`00000000 : mslldp!lldpProtPauseBinding+0x3b
ffffcb0d`c8ee6ac0 fffff803`0f4e696a : ffffcc0f`e017cba0 00000000`00000008 ffffcb0d`c8ee6cf0 ffffcc0f`d3444c00 : mslldp!lldpProtNetPnPEvent+0x2f6
ffffcb0d`c8ee6af0 fffff803`0f4e66e9 : 00000000`00000000 ffffcb0d`c8ee6cf0 ffffcc0f`e017cba0 ffffcb0d`c8ee6cf0 : ndis!ndisInvokeNetPnPEvent+0x7e
ffffcb0d`c8ee6b60 fffff803`0f51e9b2 : ffffcc0f`dff44260 ffffcc0f`d3444c00 ffffcb0d`c8ee6ce0 ffffcc0f`e017cba0 : ndis!ndisDeliverNetPnPEventSynchronously+0xf5
ffffcb0d`c8ee6be0 fffff803`0f4e9ddc : 00000000`00000000 ffffcb0d`c8ee6e50 ffffcb0d`c8ee6e50 ffffcc0f`e3feb1a0 : ndis!ndisPnPNotifyBinding+0x18e
ffffcb0d`c8ee6de0 fffff803`0f4e5149 : ffffcc0f`e017cba0 fffff803`0e6e12a6 ffffcb0d`c8ee6f90 ffffcb0d`c8ee6f90 : ndis!ndisPnPNotifyBindingUnlocked+0x44
ffffcb0d`c8ee6e30 fffff803`0f4e502d : ffffa588`8a2e1930 ffffa588`8a2e1930 00000000`00000000 ffffcc0f`e3feb1a0 : ndis!ndisPauseProtocolInner+0x79
ffffcb0d`c8ee6f30 fffff803`0f4e7980 : 00000000`00000000 ffffcb0d`c8ee7090 00000000`00000004 ffffcc0f`e3fec598 : ndis!ndisPauseProtocol+0xb1
ffffcb0d`c8ee6f90 fffff803`0f4e7574 : ffffcc0f`e3feb1a0 ffffcc0f`e3feb1a0 ffffcc0f`e3fec610 ffffcc0f`e3fec598 : ndis!Ndis::BindEngine::Iterate+0x13c
ffffcb0d`c8ee7110 fffff803`0f4ebcd6 : ffffcc0f`e3fec598 ffffcc0f`d9aaa000 00000000`00000000 fffff803`0f4e80c5 : ndis!Ndis::BindEngine::UpdateBindings+0x98
ffffcb0d`c8ee7160 fffff803`0f4ebbd0 : ffffcc0f`e3fec598 00000000`00000000 ffffcc0f`e3fec501 fffff803`0f4e8007 : ndis!Ndis::BindEngine::DispatchPendingWork+0x76
ffffcb0d`c8ee7190 fffff803`0f3f448c : ffffcc0f`e3feb1a0 ffffcc0f`d9aaa010 ffffcc0f`d9aaa010 ffffcc0f`d9aaa010 : ndis!Ndis::BindEngine::ApplyBindChanges+0x54
ffffcb0d`c8ee71e0 fffff803`0f3f40dd : 00000000`00000000 ffffcc0f`e3feb1a0 fffff803`0f4b1568 ffffcc0f`e3feb1a0 : ndis!ndisPrepForLowPowerCommon+0xa4
ffffcb0d`c8ee72d0 fffff803`0f41e5df : ffffcc0f`df2c9960 ffffcc0f`d9aaa010 ffffcc0f`e3feb1a0 ffffcc0f`e3feb1a0 : ndis!ndisPrepForLowPower+0x1d
ffffcb0d`c8ee7320 fffff803`0f3f4b41 : 00000000`00000000 ffffcc0f`e3feb1a0 ffffcc0f`d9aaa680 ffffcc0f`d9aaa680 : ndis!ndisSetDevicePower+0x29627
ffffcb0d`c8ee7390 fffff803`0f3f68ce : ffffcc0f`d9aaa010 ffffcc0f`de8aed80 ffffcc0f`d9aaa680 ffffcc0f`e3feb1a0 : ndis!ndisSetPower+0x91
ffffcb0d`c8ee73f0 fffff803`0cdac2b7 : ffffcc0f`d86ef040 ffffcb0d`c8ee74d0 00000000`00000000 ffffcc0f`e3feb050 : ndis!ndisPowerDispatch+0x11e
ffffcb0d`c8ee7450 fffff803`0cd304b5 : ffffffff`fa0a1f00 fffff803`0cdac0b0 ffffcc0f`db2fa2b0 00000000`00000713 : nt!PopIrpWorker+0x207
ffffcb0d`c8ee74f0 fffff803`0ce1be24 : ffffe201`525c0180 ffffcc0f`d86ef040 fffff803`0cd30460 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffcb0d`c8ee7540 00000000`00000000 : ffffcb0d`c8ee8000 ffffcb0d`c8ee1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

STACK_COMMAND: .thread 0xffffcc0fd86ef040 ; kb
SYMBOL_NAME: mslldp!lldpWaitForValueToZero+36
MODULE_NAME: mslldp
IMAGE_NAME: mslldp.sys
BUCKET_ID_FUNC_OFFSET: 36
FAILURE_BUCKET_ID: 0x9F_3_mslldp!lldpWaitForValueToZero
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9791d8f1-a521-a4cc-0211-2a4b606bb3b5}
Followup: MachineOwner

*******************************************************************************

Thank you.

Was this reply helpful? Yes No

‎09-14-2022 09:02 PM - edited ‎09-14-2022 09:27 PM

HP Recommended
@ArserHsieh wrote:

Hi Ub6424,

Stability testing for six hours without a crash.

Sounds good.

 

@ArserHsieh wrote:

Hi Ub6424,

 

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: ffffcc0fde8aed80, Physical Device Object of the stack
Arg3: fffff8030846a0d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

...

Thank you.

You're welcome !

 

(1) What stability testing software do you use ? Url please.

(2) Please get a <replacement charger> and compare.

 

Good luck

Was this reply helpful? Yes No

‎09-14-2022 09:12 PM

HP Recommended

Hi Ub6424,

(1) What stability testing software do you use ? Url please.

AIDA64 Extreme 

 

(2) Please get a <replacement charger> and compare.

I always use the same 100W adapter and the crash happens when upgrading to Windows 11 for shutdown.
I mentioned in the first post that I had to do a second shutdown to actually shutdown, which I think has something to do with the power management drivers.

 

Thank you.

Was this reply helpful? Yes No

‎09-14-2022 09:34 PM

HP Recommended
@ArserHsieh wrote:

Hi Ub6424,

I always use the same 100W adapter and the crash happens when upgrading to Windows 11 for shutdown.
I mentioned in the first post that I had to do a second shutdown to actually shutdown, which I think has something to do with the power management drivers.

Thank you.

Hello @ArserHsieh 

 

If the problem never occurred in Windows 10, it is definitely a software/driver bug in Windows 11. Maybe a future update will fix the problem. I hereby close the case and wish you all the best.

 

Nice to have written with you.

Kind regards

Was this reply helpful? Yes No

‎09-15-2022 08:13 PM

HP Recommended

Hi Ub6424,

I found the root cause, which is the Type-C Hub 1PM64AA, when it is connected to my laptop, it causes the system shutdown process to not complete at one time.

 

In the crash dump on Sep 13, it shows that mslldp.sys is the cause, and I have found the same problem in other discussions:
DRIVER POWER STATE FAILURE 


But in the HP official website, the 1PM64AA driver still have not supported the Windows 11 (21H2), hope HP can release the new driver ASAP to support the Windows 11(21H2).

 

Thank you.

Was this reply helpful? Yes No

‎09-15-2022 08:45 PM

HP Recommended
@ArserHsieh wrote:

Thank you.

Good luck

Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.