Fiery
-
Posts
12389 -
Joined
-
Last visited
-
Days Won
550
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
In the next AIDA64 beta release we'll extend the number of logical CPUs that the hardware monitoring module could handle from 16 to 32.
Thanks,Fiery
-
Many modern AMD processors (since Llano/A-Series and Zambezi/FX) have a hardware flaw that yields into unreal core diode temperature readings at idle. AMD said the core temperatures are only reliable when the processor is under heavy load.
As for the "CPU" temperature, that is measured by the motherboard sensor chip. Make sure to compare the value against Gigabyte EasyTune6. If you can see a different temperature reading there, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump, and copy-paste the full results into this topic.
Thanks,
Fiery -
Thank you for the feedback
-
Thank you for the feedback
-
We've fixed the reported issue in the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2341k6jy8ntsxlzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps. -
Thank you. I'm afraid so far we haven't been able to figure out what sort of device is responsible for the higher Vcore. It could be the one at B06-D30, but it's an unknown device to us.
BTW, what exact model of Sapphire HD7970 is it? -
Your SSD does not implement a thermal sensing logic, so it's normal that it doesn't appear on the Sensor page in AIDA64.
Regards,Fiery
-
Thank you for the feedback
-
Hi all on this forum! Please help in the issue with updating the BIOS. How to upgrade the BIOS, and how it works in this program?
AIDA64 doesn't specifically perform driver updates or BIOS updates, it only offers you links to motherboard makers' websites where you can download the drivers or BIOS updates. And it also offers links to eSupport automatized driver update and BIOS update facilities at:
BIOS Updates: http://aida64.com/bios-updates
Driver Updates: http://aida64.com/driver-updates
-
We've just released a new AIDA64 Business Edition beta:
http://www.aida64.com/downloads/aida64businessbuild2338x2r6vwzglkzip
-
Thank you. You're using an old version of AIDA64. The reported issue has already been fixed in the latest AIDA64 release:
-
Thank you for the info. We'll try to get a similar box to diagnose this issue. However, as with other multi-bay external HDD/SSD boxes, there's only a slim chance that we could provide SMART information (incl. temperature readings) for more than 1 drive in the box
-
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
-
Please give us a few more days, we need to investigate this issue by trying AIDA64 on a few Sandy Bridge and Ivy Bridge systems in our labs, in a hope that we can reproduce the problem you're experiencing.
Thank you for your patience.
-
Many motherboards do not implement a serial number. But when they do, the serial number is shown on the Computer / DMI page, under Motherboard.
Regards,Fiery
-
-
What do you mean by not indicating the drive? Can you see the drive details on the Storage / ATA page? Can you see the SMART attributes list on the Storage / SMART page?
Thanks,Fiery
-
Yes, that's exactly the settings I had.
Thank you. We'll fix that issue in the next AIDA64 beta release.
-
BUG>>
Double click on labels and Read columns are working
Burt Write, Copy and latency columns works on single click
You also forgot to disable clicking on objects that are not active such as L3 when L3 cache is not available
Thank you, it will be fixed in the next AIDA64 beta release.
Also why not try to display the info's on load such as CPU type, clock, fsb and below items... but don't remove the refreshing thing when starting the test
It could take a few seconds to collect those info, and it's best not to make the user wait that time before he can start the benchmark. Our users prefer to launch the benchmark right away, and then collect CPU/chipset info.
-
By semi-automatic I meant a scaling solution that is half-way between manual and automatic. We either do manual scaling or auto-scaling, but we're not so keen on making it more complicated with a semi-automatic (partly manual, partly automatic) method.
-
Thank you for the feedback. I'm sorry for the mixup about the HDD/SSD temperature labels, that was a one-time issue that only happened because of the bug fix. As for the "Detecting sensor information" message, that could be displayed when AIDA64 is started minimized or hidden, and the "Remember last page" option is enabled, and the last page you've used was the Sensor page
-
Such things may happen when you don't have the iGPU of your Intel processor utilized, because e.g. you use a discrete graphics card (video card) in your system.
"GT Cores" means the integrated GPU of Intel processors.
Regards,Fiery
-
Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2334r5bzp8vxskzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
Thanks,
Fiery -
We've fixed the reported issue about LAMD SSD controllers in the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2334r5bzp8vxskzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know how it works.
Thanks,Fiery
AMD GPU Vcore
in Hardware monitoring
Posted
We've tried AIDA64 on our Sapphire HD6850 that we've overclocked from the default 1.150V Vcore to 1.168V using Sapphire TriXX 4.6.0 (latest version). On this particular video card AIDA64 reports the default Vcore (VID) as "GPU Core" voltage, and reports the actual Vcore used by the GPU as "GPU VRM" voltage (via the onboard CHL8214 VRM). Since on CHL8225 and CHL8228 chips we do the same method of voltage measurements, I'd expect the same behavior from AIDA64 there as well.
BTW, we use ADL_OverDrive5_CurrentActivity_Get call from ADL to measure VDDC that we report as "GPU Core" voltage. On CHL8214 we report register 0x8D as "GPU VRM" voltage. On CHL8225 and CHL8228 we report register 0x8B as "GPU VRM" voltage.