Question HP Omen 25L shutting down at high load ?

[GabeTC]

So I have this prebuilt HP Omen 25L that seems to shut down for no apparent reason at high load on demanding games or OCCT.

• I have checked the temps and everything is within reason
• tried a new higher wattage PSU,
• tried underclocking the GPU,
• tried a single stick of ram,
• tried reseating all the components,
• tried to recover the bios,
• tried limiting the GPU power to 50%

Im at a complete loss on this one, sometimes it just locks up sometimes the screen goes black and all the RGBs freeze and sometimes it just shuts down, whenever it does any of that it won’t turn back on for at least 10-15 minutes if I try plugging it back in sooner the keyboard lights up but it will not even try to boot nothing spins up no beeps nothing.

Nothing happens if it’s not under heavy load it will run for days totally fine until heavy load happens.

I do have a dump log from windows but I can’t make sense of that if I should upload that somewhere let me know!

the specs for this one are
AMD Ryzen 7 5700G
HyperX 16GB Memory
NVIDIA GeForce RTX 3060 Ti
512GB SSD + 1TB HDD

 

[Phillip Corcoran]

• "tried a new higher wattage PSU "

Please post make & model.

 

[GabeTC]

• "tried a new higher wattage PSU "

Please post make & model.

It’s a thermaltake smart 700w, was the only one I found locally my locally bestbuy was stripped clean of PSUs

 

[GabeTC]

I found this in the dump logs does it point to anything?


13: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

WIN32K_POWER_WATCHDOG_TIMEOUT (19c)
Win32k did not turn the monitor on in a timely manner.
Arguments:
Arg1: 0000000000000050, Calling monitor driver to power on.
Arg2: ffffd007dfde5080, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 983

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 13972

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

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

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

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x19c

Key : Bugcheck.Code.Register
Value: 0x19c

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


ORIGINAL_CAB_PATH: C:\Users\jillc\Downloads\GABES-PC-2023-01-12_23-02-15.zip

FILE_IN_CAB: autorun.txt

FILE_IN_CAB: cpu.txt

FILE_IN_CAB: disks.txt

FILE_IN_CAB: driver-table.txt

FILE_IN_CAB: driver-versions.txt

FILE_IN_CAB: dxdiag.txt

FILE_IN_CAB: genuine.txt

FILE_IN_CAB: gpu.txt

FILE_IN_CAB: hashes.txt

FILE_IN_CAB: hosts.txt

FILE_IN_CAB: installed-software.txt

FILE_IN_CAB: motherboard.txt

FILE_IN_CAB: msinfo32.nfo

FILE_IN_CAB: network-info.txt

FILE_IN_CAB: os-details.txt

FILE_IN_CAB: partitions.txt

FILE_IN_CAB: pnp-devices.txt

FILE_IN_CAB: processes.txt

FILE_IN_CAB: ram.txt

FILE_IN_CAB: restore-points.txt

FILE_IN_CAB: services.txt

FILE_IN_CAB: transcript-elevated.txt

FILE_IN_CAB: transcript-main.txt

FILE_IN_CAB: windows-updates.txt

FILE_IN_CAB: Crash Dumps/011123-8703-01.dmp

FILE_IN_CAB: Crash Dumps/011123-9000-01.dmp

FILE_IN_CAB: Crash Dumps/crash-dump-settings.txt

FILE_IN_CAB: Crash Dumps/driver-verifier.txt

FILE_IN_CAB: Crash Dumps/live-kernel-reports.txt

FILE_IN_CAB: Crash Dumps/memory-dumps.txt

FILE_IN_CAB: Crash Dumps/mini-crash-dumps.txt

FILE_IN_CAB: Error Reports/AppCrash_GPU3DDX11.exe_2854416e10184c86cc5fd4a6405bb276a17_cd558828_cae30217-34de-4a6a-ab4f-3027474d9d7e/Report.wer

FILE_IN_CAB: Error Reports/Critical_10.0.22000.1_8b5f3f6f3f135664fc2d5eec8c2ea20b55d17_00000000_1afbd7e7-14d7-45fc-be50-a96ffe1ba260/Report.wer

FILE_IN_CAB: Error Reports/Kernel_141_b33a6bfed86a883d7995bbe50d567544f61a40_00000000_cab_10a522c7-f7bc-408c-95ba-fc68207e099b/Report.wer

FILE_IN_CAB: Error Reports/NonCritical_4097_2b3053ed4a5e33daf10e57493f1bd51157760_00000000_4bed4f5a-67c2-41d9-9338-82abdb411978/Report.wer

FILE_IN_CAB: Error Reports/NonCritical_Reset_f8aeeebc83c474686ee1fe9b4b503babf4abc7_00000000_9fca1c77-1db5-4954-8f90-6a23978862d5/Report.wer

FILE_IN_CAB: Event Logs/application-events.txt

FILE_IN_CAB: Event Logs/pnp-events.txt

FILE_IN_CAB: Event Logs/system-events.txt

FILE_IN_CAB: Power Reports/power-plan.txt

FILE_IN_CAB: Power Reports/power-report.html

FILE_IN_CAB: Power Reports/sleep-states.txt

BUGCHECK_CODE: 19c

BUGCHECK_P1: 50

BUGCHECK_P2: ffffd007dfde5080

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

FAULTING_THREAD: ffffd007dfde5080

STACK_TEXT:
ffffb58ac4d9d640 fffff801388702b7 : ffffe10100000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSwapContext+0x76
ffffb58ac4d9d780 fffff80138872169 : ffffd00700000001 fffff8010000000f 0000000000000000 0000002d00000000 : nt!KiSwapThread+0x3a7
ffffb58ac4d9d860 fffff80138875e26 : 0000000000000000 0000000000000000 000000000000005b 0000000106310b1e : nt!KiCommitThreadWait+0x159
ffffb58ac4d9d900 fffff8015aa12d19 : 00000000987bfe00 0000000000000000 ffffb58ac4d9db00 0000000000000002 : nt!KeDelayExecutionThread+0x416
ffffb58ac4d9d990 00000000987bfe00 : 0000000000000000 ffffb58ac4d9db00 0000000000000002 0000000000000000 : nvlddmkm+0x8f2d19
ffffb58ac4d9d998 0000000000000000 : ffffb58ac4d9db00 0000000000000002 0000000000000000 0000000000000000 : 0x987bfe00


SYMBOL_NAME: nvlddmkm+8f2d19

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffd007d138c0c0; .thread 0xffffd007dfde5080 ; kb

BUCKET_ID_FUNC_OFFSET: 8f2d19

FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_nvlddmkm!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {830d81bf-fada-74e3-80d9-75aa3363ba13}

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

 

[drivinfast247]

Try using DDU to remove the GPU drivers. Then install the latest version.

 

[GabeTC]

Try using DDU to remove the GPU drivers. Then install the latest version.

Well the good news is I was actually in the process of doing that! Bad news is it froze during a bios update that I guess windows pushed?? Now it won’t turn back on keyboard lights up but nothing happens

 

[ohio_buckeye]

Froze? When did it freeze? Did it freeze within windows or while on the loading screen? You are NEVER supposed to interrupt a system during a bios update or you can brick the motherboard. I’m guessing the stock hp board doesn’t have a bios flashback feature.

If the system turned off you may unplug it for a few minutes and try again. If you still have the same symptoms, you may open the case and remove the cmos battery for 20 minutes or so. Unplug the pc again and press the power button a few times to discharge any static.

If a bios update did brick the board and if you don’t have any warranty left, about the only thing to do would be if you’ve got a microcenter nearby, head that way and pick up a new case(sometimes cases can be proprietary), and pick up a new motherboard, and basically pull the components and rebuild.

 

[GabeTC]

Froze? When did it freeze? Did it freeze within windows or while on the loading screen? You are NEVER supposed to interrupt a system during a bios update or you can brick the motherboard. I’m guessing the stock hp board doesn’t have a bios flashback feature.

If the system turned off you may unplug it for a few minutes and try again. If you still have the same symptoms, you may open the case and remove the cmos battery for 20 minutes or so. Unplug the pc again and press the power button a few times to discharge any static.

If a bios update did brick the board and if you don’t have any warranty left, about the only thing to do would be if you’ve got a microcenter nearby, head that way and pick up a new case(sometimes cases can be proprietary), and pick up a new motherboard, and basically pull the components and rebuild.

Yeah the update froze and just stuck half way through I left it for like an hour no progress. But apparently it’s still under warranty so I’ve gone ahead and sent to to HP! Hopefully they explain what was wrong I’m really interested

 

[ohio_buckeye]

Yeah if it froze during the bios update most likely the board got bricked. Sometimes the Microsoft driver updates aren’t great or may be the wrong update. Most of the time they are fine but occasionally they mess things up. If they fix it you may look up how to disable driver updates through Windows update and update drivers manually as needed.