IRQL_NOT_LESS_OR_EQUAL (a)蓝屏文件分析处理

queyue 0 信誉分
2025-12-25T10:53:41.3666667+00:00
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: 00000000001000f0, 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: fffff80778228a06, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1218

    Key  : Analysis.Elapsed.mSec
    Value: 1267

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    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!KiStartReadyQueueEnumeratorForRescheduleContext

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

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

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

    Key  : Failure.Hash
    Value: {f7c1e764-4304-dcdc-00c9-26a83244df9a}

    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  : Stack.Pointer
    Value: NMI

    Key  : WER.System.BIOSRevision
    Value: 1.15.0.0


BUGCHECK_CODE:  a

BUGCHECK_P1: 1000f0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80778228a06

FILE_IN_CAB:  122325-13515-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff80778fd0640

READ_ADDRESS: fffff80778fc34b0: 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
 00000000001000f0 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

DPC_STACK_BASE:  FFFFF8070AB57FB0

IP_IN_PAGED_CODE: 
nt!KiStartReadyQueueEnumeratorForRescheduleContext+96
fffff807`78228a06 f6417002        test    byte ptr [rcx+70h],2

STACK_TEXT:  
fffff807`0ab4f508 fffff807`7868cee9     : 00000000`0000000a 00000000`001000f0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff807`0ab4f510 fffff807`786881a8     : fffff807`0ab4f900 ffff950e`25b23000 ffff950e`259c7d50 00000000`00000718 : nt!KiBugCheckDispatch+0x69
fffff807`0ab4f650 fffff807`78228a06     : 00000000`00000000 fffff807`78f20da0 00000000`00000000 fffff807`78f20da0 : nt!KiPageFault+0x468
fffff807`0ab4f7e0 fffff807`782279fd     : 00000000`00000000 fffff807`78f20da0 fffff807`0ab4f910 fffff807`07e5d180 : nt!KiStartReadyQueueEnumeratorForRescheduleContext+0x96
fffff807`0ab4f810 fffff807`78309849     : 00000000`00000000 fffff807`07e5d180 fffff807`78fd0640 00000000`00000001 : nt!KiSearchForNewThreadsForRescheduleContext+0xcd
fffff807`0ab4f9f0 fffff807`78308e47     : fffff807`07e5d101 fffff807`0ab4fb40 00000000`0083ae3c fffff807`00000000 : nt!KiGroupSchedulingGenerationEnd+0xad
fffff807`0ab4fa80 fffff807`7820dcfd     : 00000000`00000000 fffff807`0ab4fb40 fffff807`78fd0640 00000000`00000000 : nt!KiGroupSchedulingQuantumEnd+0x97
fffff807`0ab4fb10 fffff807`78679ef4     : fffff807`07e5d100 fffff807`07e5d180 00000000`001a7550 fffff807`00000000 : nt!KiQuantumEnd+0x35d
fffff807`0ab4fc00 00000000`00000000     : fffff807`0ab50000 fffff807`0ab49000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0xb4


SYMBOL_NAME:  nt!KiStartReadyQueueEnumeratorForRescheduleContext+96

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.3194

STACK_COMMAND: .process /r /p 0xfffff80778fcdf80; .thread 0xfffff80778fd0640 ; kb

BUCKET_ID_FUNC_OFFSET:  96

FAILURE_BUCKET_ID:  AV_nt!KiStartReadyQueueEnumeratorForRescheduleContext

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f7c1e764-4304-dcdc-00c9-26a83244df9a}

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


Windows 家庭版 | Windows 11 | 性能和系统故障
0 个注释 无注释
{count} 票

1 个答案

排序依据: 非常有帮助
  1. Igor Leyko 109.6K 信誉分 独立顾问
    2025-12-25T12:19:52.3666667+00:00

    Hi,is this a single minidump? If not, please share 4-5 minidumps to OneDrive for analysis.

    If yes, please use driver verifier to gather additional information. https://support.microsoft.com/en-us/help/244617/using-driver-verifier-to-identify-issues-with-windows-drivers-for-adva

    Run

    verifier /standard /all /bootmode resetonbootfail

    command, reboot PC and use it as usual (it will be slower). If blue screen happens please share memory dumps to OneDrive for analysis. In a case of endless reboot please boot in safe mode and disable verifier by

    verifier /reset

    command.

    0 个注释 无注释

你的答案

提问者可以将答案标记为“已接受”,版主可以将答案标记为“已推荐”,这有助于用户了解答案是否解决了提问者的问题。