Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\wch\OneDrive\桌面\120222-13734-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\mysymbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\mysymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 22621 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff805`51200000 PsLoadedModuleList = 0xfffff805`51e12fe0 Debug session time: Fri Dec 2 15:01:33.278 2022 (UTC 8:00) System Uptime: 0 days 0:36:38.988 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................................... Loading User Symbols Loading unloaded module list ............... Cannot read PEB32 from WOW64 TEB32 0a086000 - Win32 error 0n30 For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805`516288f0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffffd89`cb9e5870=000000000000004a 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a) Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL. Arguments: Arg1: 0000000077561cf3, Address of system function (system call routine) Arg2: 0000000000000002, Current IRQL Arg3: 0000000000000000, 0 Arg4: fffffd89cb9e5aa0, 0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 780 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2899 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: 77 Key : Analysis.Init.Elapsed.mSec Value: 13333 Key : Analysis.Memory.CommitPeak.Mb Value: 99 Key : Bugcheck.Code.DumpHeader Value: 0x4a Key : Bugcheck.Code.Register Value: 0x4a Key : Dump.Attributes.AsUlong Value: 1808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 FILE_IN_CAB: 120222-13734-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump BUGCHECK_CODE: 4a BUGCHECK_P1: 77561cf3 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffffd89cb9e5aa0 PROCESS_NAME: ŒŽLހsð.exe BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: fffffd89`cb9e5868 fffff805`5163dfa9 : 00000000`0000004a 00000000`77561cf3 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffffd89`cb9e5870 fffff805`5163de6b : fffff805`4f518000 ffffeec8`31bf76f4 00000000`001702fa 00000000`1356ef10 : nt!KiBugCheckDispatch 0x69 fffffd89`cb9e59b0 00000000`77561cf3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico 0x380 00000000`1356ef08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77561cf3 SYMBOL_NAME: nt!KiSystemServiceExitPico 380 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.900 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 380 FAILURE_BUCKET_ID: RAISED_IRQL_FAULT____L__s_.exe_nt!KiSystemServiceExitPico OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {e5efc25c-f58e-368a-00b4-e27d28ba2909} Followup: MachineOwner ---------

Hi,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,你好,迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面,然后通过OneDriveGoogleDrive共享它们,以便分析并指出导致崩溃的文件。问候,


https://1drv.ms/u/s!AvXXnJx5EdTyeZ1iYGutz9TKZ6o?e=MDseJI此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


你好,感谢分享minidump文件,抱歉晚了minidump文件没有命名任何驱动程序,仅表明ntkrnlmp.exe是一个Windows组件,这意味着其他原因导致系统出现故障,或者它可能是通常由于驱动程序不兼容而发生的内存损坏。如果只出现一次,可能是更新驱动或驱动不兼容造成的。如果它经常发生,请尝试以下步骤来解决此问题:1-检查更新:转到设置>更新和安全>检查更新>安装所有待处理的更新2-使用DDU免费工具完全卸载显卡驱动:https://www-guru3d-com.translate.goog/files-det.然后,安装制造商网站上提供的最新驱动程序。3-卸载任何第三方安全软件并使用免费的Malwarebytes扫描病毒和恶意软件:https://www-malwarebytes-com.translate.goog/mwb.4-以管理员身份运行命令提示符。键入此命令并按回车键:dism.exe/online/cleanup-image/restorehealth然后,键入此命令并按回车键:sfc/scannow5-如果您要超频您的PC,请尝试以它们的库存速度运行所有东西(CPU、GPU、系统内存)。看看问题是否仍然可以重现。或者,关闭XMP配置文件或将其设置为自动。6-从制造商的网站下载并安装最新版本的BIOS和芯片组驱动程序。7-使用免费实用程序MemTest86测试RAM,然后运行完整的8次扫描以测试您的RAM是否存在物理错误:https://www-tenforums-com.translate.goog/tutori.8-运行Windows内存诊断:https://www-howtogeek-com.translate.goog/260813.运行硬盘诊断:https://www-lifewire-com.translate.goog/free-ha.9-如果您愿意这样做,请取出所有系统内存条,检查它们是否有任何明显的缺陷,然后将它们重新插入插槽。确保它们正确安装在插槽中。如果您安装了多根系统内存并且您怀疑其中一根有故障,则可以尝试的一件事是一次仅使用一根内存模块重现该问题。这将帮助您隔离故障模块。10-如果执行上述步骤后问题仍然存在,请启用驱动程序验证程序并让计算机崩溃3次,然后将其禁用并共享新创建的minidump文件:https://www-tenforums-com.translate.goog/tutori.请随时询问您是否需要进一步的帮助。


点赞(72) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部