******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffff928dad48a080, memory referenced. Arg2: 0000000000000011, X64: bit 0 set if the fault was due to a not-present PTE. bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the processor decided the fault was due to a corrupted PTE. bit 4 is set if the fault was due to attempted execute of a no-execute PTE. - ARM64: bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the fault was due to attempted execute of a no-execute PTE. Arg3: ffff928dad48a080, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.PTE Value: Valid Key : AV.Type Value: Execute Key : Analysis.CPU.mSec Value: 1984 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2300 Key : Analysis.IO.Other.Mb Value: 3 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 26 Key : Analysis.Init.CPU.mSec Value: 2015 Key : Analysis.Init.Elapsed.mSec Value: 78080 Key : Analysis.Memory.CommitPeak.Mb Value: 91 Key : Bugcheck.Code.DumpHeader Value: 0x50 Key : Bugcheck.Code.KiBugCheckData Value: 0x50 Key : Bugcheck.Code.Register Value: 0x50 Key : Dump.Attributes.AsUlong Value: 1000 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 100 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Timestamp Value: 2022-05-06T12:50:00Z Key : WER.OS.Version Value: 10.0.22621.1 FILE_IN_CAB: MEMORY.DMP DUMP_FILE_ATTRIBUTES: 0x1000 BUGCHECK_CODE: 50 BUGCHECK_P1: ffff928dad48a080 BUGCHECK_P2: 11 BUGCHECK_P3: ffff928dad48a080 BUGCHECK_P4: 2 WRITE_ADDRESS: ffff928dad48a080 Nonpaged pool MM_INTERNAL_CODE: 2 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System TRAP_FRAME: fffffa8bc6a68ac0 -- (.trap 0xfffffa8bc6a68ac0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=ffff928d977a1040 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=ffff928dad48a080 rsp=fffffa8bc6a68c58 rbp=0000000000000000 r8=0000000000000000 r9=fffffa8bc6a68990 r10=0000fffff804585a r11=fffffa8bc6a68560 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc ffff928d`ad48a080 06 ??? Resetting default scope STACK_TEXT: fffffa8b`c6a68898 fffff804`5867e1ef : 00000000`00000050 ffff928d`ad48a080 00000000`00000011 fffffa8b`c6a68ac0 : nt!KeBugCheckEx fffffa8b`c6a688a0 fffff804`58453c4c : 00000000`00000000 00000000`00000011 fffffa8b`c6a68a59 00000000`00000000 : nt!MiSystemFault 0x22d4bf fffffa8b`c6a689a0 fffff804`58636ddd : 00000060`621f6a82 00000000`00000000 ffff928d`ad48a080 00001f80`00000000 : nt!MmAccessFault 0x29c fffffa8b`c6a68ac0 ffff928d`ad48a080 : ffff928d`a8ff8080 00000003`00000380 00000000`00000000 fffffa8b`c6a69000 : nt!KiPageFault 0x35d fffffa8b`c6a68c58 ffff928d`a8ff8080 : 00000003`00000380 00000000`00000000 fffffa8b`c6a69000 fffffa8b`c6a63000 : 0xffff928d`ad48a080 fffffa8b`c6a68c60 00000003`00000380 : 00000000`00000000 fffffa8b`c6a69000 fffffa8b`c6a63000 00000000`00000000 : 0xffff928d`a8ff8080 fffffa8b`c6a68c68 00000000`00000000 : fffffa8b`c6a69000 fffffa8b`c6a63000 00000000`00000000 00000000`00000000 : 0x00000003`00000380 SYMBOL_NAME: nt!MiSystemFault 22d4bf MODULE_NAME: nt STACK_COMMAND: .cxr; .ecxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 22d4bf FAILURE_BUCKET_ID: AV_X_(null)_nt!MiSystemFault OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {49578414-34a9-c6dc-c795-b8c5552d5975} Followup: MachineOwner ---------
您好！感谢您联系本站支持平台!了解到您目前遇到Windows操作系统出现蓝屏，您不用担心，此问题一般是由于系统中某些应用所属进程或驱动出现问题导致系统宕机引起的，需要您提供您的Minidump文件来分析您系统故障的原因，您可以通过以下方案收集您的Dump日志文件：打开控制面板>>系统>>高级系统设置>>高级>>启动和故障恢复>>设置，写入调试信息>>选择“小内存转储（256KB）”，路径选择默认，确定并重启您的计算机。再次异常关机后，前往C:\Windows\Minidump提取即可。再将您收集到的Minidump文件通过私信提供给。当收到私人消息时，可以通过收到的邮件直接进入私人消息界面，或在本站点头像，点击“我的个人资料”右侧的“.”，选择“查看私人消息”进入私人消息界面。另外，也
DPC_WATCHDOG_VIOLATION(133)TheDPCwatchdogdetectedaprolongedruntimeatanIRQLofDISPATCH_LEVELorabove.Arguments:Arg1:0000000000000001,ThesystemcumulativelyspentanextendedperiodoftimeatDISPATCH_LEVELorabove.Arg2:0000000000001e00,Thewatchdogperiod(inticks).Arg3:fffff8004671c340,casttont!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK,whichcontainsadditionalinformationregardingthecumulativetimeoutArg4:0000000000000000DebuggingDetails:
您好！很抱歉，仅凭您上传的dump文件的部分内容，无法解析出具体的蓝屏原因，需要您将您收集的dump文件发送给，以便于呢进行解析，找到问题所在。已经向您发送了私人讯息，您可以在私人讯息中将dump文件以附件的形式发送过来。当收到私人消息时，可以通过收到的邮件直接进入私人消息界面，或在本站点头像，点击“我的个人资料”右侧的“.”，选择“查看私人消息”进入私人消息界面。期待可以帮助您解决您的问题。如果存在疑问或其他问题，也。Yu
您好！根据您提供的dump文件分析，可能是以下文件出现问题导致的蓝屏，该文件是某三方桌面“美化”软件，用于Windows11任务栏的主题自定义。尝试更新、重新安装或直接卸载它，看看是否可以解决您蓝屏的问题。Yu
您好！请问您的蓝屏问题是否得到了解决？如果没有的话，可以尝试将您再次收集到的dump文件上传过来，会为您进行解析，找到蓝屏的原因，协助您解决这个蓝屏的问题。期待得到您的，如果存在疑问或其他问题，也。Yu
