-
Posts
12744 -
Joined
-
Last visited
-
Days Won
583
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
the link you posted is for the trial version 2571 but the sites latest beta is 2578 which one should we use?
I tried the beta 2578 and no change, hopefully you will find a fix for this soon
Beta 2578 is the latest and greatest beta release
We believe the stuck temperature issue is more a BIOS or Asus software/service issue than an AIDA64 bug. If both with and without ATKEX sensor support the temperature readout stucks, then I'm afraid we cannot do anything more to get around that issue 
-
Fiery, I have a logitech G15 and I use aida64 to display all of my system temps on the Keyboard screen. It worked flawless on my old setup. I got a new board reinstalled windows 7 64bit and now Everytime at startup it locks up my whole computer for 2 mins. It only locks up when I have the both aida 64 and logitech gamepanel starting at boot. I have literally tried everything I can think of. I have updated every single driver, even uninstalled and reinstalled a few to see if I get a change to no avail. All the hardware is the same except the board, So it isnt any of my other hardware. The new MOBO is a MSI 970A-G46. Any help would be greatly appreciated. Everything is up to date Aida64 logitech gamepanel ect.
What happens if you let AIDA64 start with Windows, but later you close AIDA64 and re-open it manually? Does it start slow then as well?
-
It looks like it may be due to a BIOS issue. We've checked both AIDA64 versions on our Intel DX79SI test system with Core i7-3960X CPU, but haven't found any difference in the scores obtained. We did update the benchmark module between AIDA64 v3.00.2500 (stable release) and AIDA64 v3.00.2578 (latest beta release), but it only affects Ivy Bridge-E/EN/EP processors.
Since your memory latency scores seem unchanged, but the memory bandwidth scores seem to drop to half, it looks like if the memory controller was configured for dual-channel operation instead of quad-channel operation. Although the memory controller (IMC) reports quad-channel mode, as AIDA64 reports it.
-
Thank you for the feedback

-
Thank you for the debug dump. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2578wrdfs3x2vhzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know how it works

Thanks,
Fiery
-
1
-
-
We've implemented a workaround for the mentioned issue. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2578wrdfs3x2vhzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Regards,
Fiery
-
Please try to uninstall it temporarily, and let us know if it makes a difference.
-
im having the same issue too, just started
CPU reading always reads 40C until i re boot then drops back to 25c on idle
i73930k at 4.5 (liquid cooled)
Asus RE4 (liquid cooled)
Aida64 CPU 24
Aida64 CPU #1 32
Aida64 CPU #3 27
Aida64 CPU #4 30
Aida64 CPU #5 35
Bios Version 4002
On Asus ROG motherboards, when you've got AI Suite II installed, it's best activating Asus ATKEX sensor support in AIDA64 / main menu / File / Preferences / Stability. It may help in your case
If you decide to give it a try, then first please make sure to have the latest AIDA64 beta release:http://www.aida64.com/downloads/aida64extremebuild2571jfzsxrb3qdzip
-
One of the drivers (maybe ForceWare) or one of the installed and background running software or services may be sensitive to the heavy stress AIDA64 puts on the system. Do you have AI Suite II installed?

-
AIDA64 also supports RAID members enumeration, but it doesn't support Adaptec RAID controllers. It may change in the future, but not in the near future I'm afraid

Regards,
Fiery -
AIDA64 reads CPU temperature from the 3rd temperature register of the sensor chip of the X79-UD5 motherboard. What you wrote to me sounds like a BIOS issue, or a collision between AIDA64 and another monitoring software. Try to upgrade the BIOS to the latest one, and temporarily uninstall other monitoring software that you may have installed.
-
Same problem here. I'ts very annoying. I have tray icon disabled (it's unuseful if you have many snesor tray icons visible, they allow you to open AIDA64). Do you mean that if I enable the tray icon main window will minimize OK?
Yes, that's how it works. By having no AIDA64 tray icon and main window hidden, but sensor icons enabled, that would in theory enable you to show and hide the main window by double-clicking on one of the sensor icons. But if you had the main window hidden, right-clicked on any of the sensor icons and choose to hide sensor icons, then you would block yourself out of using AIDA64. Hence it would require a complicated rule if we'd involved sensor icons in that logic.
-
We'll rename PLX to a generic temperature label on your motherboard, and will also check if it's possible to read VRM temperatures.
-
Works great! I have the motherboard temp option back again. Under sensor temps there is also a measurement for PLX temp but this board does not have a PLX chip. Could this label be measuring some other temp on the board? Thanks for all your help Fiery.
Thank you for the feedback. In case the "PLX" temperature reading looks valid (not stuck, not showing anything unreal), then it must be another temperature reading. Although we currently have no information on which temperature would it be.
-
The mentioned new AIDA64 beta release is available for download at:
http://www.aida64.com/downloads/aida64extremebuild2571jfzsxrb3qdzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know how it works

-
Thank you for letting us know, I'm glad you managed to make it work.
-
At this time it looks like it's a driver issue that cannot be fixed from AIDA64, HWiNFO or GPU-Z

-
We do have plans about a GPGPU benchmark based on OpenCL. However, our efforts on the benchmarks development are slowed down and somehow blocked as well by the improper quality of OpenCL compilers. Therefore, we have to delay the release of the existing benchmarks until the compilers get more mature. Not mentioning names, but 2 out of the 3 major GPU manufacturers have really poor OpenCL compilers, not being able to properly compile our benchmark code. We've notified both companies in question, so they know about the issues, and they promised things will slowly improve in the upcoming months. So we expect to roll out our OpenCL GPGPU benchmarks before the end of the year.
Regards,
Fiery
-
In that case then I guess it would be better if you could create a TXT report of the Devices / USB Devices page of AIDA64, and copy-paste into this topic. We'll then find the ID in there

I understand that the issue may not be directly in connection with the RAID member enumeration (due to the fact that you mentioned about stick behavior), but it may still be useful to exclude the stick from the RAID member enumeration. Maybe it helps, maybe not, but sticks shouldn't be scanned anyway for RAID members

-
I voted and shared.
Thank you

-
1
-
-
Borrowing the tread a quickie, How do I change the time from AM/PM to regular digital time, how do i change other formats, MHz / GHz?
Currently it's not possible to adjust those.
-
My only guess would be that the RAID and external drives scanning module of AIDA64 makes the stick's firmware go crazy for some reason. The solution would be to exclude the drive from the scanning. In order for us to add your drive to the exclusion list, we need to have its USB hardware ID. Please go to the Device Manager, find the drive in the list, right-click on it --> Properties --> Details --> Parent. The USB hardware ID should be in the format of "USB\VEN_xxxx&PID_yyyy". If you could send us the ID, we can add it to the exclusion list, and send you a new AIDA64 beta to try it on your system.
Thanks,
Fiery
-
Thank you. We'll implement sensor tweakings for your motherboard in the next AIDA64 beta release due in a few days. I'll post a message into this topic once the new AIDA64 beta is available for download.
-
"CPU Package" is one of the temperatures that Intel processors measure using their integrated on-die temperature diode. Only Intel knows what exactly does it measure and how.
Regards,
Fiery

sony vaio problem
in Hardware monitoring
Posted
Up to 80 Celsius is normal for notebook CPU temperature, so your temperatures of 43 to 66 Celsius is absolutely fine. Based on the description of the issue, I'd say it could be either a RAM failure or motherboard failure.
Regards,
Fiery