WaffeSS Posted January 26, 2017 Share Posted January 26, 2017 I use a HWInfo64 with RivaTuner and AIDA64 for Save LOG on Disk, but i discovery a weird bug on AIDA64, this error i think is caused if you use HWInfo64 with AIDA64. Look a LOG generated by AIDA64 running with HWInfo64, Sensor inform a wrong CPU Clock's and FSB. After various test's, changing Power Energy Control profile of Windows, i noted this BUG of AIDA64 Sensor LOG wont appear, if you close HWInfo64.There may be some kind of interference between the two, preventing both from operating simultaneously.Unfortunately the use of HWinfo64 is necessary ATM, as it works very well with RivaTuner for monitoring OSD in games. A good suggestion for AIDA64 future Update, is add more Options to customize the Integration of AIDA64 Sensor to work with RivaTuner OST. Options such Rename and Custom Position of Item listed on OSD is welcome. Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 30, 2017 Share Posted January 30, 2017 What processor and motherboard do you have, and what version of Windows are you using? Options such Rename and Custom Position of Item listed on OSD is welcome. We're not planning to enable that, since you can already do that using the SensorPanel module of AIDA64. Quote Link to comment Share on other sites More sharing options...
WaffeSS Posted January 30, 2017 Author Share Posted January 30, 2017 MB: ASRock Z97 Extreme6 CPU: i7-4790K Quote Link to comment Share on other sites More sharing options...
Fiery Posted February 8, 2017 Share Posted February 8, 2017 Thank you. We've added a new synchronization mutex to make sure AIDA64 works properly with other monitoring software running simultaneously. We've notified the authors of HWiNFO, HWMonitor and SIV about this issue. It's now up to them to implement the same mutex. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Quote Link to comment Share on other sites More sharing options...
WaffeSS Posted February 18, 2017 Author Share Posted February 18, 2017 Thanks Fiery, today i discover CPU-Z cause this issue too. I'm updating now to BETA Build. ATM i use v5.80.4000. Quote Link to comment Share on other sites More sharing options...
Fiery Posted February 18, 2017 Share Posted February 18, 2017 6 hours ago, WaffeSS said: Thanks Fiery, today i discover CPU-Z cause this issue too. I'm updating now to BETA Build. ATM i use v5.80.4000. We've notified the authors of CPU-Z about this issue, asking them to implement the synchronization mutex that we've defined in order to avoid this issue. I'm not sure if it is already implemented in HWiNFO, so we'll ping its authors too. 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.