Overclockeverything Posted March 26, 2018 Share Posted March 26, 2018 When my system resumes after sleep mode Aida is shut down. This happens even when my CPU/GPU are at stock clocks/voltages. I also tried different sleep modes, hybrid and hibernate. I am running a Gigabyte G7 with an I5-8600k, GTX 1060, Samsung SSD and 16GB of G Skill Aegis F4-2400 RAM. Any help would be appreciated. Thank you Quote Link to comment Share on other sites More sharing options...
Fiery Posted April 9, 2018 Share Posted April 9, 2018 On 2018. 03. 26. at 9:47 PM, Overclockeverything said: When my system resumes after sleep mode Aida is shut down. This happens even when my CPU/GPU are at stock clocks/voltages. I also tried different sleep modes, hybrid and hibernate. I am running a Gigabyte G7 with an I5-8600k, GTX 1060, Samsung SSD and 16GB of G Skill Aegis F4-2400 RAM. Any help would be appreciated. Thank you I'm not sure what Gigabyte G7 refers to. Is it a Gigabyte motherboard with Z370 chipset? If yes, then which one? Do you have any special sensor devices connected, like via USB? Do you have any RAID arrays defined? Please also let me know what version of ForceWare do you have installed. Quote Link to comment Share on other sites More sharing options...
Overclockeverything Posted April 10, 2018 Author Share Posted April 10, 2018 Sorry. It is the z370 Aorus Gaming 7 motherboard. Thank you for your help. Odospace is causing the crash. I moved the topic this post: 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 program and not had its values written to the windows registry Quote Link to comment Share on other sites More sharing options...
netjack Posted November 5, 2020 Share Posted November 5, 2020 On 5/11/2020 at 10:23 PM, Omari said: I think this bug occurs because aida has been installed as a portable program and not had its values written to the windows registry So how does one go about fixing this? Quote Link to comment Share on other sites More sharing options...
Fiery Posted November 17, 2020 Share Posted November 17, 2020 On 5/12/2020 at 4:23 AM, Omari said: I think this bug occurs because aida has been installed as a portable program and not had its values written to the windows registry I don't think that could cause any issues, since AIDA64 initializes its Registry entries whenever they're missing. You can remove the entries completely if you want, and you will see the next time you start AIDA64 that they will be re-created automatically. Quote Link to comment Share on other sites More sharing options...
Fiery Posted November 17, 2020 Share Posted November 17, 2020 On 11/5/2020 at 1:23 PM, netjack said: So how does one go about fixing this? If you believe it could be related to an issue about AIDA64, you can simply download and install the self-installing EXE package of AIDA64: https://www.aida64.com/downloads/latesta64xe 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.