关于#windows#的问题:用过联想自带的驱动软件,360驱动软件 没有啥用重装过电脑

电脑玩着玩着就死机蓝屏,有时候刚刚开机就蓝屏
主机是联想拯救者 刃7000k

用windbg preview 显示是ACPL.sys导致蓝屏
代码 DPC_WATCHDOG_VIOLATION


Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.







```c++
```c++
Loading Dump File [C:\WINDOWS\Minidump\021222-6078-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 = 0xfffff800`82600000 PsLoadedModuleList = 0xfffff800`8322a2b0
Debug session time: Sat Feb 12 19:57:51.873 2022 (UTC + 8:00)
System Uptime: 0 days 23:18:12.703
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:
fffff800`829f72e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb201`38f01e20=0000000000000133
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff800832fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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: 2640

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2634

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

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

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


FILE_IN_CAB:  021222-6078-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff800832fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffb201`38f01e18 fffff800`82a1f67e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`832fb320 : nt!KeBugCheckEx
ffffb201`38f01e20 fffff800`82816953     : 00000dff`016e520f ffffb201`38eaf180 00000000`00000000 ffffb201`38eaf180 : nt!KeAccumulateTicks+0x2064ce
ffffb201`38f01e80 fffff800`8281643a     : ffff9e07`c6d14260 ffff9c85`45f0d740 00000000`00000000 ffff9e07`c6ca5040 : nt!KeClockInterruptNotify+0x453
ffffb201`38f01f30 fffff800`828de195     : ffff9e07`c6d14260 00000000`00000000 00000000`00000000 fffff8e3`f184d3e0 : nt!HalpTimerClockIpiRoutine+0x1a
ffffb201`38f01f60 fffff800`829f8d8a     : ffff9c85`45f0d740 ffff9e07`c6d14260 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb201`38f01fb0 fffff800`829f92f7     : 00000000`b76e775b fffff800`855a2490 ffff9e07`d95c3010 ffff9e07`d95c3010 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9c85`45f0d6c0 fffff800`828d7b0c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9c85`45f0d850 fffff800`828d7ad8     : fffff800`85601f98 ffffb201`38eaf180 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x2c
ffff9c85`45f0d880 fffff800`855b0bab     : ffff9e07`d95c3198 00000000`00040408 00000000`00000000 ffff9e07`d95c3198 : nt!KeAcquireSpinLockRaiseToDpc+0x88
ffff9c85`45f0d8b0 fffff800`85585243     : ffff9e07`d95c3010 ffff9e07`00040408 ffff9e07`d95c3198 00000000`00000300 : ACPI!ACPIInterruptEventCompletion+0x2b
ffff9c85`45f0d8e0 fffff800`85584685     : ffff9e07`c71ae000 ffff9e07`d95c3010 00000000`00000000 00000000`00000019 : ACPI!RunContext+0x833
ffff9c85`45f0da10 fffff800`855aa325     : ffff9e07`d95c3010 00000000`00000080 ffff9e07`d95c3010 00000000`0000030a : ACPI!InsertReadyQueue+0x2a5
ffff9c85`45f0da70 fffff800`855a8c97     : fffff800`85602790 00000000`00000000 00000000`00000000 ffff9c85`45f04c00 : ACPI!RestartCtxtPassive+0x35
ffff9c85`45f0daa0 fffff800`82955995     : ffff9e07`c6ca5040 fffff800`855a8b90 00000000`00000000 ffff9e07`c6cc21c0 : ACPI!ACPIWorkerThread+0x107
ffff9c85`45f0db10 fffff800`829fe938     : ffffb201`38eaf180 ffff9e07`c6ca5040 fffff800`82955940 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff9c85`45f0db60 00000000`00000000     : ffff9c85`45f0e000 ffff9c85`45f07000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  ACPI!ACPIInterruptEventCompletion+2b

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION:  10.0.19041.1110

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2b

FAILURE_BUCKET_ID:  0x133_ISR_ACPI!ACPIInterruptEventCompletion

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {66ccecbc-0d7a-4186-e177-11481af8fb9f}

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

用过联想自带的驱动软件,360驱动软件 没有啥用
重装过电脑,过几个月之后又开始蓝屏

希望能够解决这个问题

WIN10 系统有很多的不兼容性,尝试更换一下不同版本的系统。
至于驱动去官网进行下载,联想是有对应驱动噶。

Acpi.sys属于电源管理驱动程序,重装后没问题,说明你的电源管理驱动在几个月后自动更新了。你卸载电源驱动,装上不会蓝屏的驱动,找一下联想的驱动管理相关软件,把自动更新去掉