Secondary-Son

I positioned HWiNFO64 screen under the GPU Temp bar to show the two together, then realized that the bar was tracking the GPU hotspot temperature. I checked that sensor and confirmed that I had indeed selected the wrong sensor and renamed it GPU TEMP. This happened during my learning process for this program (I'm still learning). I selected the correct sensor and all looks good now. I'm sorry for being a source of bother. I really did try to search the forum for a solution but kept finding a lot of unanswered questions. Thank you much for the help you provided.

I updated to v7.4 and confirmed that version is displayed in program. Initial tests showed the same +9 degree temperature error compared to HWiNFO64 and MSI Afterburner. I rebooted my computer and still had the same +9 degree temperature error. Attached is the nvidiagpureg file. Thanks for any help you can provide. nvidiagpureg.txt

I have a Asus RTX 4080 TUF super. I downloaded and installed the program from the AIDA64 site about 2 weeks ago but the version shows it being v7.00, I don't even see an option to download v7.00, I'm not sure how that happened. If I upgrade to v7.40 should that fix the problem? Again, sorry for the harsh words but I wanted to research and resolve the problem myself but when searching the forum I saw inaccurate sensor readings problems listed many times without any responses from support.

I just started using AIDA64 and found that the GPU idle Temp displayed is 9 degrees higher than HWInfo and MSI Afterburner. Possibly others sensor measurements could be off as well, I didn't compare. I'm seeing other users with inaccurate readings reported without responses from the AIDA64 staff. Is there a plan to fix incorrect sensor info being displayed? If so, what is in works? One post suggested importing HWiNFO64 readings into AIDA64 to correct issues. Also no response for that posting. It seems like that would provide a long term fix, and possibly the simplest fix. Your product is not worth having if it is just going to display arbitrary sensor readings. I know the title of this posting is harsh but it seemed necessary to encourage a constructive response.