Fiery
-
Posts
11182 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
11 hours ago, jon.d said:
Thanks Fiery,
I've traced an issue to a usb splitter I was using.
I've removed the splitter and the speed has improved. Its still taking around 5 seconds to refresh though.
Any ideas?
Many thanks
Jon
According the updated dump the refresh should take 1 second. It is still quite long, but the Aquaero USB protocol is quite slow, and we cannot get around that
-
1 hour ago, jon.d said:
Thank you! The Corsair RMi module causes the extreme high latency. If you can let it go, just disable that module in AIDA64 / Preferences / Stability / Corsair HXi/RMi sensor support.
-
3 hours ago, jon.d said:
Hi I have recently upgraded my system from a Ryzen 5000 on an ASUS motherboard to a Ryzen 7000 on an ASUS motherboard. Since the upgrade I cannot get a sensor panel to work. My issue is that the sensors take too long to refresh. For example I set up the most basic one I could which is system up time, MM:SS this takes so long to refresh that it went from 39:55 to 42:52.
Previous to this I had a sensor panel with over 40 items on it with graphs and guages and it worked flawlessly.
In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> Sensor Profiling Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.
Thanks,
Fiery -
1 hour ago, ldwilliams.uk said:
I cannot find that zip file
Can you relink it please?I've checked the link and it still works.
-
5 hours ago, tigansan said:
I have purchased and have a valid key for version 7.0. But the key does not work for version 7.2!! Does v7.2 need a new key? How do I get it?
Thx
Please send me your product key in private message, and I will check it out for you. Please also let me know where did you purchase your key from.
-
On 3/13/2024 at 12:43 PM, Meta_9792 said:
Did this ever get a fix so that the sensor panel position is not relative to the main monitor?
It's not relative to the main monitor. It simply has a fixed X,Y coordinate on the Windows Desktop. The Windows Desktop may span across multiple monitors, and the Windows Desktop arrangement may change in case Windows shuffles monitors around or when resolution of one ore more monitors change. It's best if you could assure that the monitor where your SensorPanel is placed gets fixed coordinates on the whole Windows Desktop. Try to make that monitor to be left and top of everything else.
-
1
-
-
59 minutes ago, fossi said:
awesome, excellent news! renewed my license for this, works great 👍
Thank you for your continued support.
-
1
-
-
12 hours ago, Dryst said:
Two updates ago I enabled remote sensor to view sensor items from my Android phone while connected to my local wifi network. It worked fine after a brief configuration. What I am noticing is after every AIDA64 update the http sensor page stops loading from my Android phone. To get it to work again I have to change the http port from the original 80 to 8080 or 8080 back to 80. Unless I do this, the http page will not load after every update gets installed. I have not tried a reboot after update, but a port change after update gets it working again.
Is there perhaps another way to get remote sensor working again that I am unaware of? I have had two updates so far, and remote sensor stopped wortking both updates. Switching the http port as I mentioned resolved the issue.
I suppose it's because when AIDA64 is restarted during the automatic update process, the RemoteSensor module may not be properly closed and de-initialized. We will tweak that in the next AIDA64 beta update.
-
2 hours ago, Loyd said:
It is called Razer PWM fan controller, (Amazon) from the comments razer support doesn't support it very well. It plugs into a MOBO usb port and a sata port for power then runs it own software to control fans. when running "fan control" I set all other fan controls to 50% then "fan control" can run them to 0 up to 100 works great. If you can get this to inface with 64 it would be great
Thank you, we'll order a unit and check it out.
-
23 minutes ago, poiuycat said:
tried few type wording but still not get it right 😅
Custom Variables is a feature that is designed for a different purpose, it's geared towards assisting network audits in corporate environments.
AIDA64 currently supports reading strings and DWORD values from the Registry, and put them on external displays (or SensorPanel, OSD Panel, etc). You need to find a way to write the Registry values into the following path:
HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues
And name them as:
Str1
Str2
...
Str10for string values, or:
DW1
DW2
...
DW10for DWORD values. As you keep updating those values in the Registry, the values get updated on your external display.
-
1 minute ago, Loyd said:
Yes, fan control not only monitors it controls them by curves you set up. these fans in my case are directly connected to the mobo, to a razer 8 port hub, and a asus 5700 xt GPU. it works all 12 fans and it seems to use very little resources. Aida64 only monitors mobo connected fans try it
I suppose in your case we'd need to focus on the Razer 8-port hub you've mentioned. That's the device that we need to natively support in AIDA64. Please let us know what's the model name or part number of that Razer device. I assume it is connected via USB to your motherboard, is it the case?
-
On 6/8/2023 at 8:47 PM, Malcolm1822 said:
Hi,
I am having issues on the above Graphicscard, that the memory temps are not showing up in the sensor tab. Any advice ?
Thank you
I've sent you a private message about this.
-
On 3/7/2024 at 2:01 PM, Malcolm1822 said:
Hi,
I am mainly missing the GPU Memory Junction temp. However, there is a whole lot more info that the HWinfo shows such as individual MCD temps and different power measurements.
My card is a reference Sapphire 7900xtx not sure if it helps or not.
Thank you
Thank you! I've sent you a private message about this.
-
33 minutes ago, rontant said:
Oh yes.... I totally forgot I could check the fan speeds also in the BIOS.
Here is the info I found in the BIOS:
SYS FAN2 speed 833 RPM
SYS FAN speed 1537 RPM
CPU FAN 1222 RPM
SSD FAN 2667 RPM
I am using Noctua NF-A12x25 PWM for the CPU
Awesome, thank you! We will fix the fan labels in the next AIDA64 beta update. I will post a message into this topic once the new build is available for download.
-
2 minutes ago, rontant said:
Thank you very much for responding. Under the Cooling Fans section, Aida64 shows 6 fans for my Minisforum BD770i motherboard:
Chassis 793RPM
Power Supply 1452 RPM
Fan #4 (LM78) 1100 RPM
Fan#5 (LM78) 2616 RPM
GPU1: GPU 0 RPM
GPU1: GPU2 0 RPM
I just don't know which one is the CPU fan.
Do you have a reference software, made by e.g. Minisforum that could show you the list of fans with their proper labels?
Another solution may be to go to your BIOS Setup (UEFI Setup) and check the fan RPM readings there. If you do this, please take a photo of the page where the BIOS Setup shows the fan readings, and send us here.
-
8 hours ago, gtm said:
Hello Fiery,
The fix worked. Great job!
I'm attaching a picture showing the drive in the Sensor output.
George
Thank you for your feedback!
-
2 hours ago, Zeke009 said:
On one PC where I use aida64 I am encountering this error when I attempt to access Preferences. This occurred with version 7.20, so I updated to the latest beta where it also occurs.
We’ve fixed the issue in an updated v7.20 build that you can download from:
https://www.aida64.com/downloads/latesta64xe
-
1
-
-
On 3/7/2024 at 6:50 PM, TOKAR said:
Nothing, just now I can enter in import again
Can you please share one of the layouts you're trying to import?
-
7 minutes ago, Zeke009 said:
On one PC where I use aida64 I am encountering this error when I attempt to access Preferences. This occurred with version 7.20, so I updated to the latest beta where it also occurs.
I've sent you an email about this issue.
-
1
-
-
34 minutes ago, Loyd said:
I found the problem. I had put in a splitter on that fan and the splitter did not have the proper wiring once removed speed reporting was back. I did look in the bios and sys_fan1 was not reporting but i could see it was working and I could change the speed, then I remembered the splitter. On an another note how can i get input from a program called Fan control. would be nice to be able to use that to display the fans' speed. thanks for all the trouble great program
Do you mean this software?
And if so, how come it can monitor more fans than AIDA64?
What are those fans connected to?
-
17 hours ago, Loyd said:
here is the requested fil
Thank you. We've checked the sensor chip registers, but we can only find 2 fans spinning there. Are you sure your motherboard can monitor the 3rd fan properly? Can you see it having a meaningful RPM value reported in the BIOS Setup (UEFI Setup) ?
-
4 hours ago, BShenV12 said:
Late reply - but just to update, still no go. This is bare metal (and VBS is already off), while Defender is on default settings which I've never touched (turning off some of the related switches didn't work anyway).
AIDA64 7.2 did give a more detailed description of the error, saying the SSD is used by a process - which it shouldn't be, given that I've gone as far as to delete the partition of the drive.
Any ideas what else could be blocking write access to the drive?
We've done test runs, and so far we haven't found a solution. So far our conclusion is that Windows 11 simply discontinued granting low-level write access to drives
-
3 hours ago, mencall said:
Uh, I went to work today and re-downloaded and tested and took screenshots with the virtual machine and found no problem.
After analyzing it, I realized that the downloaded file should have been updated, the date of the file didn't change, but the signature time was delayed.
There was a problem running the previously downloaded version, comparing the contents and signature times of the two program files was different.
It seems that there is no problem, thanks.Thank you for your feedback!
-
1 hour ago, Vipeg said:
Let me continue this thread. I have exact same problem. Clicking menu -> Monitor diagnostics instantly causes MessageBox with error. Monitor Diagnostics window never appears. Here are screenshots.
(Windows 7 x64 SP1, DELL Inspiron 5767).
UPD. Problem solved by downloading exact same version couple days later. Seems to be, problem has been fixed. Application version is still the same though.
Yes, we've updated the packages to roll the hotfix out ASAP.
-
1
-
Threadripper 7975WX bench results
in Benchmarking, system performance
Posted
1) The current Queen benchmark scales quite bad on many-core systems. It typically stops performing any better at around 30 cores. We're already working on a new Queen benchmark that would replace the current out-dated one in the next AIDA64 stable update.
2) Our suspicion is that there may be cooling issues about the 7975WX test system. We'll make sure to improve on that and re-measure the Mandel benchmark result.