-
Posts
11190 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
We'll implement support for the new i320 firmware in the next beta release of AIDA64. I'll post a download link into this topic once the new beta is available.
Thanks,
Fiery
-
I'm afraid we have no plans about OSD in games for 2011. We've implemented Rivatuner OSD Server support to let you put AIDA64 readings via Rivatuner onto OSD in games. I know, it's not a convenient method, but at least there's a way now to make that work
-
now the Cpu Temperature is shown,but the Core´s Temperature is as the same before on 0 C° .
Thanks for the feedback.
As I wrote above:
Zero core temperatures are normal on systems where ACC is enabled. ACC is usually enabled to unlock the disabled cores of AMD processors. Due to a hardware limitation, core temperatures cannot be measures when ACC is active.
-
Do you have any USB, FireWire or eSATA external storage devices connected?
-
Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic.
Thanks,
Fiery
-
In certain unfortunate cases such issues may happen due to a glitch in the hardware monitoring module of AIDA64. We'll try to improve that in AIDA64 v2.00 that is due in a few months.
Until then, if you can identify which item is it, you can manually edit the AIDA64.INI file, and remove the OSD item(s) that cause the issues. I know it's not a sophisticated method though
Regards,
Fiery
-
Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild1625bd4flk0yznzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know how it works.
Thanks,
Fiery
-
1) Unfortunately firewall software status cannot be detected for most firewall software. In such cases "?" is normal to be shown.
2) We've implemented support for Anti-Malware in the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.co...25bd4flk0yznzip
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 fixed the sensor info in the following new beta version of AIDA64 Extreme Edition:
http://www.aida64.com/downloads/aida64extremebuild1625bd4flk0yznzip
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 suggestion. We'll work on enhancing the Rivatuner support in the upcoming releases of AIDA64.
Regards,
Fiery
-
1) Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic.
2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic.
Thanks,
Fiery
-
Hi
I have the same issue, the screen freeze in scanning raid devices and it takes a long time in that part to star aida, almost 50 seconds in my laptop
its a asus K53SJ :-(
Damiam.
Have you tried to disable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability?
-
Thank you for the feedback
-
I'm sorry for the late reply. We do have special support in AIDA64 for previous generation 3ware SATA RAID controllers, but no support yet for your RAID controller. In case you receive annoying event log entries due to the RAID controller polling layer of AIDA64, then please try to disable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability.
We'll need a bit more time to investigate this issue, since we currently only have older 3ware controllers in our test labs. So first we have to get one of the newer ones to try and reproduce the issues you're having.
Regards,
Fiery
-
Please remove the Time (Zeit) item, and add a new one using the Simple Sensor Item item type. I guess the current Time item uses the more complicated Sensor Item type, and it requires a bit of tweaking to get a proper placement for such items like Date and Time.
Regards,
Fiery
-
The sensor readings will be fixed in the very next beta release of AIDA64 due next week. It will clear up the temperature labelling issue
I'll post a message into this topic once the new beta is available.
-
Crucial M4 SSD drives do not implement a working thermal sensor logic. Most SSDs suffer from the same issue, since somehow SSD manufacturers don't think it's important to implement a temperature sensor. Some SSDs may have a temperature reading among the SMART attributes, but it either reports a constant zero Celsius, 1 Celsius, or a stuck value of e.g. 30 or 40 Celsius.
Regards,
Fiery
-
Zero core temperatures are normal on systems where ACC is enabled. ACC is usually enabled to unlock the disabled cores of AMD processors. Due to a hardware limitation, core temperatures cannot be measures when ACC is active.
As for the "CPU" temperature, we'll need two dumps to check what's wrong with that:
1) Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic.
2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic.
Thanks,
Fiery
-
We've further tweaked the Preferences window restoring in the following new AIDA64 beta release:
http://www.aida64.com/downloads/aida64extremebuild1618o2v4jwkrfzzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
Thanks,
Fiery
-
Removing the whole path under HKEY_CURRENT_USER\Software\FinalWire\AIDA64 should help to eliminate weird Preferences window placement issues. Of course it's possible to just reset the Preferences window values in the Registry by removing the following entries from HKEY_CURRENT_USER\Software\FinalWire\AIDA64:
PrefWindowPosX
PrefWindowPosY
PrefWindowSizeX
PrefWindowSizeY
PrefWindowState
- 1
-
Have you tried to upgrade to the latest beta release?
http://www.aida64.com/downloads/aida64extremebuild1611kb6wjk2msdzip
When you removed the Registry entries, did you remove the complete path of HKEY_CURRENT_USER\Software\FinalWire\AIDA64 ?
- 1
-
Thank you for your support
-
Have you checked that AIDA64 auto-launch is still disabled in Logitech LCD Manager?
Alternatively, you can have the option in AIDA64 ("Load AIDA64 at Windows startup") disabled, and let Logitech LCD Manager to launch AIDA64 at Windows bootup.
-
Edit: with netplwiz command I can see a window reporting me that my username account is associated to Homeusers and Administrators group.
This could explain the behavior? Personally I don't like & use Windows 7 Home Group. Maybe this has been done automatically by Win7.
Hope this helps.
That's a normal to have the user associated to both those groups.
Acer emachines ER1401 sensors
in Hardware monitoring
Posted
In the beta I've given you there should be no Aux temperature, since we've renamed Aux to CPU.