Fiery
-
Posts
11202 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
Yes, I'm afraid a slight issue has slipped into Build 1847 about that. It sometimes works, but other cases it fails. We'll fix that in the next AIDA64 beta release.
Thanks,
Fiery
-
Thank you, we'll check that and fix it in the next AIDA64 release.
Regards,
Fiery
-
AIDA64 detects NOD32/ESS version by checking the version number of EGUI.EXE. If that fails, it will detect version using the Registry path:
HKLM\Software\Eset\Eset Security\CurrentVersion\Info\ProductVersion
I guess one of those places contain an incorrect product version. It's not the fault of AIDA64, but a slight mistake by Eset.
Regards,
Fiery
-
Thank you for the feedback
-
We've just released a new AIDA64 beta with the updated gadget:
http://www.aida64.com/downloads/aida64extremebuild1847lcsxfgtjmzzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Regards,
Fiery
-
No, no any external applications.
I'm using Logitech LCD and sidebar on my desktop computer, there is no such issue.
And I'm not the only person encounter this problem. As I mentioned above, ALL the ThinkPad X201i, X201, T410 users encountered this issue.
Thanks for the info. It's quite odd that noone else (out of those users you mentioned) reported this issue to us. And stating that all of them face this issue is even more odd...
Just to clarify: if you start AIDA64 on such notebooks with its default settings (so OSD Panel not activated, Sidebar support not activated), and you just leave it sitting on the main screen, does it still lock up after a while?
-
Does it lock up while it is measuring some sensor values? In other words, do you have such features like the OSD Panel, Logitech LCD, Vista Sidebar, Logging, Alerting, SensorPanel, or External Applications activated?
-
Please post a screen shot that shows all settings of the Stability page (AIDA64 / main menu / File / Preferences / Stability).
Also, right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic.
Finally, right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic.
Thank you for your time.
-
AIDA64 fully supports the Core i7-2700K processor. Please start Task Manager (e.g. by using the Shift+Ctrl+Escape key combination), click on the Performance tab, and count the number of logical processors in the CPU Usage History box. There should be 8 graphs there, associated with the 8 threads your processor supports. If you can see less than 8 threads there, then it means one or more of the CPU cores are disabled in the BIOS Setup.
Alternatively, you can check in the BIOS Setup whether core disabling is activated there.
Regards,
Fiery
-
Me too, works like charm after i disabled the option.
Thanks for the feedback
-
Please send me your full name and email address in private message to me. I'll find your key and send it to you.
Regards,
Fiery
-
I saw the DRAM Voltage in BIOS/Power/PC Health with fan speeds, temperatures and voltages…
BIOS: "AMI BIOS"
Thank you. Please note down all voltage values you can see on the PC Health Status page in the BIOS Setup, and copy the values here.
Also, please start AIDA64, right-click on the bottom status bar of its main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic.
Thanks,
Fiery
-
CPU VID and NB VID are shown on the Computer / Overclock page. They aren't measured values, but detected values, hence they don't fit on the Sensor page.
DRAM Voltage can only be shown if it is a sensor reading. Did you see that value on the PC Health Status or HW Monitor page in the BIOS Setup?
I'm sorry, but we have no plans on making a DLL or other component just to read sensor information. Compared to how much system memory modern computers have (typically 2GB or more), the memory footprint of AIDA64 is negligible (less than 1 or 2 percent).
Regards,
Fiery
-
it doesn't use the color i choosed on startup…
It's normal. When AIDA64 is not running, the default Blue colour schema is used.
-
If you'll allow me…
I'll try to make a form application that makes a gadget that looks like the sensor panel…
I'm not too familiar with java and HTML coding, so i think it will take a month or more to finish…
…
it's ok if it will not be granted
…
We're currently working on improving the AIDA64 Sidebar Gadget. You can develop your own gadget that has advanced features, but I'm afraid due to intellectual property rights and other boring legal issues we cannot use external components in our software
-
I am confuse. How I can do that?
All the Aida64 settings are by default. I'd make only one change in this settings, which you can see from the following picture.
In this case I don't have latency problem.
It means you haven't upgraded to the latest AIDA64 beta available at:
http://www.aida64.co...39s1y6ftjhwkzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
With that beta a new UPS entry should be available among the HWMon Modules.
-
If I disable the GPU module in the HWMon I don't have latency problem.
If you have the GPU module enabled, but the UPS module disabled, then do you get latency issues?
-
With this new beta I didn't resolve my latency problem.
The next suggestion - HWMon and disabling diffrent devices.
In my case... I don't have latency problem when I disable the GPU Module, which is NVIDIA GT555 with the latest drivers.
Thank you for the feedback. Just disabling the UPS module didn't solve the latency issues, did it?
-
Yes thought of that, but if I have AIDA64 monitoring the CPU and at the same time Intel's solution then the Intel shows the CPU at rest 2.5Ghz whilst AIDA shows it at turbo!
Further, if under load, then the Intel solution may show the CPU at say 2.7, then AIDA will also show the CPU at 2.7, it's as though AIDA is seeing rest as turbo and visa versa!
Please note that Turbo is engaged so quickly, and for such a small amount of time, then it is possible that for the fraction of time AIDA64 (or CPU-Z) measures the CPU clock the processor switches up to Turbo clock, and while Intel's tool measures the clock it switches back to non-Turbo clock. Even though it looks as if those tools work in parallel and measure the very same things, all those low-level clock measurements are done exclusively, without multi-tasking, for a very short amount of time.
It's not easy to explain all that without using deep technical terms. The whole point of Turbo Boost and other performance enhancement and power saving "magic" of Nehalem and later Intel processors are designed to work very fast, by switching clock speeds in a fraction of a second. Hence the CPU can adjust to the necessary workload with an extreme response time.
-
Thank you. We have different plans about the System Stability Test, which involves a complete redesign of the user interface, and also to make it easier to use while retaining the current layout with improvements. Stay tuned
-
Fiery, one thing. This item has appeared in the Sensor Icons item in the Preferences but it can't be configured and it doesn't have an icon so it isn't shown in the tray (but it's always checked).
Thank you, we'll fix that in the next AIDA64 beta release.
And one problem in this forum: attached image isn't clickable in the Post Preview.It works fine in IE 9.0 and Chrome 17 for me. What web browser do you use?
Thanks,
Fiery
-
Hi.Another problem with the sidebar gadget is: I started my computer this morning, but the gadget shows me that my pc is since for more than 16 hours.At this moment the pc is not more than 4 hours in use.May be a problem with a sensor ? thanks.
In order to find out whether it's a gadget-related issue or a flaw in AIDA64's engine, please check the UpTime on the Operating System / Operating System page of AIDA64 as well. Let us know what can you find out.
-
Maybe the CPU senses the light CPU load that CPU-Z or AIDA64 CPUID Panel puts on the processor, and instead of leaving itself resting, it kicks in the Turbo Boost to assure it provides the maximum single-threaded performance. Please note that unlike other applications, both CPU-Z and AIDA64 CPUID Panel monitors more aspects of the system and updates those properties dynamically, hence they put a bit more stress on the CPU than other solutions. In most cases the difference is only 1-2% of total CPU time, but it may just be enough for the CPU to activate Turbo Boost.
-
Thank you for the feedback
Windows 8 CP (Sidebar gadget background color)
in General Discussion
Posted
The gadget will be updated in the next beta. We'll also remove APIC clock measurement in the next AIDA64 beta, since that -- under Win8 Consumer Preview -- causes issues with CPU core clock measurement and benchmark results calculation as well. A bit more things have changed between Win8 Developer Preview and Win8 Consumer Preview than we expected. Who knows, maybe the Win8 Release Candidate will revamp even more things internally, on the Windows kernel level...
Anyway, I'll post a message into this topic once the new AIDA64 beta is available.