![]() If all is OK, open the Settings and check one drive at a time until there is a problem. Then load the skin and see if it crashes. One thing you can do to debug is open the file and set all the "HideDisk N" variables to "1" except for disk C. To fix this, verify that you don't have any network drives marked "Disconnected" in Windows, or make sure you have unchecked it to ignore it. The Gadget checks ALL drives (even network drives) except ones you have unchecked so they are ignored. That duration is more than a second, so effectively during that time Rainmeter is hung. There will be a long delay as Windows tries and retries accessing that drive, and finally gives up. Rainmeter will keep trying that drive once a second to check its status. One thing that has caused issues for me in the past is if I map a network drive to a drive letter, then for some reason that network drive no longer exists (i.e., the drive is mapped to a dead share or the server is offline). ![]() The gadget was working fine with these less than a month ago. I am running an NVMe SSD as my system drive, and a couple of raid 5 arrays of SAS drives connected to an HP p812 raid controller in a PCI-E slot. I haven't added a drive in months, so I don't know what change caused the issue. All the others run and refresh properly, but when I start the drivemeter, all the gadgets and rainmeter lock up. The one causing the issue is the drivemeter. Thanks for suggesting the way to find the culprit. Both the items you mention above are simply trying to open your text editor so you can edit/view the file. Open Rainmeter > Manage > Settings and double-check that the Editor that is listed there actually exists. Let's move this to a new issue, but first, one simple thing you can check. The gadgets are running fine there, I just can't configure the GPU and CPU settings to show the correct sensors from HWINFO64ĭo you want me to open another issue, or deal with it here? On that machine I am running the latest version of hwinfo64, and have turned on the "Enable reporting to gadget" option in the sensors settings.Īny suggestions to get this working? It's an older machine running an Intel Core 2 quad Q6700 with 8GB of ram and an AMD Radeon R5 240 1GB video card, running Win 11 pro 圆4. It doesn't open the page to assign the values. When I go into the gadget's settings, and try to edit the hwinfo64 sensor settings for the gadgets, clicking on the "List HWinfo indexes" or the "Edit HWinfo settings" links in the settings does nothing. I have one other issue that's happening on another machine (a windows 11 pro machine). Once I see which it is, I can let you know how to fix it. At the bottom you might see the same skin refreshing over and over. Another way to find out is (after Rainmeter hangs and you kill it) to look at the Rainmeter.log file (it will be in that same folder). Exit Rainmeter and go back to the Rainmeter.ini file and set Active=0 for that skin. If you get a freeze, that's the one that is causing problems. Because no skins are active, it will open some Illustro skins (I think). ![]() Do a search and replace and change the string Active=1 to Active=0. Open the file C:\Users\\AppData\Roaming\Rainmeter\Rainmeter.ini with your preferred text editor.Exit Rainmeter (if you are not already exited).The main culprit is the Weather Meter skin. It sounds like one of the Gadgets is stuck in a loop (refreshing over and over). This is on an HP z460 workstation with an 8 core Xeon E5-4655 v4, 64GB memory running windows 10 pro 64bit 21H2 with all updates, and an NVIDIA GeForce GTX 1060 3GB video card using the more "stable" "enterprise" "Studio Driver" (installed after the "Geoforce game ready driver" started to hang my system when the screen was turned off). I can't pinpoint it to any individual event, but it could be related to a recent windows 10 update? This started happening within the last couple of weeks. ![]() I also did an SFC /scannow, and had no errors, and did a DISM /Online /Cleanup-Image /ScanHealth to verify that my windows installation was healty - no issues there. One thing that seems a bit odd that I noticed, is that when I click on the "show desktop" button, the clock shows the correct time, but the second hand is frozen, and the clock does not advance while I am on the desktop. I have updated to the latest version of your gadgets and that didn't help. I tried uninstalling rainmeter and downgrading to the previous version but that didn't help. The gadgets paint very slowly during the bootup, and then are frozen, as is Rainmeter itself. I have followed your documented procedure for rebuilding the perfmon databases, twice, rebooting afterwards each time, and I get the same result. I am experiencing all of the gadgets being frozen, and the Rainmeter icon is also frozen (when I rightclick on it, nothing happens). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |