win10电脑频繁出现蓝屏，系统日志文件格式无法发出来，这是导入到WinDbg后的
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : 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.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46
Microsoft (R) Windows Debugger Version 10.0.29507.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File
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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff803`54000000 PsLoadedModuleList = 0xfffff803`54c2a420
Debug session time: Mon Feb2 11:10:57.301 2026 (UTC + 8:00)
System Uptime: 18 days 2:18:20.170
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................................
Loading User Symbols
Unable to read KTHREAD address fffff80354d27ab8
Unable to read KTHREAD address fffff80354d27ab8
PEB is paged out (Peb.Ldr = 000000c1`9832e018).Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
Unable to read KTHREAD address fffff80354d27ab8
Unable to read KTHREAD address fffff80354d27ab8
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`543fd5c0 48894c2408 mov qword ptr ,rcx ss:0018:ffffab85`b18df400=0000000000000162
9: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000c1`9832e018).Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE (162)
A lock tracked by AutoBoost was released by a thread that did not own the lock.
This is typically caused when some thread releases a lock on behalf of another
thread (which is not legal with AutoBoost tracking enabled) or when some thread
tries to release a lock it no longer owns.
Arguments:
Arg1: ffffbc8e6c8e1080, The address of the thread
Arg2: ffffbc8e61f0d548, The lock address
Arg3: 00000000ffffffff, The session ID of the thread
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for 360Hvm64.sys
*** WARNING: Check Image - Checksum mismatch - Dump: 0x180284, File: 0x180292 - C:\ProgramData\Dbg\sym\BTHport.sys\5202AECA187000\BTHport.sys
KEY_VALUES_STRING: 1
Key: Analysis.CPU.mSec
Value: 1250
Key: Analysis.Elapsed.mSec
Value: 6518
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: 484
Key: Analysis.Init.Elapsed.mSec
Value: 21919
Key: Analysis.Memory.CommitPeak.Mb
Value: 131
Key: Analysis.Version.DbgEng
Value: 10.0.29507.1001
Key: Analysis.Version.Description
Value: 10.2511.5.1 amd64fre
Key: Analysis.Version.Ext
Value: 1.2511.5.1
Key: Bugcheck.Code.LegacyAPI
Value: 0x162
Key: Bugcheck.Code.TargetModel
Value: 0x162
Key: Failure.Bucket
Value: 0x162_360Hvm64!unknown_function
Key: Failure.Hash
Value: {966ceb41-0d9d-0d1c-c6fd-92e8dc6756de}
Key: WER.OS.Branch
Value: vb_release
Key: WER.OS.Version
Value: 10.0.19041.1
Key: WER.System.BIOSRevision
Value: 5.27.0.0
BUGCHECK_CODE:162
BUGCHECK_P1: ffffbc8e6c8e1080
BUGCHECK_P2: ffffbc8e61f0d548
BUGCHECK_P3: ffffffff
BUGCHECK_P4: 0
FILE_IN_CAB:020226-8281-01.dmp
FAULTING_THREAD:ffffbc8e6c8e1080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT:1
PROCESS_NAME:JX3ClientX64.exe
STACK_TEXT:
ffffab85`b18df3f8 fffff803`5444b57a : 00000000`00000162 ffffbc8e`6c8e1080 ffffbc8e`61f0d548 00000000`ffffffff : nt!KeBugCheckEx
ffffab85`b18df400 fffff803`54637f9f : 00000000`00000001 ffffbc8e`00000000 00000000`00000000 00000000`002e0000 : nt!UNLOCK_ADDRESS_SPACE+0x1b669a
ffffab85`b18df460 fffff803`545f8993 : ffffab85`b18df630 00000000`00000000 ffffab85`00000004 00000000`00000001 : nt!MiReserveUserMemory+0x3af
ffffab85`b18df530 fffff803`545fa8eb : ffffbc8e`00000000 ffffab85`00000000 00000000`00000000 000000c1`9f0fe688 : nt!MiAllocateVirtualMemory+0x343
ffffab85`b18df6b0 fffff803`6e56e43a : ffffffff`ffffffff 00000000`00000000 00000000`00000000 000000c1`9f0fe628 : nt!NtAllocateVirtualMemory+0x1ab
ffffab85`b18df860 ffffffff`ffffffff : 00000000`00000000 00000000`00000000 000000c1`9f0fe628 00000000`00001000 : 360Hvm64+0x1e43a
ffffab85`b18df868 00000000`00000000 : 00000000`00000000 000000c1`9f0fe628 00000000`00001000 00007ffb`00000004 : 0xffffffff`ffffffff
SYMBOL_NAME:360Hvm64+1e43a
MODULE_NAME: 360Hvm64
IMAGE_NAME:360Hvm64.sys
STACK_COMMAND: .process /r /p 0xffffbc8e61f0d080; .thread 0xffffbc8e6c8e1080 ; kb
BUCKET_ID_FUNC_OFFSET:1e43a
FAILURE_BUCKET_ID:0x162_360Hvm64!unknown_function
OS_VERSION:10.0.19041.1
BUILDLAB_STR:vb_release
OSPLATFORM_TYPE:x64
OSNAME:Windows 10
FAILURE_ID_HASH:{966ceb41-0d9d-0d1c-c6fd-92e8dc6756de}
Followup: MachineOwner
---------
您好，这个需要看完整的dump文件，您说复制不出来，主要是提示啥啊，您可以先关闭我们的核晶防护试试看，看看关闭核晶后是否还有蓝屏问题
页:
[1]