Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\052522-11171-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 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff802`1d800000 PsLoadedModuleList = 0xfffff802`1e413450 Debug session time: Wed May 25 15:22:11.423 2022 (UTC 8:00) System Uptime: 0 days 2:51:02.204 Loading Kernel Symbols .. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ............................................................. ................................................................ ................................................................ ............................................ Loading User Symbols Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`1dc1d050 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffffe86`633d3220=0000000000000139 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 000000000000000a, Indirect call guard check detected invalid control transfer. Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1171 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 9884 Key : Analysis.Init.CPU.mSec Value: 249 Key : Analysis.Init.Elapsed.mSec Value: 72182 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Dump.Attributes.AsUlong Value: 808 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 052522-11171-01.dmp DUMP_FILE_ATTRIBUTES: 0x808 Kernel Generated Triage Dump BUGCHECK_CODE: 139 BUGCHECK_P1: a BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 TRAP_FRAME: 0000000000000000 -- (.trap 0x0) EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0) Cannot read Exception record @ 0000000000000000 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe STACK_TEXT: fffffe86`633d3218 fffff802`1dc2645e : 00000000`00000139 00000000`0000000a 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffffe86`633d3220 fffff802`1debe6cc : fffffe86`633d33e0 ffffe586`d805deb0 ffffe586`df0486d0 ffffe586`ea24eb00 : nt!guard_icall_bugcheck 0x1e fffffe86`633d3250 fffff802`1dec2669 : 00000000`0000001d fffffe86`633d3410 fffffe86`633d3450 00000000`00000000 : nt!CmpCallCallBacksEx 0x42c fffffe86`633d3380 fffff802`1deca057 : fffff802`1dec2201 ffffc30e`00000000 ffffc30e`73baaaa0 00000000`00000001 : nt!CmpParseKey 0x3c9 fffffe86`633d3570 fffff802`1dec9482 : ffffc30e`73baaaa0 fffffe86`633d37a0 00000000`00000040 ffffc30e`601efa60 : nt!ObpLookupObjectName 0x697 fffffe86`633d3710 fffff802`1dec44a8 : fffffe86`00000000 ffffc30e`601efa60 00000070`8befe030 00000000`00000000 : nt!ObOpenObjectByNameEx 0x1f2 fffffe86`633d3840 fffff802`1dfae718 : 00000070`8befdf88 000001d9`06f3ccf0 fffffe86`633d3b60 fffff802`1dec5869 : nt!CmOpenKey 0x2c8 fffffe86`633d3a90 fffff802`1dc2fa68 : ffffc30e`9068e080 ffffc30e`710f0b00 000001d9`08071360 ffffc30e`00000000 : nt!NtOpenKeyEx 0x48 fffffe86`633d3ae0 00007ffe`5bfb11d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd 0x28 00000070`8befdf68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`5bfb11d4 SYMBOL_NAME: nt!guard_icall_bugcheck 1e MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.1 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1e FAILURE_BUCKET_ID: 0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {391a5384-38fb-03d6-baa8-4a74bc53c199} Followup: MachineOwner ---------
Hi,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,嗨，黑花飞，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，
https://drive.google.com/file/d/1zMHyUbIvCWcjrgNgkXSwclaJTVROVJCI/view?usp=sharing此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
嗨，黑花飞，感谢您分享小型转储文件。minidump文件没有命名任何驱动程序，仅指示ntkrnlmp.exe这是一个Windows组件，这意味着其他东西导致系统出现故障，或者它可能是通常由于驱动程序不兼容而发生的内存损坏。您的计算机是第一次遇到BSOD吗？如果只是一次BSOD，很可能是更新驱动程序引起的。如果您的计算机遇到其他BSOD，请启用驱动程序验证程序并让计算机崩溃4次然后禁用它并共享新创建的minidump文件：https://www-tenforums-com.translate.goog/tutori.请随时询问您是否需要进一步的帮助。
电脑无缘无故又绿屏了，麻烦看看是什么情况，谢谢了文件链接https://drive.google.com/file/d/1a0HlF9P6xOTCldeZvPpZhyHQouNgxedq/view?usp=sharingMicrosoft(R)WindowsDebuggerVersion10.0.25111.1000AMD64Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile
你好minidump文件指示内存损坏。要解决此问题，请尝试以下步骤并跳过您已经尝试过的步骤：1-如果您要对PC进行超频，请尝试以它们的存储速度运行所有东西（CPU、GPU、系统内存）。看看问题是否仍然可以重现。或者，关闭XMP配置文件或将其设置为自动。2-使用免费实用程序MemTest86测试RAM，然后运行完整的8次扫描以测试您的RAM是否存在物理错误：https://www-tenforums-com.translate.goog/tutori.3-如果您愿意这样做，请取出所有系统内存条，检查它们是否有任何明显的缺陷，然后将它们重新插入插槽。确保它们正确安装在插槽中。如果您安装了多根系统内存并且您怀疑其中一根有故障，那么可以尝试的一件事是一次仅使用一根内存模块重现该问题。这将帮助您隔离故障模块。4-尝试为您的主板刷新最新版本的系统BIOS。从制造商的网站下载最新版本的BIOS，以提高与各种内存模块的兼容性。5-从设备管理器更新所有驱动程序或下载然后安装制造商网站上提供的最新驱动程序。我
