-
Posts
11188 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
AIDA64 sensor reporting all over the map (MSI P55-GD85)
Fiery replied to Capt Proton's topic in Hardware monitoring
The old "Aux" temperature is now what AIDA64 reports as "CPU" temperature. It's the same reading. And please understand in AIDA64 we're just trying to report the same sensor values (or even more sensor readings if possible) as what the BIOS Setup or the manufacturer's own hardware monitoring software measures. If the measured temperature(s) match e.g. MSI Control Center, but they still don't make much sense to you, then it's not the fault of our software, but maybe your hardware measures incorrect or unreal values -
It's up to you Our beta releases are usually just as stable as a stable release, so no risk on using a beta.
-
AIDA64 sensor reporting all over the map (MSI P55-GD85)
Fiery replied to Capt Proton's topic in Hardware monitoring
Can you see an exact 10C offset both at idle and under heavy system load? If so, then you can use the Correction feature of AIDA64 to substract 10C from the CPU temperature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction). Does MSI Control Center measure MOSFET temperatures? Or you referred to BIOS Setup temperature readings there? -
AIDA64 sensor reporting all over the map (MSI P55-GD85)
Fiery replied to Capt Proton's topic in Hardware monitoring
Please make sure to compare CPU and Motherboard temperatures against MSI Control Center. We're certain the current solution should match MSI Control Center values. The 10 other temperatures are the MOSFET temperatures. Most monitoring software cannot measure them -
AIDA64 freezes when entering Overclock page or CPUID Panel
Fiery replied to hash859's topic in Bug reports
Thank you for letting us know about the solution. It will hopefully help others who face similar issues. Regards, Fiery -
I'm afraid certain AMD processor models, especially the latest FX Series are infamous for providing very low core diode temperature readings, usually way below ambient temperature at idle. So you may want to ignore the core diode temperature readings.
-
Thank you for the feedback. AFAIK your motherboard cannot measure the regular voltages (+5V, +12V), so that's why we've removed those bogus readings. You can check in the BIOS Setup whether your motherboard is capable of measuring a specific voltage rail or not.
-
Thank you. We'll contact Intel and try to talk to Eric about Quick Sync detection in AIDA64. However, as Intel seems to be unusually closed on the Quick Sync topic, we may not be able to get the necessary low-level information. I'll let you know in this topic once we have an update.
-
I'm afraid Intel haven't really published any low-level information about Quick Sync, or at least so far we couldn't find any useful info on how to detect that feature. Do you know any software (either made by Intel or a 3rd party) that can show any information on Quick Sync? Thanks, Fiery
-
No problem
-
Asus Maximus Gene-Z (rev 1.0) MotherBoard Temperature Sensor
Fiery replied to Ramses's topic in Hardware monitoring
That indeed sounds weird. But in case Asus Probe shows the same, then the sensor most likely provides incorrect readings. I'm not sure if it makes sense to correct it, but if you wanna do that, then you can enable Correction in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction. Regards, Fiery -
In the BIOS Setup processors are unable to execute halt cycles to put their clocks down in order to cool themselves down. Hence if in the BIOS Setup you can see 20+ Celsius, but AIDA64 measures 15-19C, it may be correct. Please compare AIDA64 values against MSI Control Center values. Regards, Fiery
-
As Squall Leonhart suggested, under Windows Vista and Windows 7 you can find the scheduled task that starts AIDA64 at Windows boot using Task Scheduler. Please check if the task is there, and if it is enabled. There's a chance NIS removes the task, or prevents AIDA64 from creating the task. Regards, Fiery
- 5 replies
-
- Windows 7
- starting with windows
-
(and 1 more)
Tagged with:
-
It looks like the AIDA64 Remote Control Server had some issues on the workstations. We'll check what's going on, although as I can see you already have up on AIDA64 If you reconsider sometime, then you can fix such issues by removing the DLL file that causes the issue (AIDA_RCS.DLL). That will of course disable the Remote Control feature, but at least you can evaluate the other features without such error messages. Regards, Fiery
-
System instability is something you cannot measure using a mathematical formula or a specific detection method. Some of the instability issues can be revealed by only AIDA64, some others can only be revealed by Prime, and some can be revealed by any of them. BTW, AIDA64 System Stability Test has multiple subtests. Sometimes an instable system can be put to "its knees" by only using the FPU subtest (and leaving the rest of the tests disabled), while in other cases you should enable all subtests to reveal the instability. It takes a lot of time to check out how stable your system is, but if you can achieve a high clocks via overclocking, then it worth the efforts to play around with stability tests Regards, Fiery
-
It is definitely a conflict between Asus AI Suite II and AIDA64. We've already contacted Asus a while ago, and asked them to implement the now industry standard mutexes that many sysinfo and diagnostics software use (e.g. AIDA64, HWiNFO32/64, CPU-Z, HWMonitor, SpeedFan, SIV, etc) to make sure their low-level code doesn't collide with each other when you use multiple of such software in the same time. But Asus don't seem to care about that at all. So in case you observe any collisions between such 3rd party software and AI Suite II, then I'm afraid it can only be solved if you put a bit of pressure on Asus to improve their software. Regards, Fiery
-
AIDA64 freezes when entering Overclock page or CPUID Panel
Fiery replied to hash859's topic in Bug reports
If it's possible, please try it with EIST (SpeedStep) enabled, C1E disabled, C-States enabled. Let me know if it makes any difference. BTW, are you using the latest BIOS for your motherboard? Thanks, Fiery -
No problem Please let us know if you have any further issues with AIDA64. Regards, Fiery
-
Thank you for the data. We've tweaked the sensor readings to better support your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery
-
Thank you for the data. We've tweaked the sensor readings to better support your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery
-
AIDA64 sensor reporting all over the map (MSI P55-GD85)
Fiery replied to Capt Proton's topic in Hardware monitoring
We've improved the sensor readings for your motherboard in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery -
We've implemented the requested menu item in the System Tray menu in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery
-
AIDA64 sensor reporting all over the map (MSI P55-GD85)
Fiery replied to Capt Proton's topic in Hardware monitoring
The issue will be fixed in the next AIDA64 beta release that will go online later today.