Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,571 questions
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- 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.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41
Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\桌面\051924-13187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff807`79200000 PsLoadedModuleList = 0xfffff807`79e13130
Debug session time: Sun May 19 20:50:05.214 2024 (UTC + 8:00)
System Uptime: 0 days 1:57:03.898
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`0a3e6018). Type ".hh dbgerr001" for details
Loading unloaded module list
............
Cannot read PEB32 from WOW64 TEB32 0a29e000 - Win32 error 0n30
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`79617f80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa007`9daef2b0=0000000000000001
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
BugCheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 0000000077981cf3, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffa0079daef4e0, Call type (0 - system call, 1 - worker routine)
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1453
Key : Analysis.Elapsed.mSec
Value: 4141
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 140
Key : Analysis.Init.Elapsed.mSec
Value: 6600
Key : Analysis.Memory.CommitPeak.Mb
Value: 101
Key : Bugcheck.Code.LegacyAPI
Value: 0x1
Key : Bugcheck.Code.TargetModel
Value: 0x1
Key : Dump.Attributes.AsUlong
Value: 808
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico
Key : Failure.Hash
Value: {1d25e8fe-40eb-1b84-9166-c3af30bbaf7e}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94
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: 4853999
Key : Hypervisor.Flags.ValueHex
Value: 4a10ef
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: 3f7
BUGCHECK_CODE: 1
BUGCHECK_P1: 77981cf3
BUGCHECK_P2: 0
BUGCHECK_P3: ffff
BUGCHECK_P4: ffffa0079daef4e0
FILE_IN_CAB: 051924-13187-01.dmp
DUMP_FILE_ATTRIBUTES: 0x808
Kernel Generated Triage Dump
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: LÞsð.exe
STACK_TEXT:
ffffa007`9daef2a8 fffff807`7962de29 : 00000000`00000001 00000000`77981cf3 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffa007`9daef2b0 fffff807`7962dce9 : 00000000`77984770 00000000`17aebb98 00000000`1281fda0 00000000`0a29c000 : nt!KiBugCheckDispatch+0x69
ffffa007`9daef3f0 00000000`77981cf3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3ad
00000000`1281ea48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77981cf3
SYMBOL_NAME: nt!KiSystemServiceExitPico+3ad
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.3593
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 3ad
FAILURE_BUCKET_ID: 0x1_SysCallNum_1b0007_nt!KiSystemServiceExitPico
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {1d25e8fe-40eb-1b84-9166-c3af30bbaf7e}
Followup: MachineOwner
---------
您好。
从bugcheck code看大概率是 驱动适配错误造成的蓝屏,也就是安装的驱动不兼容造成的。当然也有可能是系统文件损坏,或者驱动损坏造成的。
Bug 检查 0x1 APC_INDEX_MISMATCH - Windows drivers | Microsoft Learn
报错显示是一个内核的错误,没有特别的信息,可以参考上方的链接进行查看。
同时建议您检查更新,并更新安装显卡驱动再观察。
如果答案有帮助,请点击”接受答案“并投赞成票。