STARRAIN@ROG wrote:
Hi Jimbo93,
I'm afraid I have some questions about the video.
Do you mean wmiPrvSE.exe is high CPU usage or the CPU usage of wmiPrvSE.exe keep changing so you think it is a sign of an issue?
If you uninstall Armoury Crate, this CPU activity will disappear, so you think it is caused by Armoury Crate?
If yes, may I have a video about Armoury Crate uninstalled?
Did you put Armoury Crate just in background or did you adjust any settings in Armoury Crate when record the video?
Thank you.
I am happy to respond to your questions STARRAIN. The wmiPrvSE.exe cpu usage does seem out of the ordinary. I can easily disable Armoury Crate services and programs and run that video. I prefer not to uninstall it again because other than this symptom its working reasonably well for like 24 hours. I would really like to let it settle and watch for other problems for a few days at this point.
This cpu activity/ wmi activity has been connected to Armoury Crate since the first time I installed it, Since then I have reinstalled windows and I documented that in a post some weeks back. The only way to stop the wmi activity from being what I consider excessive is to restart windows management instrumentation service, but other programs like windows defender don't like that so not really an option. In conjunction with this cpu activity is a ton of errors in the WMI activity log. My theory is that there is some kind of issue with the Armoury Crate motherboard device software on this system. But maybe it is normal, that is the question.
I continue to look for answers about Armoury Crate instability. Here is a snapshot of my system reliability below, today is good so far, all the errors are from yesterday and earlier. Logging out and back into windows, or rebooting the pc, often results in crashing Armoury Crate service especially ArmourySocketServer.exe. But today it is better. I shared some change I made yesterday having to do with windows prefetch setting. Prefetch Off seems better for Armoury Crate. The crashing of the ArmourySocketServer.exe seems to throw the AC RGB devices out of whack. and things get progressively worse. So now if it crashes I reset the AC app, I have posted elsewhere about that. But I need to see how it goes for a few days since the change to prefetch. Maybe I won't need to reset it again.
When I took the video above, the AC app was closed, shutdown, but all the startups were enabled as you can see in the list of running processes. If the AC app had been opened the video would not be that much different, maybe 1 percent more cpu usage, wmi process the same. I will post the video with no AC processes enabled in the next couple of hours. Thank you for taking the time STARRAIN.
🙂
