-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Gaming
- Gaming Desktops
- My PC keeps on rebooting while gaming

Create an account on the HP Community to personalize your profile and ask a question
08-11-2024 05:49 AM
My computer has been rebooting from a bugchecks for maybe 2 years on and off but now it is worse than ever.
I have tried a lot of things but can't seem to find the issue and fix it myself.
The error that I keep on getting in the Event Viewers is this:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000113 (0x0000000000000019, 0x0000000000000001, 0x00000000000010de, 0x0000000000002216).
I have also added the DMP-file information from the latest crash here bellow.
Hope that someone can help me understand what the issue might be and how it can be solved.
thanks!
************* 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.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.157 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42 Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Primary dump contents written successfully ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Kernel base = 0xfffff804`4f800000 PsLoadedModuleList = 0xfffff804`504134f0 Debug session time: Sun Aug 11 13:26:59.067 2024 (UTC + 2:00) System Uptime: 0 days 0:04:40.752 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................ Loading User Symbols Loading unloaded module list ........ For analysis of this file, run !analyze -vnt!KeBugCheckEx: fffff804`4fc15820 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb85`d09e81d0=0000000000000113 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000002216 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1311 Key : Analysis.Elapsed.mSec Value: 2126 Key : Analysis.IO.Other.Mb Value: 7 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 33 Key : Analysis.Init.CPU.mSec Value: 186 Key : Analysis.Init.Elapsed.mSec Value: 430650 Key : Analysis.Memory.CommitPeak.Mb Value: 109 Key : Bugcheck.Code.KiBugCheckData Value: 0x113 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 : Dump.Attributes.AsUlong Value: 1800 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.LastLine Value: Dumping physical memory to disk: 100% Key : Dump.Attributes.ProgressPercentage Value: 100 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 : SecureKernel.HalpHvciEnabled Value: 1 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: 2216 FILE_IN_CAB: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1800 FAULTING_THREAD: ffff9b88c7cdc040 PROCESS_NAME: System STACK_TEXT: fffffb85`d09e81c8 fffff804`59455745 : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx fffffb85`d09e81d0 fffff804`5935794c : ffff9b88`cea9d100 ffff9b88`cb482590 ffff9b88`cb482598 ffff9b88`cb4825a0 : watchdog!WdLogSingleEntry5+0x3c05 fffffb85`d09e8280 fffff804`591dae14 : fffffb85`d09e8300 ffff9b88`cea9d117 ffff9b88`cea9d030 00000000`00000000 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x15c fffffb85`d09e82d0 fffff804`591911c9 : ffff9b88`cea9d030 ffff9b88`eba2b010 ffff9b88`ddcf0000 00000000`00000000 : dxgkrnl!DpiFdoDispatchPnp+0xd4 fffffb85`d09e8370 fffff804`79f2848e : 00000000`00000000 fffffb85`069f0000 ffff9b88`cebd0000 fffff780`00000000 : dxgkrnl!DpiDispatchPnp+0xe9 fffffb85`d09e8490 fffff804`4fb12665 : ffff9b88`cea9d030 fffffb85`d09e8601 00000000`00000017 ffff9b88`cebd0000 : nvlddmkm+0x151848e fffffb85`d09e85b0 fffff804`4fe9dde0 : ffff9b88`cea9d030 00000000`00000000 fffffb85`d09e86a0 ffff9b88`eba2b010 : nt!IofCallDriver+0x55 fffffb85`d09e85f0 fffff804`50066590 : 00000000`00000017 ffff9b88`c98f0120 ffff9b88`c9ce74a0 ffff9b88`c98f0120 : nt!IopSynchronousCall+0xf8 fffffb85`d09e8660 fffff804`5007d548 : ffffb002`cf967890 00000000`00000000 00000000`00000310 00000000`0000030a : nt!IopRemoveDevice+0x108 fffffb85`d09e8710 fffff804`50062c7c : ffff9b88`c9ce74a0 00000000`00000000 00000000`00000000 fffff804`50062bbb : nt!PnpSurpriseRemoveLockedDeviceNode+0xc4 fffffb85`d09e8770 fffff804`500629c3 : ffff9b88`c9ce74a0 fffffb85`d09e87f0 ffff9b88`c98f0120 00000000`00000004 : nt!PnpDeleteLockedDeviceNode+0x8c fffffb85`d09e87b0 fffff804`50061e0e : ffff9b88`c98f0120 00000002`00000002 00000000`00000000 00000000`00000003 : nt!PnpDeleteLockedDeviceNodes+0xd3 fffffb85`d09e8830 fffff804`4fe81dad : fffffb85`d09e8970 ffff9b88`c9ce7400 ffff9b88`e5279000 ffffb002`00000002 : nt!PnpProcessQueryRemoveAndEject+0x1ce fffffb85`d09e8910 fffff804`4fe894fa : ffffb002`cf967890 ffffb002`cf732010 ffff9b88`c4ae0c00 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x109 fffffb85`d09e8940 fffff804`4fb52325 : ffff9b88`c4ae0cb0 ffff9b88`c7cdc040 fffffb85`d09e8ac0 ffff9b88`00000000 : nt!PnpDeviceEventWorker+0x2ca fffffb85`d09e89c0 fffff804`4fb54d17 : ffff9b88`c7cdc040 00000000`00000130 ffff9b88`c7cdc040 fffff804`4fb521d0 : nt!ExpWorkerThread+0x155 fffffb85`d09e8bb0 fffff804`4fc1a994 : ffff8380`80f97180 ffff9b88`c7cdc040 fffff804`4fb54cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x57 fffffb85`d09e8c00 00000000`00000000 : fffffb85`d09e9000 fffffb85`d09e2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nvlddmkm+151848e MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffff9b88c4aff040; .thread 0xffff9b88c7cdc040 ; kb BUCKET_ID_FUNC_OFFSET: 151848e 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} Followup: MachineOwner ---------
08-13-2024 12:15 PM
Hi @berggrenmarcus,
Welcome to HP Support Community.
Thank you for posting your query, I will be glad to help you.
The bugcheck error code 0x00000113 indicates a DPC_WATCHDOG_VIOLATION, which typically points to issues with system drivers or hardware. The 0x19 parameter suggests a BAD_POOL_HEADER error, which could indicate memory corruption or issues with device drivers.
Here's a troubleshooting guide to help identify and resolve the issue:
Update Drivers and Firmware
- Graphics Drivers: Update your graphics card drivers from the manufacturer's website (NVIDIA or AMD).
- Chipset Drivers: Update your motherboard’s chipset drivers from the motherboard manufacturer’s website.
- BIOS/Firmware: Ensure your BIOS is up-to-date. Check the HP support site for BIOS updates.
Check for Hardware Issues
- Memory Test: Run a memory diagnostic tool like Windows Memory Diagnostic or MemTest86 to check for faulty RAM.
- Temperature Check: Use software like HWMonitor or Core Temp to monitor your CPU and GPU temperatures. Overheating can cause crashes.
- Power Supply: Ensure your power supply unit (PSU) is sufficient and functioning properly. A failing PSU can lead to instability.
Check for Software Conflicts
- Clean Boot: Perform a clean boot to rule out software conflicts. Disable all non-Microsoft services and startup items, then gradually re-enable them to identify the problematic software.
- Windows Updates: Ensure Windows is fully updated.
Check System Files
Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth commands in Command Prompt as Administrator to check and repair system files.
Check Event Viewer
Look for other related errors in Event Viewer that might give clues about the cause of the bugcheck.
Check for Malware
Run a full system scan with your antivirus software to rule out malware as a potential cause.
Reinstall Windows
As a last resort, if none of the above steps resolve the issue, consider reinstalling Windows to eliminate software 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!
Alden4
HP Support
HP Support Community Moderator
08-25-2024 02:27 PM
Been going through the full list of suggested things now (+ a few more suggested in other threads online). Seems that it could be CPU temperature that becomes too high. Saw a MAX spike in HWMonitor at slightly above 90°c and as I understand that is the max temp it is built for (?).
First I thought that it had fixed it without doing anything about the cooling, but my computer just shut down after a few hours of gaming (longer than usual). with the exact same error in event viewer
Do you think that overheating might be the issue?
08-26-2024 10:13 AM
Hi @berggrenmarcus,
Thank you for your response,
I'm sending a private message to assist you with the next action.
Please check your Private message icon on the upper right corner of your HP Community profile Next, to your profile Name, you should see a little blue envelope, please click on it or simply click on this link.
I hope this helps! Keep me posted.
Alden4
HP Support
HP Support Community Moderator