这是我的电源设置，我待机了很久，今天早上使用电脑，应该像往常一样一移动鼠标，显示器就会亮，。然而，显示器亮了闪了桌面一下，紧接着就进入蓝屏。代码分析如下，看不懂。麻烦工作人员帮忙仔细分析下这个情况是第一次出现的，。如果不再次出现我是不是不用管它Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041922-18250-01.dmp] 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 Machine Name: Kernel base = 0xfffff806`42800000 PsLoadedModuleList = 0xfffff806`4342a230 Debug session time: Tue Apr 19 13:11:27.685 2022 (UTC 8:00) System Uptime: 0 days 17:21:25.696 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ......................... Loading User Symbols Loading unloaded module list ........................... For analysis of this file, run !analyze -v ACPI!ProcessorCopyData 0x189: fffff806`47c14359 488b3b mov rdi,qword ptr [rbx] ds:002b:00000010`08000001=???????????????? 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80647c14359, The address that the exception occurred at Arg3: ffff8509fe1d0188, Exception Record Address Arg4: ffff8509fe1cf9c0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 4999 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 22473 Key : Analysis.Init.CPU.mSec Value: 561 Key : Analysis.Init.Elapsed.mSec Value: 29327 Key : Analysis.Memory.CommitPeak.Mb Value: 103 FILE_IN_CAB: 041922-18250-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80647c14359 BUGCHECK_P3: ffff8509fe1d0188 BUGCHECK_P4: ffff8509fe1cf9c0 EXCEPTION_RECORD: ffff8509fe1d0188 -- (.exr 0xffff8509fe1d0188) ExceptionAddress: fffff80647c14359 (ACPI!ProcessorCopyData 0x0000000000000189) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000001008000001 Attempt to read from address 0000001008000001 CONTEXT: ffff8509fe1cf9c0 -- (.cxr 0xffff8509fe1cf9c0) rax=ffff9f0f95082e80 rbx=0000001008000001 rcx=ffff9f0fb48cd380 rdx=ffff8509fe1d03e0 rsi=0000000000000008 rdi=0000000000000fff rip=fffff80647c14359 rsp=ffff8509fe1d03c0 rbp=ffff8509fe1d0439 r8=ffff9f0fb48cd3a8 r9=ffff8509fe1d03f8 r10=fffff80642f4f101 r11=ffff9f0f87d86330 r12=0000000000000001 r13=0000000000000000 r14=0000000000000008 r15=ffff8902f36b12d0 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202 ACPI!ProcessorCopyData 0x189: fffff806`47c14359 488b3b mov rdi,qword ptr [rbx] ds:002b:00000010`08000001=???????????????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff806434fb390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse 0000001008000001 ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p %s EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000001008000001 EXCEPTION_STR: 0xc0000005 LOCK_ADDRESS: fffff806434449e0 -- (!locks fffff806434449e0) Cannot get _ERESOURCE type Resource @ nt!PiEngineLock (0xfffff806434449e0) Available 1 total locks PNP_TRIAGE_DATA: Lock address : 0xfffff806434449e0 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 STACK_TEXT: ffff8509`fe1d03c0 fffff806`47c13ff9 : ffff8509`fe1d0540 ffff8509`00070000 00000000`00080000 00000000`00070000 : ACPI!ProcessorCopyData 0x189 ffff8509`fe1d04a0 fffff806`47c212cb : ffff8902`f31fc060 ffff9f0f`00000000 fffff806`47c01620 ffff9f0f`87d86b00 : ACPI!IrqArbBootAllocation 0x29 ffff8509`fe1d04d0 fffff806`42fa3a09 : ffff9f0f`87d86bb8 ffff9f0f`87d86be8 ffff9f0f`a68d22a0 00000000`00000000 : ACPI!ArbArbiterHandler 0x9b ffff8509`fe1d0510 fffff806`42fa38ce : ffff8903`049d8cc0 ffff9f0f`a68d22a0 00000000`00000000 ffff9f0f`00000005 : nt!IopBootAllocation 0x95 ffff8509`fe1d0580 fffff806`42fa3800 : ffff9f0f`b48c7ca0 00000000`00000004 ffff8903`08610260 00000000`00000000 : nt!IopAllocateBootResourcesInternal 0x8e ffff8509`fe1d05f0 fffff806`42f3c725 : ffff9f0f`b48c7ca0 00000000`00000000 ffff9f0f`b48c7ca0 00000000`00000000 : nt!IopAllocateBootResources 0x50 ffff8509`fe1d0630 fffff806`42f26fc6 : 00000000`0000003c ffffffff`80004e4c ffff9f0f`b48c7ca0 ffffffff`00000000 : nt!PiQueryAndAllocateBootResources 0x199 ffff8509`fe1d06c0 fffff806`42f29000 : ffff8903`049d8cc0 ffff8903`049d8cc0 00000000`00000001 00000000`00000002 : nt!PiProcessNewDeviceNode 0x9a6 ffff8509`fe1d0890 fffff806`42f39c58 : ffff8903`0dff7600 fffff806`42a07b01 ffff8509`fe1d09b0 fffff806`00000002 : nt!PipProcessDevNodeTree 0x380 ffff8509`fe1d0960 fffff806`42b6e1a6 : 00000001`00000003 ffff8902`f36beaa0 ffff8903`0dff7650 ffff8903`0dff7650 : nt!PiProcessReenumeration 0x88 ffff8509`fe1d09b0 fffff806`42ab86d5 : ffff8902`fee10040 ffff8902`f00e7a20 fffff806`434433a0 fffff806`00000000 : nt!PnpDeviceActionWorker 0x206 ffff8509`fe1d0a70 fffff806`42b55a15 : ffff8902`fee10040 00000000`00000080 ffff8902`f00b20c0 00000000`00000001 : nt!ExpWorkerThread 0x105 ffff8509`fe1d0b10 fffff806`42bfeef8 : ffffc881`49300180 ffff8902`fee10040 fffff806`42b559c0 00000000`009e7800 : nt!PspSystemThreadStartup 0x55 ffff8509`fe1d0b60 00000000`00000000 : ffff8509`fe1d1000 ffff8509`fe1ca000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread 0x28 SYMBOL_NAME: ACPI!ProcessorCopyData 189 MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys IMAGE_VERSION: 10.0.19041.1110 STACK_COMMAND: .cxr 0xffff8509fe1cf9c0 ; kb BUCKET_ID_FUNC_OFFSET: 189 FAILURE_BUCKET_ID: AV_ACPI!ProcessorCopyData OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ed507992-e8d9-ef8e-882b-3df6ffd7938f} Followup: MachineOwner ---------
您好，
