Unsolved
2 Posts
0
255
July 3rd, 2023 19:00
System interrupt runaway problem on T3620
I’m using Precision Tower 3620, but recently the system interrupts have been running amok every day and consuming CPU. I’ve spent a lot of time trying to solve this problem. And I was able to find my way to the following community:
High CPU Usage - System/ACPI.sys - GPE.L6F Storm [Omen 15/17/Zbook 17 G5/Other HP Devices]
Here, I learned to get ACPI logs with the command “logman start HPbug -ets -p Microsoft-Windows-Kernel-Acpi -o C:\x.etl”. (Be careful because if you take logs from before the problem occurs, it will become huge in size. It is sufficient to run it only for a few seconds after the problem occurs.) As a result, I found out that L6F storm is still the cause.
I am convinced that this problem is a BIOS bug. However, since I purchased this workstation second-hand, I cannot receive support. I would like someone who has the same problem to report this bug to DELL.
I apologize if this is not what I should have written here.
0 events found
Chino de Oro
11 Legend
•
8.3K Posts
•
46K Points
0
July 4th, 2023 12:00
To be certain that it was a BIOS issue, considering to downgrade to previous BIOS version(s) for testing. So far, haven't seen any user complaint post regarding BIOS issue for the 3620
I guess that when there is a large number of posts concerning issue caused by a newly released firmware, Dell social media and forum mods will be involved to report problem.
bradthetechnut
9 Technologist
•
9.5K Posts
•
40.1K Points
0
July 4th, 2023 18:00
Something that might be worth a try: How to Perform a BIOS or CMOS Reset and Clear the NVRAM on Dell Computers and use a brand new size 2032 CMOS battery if 5+ years old.
soyjoy
2 Posts
0
July 4th, 2023 18:00
I faced this problem with BIOS version 2.22 and updated it to 2.25. However, the problem was not resolved.
Furthermore, this problem has been around since I purchased this workstation two years ago, but the frequency of occurrence has decreased over time, so I left it as it was. Recently, the frequency of occurrence has increased, so I think something has changed by Windows Update and that is triggering it.
This problem often occurs during the time when I leave my PC on while sleeping, that is, when the monitor is off.
This workstation is primarily used for work, and since few people use it in this way, I suspect that there are no reports.