电脑每天都要蓝屏,唉。。。。今天将最新的这个蓝屏分析出来的代码发上去,麻烦大神们帮忙分析,解决一下,谢谢。Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be 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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`09a00000 PsLoadedModuleList = 0xfffff802`0a62a250
Debug session time: Fri Sep 2 18:38:11.650 2022 (UTC + 8:00)
System Uptime: 0 days 6:28:02.229
Loading Kernel Symbols
...............................................................
................................................................
..................Page 3e8d16 not present in the dump file. Type ".hh dbgerr004" for details
....Page 3e26af not present in the dump file. Type ".hh dbgerr004" for details
.Page 3eb379 not present in the dump file. Type ".hh dbgerr004" for details
.........................................
.
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000089`22017018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`09df88c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc889`59ac17f0=0000000000000162
6: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffdc0bbfe7d080, The address of the thread
Arg2: ffffdc0bc1557f08, The lock address
Arg3: 00000000ffffffff, The session ID of the thread
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2468
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2873
Key : Analysis.Init.CPU.mSec
Value: 1374
Key : Analysis.Init.Elapsed.mSec
Value: 16930
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.DumpHeader
Value: 0x162
Key : Bugcheck.Code.KiBugCheckData
Value: 0x162
Key : Bugcheck.Code.Register
Value: 0x162
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 162
BUGCHECK_P1: ffffdc0bbfe7d080
BUGCHECK_P2: ffffdc0bc1557f08
BUGCHECK_P3: ffffffff
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
PROCESS_NAME: MsMpEng.exe
STACK_TEXT:
ffffc889`59ac17e8 fffff802`09e2cb8a : 00000000`00000162 ffffdc0b`bfe7d080 ffffdc0b`c1557f08 00000000`ffffffff : nt!KeBugCheckEx
ffffc889`59ac17f0 fffff802`09c47e44 : 00000000`00000001 ffffdc0b`00000001 ffffdc0b`00000001 ffffdc0b`00000000 : nt!MiFinishVadDeletion+0x1d724a
ffffc889`59ac1890 fffff802`0a07d4b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0xae4
ffffc889`59ac19a0 fffff802`0a07d292 : ffffdc0b`c0557ee0 00000000`00000000 ffffdc0b`bdf7a080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffc889`59ac19d0 fffff802`0a07d109 : ffff9556`f634bb2d 00000089`2437e400 00000000`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x152
ffffc889`59ac1ab0 fffff802`09e0a2b8 : ffffdc0b`bfe7d080 000001bf`70e00000 ffffc889`59ac1b80 ffffdc0b`bdf7a080 : nt!NtUnmapViewOfSectionEx+0x99
ffffc889`59ac1b00 00007ffe`b30708b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000089`2437e578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`b30708b4
SYMBOL_NAME: nt!MiFinishVadDeletion+1d724a
MODULE_NAME: nt
STACK_COMMAND: .cxr; .ecxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 1d724a
FAILURE_BUCKET_ID: 0x162_nt!MiFinishVadDeletion
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {76bbccac-c7ba-6d1a-4914-edaf6e42c402}
Followup: MachineOwner
--------- 欢迎访问本站!。若是有超频,降压等,建议恢复正常,xmp也关闭。若是有使用虚拟机,模拟器,手游助手等,建议卸载。然后参考以下链接,检测一下内存和硬盘:https://answers.microsoft.com/zh-hans/windows/f.若是硬盘和内存完好,建议到电脑品牌的官网更新一下bios,覆盖安装一下芯片组驱动,硬盘相关的驱动(例如英特尔快速存储技术驱动),请勿使用第三方的驱动安装程序。完成后在任务栏搜索框输入cmd,点击右侧的以管理员身份运行,输入:sfc/SCANNOW(按下Enter键)Dism/Online/Cleanup-Image/ScanHealth(按下Enter键)Dism/Online/Cleanup-Image/CheckHealth(按下Enter键)DISM/Online/Cleanup-image/RestoreHealth(按下Enter键)RD/S/Q"%WinDir%\System32\GroupPolicyUsers"(按下Enter键)RD/S/Q"%WinDir%\System32\GroupPolicy"(按下Enter键)gpupdate/force(按下Enter键)重启电脑。看下是否恢复正常。
欢迎访问本站!。若是有超频,降压等,建议恢复正常,xmp也关闭。若是有使用虚拟机,模拟器,手游助手等,建议卸载。然后参考以下链接,检测一下内存和硬盘:https://answers.microsoft.com/zh-hans/windows/f.若是硬盘和内存完好,建议到电脑品牌的官网更新一下bios,覆盖安装一下芯片组驱动,硬盘相关的驱动(例如英特尔快速存储技术驱动),请勿使用第三方的驱动安装程序。完成后在任务栏搜索框输入cmd,点击右侧的以管理员身份运行,输入:sfc/SCANNOW(按下Enter键)Dism/Online/Cleanup-Image/ScanHealth(按下Enter键)Dism/Online/Cleanup-Image/CheckHealth(按下Enter键)DISM/Online/Cleanup-image/RestoreHealth(按下Enter键)RD/S/Q"%WinDir%\System32\GroupPolicyUsers"(按下Enter键)RD/S/Q"%WinDir%\System32\GroupPolicy"(按下Enter键)gpupdate/force(按下Enter键)重启电脑。看下是否恢复正常。
感谢,若是没有手动更改,主板等默认是不会超频的。可以看下是否有xmp功能,可以关闭一下。另外是否有amd控制面板等,可以看下是否有超频等相关的设置。
感谢,若是没有手动更改,主板等默认是不会超频的。可以看下是否有xmp功能,可以关闭一下。另外是否有amd控制面板等,可以看下是否有超频等相关的设置。
感谢,建议看下是否有恢复默认的,建议恢复默认。然后卸载或禁用该程序,暂时不运行。