浪潮虚拟化平台上的windows2022出现蓝屏IRQL_NOT_LESS_OR_EQUAL

Question

浪潮虚拟化平台上的windows2022出现蓝屏IRQL_NOT_LESS_OR_EQUAL

浩张 0

- 三个 dump 的崩溃指纹（WER Hash `{67f025a4-6118-fb27-8e14-38ed32b277a0}` + `nt!KiTimer2Expiration+0x181`）完全一致
- 所有 dump 的 ntoskrnl 均为 10.0.20348.4647
- 请微软工程师：
  1. **查 WER 内部遥测数据**：这个 hash 在微软 WER 数据库里有多少次出现、什么时间分布、什么 OS 版本分布
  2. **判断 KB 关联**：是否已知是某个 KB 引入，是否有相关 KB 修复
  3. **请求技术答复**：这个崩溃的官方修复路径是什么

服务器上只安装了sqlserver2022，

0 个注释

1 个答案

你的答案

Answer 1

Xuan Nhu 1,370 独立顾问

您好，

根据您提供的信息，目前只能确认：

Bug Check：IRQL_NOT_LESS_OR_EQUAL
操作系统版本：Windows Server 2022 (10.0.20348.4647)
服务器运行于浪潮虚拟化平台，仅安装了 SQL Server 2022。

仅凭 WER Hash 或 ntoskrnl.exe 版本，无法判断是否对应某个已知 Windows 缺陷，也无法通过 Microsoft Q&A 查询内部 WER 遥测数据或内部 Bug ID。

要进一步分析崩溃原因，建议提供以下信息：

完整的 MEMORY.DMP 或至少 Minidump 文件。
WinDbg 的 !analyze -v 输出。
Bug Check 参数（Arg1～Arg4）。
调用堆栈（Call Stack）。
lmvm 输出，确认是否涉及第三方驱动程序。
浪潮虚拟化平台版本及其 Integration/Guest 驱动版本。

如果多个 Dump 的调用堆栈和故障模块一致，就可以进一步判断问题是否由：

Windows 内核已知问题；
第三方驱动（存储、网络、虚拟化驱动等）；
或特定累计更新（LCU）引入。

如果您希望 Microsoft 工程团队进一步确认是否存在已知问题或分析内部符号，建议通过 Microsoft Unified Support / Premier Support 提交支持请求，并上传完整 Dump 文件。工程团队可以利用私有符号和内部调试信息进行更深入的分析，并确认是否已有对应的修复或正在调查中的问题。

如果您能提供 !analyze -v 的完整输出或 Dump 文件，我也可以协助您进行进一步分析。

浩张 0

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\071526-927218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 20348 MP (48 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 20348.2849.amd64fre.fe_release_svc_prod1.241101-1732
Kernel base = 0xfffff804`3e400000 PsLoadedModuleList = 0xfffff804`3f033b30
Debug session time: Wed Jul 15 20:34:40.456 2026 (UTC + 8:00)
System Uptime: 19 days 0:27:51.668
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000007b`a5eaf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`3e82ec70 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff804`3d57ca70=000000000000000a
0: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000007b`a5eaf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        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: 0000000000000000, 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: fffff8043e771711, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1812

    Key  : Analysis.Elapsed.mSec
    Value: 18062

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

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

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

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

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_nt!KiTimer2Expiration

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

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

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

    Key  : Failure.Hash
    Value: {67f025a4-6118-fb27-8e14-38ed32b277a0}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.Value
    Value: 368

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x170

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

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 1

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 536585

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x83009

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x0

    Key  : Stack.Pointer
    Value: NMI

    Key  : WER.OS.Branch
    Value: fe_release_svc_prod1

    Key  : WER.OS.Version
    Value: 10.0.20348.2849


BUGCHECK_CODE:  a

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8043e771711

FILE_IN_CAB:  071526-927218-01.dmp

FAULTING_THREAD:  ffffa88f2ddab080

READ_ADDRESS: fffff8043f10f3d8: Unable to get MiVisibleState
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

DPC_STACK_BASE:  FFFFF8043D57CFB0

IP_IN_PAGED_CODE: 
nt!KiTimer2Expiration+181
fffff804`3e771711 488b1b          mov     rbx,qword ptr [rbx]

STACK_TEXT:  
fffff804`3d57ca68 fffff804`3e844629     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff804`3d57ca70 fffff804`3e83fc61     : ffffa88f`2797dae8 00000000`00000000 ffffa88f`2797db00 ffffa88f`2e8f51c0 : nt!KiBugCheckDispatch+0x69
fffff804`3d57cbb0 fffff804`3e771711     : 00000000`00000000 00000000`00000001 ffffa88f`2797dae8 fffff804`3d4d6180 : nt!KiPageFault+0x461
fffff804`3d57cd40 fffff804`3e824ab6     : fffff804`3d4d6180 fffff804`3d4d953c fffff804`3d4d6180 00000000`00000001 : nt!KiTimer2Expiration+0x181
fffff804`3d57ce00 fffff804`3e6e0cfb     : 00000000`00000000 fffff804`3d4d6180 ffffd906`d4587ca0 fffff804`3f1018f0 : nt!KiRetireDpcListEx+0x1a2
fffff804`3d57cf80 fffff804`3e8385b5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0xb
fffff804`3d57cfb0 fffff804`3e8383e0     : 00000000`00000060 fffff804`3e837a81 00000000`00000010 00000000`00000282 : nt!KxRetireDpcList+0x5
ffffd906`d4587be0 fffff804`3e837a95     : 00000000`00000000 fffff804`3e8317b1 ffffa88f`2ddab080 00000000`00000100 : nt!KiDispatchInterruptContinue
ffffd906`d4587c10 fffff804`3e8317b1     : ffffa88f`2ddab080 00000000`00000100 00000000`00000000 ffffa88f`00000000 : nt!KiDpcInterruptBypass+0x25
ffffd906`d4587c20 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1


SYMBOL_NAME:  nt!KiTimer2Expiration+181

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.20348.4647

STACK_COMMAND: .process /r /p 0xffffa88f2dc960c0; .thread /r /p 0xffffa88f2ddab080 ; kb

BUCKET_ID_FUNC_OFFSET:  181

FAILURE_BUCKET_ID:  AV_nt!KiTimer2Expiration

OS_VERSION:  10.0.20348.2849

BUILDLAB_STR:  fe_release_svc_prod1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {67f025a4-6118-fb27-8e14-38ed32b277a0}

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