Bluescreen and other crashes

SnotMcBooger · ‎04-11-2025

4 months ago I bought this HP Omen 45l. Everything was great at the beginning. Over the past month I've been getting more and more bluescreens as well as Chrome crashing.

I did already do a fresh install of Windows 11, but the errors persist. I also ran the hardware diagnostics from HP Support Assistant in extensive mode, but nothing was found. So, I'm starting to lose my marbels. I really don't know what other steps to take at this point.

Any help is greatly appreciated. Error logs below.

The chrome errors are the following:
status_access_violation

status_breakpoint

Same happens in Edge, so Chromium browsers. Haven't tested Firefox or any other tho. Occasianly it also crashes completely. Error Viewer Log entry:

Faulting application name: chrome.exe, version: 135.0.7049.42, time stamp: 0x67e3212c
Faulting module name: chrome.dll, version: 135.0.7049.42, time stamp: 0x67e3212c
Exception code: 0xc0000409
Fault offset: 0x0000000004a3f2ed
Faulting process id: 0x4DB8
Faulting application start time: 0x1DBAA2537402C5E
Faulting application path: C:\Program Files\Google\Chrome\Application\chrome.exe
Faulting module path: C:\Program Files\Google\Chrome\Application\135.0.7049.42\chrome.dll
Report Id: 476343b2-9a27-4ea2-b0c6-dd35af434895
Faulting package full name:
Faulting package-relative application ID:

Then there are also the bluescreens PAGE_FAULT_IN_NON_PAGED_AREA and IRQL_NOT_LESS_OR_EQUAL

PAGE_FAULT_IN_NON_PAGED_AREA:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffa608e5e9f89f, 0x0000000000000002, 0xfffff80042ba16e8, 0x0000000000000002). A dump was saved in: C:\WINDOWS\Minidump\041125-16203-01.dmp. Report Id: 2663b811-69dd-4782-abf6-5c4c043062c2.

Minidump of PAGE_FAULT_IN_NON_PAGED_AREA analyze:

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: ffffa608e5e9f89f, memory referenced.

Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.

bit 1 is set if the fault was due to a write, clear if a read.

bit 3 is set if the processor decided the fault was due to a corrupted PTE.

bit 4 is set if the fault was due to attempted execute of a no-execute PTE.

- ARM64: bit 1 is set if the fault was due to a write, clear if a read.

bit 3 is set if the fault was due to attempted execute of a no-execute PTE.

Arg3: fffff80042ba16e8, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : AV.Type

Value: Write

Key : Analysis.CPU.mSec

Value: 921

Key : Analysis.Elapsed.mSec

Value: 3950

Key : Analysis.IO.Other.Mb

Value: 4

Key : Analysis.IO.Read.Mb

Value: 1

Key : Analysis.IO.Write.Mb

Value: 24

Key : Analysis.Init.CPU.mSec

Value: 265

Key : Analysis.Init.Elapsed.mSec

Value: 16918

Key : Analysis.Memory.CommitPeak.Mb

Value: 89

Key : Analysis.Version.DbgEng

Value: 10.0.27793.1000

Key : Analysis.Version.Description

Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext

Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI

Value: 0x50

Key : Bugcheck.Code.TargetModel

Value: 0x50

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: AV_W_(null)_BEDaisy!unknown_function

Key : Failure.Exception.IP.Address

Value: 0xfffff80042ba16e8

Key : Failure.Exception.IP.Module

Value: BEDaisy

Key : Failure.Exception.IP.Offset

Value: 0x6c16e8

Key : Failure.Hash

Value: {4024c46b-040f-2932-f980-447accda06b7}

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

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffa608e5e9f89f

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80042ba16e8

BUGCHECK_P4: 2

FILE_IN_CAB: 041125-16203-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x21808

Kernel Generated Triage Dump

FAULTING_THREAD: ffffd78bde4e7080

READ_ADDRESS: fffff8008c7c34c0: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

unable to get nt!MmSpecialPagesInUse

ffffa608e5e9f89f

MM_INTERNAL_CODE: 2

IMAGE_NAME: BEDaisy.sys

MODULE_NAME: BEDaisy

FAULTING_MODULE: fffff800424e0000 BEDaisy

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

TRAP_FRAME: ffffd304aab66c10 -- (.trap 0xffffd304aab66c10)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000006023 rbx=0000000000000000 rcx=ffff1f1748bb39e8

rdx=000001f4cf9c0001 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80042ba16e8 rsp=ffffd304aab66da8 rbp=fffff80042ba16d8

r8=0000000140396e05 r9=fffff800426fdc89 r10=ffffd304aab67028

r11=ffffd304aab66e00 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

BEDaisy+0x6c16e8:

fffff800`42ba16e8 4e299414cf1a7d90 sub qword ptr [rsp+r10-6F82E531h],r10 ss:0018:ffffa608`e5e9f89f=????????????????

Resetting default scope

STACK_TEXT:

ffffd304`aab669a8 fffff800`8ba73351 : 00000000`00000050 ffffa608`e5e9f89f 00000000`00000002 ffffd304`aab66c10 : nt!KeBugCheckEx

ffffd304`aab669b0 fffff800`8ba913cf : ffffa608`e5e9f89f 00000000`00001000 00000000`00000002 fffff800`8b800000 : nt!MiSystemFault+0x735

ffffd304`aab66aa0 fffff800`8be8aacb : 00000000`00000000 ffffe781`82303180 ffff4006`57881886 00007ff9`ade5c6f0 : nt!MmAccessFault+0x2ff

ffffd304`aab66c10 fffff800`42ba16e8 : ffff1f17`48bb39e8 00000000`00000000 d78bde4e`70800246 ffffe781`8230ffff : nt!KiPageFault+0x38b

ffffd304`aab66da8 ffff1f17`48bb39e8 : 00000000`00000000 d78bde4e`70800246 ffffe781`8230ffff 6bc5f4f0`50287fff : BEDaisy+0x6c16e8

ffffd304`aab66db0 00000000`00000000 : d78bde4e`70800246 ffffe781`8230ffff 6bc5f4f0`50287fff ffffd78b`de4e78f0 : 0xffff1f17`48bb39e8

SYMBOL_NAME: BEDaisy+6c16e8

STACK_COMMAND: .process /r /p 0xffffd78bde427080; .thread 0xffffd78bde4e7080 ; kb

BUCKET_ID_FUNC_OFFSET: 6c16e8

FAILURE_BUCKET_ID: AV_W_(null)_BEDaisy!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4024c46b-040f-2932-f980-447accda06b7}

Followup: MachineOwner

IRQL_NOT_LESS_OR_EQUAL:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x000000000000000a, 0x0000000000000002, 0x0000000000000000, 0xfffff801b4a84819). A dump was saved in: C:\WINDOWS\Minidump\040925-16890-01.dmp. Report Id: ff24e59b-6986-4d96-9151-c9c424a241da.

Minidump IRQL_NOT_LESS_OR_EQUAL:

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 000000000000000a, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff801b4a84819, address which referenced memory

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 953

Key : Analysis.Elapsed.mSec

Value: 3096

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

Key : Analysis.Init.Elapsed.mSec

Value: 22798

Key : Analysis.Memory.CommitPeak.Mb

Value: 88

Key : Analysis.Version.DbgEng

Value: 10.0.27793.1000

Key : Analysis.Version.Description

Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext

Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI

Value: 0xa

Key : Bugcheck.Code.TargetModel

Value: 0xa

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: AV_nt!KiDeliverApc

Key : Failure.Exception.IP.Address

Value: 0xfffff801b4a84819

Key : Failure.Exception.IP.Module

Value: nt

Key : Failure.Exception.IP.Offset

Value: 0x284819

Key : Failure.Hash

Value: {f94393b9-4308-5aa6-9044-71825dde3286}

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

BUGCHECK_CODE: a

BUGCHECK_P1: a

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801b4a84819

FILE_IN_CAB: 040925-16890-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x21808

Kernel Generated Triage Dump

FAULTING_THREAD: ffffcd8ea6e2e080

READ_ADDRESS: fffff801b57c34c0: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

unable to get nt!MmSpecialPagesInUse

000000000000000a

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

TRAP_FRAME: fffff68c85aef260 -- (.trap 0xfffff68c85aef260)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002

rdx=fffff68c85aef1f8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff801b4a84819 rsp=fffff68c85aef3f0 rbp=fffff68c85aef458

r8=fffff68c85aef1d0 r9=0000000000000002 r10=0000000000000003

r11=ffff9a0d1b213800 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!KiDeliverApc+0x2c9:

fffff801`b4a84819 48395108 cmp qword ptr [rcx+8],rdx ds:00000000`0000000a=????????????????

Resetting default scope

STACK_TEXT:

fffff68c`85aef118 fffff801`b4e8f8e9 : 00000000`0000000a 00000000`0000000a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff68c`85aef120 fffff801`b4e8aba8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffff68c`85aef260 fffff801`b4a84819 : 00000000`00000000 00000000`00000000 fffff68c`85aef210 fffff68c`85aef220 : nt!KiPageFault+0x468

fffff68c`85aef3f0 fffff801`b4a83494 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x2c9

fffff68c`85aef490 fffff801`b4a83449 : 00000000`00000000 00000000`00000000 00000000`00000001 ffff9a0d`0314c610 : nt!KiCheckForKernelApcDelivery+0x34

fffff68c`85aef4e0 fffff801`b50fd5fb : ffff9a0d`1b2137d0 ffff9a0d`1b2137e0 00000000`00000000 fffff801`b563e568 : nt!KeLeaveGuardedRegion+0x29

fffff68c`85aef510 fffff801`b50fe412 : 00000000`00000001 ffff9a0d`1b2137d0 00000000`00000000 00000000`00000000 : nt!WbCreateHeapExecutedBlock+0x9fb

fffff68c`85aef590 fffff801`b51b5a9e : ffff9a0d`0314c610 00000000`00000000 00000000`00000000 ffffcd8e`a1e2bb30 : nt!WbValidateHeapExecuteCallArguments+0x81a

fffff68c`85aef600 fffff801`b51b25fe : 00000239`65e3b4d0 00000239`65e3b758 00000239`65e37fe0 00000000`00000000 : nt!ExpQuerySystemInformation+0x333e

fffff68c`85aef9e0 fffff801`b4e8ef55 : 0000000f`056a0000 ffffcd8e`a6e2e080 ffffcd8e`a6e2e080 00000000`00000007 : nt!NtQuerySystemInformation+0x3e

fffff68c`85aefa20 00007ffd`6619c684 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

00000088`b7a7d508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`6619c684

SYMBOL_NAME: nt!KiDeliverApc+2c9

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.3775

STACK_COMMAND: .process /r /p 0xffffcd8ea2f85080; .thread 0xffffcd8ea6e2e080 ; kb

BUCKET_ID_FUNC_OFFSET: 2c9

FAILURE_BUCKET_ID: AV_nt!KiDeliverApc

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f94393b9-4308-5aa6-9044-71825dde3286}

PROCESS_NAME: Unknown

Followup: MachineOwner

---------

Kuroi_Kenshi · ‎04-12-2025

Hi @SnotMcBooger,

Welcome to the HP Support Community!

Thanks for reaching out about your query regarding your PC!

We're thrilled to have the opportunity to assist you and provide a solution.

Try these steps:

Update Drivers:

Ensure all drivers are up to date. Use the HP Support Assistant for automatic updates:
- Open HP Support Assistant.
- Go to the My devices tab.
- Click Updates > Check for updates. Follow the on-screen instructions.

Check for Windows Updates:

Ensure you have all the latest Windows updates installed:
- Go to Settings > Update & Security > Windows Update.
- Click Check for updates.

Check Event Viewer:

Analyse the Event Viewer for error logs that might give more insight into the blue screens and crashes:
- Press Win + X and select Event Viewer.
- Look under Windows Logs > System and Applications for any error messages.

Check for Disk Errors:

Run CHKDSK to check for any disk errors:
- Open Command Prompt as administrator.
- Type chkdsk C: /f /r and press Enter. Follow on-screen instructions.

Disable Overclocking:

If you have enabled any overclocking features, disable them to see if stability improves.

Reinstall Chrome:

Reinstall Google Chrome as it is commonly involved in crashes. This might resolve browser-specific issues:
- Uninstall Chrome via Settings > Apps.
- Restart the computer.
- Download and install the latest version from Chrome's official site.

Check for Malware:

Run a full malware scan using Windows Defender or a trusted antivirus software.

Monitor Temperatures:

Use HWMonitor or similar software to ensure your CPU and GPU temperatures are within safe boundaries, especially during gaming or intensive tasks.

I hope this helps.

I'm glad I could help! 😊 If this resolved your issue, please mark it as "Accepted Solution" and click "Yes" on "Was this reply helpful?" Your feedback not only keeps us going but also helps others find the solution faster! 👍✨

Take care and have an amazing day ahead! 🚀

Best regards,

Kuroi_Kenshi
I am an HP Employee

SnotMcBooger · ‎04-14-2025

Hi, thanks for your reply.

Update Drivers and Check for Windows Updates:

- Already did that. All up to date.

Check Event Viewer:

- Attached the logs as you can see in my post.
Check for Disk Errors:

- Already did that as well. All clear.

Disable Overclocking:

- Was never enabled.

Reinstall Chrome:

- As mentioned in the post, not only did I do that, I did a complete fresh install of Windows.

Check for Malware:

- Neither Defender, nor McAfee could find anything.

Monitor Temperatures:

- Nothing out of the ordinary.

I ran Memtest86 as well as HP Support Assistant extensive test, all clear, nothing was found.

Oh yeah, and since I assume that will be your next suggestion. I did update the BIOS as well.

So, no, the issue still persists. Especially the Chrome errors, which happened again just now while writing this.

As a side note. archiving a post after just two days is quite something.

Kuroi_Kenshi · ‎04-17-2025

Hi @SnotMcBooger,

Thank you for the response. Even though the post is archived, you can always reach out to us anytime.

Since the issue persists even after performing the provided steps, and to get you the best assistance, we need to take this conversation to a private chat. We're inviting you to a private message to protect your privacy and ensure that any sensitive information remains confidential.

To access your private message, just click the little blue envelope icon on the upper right corner of your HP Community profile, next to your profile name. Alternatively, you can click on this link.

You can use this link as well:

Private Messages - HP Support Community

We're looking forward to helping you resolve this issue!

Stay tuned, and thanks for your patience!

Best regards,

Kuroi_Kenshi
I am an HP Employee

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