Hp omen keeps crashing (blue screen of death)

[JosehSutcliffe]

Hp omen keeps crashing, blue screen (sometimes)

I've ran a handwear check and got nothing

My dump files are also showing me nothing 

Here is everything from WinDbg, please help 🙁

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

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

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

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

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

Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\020125-15062-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 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff803`a5400000 PsLoadedModuleList = 0xfffff803`a62f4870
Debug session time: Sat Feb  1 17:22:13.559 2025 (UTC + 1:00)
System Uptime: 0 days 0:05:53.532
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols

Loading unloaded module list
...................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff803`a58b85d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa801`9283c200=????????????????
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000500, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff803a63c33a0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4578

    Key  : Analysis.Elapsed.mSec
    Value: 11591

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 31808

    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: 0x133_DPC_nt!KiIdleLoop

    Key  : Failure.Hash
    Value: {aa2c7b44-71a3-1405-6cf6-f2b87b7cc565}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7497cf94

    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: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 24a10ef

    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:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 500

BUGCHECK_P3: 500

BUGCHECK_P4: fffff803a63c33a0

FILE_IN_CAB:  020125-15062-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x31808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffba0dfa580040

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff889`64e45c40 00000000`00000000     : fffff889`64e46000 fffff889`64e40000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KiIdleLoop+9e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.2894

STACK_COMMAND:  .process /r /p 0xfffff803a63cdf80; .thread 0xffffba0dfa580040 ; kb

BUCKET_ID_FUNC_OFFSET:  9e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KiIdleLoop

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {aa2c7b44-71a3-1405-6cf6-f2b87b7cc565}

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

[adn0x0]

I have the same issue, does it say "Video Dxg Krnl fatal error " when you blue screen?

[Max3Aj]

Hi @JosehSutcliffe, Welcome to HP Support Community. 

Thank you for posting your query, I will be glad to help you. 

Since your HP Omen keeps crashing, sometimes with a blue screen (BSOD), and hardware checks/dump files aren't revealing anything, let's go through a systematic approach:

1. Check Event Viewer for Clues

• Open Event Viewer (Win + X → Event Viewer).
• Navigate to Windows Logs > System.
• Look for Critical Errors or Kernel-Power / BugCheck events around the time of crashes.

2. Run a Memory Test

Even if hardware checks didn’t show errors:

• Open Windows Memory Diagnostic (Win + R, type mdsched.exe, press Enter).
• Choose Restart now and check for problems.
• If errors appear, your RAM may be faulty.

3. Check CPU & GPU Temperatures

• Your HP Omen has had overheating issues before.
• Use HWMonitor or Core Temp to check real-time temperatures.
• If CPU or GPU exceeds 90°C, it might cause instability.
• Solution: Reapply thermal paste, clean vents, or undervolt.

4. Disable Overclocking

• If XMP (RAM overclock), GPU OC, or Undervolt is active, return to stock settings in BIOS.

5. Update / Rollback Drivers

• GPU Driver (NVIDIA/AMD): Try both the latest & previous stable version.
• Chipset & Storage Drivers (from HP’s website).
• BIOS Update: Check HP’s site for the latest version.
  
  6. Check for Windows Corruption

Run the following in Command Prompt (Admin):

sfc /scannow 
DISM /Online /Cleanup-Image /RestoreHealth 
chkdsk /f /r
 

Restart your laptop after running these commands.

7. Analyze BSOD Codes Manually

Since dump files aren’t showing anything, try BlueScreenView or WinDbg:

• Download BlueScreenView and check for the STOP code.
• Common codes:
  • WHEA_UNCORRECTABLE_ERROR → Hardware failure (CPU/GPU overheating, PSU issues).
  • IRQL_NOT_LESS_OR_EQUAL → Bad drivers or RAM issues.
  • MEMORY_MANAGEMENT → RAM failure or pagefile corruption.

I hope this helps. 

Take care and have a good day. 

Please click “Accepted Solution” if you feel my post solved your issue, it will help others find the solution. Click the “Kudos/Thumbs Up" on the bottom right to say “Thanks” for helping! 

Max3Aj

HP Support 

[Max3Aj]

Hi @adn0x0, Welcome to the HP Support Community!

Thanks for reaching out! 

If you're seeing "Video Dxg Krnl Fatal Error" on your HP Omen, it’s a DirectX Graphics Kernel failure, usually caused by GPU driver issues, overheating, or hardware faults. Here’s how to fix it:

Update or Rollback GPU Drivers

NVIDIA/AMD Users:

1. Download DDU (Display Driver Uninstaller) and run it in Safe Mode.
2. Uninstall the GPU driver completely.
3. Download & install the latest stable driver from:
   • NVIDIA: https://www.nvidia.com/download/index.aspx
   • AMD: https://www.amd.com/en/support
4. If the latest driver still causes crashes, try an older version.

Check for Overheating Issues

• Open HWMonitor or MSI Afterburner to check GPU & CPU temperatures.
• If your GPU is overheating (>85°C):
  • Clean the vents & fans (use compressed air).
  • Reapply thermal paste (if possible).
  • Use a cooling pad.
  • Undervolt the GPU using MSI Afterburner.

Disable Fast Startup & Hardware-Accelerated GPU Scheduling

Disable Fast Startup:

1. Open Control Panel → Power Options → Choose what the power buttons do.
2. Click Change settings that are currently unavailable.
3. Uncheck "Turn on fast startup".
4. Save & restart.

Disable Hardware-Accelerated GPU Scheduling (HAGS) (Windows 10/11)

1. Win + I → System → Display → Graphics settings.
2. Toggle Hardware-accelerated GPU scheduling OFF.
3. Restart your laptop.

Run DirectX & System File Checks

Run the following in Command Prompt (Admin):

bash

sfc /scannow 
DISM /Online /Cleanup-Image /RestoreHealth 
chkdsk /f /r

Then, check DirectX:

• Press Win + R, type dxdiag, and hit Enter.
• Under Display, check for errors.

Update BIOS & Windows

• BIOS Update: Go to HP’s support page and check for BIOS updates.
• Windows Update:
  • Go to Settings → Windows Update → Install the latest updates.

Test with a Fresh Windows Installation

• If crashes persist, back up your data and perform a clean install of Windows.
• Before installing drivers, test stability using Windows' default GPU driver. 

Take care, and have an amazing day!

Did we resolve the issue? If yes, Please consider marking this post as "Accepted Solution" and click "Kudos/Thumbs Up" to give us a helpful vote - your feedback keeps us going!

Regards,

Max3Aj

[adn0x0]

I have tried all these things several times over the course of over a year.  I have also tried testing in Linux.  I think it is somewhat temperature related but not fully termperature dependent

[Max3Aj]

Hi @adn0x0, Thank you for your response. 

Since you've already tried all the common troubleshooting steps, including testing in Linux (which suggests it may be hardware-related), here are some advanced troubleshooting steps:

Perform a GPU Stress Test & Log Errors

• Use OCCT or FurMark to stress-test the GPU.
• Monitor temperatures, power usage, and error logs in Event Viewer (Windows Logs > System > Critical Errors).
• If the system crashes under stress, it could be a power delivery issue or GPU failure.

Check for VRAM or GPU Memory Errors

• Use MemtestCL or OCCT VRAM test to scan for VRAM corruption.
• If errors appear, your GPU's VRAM may be faulty.

Check HP Omen BIOS/EC Firmware Settings

• Some Omen laptops have Overboost or Adaptive Boost enabled in BIOS.
• Enter BIOS (F10 at boot) > Advanced > Disable Overclocking / Performance Mode.
• Update Embedded Controller (EC) Firmware (if available).

Check for Failing Power Delivery (PSU/Motherboard Issue)

• Try running on battery only (without the charger). If stable, the power brick or motherboard power regulation could be the problem.
• If your charger is underpowered or faulty, it might be causing system instability under GPU load.

[Max3Aj]

Run GPU in a Lower Power State (Force PCIe Gen 3)

• Reduce GPU power limit in MSI Afterburner (e.g., -20%).
• Force PCIe Gen 3 mode in NVIDIA Control Panel (if running PCIe Gen 4).
  • Run nvidia-smi -pm 1 in CMD (admin mode) to enable persistent power management mode.

Test with External Display (Bypass Internal Display Driver)

• If the crash occurs only on the laptop screen but not on an external monitor, the internal display panel, ribbon cable, or eDP controller might be faulty.

If Persistent in Windows & Linux: Possible GPU Failure

Since it’s happening across multiple OS environments, it’s likely a hardware failure in the GPU (BGA solder issue or VRAM corruption). If your laptop is under warranty, consider an RMA or GPU reballing service.

Final Step: Consider Disabling Discrete GPU

If your system has an Intel iGPU + NVIDIA dGPU, try disabling the dGPU entirely in BIOS or Device Manager to check if stability improves.

I hope this helps!

If my response resolves your issue, please click “Accepted Solution” to help others find the answer. Also, don’t forget to click the “Kudos/Thumbs Up” button to say thanks!

Take care and have a great day.

Max3Aj

HP Support