[BSOD] IRQL_NOT_LESS_OR_EQUAL — Windows 11 24H2 (26100.4946)

Hello! My computer suddenly had a BSOD out of nowhere. May I ask what happened to my computer? During the time of my crash, I was just browsing and watching videos.

V2 Log Collector
Mini Dump

*******************************************************************************
* *
* 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: ffffcc8dcd021ae0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff804bed51048, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1625

Key : Analysis.Elapsed.mSec
Value: 1707

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27871.1001

Key : Analysis.Version.Description
Value: 10.2505.01.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2505.1.2

Key : Bugcheck.Code.KiBugCheckData
Value: 0xa

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Dump.Attributes.AsUlong
Value: 0x21800

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

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

Key : Dump.Attributes.ProgressPercentage
Value: 100

Key : Failure.Bucket
Value: AV_nt!KiProcessThreadWaitList

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

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

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

Key : Failure.Hash
Value: {ab137ff5-2285-b84e-791e-2375d6352743}

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 : SecureKernel.HalpHvciEnabled
Value: 1

Key : Stack.Pointer
Value: NMI

Key : WER.OS.Branch
Value: ge_release

Key : WER.OS.Version
Value: 10.0.26100.1


BUGCHECK_CODE: a

BUGCHECK_P1: ffffcc8dcd021ae0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff804bed51048

FILE_IN_CAB: MEMORY - 3.DMP

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


DUMP_FILE_ATTRIBUTES: 0x21800

FAULTING_THREAD: fffff804bf9d1640

WRITE_ADDRESS: ffffcc8dcd021ae0 Nonpaged pool

BLACKBOXBSD: 1 (
!blackboxbsd
)


BLACKBOXNTFS: 1 (
!blackboxntfs
)


BLACKBOXPNP: 1 (
!blackboxpnp
)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

DPC_STACK_BASE: FFFFF80451619FB0

STACK_TEXT:
fffff804`51610d48 fffff804`bf0b85e9 : 00000000`0000000a ffffcc8d`cd021ae0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff804`51610d50 fffff804`bf0b38a8 : 00000000`05000000 fffff804`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff804`51610e90 fffff804`bed51048 : 00000000`00000000 ffffcc8d`bea81040 00000000`00000246 fffff804`bed2f073 : nt!KiPageFault+0x468
fffff804`51611020 fffff804`bec7d0cf : fffff804`00000000 fffff804`00000001 fffff804`00000000 fffff804`00000002 : nt!KiProcessThreadWaitList+0x148
fffff804`516110c0 fffff804`bec7dda5 : 00000332`d3e8fc91 00000000`00000000 00000332`d86b578d fffff804`4d271180 : nt!KiProcessExpiredTimerList+0x10f
fffff804`516111f0 fffff804`bec0c805 : 00000000`00000000 00000000`00000000 fffff804`4d271180 fffff804`bf9d1640 : nt!KiTimerExpiration+0x2b5
fffff804`51611330 fffff804`bf0a564e : fffff804`4d271180 fffff804`4d271180 00000000`001a7550 00000000`00000000 : nt!KiRetireDpcList+0xc45
fffff804`516115c0 00000000`00000000 : fffff804`51612000 fffff804`5160b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: nt!KiProcessThreadWaitList+148

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .process /r /p 0xfffff804bf9cef80; .thread 0xfffff804bf9d1640 ; kb

BUCKET_ID_FUNC_OFFSET: 148

FAILURE_BUCKET_ID: AV_nt!KiProcessThreadWaitList

OS_VERSION: 10.0.26100.1

BUILDLAB_STR: ge_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ab137ff5-2285-b84e-791e-2375d6352743}

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

Device Specifications

Processor AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (3.80 GHz)

Installed RAM 16.0 GB (13.8 GB usable)

RZ616 Wi-Fi 6E 160MHz

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

Windows specifications

Edition Windows 11 Home Single Language

Version 24H2

Installed on ‎Jul ‎12, ‎2025

OS build 26100.4946

Experience Windows Feature Experience Pack 1000.26100.197.0

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

Manufacturer Lenovo

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

Oof. That stop code, especially "a" is typically an indication of CPU core instability. Even more so when it indicates a fault in a system process, especially the kernel. This can mean a faulty CPU, a faulty system board, or a faulty power supply.

Because you clearly are not overclocking core(s), this looks like a defective system. Better back up files to a drive that's not internal to the system.

RJARRRPCGP said:

Oof. That stop code, especially "a" is typically an indication of CPU core instability. Even more so when it indicates a fault in a system process, especially the kernel. This can mean a faulty CPU, a faulty system board, or a faulty power supply.

Because you clearly are not overclocking core(s), this looks like a defective system.

Click to expand...

Hello! I actually had this laptop sent for warranty before and they replaced the board (months back already). Do I need to request Lenovo CS to check my system? (Warranty is still active)

Oppressor5834 said:

Hello! I actually had this laptop sent for warranty before and they replaced the board (months back already). Do I need to request Lenovo CS to check my system? (Warranty is still active)

Click to expand...

Yes!

RJARRRPCGP said:

Yes!

Click to expand...

Thank you

Oppressor5834 said:

Hello! My computer suddenly had a BSOD out of nowhere. May I ask what happened to my computer? During the time of my crash, I was just browsing and watching videos.

Click to expand...

The V2 log collector reported a very large number of BSODs.

BSODs can be missed.

If you want to view more BSODs it may be possible by remodifying the Windows settings.




Almost all were bugcheck 133 from Aug 4 - Aug 22.

zbook said:

The V2 log collector reported a very large number of BSODs.

BSODs can be missed.

If you want to view more BSODs it may be possible by remodifying the Windows settings.




Almost all were bugcheck 133 from Aug 4 - Aug 22.

Code:

Event[46791]
  Log Name: System
  Source: Microsoft-Windows-WindowsUpdateClient
  Date: 2025-09-23T21:29:22.6070000Z
  Event ID: 20
  Task: Windows Update Agent
  Level: Error
  Opcode: Installation
  Keyword: Installation,Failure,
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: LAPTOP-JUSRNELU
  Description:
Installation Failure: Windows failed to install the following update with error 0x800F081F: 2025-09 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5065426) (26100.6584).

Code:

Event[39939]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2025-09-14T00:35:31.7100000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: LAPTOP-JUSRNELU
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff806809c43b0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a15336f2-3b6a-46f8-9162-5af5600e22d2.

Click to expand...

Minidump 1
Minidump 2

Hii I have experienced some BSODs related to DPC Watch Dog Violation, but I thought that they were resolved already. I also have attached the minidump files in regards to the previous BSODs. May I ask what I can do from here?

Thank you

The Windows installation was on Jul 12, 2025.

What was done for the bugchecks 133 Aug 4 - Aug 22?

zbook said:

The Windows installation was on Jul 12, 2025.

What was done for the bugchecks 133 Aug 4 - Aug 22?

Click to expand...

I ran system checks [SFC, DISM] (but no errors were found).
I uninstalled Virtualbox.
I reinstalled my GPU drivers.
I ran system restore.

Honestly, I still don't know if what I did was enough, but I haven't had a DPC Watchdog Violation BSOD in a while.

Please contact Lenovo warranty support.

zbook said:

Please contact Lenovo warranty support.

Click to expand...

Thank you. I already did and I am waiting for a reply. Do you believe this problem is hardware-related also?

It is likely hardware.


1) Run Tuneup plus:





2) Create a new restore point


3) Monitor using:



4) Place the computer into safe mode (shift + restart)


5) For any BSOD while in safe mode post a new V2 share link into the newest post

Oppressor5834 said:

Thank you. I already did and I am waiting for a reply. Do you believe this problem is hardware-related also?

Click to expand...

Frankly, I think you are overthinking things.

EVERBODY gets a BSOD, now and then, and a simple reboot usually sorts it. Indeed, I had one a few days ago.

You only need to be concerned if the problem keeps repeating itself on a frequent basis.

It is nigh on impossible to get to the bottom of a one off BSOD.

So I would stop worrying unless BSODs happen frequently.