I'm waiting after asus support answer...
Don't think and i don't know if putting X299 prime bios in a X299 R6E can work.
Silent Scone wrote:
I'm glad. Here's your sticker.
Like I said, we're more open-minded here (usually). The thread title is even called "Single core - 100% CPU - high interrupts on ACPI". Which is exactly what me and other users are having in tandem with using certain utilities.
Probably worth pointing out that disabling TB3 isn't a fix, either. If you're happy simply doing this in your instance, then perhaps it's best to simply stop commenting.
There’s an obvious abuser:
ACPI method \_GPE._L61 has high frequency 497565.
The frequency is per 5 minutes and… this number is just astonishing. This means _L61 GPE interrupt is flooding system. In a nutshell, the firmware keeps sending us (acpi.sys) the interrupts on 61st GPE pin and expects it (acpi.sys) to execute the firmware provided method - \_GPE._L61.. which we politely do (as contracted). It’s an OEM issue to investigate
Hard to believe how dense you are for someone boasting about being "open-minded". You add little value to this thread given how many users have already confirmed that Aida has never been installed. Take the Aida issue to a different thread if that is specifically related to that program. Try to be "open-minded" here. For the rest of us who have never heard of that program and are having ACPI.sys issues due to ASUS motherboard firmware, which for the record has been confirmed by Microsoft employees to be an ASUS firmware root issue (I have emails of proof from them that I have already forwarded to ASUS support), we need to exchange information and try to get ASUS to acknowledge this is on them to fix.
Again, why don't you practice what you preach and take the aida issue in a separate thread. They share the same symptom but aren't related. It's time YOU stop commenting and create a separate thread for your aida issue. Be a big boy and move on.
In short, here are the facts as of today, April 23rd:
- Microsoft has confirmed multiple times in email to me that this is an ASUS firmware issue.
- The ACPI owners have confirmed that this is an ASUS firmware issue. See below for a detailed response from them.
- Aida users are having issues with their program, but while the symptom is similar, it is a completely different issue, as most users here are not using Aida. It's as if a doctor is saying a normal headache due to fatigue is related to a brain tumor, since they both cause a similar symptom. It's ludicrous and counter-productive to this thread. A new thread has to be created for Aida users. Most people here suffering from this bug have never installed Aida nor used it.
- ASUS has yet to acknowledge that it's an issue on their part, despite the overwhelming evidence and log inspection done by Microsoft. I have tried to get them in touch with the Microsoft employees helping me, but they haven't reached out yet. More pressure on them is needed.
- Thunderbolt 3 seems to be one of the root causes. I use TB3 and have this issue, as do the other people in this thread with the same issue.
Here is a detailed comment on the logs from a Microsoft senior programmer. He got in touch with the ACPI owners and passed along the following information. For the record, I got written permission to share this information from private email communication we had.
And in case you don't understand, OEM = ASUS. It cannot be more clear that ASUS needs to investigate this bug and solve it themselves. Microsoft has confirmed this bug is on ASUS, so have the ACPI owners.
I have one core running full blast as well it seems. As soon as I closed out Aida64 it dropped right off. Started it back up and one core picked right up again. I use it to monitor some temps for my Aquaero controller. i guess i will try Hwinfo64 and see if the same thing persists.
For me it seems Aida64 was the culprit. Killed it and tried Hwinfo and on several reboots no core going full bore at startup. I will monitor to see if it stays this way.
Silent Scone wrote:
Yes, that's fine.
For me, following my post worked - but it's not necessarily the same root cause. I'm also running insider build 171115.
Wake on magic packet isn't enabled by default, either.
Somebody got some answer from his ticket?
Because on my side nothing...
Silent have you some news from AIDA 64 team?
Silent Scone wrote:
Nothing yet. These things can take time. Seems a similar issue with the EC readout causing latency is repeatable on other platforms, too. (Z370)