你好!如何解决ACPI.sys导致的蓝屏,万分感谢！

Question

19: kd> !analyze -v
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
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000500, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff804efbc43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4062

    Key  : Analysis.Elapsed.mSec
    Value: 20264

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 703

    Key  : Analysis.Init.Elapsed.mSec
    Value: 36146

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 97

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x31008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_DPC_ACPI!AMLIGetFirstChildNoLock

    Key  : Failure.Hash
    Value: {a50202c9-a010-be04-0277-7c595932f282}

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 500

BUGCHECK_P3: 500

BUGCHECK_P4: fffff804efbc43b0

FILE_IN_CAB:  022326-8234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x31008
  Kernel Generated Triage Dump

FAULTING_THREAD:  17

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffd901`d23dbe68 fffff804`ef2b96e9     : 00000000`0000000a 00000000`01800125 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffd901`d23dbe70 fffff804`ef2b49a8     : ffff0303`69c9b487 fffff804`ef2bf600 00000000`00000002 00000000`00000008 : nt!KiBugCheckDispatch+0x69
ffffd901`d23dbfb0 fffff804`81210ff7     : fffffb00`0000c000 fffffb7d`80000060 fffffb7d`bec00000 fffffb7d`bedf6000 : nt!KiPageFault+0x468
ffffd901`d23dc140 fffff804`8122f608     : ffffc504`1bb32000 00000000`00000001 00000000`00000001 fffffb7d`bedf6c50 : ACPI!AMLIGetFirstChildNoLock+0xb
ffffd901`d23dc170 fffff804`8122ef0b     : ffffc504`1baf5288 00000000`00000001 00000000`00000001 00000000`00000000 : ACPI!AcpiAddTriageNSTree+0x6c
ffffd901`d23dc1a0 fffff804`8122f6d8     : ffffd901`d23dc238 ffffd901`d23dc3a0 fffff804`efb21e00 00000000`00000001 : ACPI!AcpiAddTriageAcpiGlobal+0x31f
ffffd901`d23dc1d0 fffff804`ef1b6d62     : fffff804`8125af50 ffffd901`d23dc3a0 fffff804`efb21e00 ffffc504`098b6280 : ACPI!AcpiDumpRoutine+0x38
ffffd901`d23dc200 fffff804`ef1b534e     : 00000000`00000000 fffff804`8125af50 fffff804`8125af50 fffff804`8125af50 : nt!KiInvokeBugCheckAddTriageDumpDataCallbacks+0x106
ffffd901`d23dc2a0 fffff804`ef1006d7     : 0000ffff`f804ef1b ffffc504`098b6280 2044301d`4266a775 00000000`00000004 : nt!KeBugCheck2+0xe4e
ffffd901`d23dca30 fffff804`eee89236     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx+0x107
ffffd901`d23dca70 fffff804`eee8876a     : fffff804`efbc43b0 00000000`00000000 fffff780`00000320 ffffd901`d23c0180 : nt!KeAccumulateTicks+0x596
ffffd901`d23dcae0 fffff804`eee8843c     : 00000000`00000018 00000000`00000001 00000000`0040c34f ffffd901`d23c0180 : nt!KiUpdateRunTime+0xca
ffffd901`d23dcca0 fffff804`eee8ecc9     : 00000000`00000000 ffffd60c`f1e8f400 ffffd901`d23c0180 00000000`0000000f : nt!KiUpdateTime+0x37c
ffffd901`d23dce60 fffff804`eee8f76b     : ffffc504`09782460 00000000`00000000 ffffc504`09782510 fffff804`efb8e600 : nt!KeClockInterruptNotify+0x2e9
ffffd901`d23dcf50 fffff804`ef2a782e     : ffffd60d`01c9ee02 ffffc504`09782460 00006c39`0e994bbf 00000103`1114f416 : nt!KiCallInterruptServiceRoutine+0x31b
ffffd901`d23dcfb0 fffff804`ef2a803c     : 00000000`00000000 00000000`00000000 ffffd901`d2585180 ffffc504`09842040 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffd60c`f1e8f4b0 fffff804`ef0297e3     : 00000000`00200000 00000000`00000200 ffff1240`be2b9867 ffffd901`d23c0180 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffd60c`f1e8f640 fffff804`eee2a4da     : 00000002`00000013 ffffd60c`00000000 ffffd60d`01c9ee90 fffff804`eee899ba : nt!KiSwapDirectoryTableBaseTarget+0x53
ffffd60c`f1e8f6a0 fffff804`eeec7916     : 00000000`00000000 00000000`00000000 00000103`0529f275 ffffc504`098b6280 : nt!KiExecuteAllDpcs+0x66a
ffffd60c`f1e8f8f0 fffff804`ef2a66be     : ffffd901`d23c0180 ffffd901`d23c0180 00000000`00000000 fffff804`ef1bb200 : nt!KiRetireDpcList+0x326
ffffd60c`f1e8fb80 00000000`00000000     : ffffd60c`f1e90000 ffffd60c`f1e89000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND: ~23 ; .cxr ; kb

SYMBOL_NAME:  ACPI!AMLIGetFirstChildNoLock+b

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION:  10.0.26100.4484

BUCKET_ID_FUNC_OFFSET:  b

FAILURE_BUCKET_ID:  0x133_DPC_ACPI!AMLIGetFirstChildNoLock

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a50202c9-a010-be04-0277-7c595932f282}

Followup:     MachineOwner
---------

Answer 1

请上传您拥有的所有 minidump 文件，我会检查这些文件，看看能否找到系统崩溃的潜在原因。

非常重要 - 请勿上传大型的 Memory.dmp 文件。

请注意，我无法从百度云盘下载文件，请使用其他云服务上传，例如 OneDrive 或 www.lanzv.com。

打开 Windows 文件资源管理器。

导航至 C:\Windows\Minidump 文件夹。

将所有 minidump 文件复制到桌面，然后将它们压缩成 zip 文件。

将 zip 文件上传到云端（例如 OneDrive），然后选择共享并获取共享链接。

然后将 zip 文件的链接发布到这里，以便我们帮您查看。

.

.

---

标准免责声明：本网站并非微软官方网站。该页面似乎提供准确、安全的信息。请注意网站上的广告，这些广告可能宣传一些通常被归类为 PUP（潜在有害程序）的产品。在决定下载和安装任何产品之前，请务必对该产品进行充分的研究。