Just bought HP 255 G10 laptop. Have had 3 Blue screen of death with immediate restarts in 5 days

[Amandoee]

Hi everyone. I just bought a new laptop, and have been using it to prepare for exams. Unfortunately i have experienced 3 BSODs in 5 days! Windows was installed during the setup of the laptop, and is also freshly installed. I can find no pattern in when the BSOD occur. My pc Specs are:

Device name    Andreas
Processor    AMD Ryzen 7 7730U with Radeon Graphics            2.00 GHz
Installed RAM    16,0 GB (15,3 GB usable)

Product ID    00355-60986-24059-AAOEM
System type    64-bit operating system, x64-based processor
Pen and touch    Pen support

 

The laptop is a HP 255 G10 Notebook.

I have narrowed it down to being because of USBHUB3.sys, but don't know how to prevent the BSOD from occurring. BSOD does not occur when plugging/Unplugging anything. I have pasted one of the dump logs below. Does anyone know how to fix this? Thanks in advance!

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.250 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Microsoft ® Windows Debugger Version 10.0.27553.1004 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051624-9687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`80a00000 PsLoadedModuleList = 0xfffff807`81613130
Debug session time: Thu May 16 00:26:29.842 2024 (UTC + 2:00)
System Uptime: 0 days 1:51:19.155
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................
Loading User Symbols

Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`80e17f80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcf04`366a7770=000000000000009f
5: 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: ffff800afda0c3c0, Physical Device Object of the stack
Arg3: ffffcf04366a77b8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff800af79aa010, The blocked IRP

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2921

Key : Analysis.Elapsed.mSec
Value: 4152

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key : Bugcheck.Code.TargetModel
Value: 0x9f

Key : Dump.Attributes.AsUlong
Value: 1808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x9F_3_POWER_DOWN_IMAGE_UsbHub3.sys

Key : Failure.Hash
Value: {251ecfe1-9403-56c9-c851-7a19f7915a32}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7


BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff800afda0c3c0

BUGCHECK_P3: ffffcf04366a77b8

BUGCHECK_P4: ffff800af79aa010

FILE_IN_CAB: 051624-9687-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffff800af4faad50

IMAGE_NAME: UsbHub3.sys

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff807bd0f0000 UsbHub3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffcf04`366a7768 fffff807`80f81526 : 00000000`0000009f 00000000`00000003 ffff800a`fda0c3c0 ffffcf04`366a77b8 : nt!KeBugCheckEx
ffffcf04`366a7770 fffff807`80f813fc : 00000000`00000002 ffffd280`a45d1180 ffff800a`f39e8308 ffffcf04`366a78e9 : nt!PopIrpWatchdogBugcheck+0x122
ffffcf04`366a77f0 fffff807`80ce5f7b : ffff800a`00000002 00000000`00000001 ffffcf04`00000000 00000000`00000002 : nt!PopIrpWatchdog+0xc
ffffcf04`366a7820 fffff807`80c410b4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff807`7cd5bb28 : nt!KiProcessExpiredTimerList+0x1eb
ffffcf04`366a7950 fffff807`80e1cf8e : 00000000`00000000 ffffd280`a45d1180 ffff800a`edd78040 ffff800a`f7c25080 : nt!KiRetireDpcList+0xaf4
ffffcf04`366a7c00 00000000`00000000 : ffffcf04`366a8000 ffffcf04`366a1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION: 10.0.22621.3640

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_IMAGE_UsbHub3.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {251ecfe1-9403-56c9-c851-7a19f7915a32}

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

5: kd> lmvm UsbHub3
Browse full module list
start end module name
fffff807`bd0f0000 fffff807`bd19f000 UsbHub3 # (pdb symbols) C:\ProgramData\Dbg\sym\usbhub3.pdb\F6F22005E1664A1F7CEAF87C0D7FBC3E1\usbhub3.pdb
Loaded symbol image file: UsbHub3.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\UsbHub3.sys\4A6450FEaf000\UsbHub3.sys
Image path: UsbHub3.sys
Image name: UsbHub3.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 4A6450FE (This is a reproducible build file hash, not a timestamp)
CheckSum: 000B3296
ImageSize: 000AF000
File version: 10.0.22621.3640
Product version: 10.0.22621.3640
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usbhub3.sys
OriginalFilename: usbhub3.sys
ProductVersion: 10.0.22621.3640
FileVersion: 10.0.22621.3640 (WinBuild.160101.0800)
FileDescription: USB3 HUB Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.