need helping knowing what causing this

Question

been having alot of crashes past week where laptop will just restart no warning not always having a crash log. i did a factory reset thinking it might fix it but had one still after

AMD RYZEN 7 4800
16G RAM
1660TI 6GB

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: 000000000000008d, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000032, 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: fffff804e37427ee, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1796

    Key  : Analysis.Elapsed.mSec
    Value: 1795

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.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!HalpHvCounterQueryCounter

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

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

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

    Key  : Failure.Hash
    Value: {243f4d41-18f6-0b74-ab55-e1707af3cd3c}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

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

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


BUGCHECK_CODE:  a

BUGCHECK_P1: 8d

BUGCHECK_P2: ff

BUGCHECK_P3: 32

BUGCHECK_P4: fffff804e37427ee

FILE_IN_CAB:  042626-19109-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb607c15ac280

READ_ADDRESS: fffff804e43c44d8: Unable to get MiVisibleState
 000000000000008d 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nt!HalpHvCounterQueryCounter+ce
fffff804`e37427ee 80b88d00000001  cmp     byte ptr [rax+8Dh],1

STACK_TEXT:  
ffffc68d`aa0d1298 fffff804`e3abe2e9     : 00000000`0000000a 00000000`0000008d 00000000`000000ff 00000000`00000032 : nt!KeBugCheckEx
ffffc68d`aa0d12a0 fffff804`e3ab95a8     : 00000002`ffffffff 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc68d`aa0d13e0 fffff804`e37427ee     : ffffffff`ffffffff 0000006a`ec081751 00000000`00000000 0000006a`ec081400 : nt!KiPageFault+0x468
ffffc68d`aa0d1570 fffff804`e3826d6a     : 00000000`0004ce78 fffff7a8`0001e1c0 00000000`00000000 00000000`00000007 : nt!HalpHvCounterQueryCounter+0xce
ffffc68d`aa0d15a0 fffff804`e36e8e5f     : 0000006a`ec0814e4 00000000`00000000 ffffdb00`ba138180 00000000`00000001 : nt!HalpTimerClockArm+0x31a
ffffc68d`aa0d15f0 fffff804`e36e880a     : ffffc68d`aa0d18e8 00000000`0004ce78 ffffc68d`aa0d1790 0000006a`e9326698 : nt!KiSetClockTickRate+0x19f
ffffc68d`aa0d1690 fffff804`e39b8587     : 00000000`00000047 ffffdb00`ba138180 ffffdb00`ba138180 00000000`00000006 : nt!KiSetNextClockTickDueTime+0x10a
ffffc68d`aa0d18a0 fffff804`e3ae197a     : 00000000`00006869 00000000`00006869 ffffb607`c7f48000 ffffdb00`ba138180 : nt!KePrepareClockTimerForIdle+0x20b
ffffc68d`aa0d19e0 fffff804`e3849090     : ffffdb00`ba138180 ffffdb00`ba138180 ffffc68d`aa0d1bd9 ffffdb00`ba1409c0 : nt!PpmIdleExecuteTransition+0x327366
ffffc68d`aa0d1b70 fffff804`e3aab2b4     : ffffdb00`ba138180 00000000`00989600 ffffb607`00000001 ffffb607`ed976000 : nt!PoIdle+0x1c0
ffffc68d`aa0d1c40 00000000`00000000     : ffffc68d`aa0d2000 ffffc68d`aa0cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  nt!HalpHvCounterQueryCounter+ce

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.8246

STACK_COMMAND: .process /r /p 0xfffff804e43cef00; .thread /r /p 0xffffb607c15ac280 ; kb

BUCKET_ID_FUNC_OFFSET:  ce

FAILURE_BUCKET_ID:  AV_nt!HalpHvCounterQueryCounter

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {243f4d41-18f6-0b74-ab55-e1707af3cd3c}

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

Answer 1

Bug check 0xA (IRQL_NOT_LESS_OR_EQUAL) is almost always caused by a faulty device driver, system service, BIOS/firmware issue, or occasionally antivirus/backup software running in the kernel.

From the dump:

• Bug check: 0xA IRQL_NOT_LESS_OR_EQUAL
• Faulting symbol: nt!HalpHvCounterQueryCounter
• Hypervisor flags show Hyper-V/virtualization is active
• Process: System

This points to a kernel-mode component (often a driver or system service) misusing memory at high IRQL, not to a user app. A factory reset rules out most software, so remaining likely causes are:

• Recently added or faulty hardware
• Out-of-date or buggy drivers (chipset, storage, GPU, etc.)
• BIOS/firmware issues
• Security/AV or backup drivers running in the kernel

Recommended steps:

1. Basic hardware/driver checks
2. Remove any recently added hardware (USB devices, external drives, etc.) and test.
3. Boot into Safe Mode and see if the crashes stop. If they do, a third‑party driver/service is likely involved. See Start your PC in safe mode in Windows 10 from the referenced article.
4. In Device Manager, look for devices with a warning icon and update, disable, or uninstall those drivers.
5. Ensure there is at least 10–15% free disk space on the system drive.
6. Install all pending Windows Updates.
7. Focus on drivers and services (typical 0xA causes)

• Update chipset, storage, and GPU drivers from the laptop OEM support page.
• If any third‑party antivirus, VPN, or backup software is installed, temporarily uninstall it and test.
• If the issue started after a BIOS update or driver change, roll back if the OEM allows it.

3. If crashes persist

• Use the advanced bug check guidance for IRQL_NOT_LESS_OR_EQUAL:
  • Remove or replace recently added hardware.
  • Disable suspected system services and test.
  • Temporarily disable antivirus software to see if the error stops, then contact the vendor for an update.
• If the error occurs during startup and prevents normal boot, use Windows recovery options (System Restore, Reset this PC) as described in the referenced recovery documentation.

4. When to suspect hardware If all drivers are current, no third‑party kernel software is present, and the system still crashes in Safe Mode, hardware (RAM, motherboard, or storage) becomes more likely. In that case, run the OEM’s hardware diagnostics and consider professional hardware testing.

---

References:

• Troubleshooting Windows unexpected restarts and stop code errors
• Bug check 0xA: IRQL_NOT_LESS_OR_EQUAL

Answer 2

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.