Random Restarts on Desktop

Lolly10 · ‎08-03-2026

I have an HP Pavilion Desktop TP01-3000i. I purchased it 4/2025, OS is Win 11 version 25H2. It's been working fine until about a month ago. The PC will then go to a black screen and say 'your device ran into a problem and needs to reboot.' The PC then reboots. I've been able to briefly 'catch' some other messages at the bottom of the screen dealing with kernel info. I'm up to date on drivers, BIOS, Windows updates, etc. I've performed the HP h/w diagnostics also. I downloaded Windbg and ran it against the minidump file generated by the restart. However, I don't know how to read it. I don't know how to attached the file. Please help.

For some reason, this was placed in Business. This is a personal desktop.

Jerry_57 · ‎08-05-2026

Hi @Lolly10,

Welcome to the HP Support Community.

Thank you for posting your query. I understand how frustrating random restarts can be, especially when the system had been working normally before the issue started.

Since you've already verified that Windows, drivers, BIOS, and HP hardware diagnostics are up to date, the next step is to identify the specific stop error or driver causing the crash.

Disable Automatic Restart:

This will allow the blue screen error to remain visible instead of the system rebooting immediately:

Type View advanced system settings in the Windows search box and open it.
Select the Advanced tab.
Under Startup and Recovery, click Settings.
Under System failure, uncheck Automatically restart.
Click OK and restart the PC.

The next time the issue occurs, please note the Stop Code and any file or driver name displayed on the screen.

Analyse the Minidump File:

Open WinDbg as Administrator.

Select File > Open Dump File and open the latest file from:

C:\Windows\Minidump

At the command prompt, type:

!analyze -v

Once the analysis completes, please copy and post the following sections:

BugCheck
MODULE_NAME
IMAGE_NAME
FAILURE_BUCKET_ID

If you're unable to attach the dump file directly, you can copy and paste the output from !analyze -v into your next reply, and we'll help interpret the results.

I look forward to your update.

Take care and have a great day.

I'm an HP Employee.

If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.

And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.

Lolly10 · ‎08-08-2026

I'm very confused. I replied earlier today, but the post is not here. I'll try again. If there's a way for me to send the entire file, please let me know. The message I received was: "your device ran into a problem and needs to restart. We're just collecting some error info, then you can restart. 100% stop code: kernel_mode_heap_corruption (ox13a)".

 Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000012, The heap detected invalid internal state during the current operation. This can be the result of a use-after-free error or a buffer overflow of an adjacent block.
Arg2: ffffce0b75100140, Address of the heap that reported the corruption
Arg3: ffffce0bf267b000, Address at which the corruption was detected
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1406

    Key  : Analysis.Elapsed.mSec
    Value: 1425

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x13a

    Key  : Bugcheck.Code.TargetModel
    Value: 0x13a

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x13a_12_dxgkrnl!operator_new[]

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff800b277417a

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0xb7417a

    Key  : Failure.Hash
    Value: {539cc552-dd5d-a4bf-6cc6-f32b6c4a53e0}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    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: 0x3f7

    Key  : WER.System.BIOSRevision
    Value: 15.52.0.0


BUGCHECK_CODE:  13a

BUGCHECK_P1: 12

BUGCHECK_P2: ffffce0b75100140

BUGCHECK_P3: ffffce0bf267b000

BUGCHECK_P4: 0

FILE_IN_CAB:  080826-10968-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffce0bee0cb0c0

CORRUPTING_POOL_ADDRESS: fffff800b2bc54d8: Unable to get MiVisibleState
 ffffce0bf267b000 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  hp-plugin-exec

IP_IN_PAGED_CODE: 
nt!ExAllocatePool2+8a
fffff800`b277417a 4c8bd0          mov     r10,rax

STACK_TEXT:  
ffff960c`37f94208 fffff800`b21f05ac     : 00000000`0000013a 00000000`00000012 ffffce0b`75100140 ffffce0b`f267b000 : nt!KeBugCheckEx
ffff960c`37f94210 fffff800`b21f060c     : 00000000`00000012 ffffce0b`751002c0 ffffce0b`75100140 fffff800`b20627e4 : nt!RtlpHeapHandleError+0x40
ffff960c`37f94250 fffff800`b1f5ba09     : 00000000`00000000 ffffce0b`f26ec050 ffffce0b`d06101e0 00000000`0000a2a0 : nt!RtlpHpHeapHandleError+0x58
ffff960c`37f94280 fffff800`b1f67cc3     : ffffce0b`ee0cb0c0 fffff800`b1f21b68 ffffce0b`7aee5610 ffff960c`37f94359 : nt!RtlpLogHeapFailure+0x45
ffff960c`37f942b0 fffff800`b1f678ef     : ffffce0b`751002c3 00000000`00000240 00000000`00000026 fffff800`00260000 : nt!RtlpHpVsSlotAllocate+0x2b3
ffff960c`37f94310 fffff800`b1fe951d     : 00000000`00000040 fffff800`00000026 ffffce0b`00000001 ffffce0b`00000002 : nt!RtlpHpVsContextAllocate+0xd3
ffff960c`37f943a0 fffff800`b1e788cf     : ffffce0b`75100000 00000000`00000240 00000000`00000002 ffffce0b`d973fd80 : nt!RtlpHpAllocateHeap+0x16d
ffff960c`37f94450 fffff800`b1e77722     : ffff858b`7552dd68 00000000`00000228 00000000`4b677844 01000000`00000000 : nt!ExAllocateHeapPool+0x113f
ffff960c`37f945b0 fffff800`b277417a     : 00000000`00000040 ffff960c`37f94aa0 00000000`00000228 fffff800`43c3d568 : nt!ExpAllocatePoolWithTagFromNode+0x52
ffff960c`37f945f0 fffff800`43c4b4f2     : ffffce0b`d973fd80 00000000`00000000 00000000`0000122e fffff800`45ec8532 : nt!ExAllocatePool2+0x8a
ffff960c`37f94650 fffff800`43fac881     : 0000004d`db0f7da0 00000000`00000228 0000004d`db0f7da0 ffffce0b`d973fd80 : dxgkrnl!operator new[]+0x32
ffff960c`37f94680 fffff800`43fac50e     : 0000004d`db0f7da0 ffffce0b`ee0cb0c0 00000000`00000020 00000000`00000228 : dxgkrnl!DxgkQueryAdapterInfoImpl+0x361
ffff960c`37f949f0 fffff800`b22bfb41     : ffffce0b`ee0cb0c0 00000239`aeb25b20 ffffce0b`ee0cb0c0 00000000`00000001 : dxgkrnl!DxgkQueryAdapterInfo+0xe
ffff960c`37f94a20 00007ffb`878c5884     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x496
0000004d`db0f7d78 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`878c5884


SYMBOL_NAME:  dxgkrnl!operator new[]+32

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.26100.8875

STACK_COMMAND: .process /r /p 0xffffce0bf405d080; .thread /r /p 0xffffce0bee0cb0c0 ; kb

BUCKET_ID_FUNC_OFFSET:  32

FAILURE_BUCKET_ID:  0x13a_12_dxgkrnl!operator_new[]

I then got a message that said invalid HTML was in the message and the system removed it.

Jerry_57 · ‎08-10-2026

Thank you for sharing the dump.

Your crash is most likely caused by a faulty or unstable graphics driver (dxgkrnl.sys is the DirectX Graphics Kernel), not hardware failure. The stop code KERNEL_MODE_HEAP_CORRUPTION (0x13A) almost always points to GPU driver corruption or memory overrun, and the fix usually involves rolling back or clean‑reinstalling your graphics driver.

Step-by-Step Fixes:

Roll back GPU driver: If crashes started after a recent update, revert to the previous stable driver via Device Manager.

Clean reinstall GPU driver: Use Display Driver Uninstaller (DDU) in Safe Mode to remove all traces, then install the latest official driver from NVIDIA/AMD/Intel.

Update Windows: Ensure all cumulative updates are installed, as Microsoft patches driver conflicts regularly.

Disable NVIDIA SLI/Surround: If using multiple GPUs or multi‑monitor setups, disable these features — they are known to trigger dxgkrnl.sys errors.

Check RAM stability: Run Windows Memory Diagnostic or MemTest86 to rule out faulty RAM, which can mimic driver heap corruption.

Remove GPU overclocks: Reset GPU to factory clocks; unstable overclocks often corrupt heap structures.

I'm an HP Employee.

If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.

And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.

Lolly10 · ‎08-10-2026

Thank you so much for your response. I'm a little confused about rolling back the GPU driver. I don't know how to do that. I went into device manager, the driver is Intel(R) UHD Graphics 730, under properties - it says it's working properly,. the other items say disable, update, uninstall, and scan for hardware changes. How do I go about rolling back that driver. Thank you.

Lolly10 · ‎08-10-2026

While I’ve been waiting to hear back from you, I decided to run the memory diagnostic. I received received 3 different errors:

#1 Log Name: System

Source: Microsoft-Windows-DeviceAssociationService

Date: 8/10/2026 3:50:14 PM

Event ID: 3502

Task Category: (7000)

Level: Error

Keywords: (16),(2)

User: SYSTEM

Computer: JSMarchione

Description:

Device Disassociation (Unpairing) Failed.

Event Xml:

<Channel>System</Channel>

<Computer>JSMarchione</Computer>

</System>

<Data Name="AepId">EsclUsb#{4c77ed32-0a79-5a64-a426-73856317996e}</Data>

<Data Name="ClientProcessName">C:\Windows\System32\spoolsv.exe</Data>

</EventData>

</Event>

#2 Log Name: System

Source: Microsoft-Windows-TPM-WMI

Date: 8/10/2026 3:49:37 PM

Event ID: 1796

Task Category: None

Level: Error

Keywords:

User: SYSTEM

Computer: JSMarchione

Description:

The Secure Boot update failed to update SBAT with error Unknown HResult Error code: 0x800700c1. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

Event Xml:

<Channel>System</Channel>

<Computer>JSMarchione</Computer>

</System>

</EventData>

</Event>

#3 Log Name: System

Source: Service Control Manager

Date: 8/10/2026 3:44:37 PM

Event ID: 7000

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: JSMarchione

Description:

The GoogleUpdaterInternalService140.0.7273.0 service failed to start due to the following error:

The system cannot find the file specified.

Event Xml:

<Channel>System</Channel>

<Computer>JSMarchione</Computer>

</System>

<Data Name="param1">GoogleUpdaterInternalService140.0.7273.0</Data>

</EventData>

</Event>

After the diagnostics finished, I received a Bitlocker message to put in my recovery keys. That made me real nervous since I had no idea what it was talking about. I took a chance and rebooted my PC and looked up the 'key' information, but didn't do anything with it.. At this point, I’m unsure as to what to do. Thanks, again.

Lolly10 · ‎08-10-2026

Now I'm getting Kernel_security_check_failure (0x139) error. Progressively worse problem? I have done a Norton security scan and it doesn't appear as if there is a virus.

Pallipurath · ‎08-12-2026

Hi @Lolly10

Thank you for responding.

I understand that the issue is still not resolved and that you are now receiving an error message. I would request you to please install the drivers that were shared, one at a time, and check after each installation whether the issue persists. This will help us identify if a particular driver is causing the issue.

Intel High-Definition (HD) Graphics Driver

https://ftp.hp.com/pub/softpaq/sp156001-156500/sp156218.exe

Intel Chipset Installation Utility and Driver

https://ftp.hp.com/pub/softpaq/sp151501-152000/sp151784.exe

HP Consumer Desktop PC BIOS (ROM Family SSID 89B5)

https://ftp.hp.com/pub/softpaq/sp155001-155500/sp155207.exe

Hope this helps, Please revert if the issue persists.

Have a good day.

I'm an HP Employee.

If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.

And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.

Lolly10 · ‎08-12-2026

Thank you. If you would please expand on "install the drivers that were shared.' What does that mean? Am I supposed to run each .exe and continue working on my PC until, or if, I have another problem? Or should I be running each .exe, one after the other, and then wait to see if I have another problem? Again, thank you for your response. This PC was only 1 year and 3 months old when I started with this issue. It's very frustrating.

Pallipurath · ‎08-12-2026

Hi @Lolly10

Thank you for responding.

I am sorry for the confusion. Please install all three drivers that were shared, one after another, and restart the PC if prompted. Once all three drivers have been installed, continue using the PC normally and check whether the issue persists; if it does, please let us know so we can assist you further.

Have a good day.

I'm an HP Employee.

If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.

And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.

Featured blog article:

Create an account on the HP Community to personalize your profile and ask a question