• ×
    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.
HP Recommended
OMEN by HP 45L Gaming Desktop PC GT22-1000a (6M9S5AV)

Good day to you all,

 

So I bought this desktop about 6 months ago. It has performed quite well, but since the past few weeks, it has been crashing quite regularly.

 

Crashes seem to be random though they seem to happen most often while gaming.  The crashes never happen at any consistent point either, as it will sometimes crash when sitting idle in a main menu, or in the middle of a game. There is no lead-up, or anything indicating something wrong. The pc will just suddenly crash to a black screen while the fans suddenly ramp up to full speed and immediately reboot.

 

Reliability monitor shows: Bugcheck is 0x00000113 (0x0000000000000019, 0x0000000000000001, 0x00000000000010de, 0x0000000000002684).

 

Debugging the minidump in WinDBG comes up with the following:

 

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the BugCheck:
Arg2: 0000000000000001
Arg3: 00000000000010de
Arg4: 0000000000002684

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1015

    Key  : Analysis.Elapsed.mSec
    Value: 1795

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x113

    Key  : Bugcheck.Code.TargetModel
    Value: 0x113

    Key  : DirectX.FatalError.Code
    Value: 19

    Key  : DirectX.FatalError.Desc
    Value: UNEXPECTED_DEFERRED_DESTRUCTION

    Key  : Failure.Bucket
    Value: 0x113_19_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f}

    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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  113

BUGCHECK_P1: 19

BUGCHECK_P2: 1

BUGCHECK_P3: 10de

BUGCHECK_P4: 2684

FILE_IN_CAB:  052124-10953-01.dmp

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


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffcc0e`94386ba8 fffff801`aa085685     : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx
ffffcc0e`94386bb0 fffff801`a9f8902c     : ffffe00b`0a292100 ffffe00b`045feb70 ffffe00b`045feb78 ffffe00b`045feb80 : watchdog!WdLogSingleEntry5+0x3b45
ffffcc0e`94386c60 fffff801`a9e02e14     : ffffcc0e`00000000 ffffe00b`0a292117 ffffe00b`0a292030 00000000`00000000 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x15c
ffffcc0e`94386cb0 fffff801`a9dbd889     : ffffe00b`0a292030 ffffe00a`f90179b0 ffffe00b`0fc77000 ffffa68c`225062e0 : dxgkrnl!DpiFdoDispatchPnp+0xd4
ffffcc0e`94386d50 fffff801`c3002df8     : ffffe00b`06422000 ffffcc0e`94386ed9 ffffe00b`06422000 fffff780`00000294 : dxgkrnl!DpiDispatchPnp+0xe9
ffffcc0e`94386e70 ffffe00b`06422000     : ffffcc0e`94386ed9 ffffe00b`06422000 fffff780`00000294 fffff801`c3002cae : nvlddmkm+0x10f2df8
ffffcc0e`94386e78 ffffcc0e`94386ed9     : ffffe00b`06422000 fffff780`00000294 fffff801`c3002cae ffffe00b`06422000 : 0xffffe00b`06422000
ffffcc0e`94386e80 ffffe00b`06422000     : fffff780`00000294 fffff801`c3002cae ffffe00b`06422000 00000000`00000000 : 0xffffcc0e`94386ed9
ffffcc0e`94386e88 fffff780`00000294     : fffff801`c3002cae ffffe00b`06422000 00000000`00000000 00000000`00000000 : 0xffffe00b`06422000
ffffcc0e`94386e90 fffff801`c3002cae     : ffffe00b`06422000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff780`00000294
ffffcc0e`94386e98 ffffe00b`06422000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x10f2cae
ffffcc0e`94386ea0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe00b`06422000


SYMBOL_NAME:  nvlddmkm+10f2df8

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10f2df8

FAILURE_BUCKET_ID:  0x113_19_nvlddmkm!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fb504da1-90a7-64ec-e7aa-d0c04338976f}

 

I've tried :

- Disabling fast boot

- Disabling automatic reboot so I could see if it gave me an onscreen error message (It didn't)

- Updating the NVIDIA graphics driver

- Rolling back the graphics driver (to see if it was a stability issue, but it wasn't)

- Clean reinstallation of the graphics driver

- Updated drivers and firmware

- Checking for updates

Running hardware diagnostics

 

Not getting anything.

HP refers automatically to virtual assistant and, of course, these forums, where I've seen people post similar problems, though I haven't found any definitive solutions. Contacting HP is something I have yet to do personally as their messenger and phone times rarely overlap with my free time.

 

As someone else pointed out here already, resetting to factory default won't help me much seeing as the problem will more than likely arise again when I start getting drivers back up to date again.

 

I really would like to know where to go from here.

 

Thanks in advance.

UPDATE 03/06/2024:
I have once again tried to do a clean reinstall of the drivers using DDU and running dxdiag to see if anything was wrong, but nothing. Same crashes still kept taking place.
I decided to reset the PC, but the same crash happened again. I have no idea what else to try.

6 REPLIES 6
HP Recommended

I've had the same issue with my Omen 30L and an Nvidia 3080.

 

I've tried everything.  What I SHOULD have done was RMA the card while I still had a chance.  I believe it's bad hardware and even though my PC is now only 2ish years old, I've been battling this issue ever since I got it so it's really my fault.

 

Pretty certain I'm completely screwed as there's no warranty in place anymore.

HP Recommended

My Son's OMEN 30L has just started having this issue, it has a GeForce RTX 3060 Ti card and is running driver version 560.94 (installed today to try and fix problem).

The PC is still under extended Warranty and I spent a month earlier this year getting a different problem resolved (BSOD on some Games)  with the PC going back to HP 3 times before it was fixed.

The first time they replaced the Graphics Card, so not that old now.  The second time they replaced the NVMe drive and they finally fixed it by replacing the CPU (which they were reluctant to do and I had to insist).

If this is another Hardware issue I could have a battle on my hands even though the warranty is still valid.

HP Recommended

That's crazy you've had so much hardware replaced but thankfully you're still under warranty.

 

Start the process now so you're not holding the bag like I was.  I ended up buying a new card and voila...  no issues since.

 

I replaced my 3080 with a 4070 Super that I caught on a really good sale.

HP Recommended

I managed t o get away from the problem by doing an overwrite install and updating the GeForce drivers, I also removed a WIndows patch and suspended Windows update for a couple of weeks.

 

All good until today (Windows updates haven't started again yet).

 

Now I have purple dashes over the top 2/3rds of the screen, my second display is no longer detected and and I'm on a basic Microsoft driver as the NVIDIA driver has reported an error code 43.

 

Guess I'll be talking to HP again tomorrow.

HP Recommended

I have the same pc and same issue. I have a RTX 4090 and Ryzen 9 79503xd. I have no warranty, please help me guys.

HP Recommended

Are you within the extended warranty period your credit card may allow?  (1 yr warranty and CC extends it a year?)

 

If not, you'll likely need to buy a new card if none of the other options solve the problem.

† 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>.