Windows 10: 'System Interrupts' which caused by ACPI.sys consumes full utilization on one single thread...

System Interrupts which is ACPI.sys consumes full utilization on one single thread of i5-10400F.


Probably caused by ACPI.sys High in 'ISR Count' and 'DPC Count', though the execution time is normal green condition on latencyMon.

Already searched the solution on google and implemented them, still the problem persists.


Windows 10 Pro is on fresh install. Already Updated all the drivers already from the manufacture Asrock website.


Remove the keyboard, mouse, wifi adapter didn't solve the problem.


Change the power-plan to high performance also didn't solve the problem.


Disable the power saving plan management in wifi adapter, etc also didn't solve the problem.


Processor: Intel i5 10400F
Motherboard: LGA1200 Asrock B460M Pro4
DDR4 Klevv KD48GU880-36A160U = 32GB 3200Mhz
Adata NVME SX8200 Pro 512GB

Zotac Nvidia 750 Ti

BIOS version: 1.2 Newest - All Default mode

Operating System:
Windows 10 Pro 2004 - OS Build 19041.421
Experience Pack 120.2212.31.0


What really cause the problem?




:)

 

CPU Util/usage: what is "System Interrupts" process....


while trying to figure why current Goog Chrome eats cpu's, I was surprised to see a generic "System Interrupts" listed in Task Manager in windows 10, constantly munching 40-50% of cpu - with no identity or info shown.....
what is that? a logging util for feedback? debugger?
any ideas? it exacerbates the problem I'm chasing with Chrome,, which seems to afflict W7/8/8.1/10 even with a fresh install

 

High CPU usage by ACPI.sys ("system" process)

Hello Lamiclem,

Just a quick rundown, the Acpi.sys acts as the interface between the operating system and the ACPI BIOS. The responsibilities of Acpi.sys include support for power management and Plug and Play (PnP) device enumeration. With that in mind, Acpi.sys issues
can be caused by a variety of hardware, firmware, driver or software issues.

As a first isolation step, I would advise starting your PC in Safe Mode. If the issue persists, try
Clean Boot as a second option. These two tests could tell us if it is a possible hardware, or a software issue.
Try both steps, observe if the issue will persist on either of the two and let us know.

if you have other hardware devices connected to your PC, try to disconnect them temporarily and and check for any changes in the Task Manager.

Another step that we can try is SFC and DISM. This is to check for any system file corruption, and fix it along the process. Please refer to
this article from
ZigZag3143 for more information and steps.

Try out the suggestions mentioned above and if you encounter any error messages, or if it shows any improvements, please do let us know by replying to this thread so we can get back to you.

 

Watchdog violation caused by acpi.sys

My windows 10 laptop has been experiencing some issues with startup recently. It takes a very long time and many hard restarts before it will finally boot.

After I finally managed to get the computer to boot, I looked through the event viewer and found a critical Kernel-Power error with event id 41 and task category 63. Upon further inspection and looking at the crash dumps I found
that it was being caused by a DCP_Watchdog_Violation with the error code 133. As far as I know, that is caused by some bad drivers, which I have had some other issues with.

In the crash dump it said that the Watchdog_Violation was cause by ACPI.sys, which apparently has to do with my system power management. I'm just not sure what to do about that.

I can't upload the full crash dump at the moment due to slow internet, Here is the full crash log, and here
are what I think are the relevant sections of the dump:

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: 0000000000000501, The DPC time count (in ticks).

Arg3: 0000000000000500, The DPC time allotment (in ticks).

Arg4: 0000000000000000

FAULT_INSTR_CODE: ffffba

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: ACPI!ACPIEcLogAction+138

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d17f

BUCKET_ID_FUNC_OFFSET: 138

FAILURE_BUCKET_ID: 0x133_DPC_ACPI!ACPIEcLogAction

BUCKET_ID: 0x133_DPC_ACPI!ACPIEcLogAction

PRIMARY_PROBLEM_CLASS: 0x133_DPC_ACPI!ACPIEcLogAction

How do I go about fixing this?