This change affects the way that CPU utilization is computed. Starting with Windows 8, a change was made to the way that Task Manager and Performance Monitor report CPU utilization. (This does not mean your observations about Win11 22H2 aren't correct, they may be true too.) If you want the long version, here it is: With all that said, I do need point out that the CPU utilization you see in Windows Task manager has not matched Rainmeter since approximately Windows 8. That is why things appear and disappear unfortunately, there's nothing I can do about that, it is a Rainmeter issue.) (The Top CPU Meter does bounce around a lot because Rainmeter does not report processes that use less than 0.1% CPU. ![]() What I can say is that all this usage info is coming from Windows itself, so Rainmeter is only telling you what Windows says. It may have something to do with Microsoft tweaking the way the thread scheduler works for the newer hybrid CPUs (p-cores vs. I can't say for sure why you see a difference between Win11 21H2 and Win11 22H2. How come Gadgets cpu usage works but not Rainformers? Worked perfectly on Windows 11 21H2. And the CPU usage in the top CPU rainmeter on both Gadgets and Rainformer show the incorrect CPU usage for processes. However the top CPU rainmeter from Gadgets seems to show the exact same symptoms as Rainformer under 22H2, it only shows a few process for a few seconds, then more processes the next second and the other second just two process for example. The Gadgets CPU-meter seems to be accurate on Windows 11 22H2 as below screenshots when I compare it to Rainformer and Task Manager. While checking the Rainmeter version I realised that what was running was actually an older version than what I had downloaded, the reason being that the update had installed files directly into my D:\ drive main directory instead of the Rainmeter folder I replaced all files with in the folder with the updated ones, and before that had added Rainmeter.Beeta wrote: ↑ September 22nd, 2022, 6:14 am RMSKIN file includes the plugin DLLs, so it may overwrite or superseed what you have)? What Rainmeter and MSI AB version do you use? What version is the MSI AB plugin for Rainmeter? What are your OS, CPU and GPUs? Which are some skins that have this problem? Have you set Rainmeter's - and other desktop applications' that shouldn't be detected as 3D applications - Application Detection Level to None in Riva Tuner Statistics Server (RTSS) that comes with MSI AB?ĭoes this simple skin work for you (be aware that the. I use MSI AB with Rainmeter as well, and don't have any problems with it. Yincognito wrote: ↑ February 19th, 2022, 11:41 pm The only changes I can think of that may have had an affect is that all around the same time I updated both Rainmeter and Afterburner to most recent versions, and installed new drivers for my GPU.Īny help or suggestions would be much appreciated, and if any additional information is required from myself then please say so! ![]() I redownloaded the MSIAfterburner.dll file in plugins to no avail also - even the original sample skin created for the plugin does not work. ini files in skins have been changed, nor can I see anything in the settings of Afterburner itself that might affect monitoring by a third party. I've deducted it's something specific to MSI Afterburner as other gadgets that use CoreTemp or HWiNFO still work correctly, but cannot for the life of me figure out the problem. This was sudden after having no issues for years. Looking for some suggestions to solve a problem with GPU monitoring gadgets - recently any skin that uses MSI Afterburner as a data source for GPU info (temperature, fan speed, load, etc) no longer fetches that info correctly, so now the gadget displays as null.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |