netjack Posted December 8, 2019 Share Posted December 8, 2019 So I'm finding that when I resume my computer (either from sleep or hibernate), Aida shows in the notification area but doesn't actually work. And when I click the notification are up arrow a second time, Aida just exits. This is causing my sensor panel to not work. Win 10 latest build. Running latest version of A64. Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 10, 2019 Share Posted December 10, 2019 On 12/8/2019 at 1:40 AM, netjack said: So I'm finding that when I resume my computer (either from sleep or hibernate), Aida shows in the notification area but doesn't actually work. And when I click the notification are up arrow a second time, Aida just exits. This is causing my sensor panel to not work. Win 10 latest build. Running latest version of A64. Please let us know more about your system configuration. Motherboard model, CPU type, video card(s) installed, any special monitoring or liquid cooling device connected? (via USB for example) Quote Link to comment Share on other sites More sharing options...
netjack Posted December 11, 2019 Author Share Posted December 11, 2019 Gigabyte Aorus Pro 390 i7-9700k (OC'd to 5ghz) EVGA 2080ti FTW3 W10 Pro 1909 CPU & GPU both watercooled Just Aida Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 15, 2019 Share Posted December 15, 2019 On 12/11/2019 at 1:07 PM, netjack said: Gigabyte Aorus Pro 390 i7-9700k (OC'd to 5ghz) EVGA 2080ti FTW3 W10 Pro 1909 CPU & GPU both watercooled Just Aida Thank you. We've tried to replicate the issue on various test systems of ours, but with no luck so far. It would be very helpful if you could help us investigating this issue by disabling GPU sensor support in AIDA64 / main menu / File / Preferences / Stability. Restart AIDA64 after altering that option, and check if it eliminates the issues after resuming from sleep/hibernation. Please let us know how it goes. Quote Link to comment Share on other sites More sharing options...
Omari Posted May 12, 2020 Share Posted May 12, 2020 I think this bug occurs because aida has been installed as a portable installation and not had a registry value installed in windows Quote Link to comment Share on other sites More sharing options...
Tudor Posted December 10, 2021 Share Posted December 10, 2021 So I had the same problem using MadCatz STRIKE 7 kb on Win10 and seem to found a solution: *Do not enable auto start in AIDA, just configure to minimize on start *Open Task Scheduler and click on “Create a Task” to create a new task. *In the new panel which opens, fill the “General” tab to suit your needs. *Next, switch to the “Triggers” tab and choose “New”. Another Panel will open. At the top of this Panel, choose “On an event” from the drop-down menu. *Then choose “Custom” under Settings, and hit “New Event Filter”. Create a “Custom Event Filter” with: Event Level: Information Log Name: System Source: Power-Troubleshooter Event ID: 1 Need to chose from droplist of Event Sources the POWER-TROUBLESHOOTER *That was the important part. Now switch to the Actions tab and choose the program you wish to run. *In Conditions tab, uncheck the option labeled “Start the task only if the computer is on AC power”. Finally, save the task by clicking on OK. Hope that helps. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.