-
Posts
11960 -
Joined
-
Last visited
-
Days Won
520
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
You've got a private message
-
We're working on it.
-
Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.
-
Missing Fan Speed Sensor Data (Asus Pro WS WRX80E-Sage SE WiFi II)
Fiery replied to beas62's topic in Bug reports
I'm afraid we cannot find the rest of the fans in the EC space -
fixed: Missing 2 system fans (MSI MAG X870E Tomahawk WiFi)
Fiery replied to Zensei's topic in Hardware monitoring
Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. -
Please avoid posting a single issue into multiple topics. I've replied you in your other topic.
-
AIDA64 throws a Blue Screen when closing it with the OSD Panel open
Fiery replied to Selim Gürsu's topic in Bug reports
Can you please post a photo of the blue screen? -
I've sent you a private message.
-
Missing Fan Speed Sensor Data (Asus Pro WS WRX80E-Sage SE WiFi II)
Fiery replied to beas62's topic in Bug reports
I'm sorry for the late response. As you can see, we haven't released a new beta build in 3 weeks. It's only because we're working extremely hard on the next generation of AIDA64 that includes major changes and improvements. We're rolling out the first beta build of the new generation in a few days from now. I'll also update you on the missing fans issue soon too. Thank you for your patience. -
I've sent you your product key both in private message and email. I apologize for the slow response from our Support Team. It's because this is a 4-day weekend (public holiday) here in Hungary.
-
New cache and memory benchmarks in AIDA64 v3.00
Fiery replied to Fiery's topic in Benchmarking, system performance
There's a brand new interconnect in Strix Halo that is quite under documented and we know very little about its pecularities. Once we can get a hold of such a platform, we can dig deeper. Until then I'm afraid I don't have the answer to your question BTW, do you have this system up and running? -
Do you have any external drives among the 15 SSD drives you've got? (BTW, wow, 15 drives! amazing setup)
-
I'm not sure what you mean. Please explain your request/idea with more details.
-
Thank you for your feedback. Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.
-
There's no native ARM binary for AIDA64. So whatever you can see there is obtained in emulation and so cannot be evaluated as true performance metrics.
-
We're working hard on the next generation of AIDA64 which will eventually turn into v8.00. We're rolling it out as a beta update in a few weeks from now. It will already support GPGPU benchmarks and GPU stress testing of GeForce RTX 5000 Series. So stay tuned and make sure to have automatic updates to beta releases enabled in AIDA64 / Preferences / General / NetUpdate / Update type / Stable and beta updates.
-
I've sent you a private message about this.
-
Thank you for your support!
-
Yes, the new generation uses a completely different, and a lot more tricky protocol. We're still waiting for our device to arrive. I'm afraid I cannot provide you with an ETA at this time.
-
Yes, just make sure to use the portable (ZIP) package for such purposes.
-
Wrong information about battery's condition
Fiery replied to DmitryMarshmallow's topic in Bug reports
Thank you for your feedback. AIDA64 relies on the standard Android Battery API to report battery health state. Sadly, on some devices the Battery API provides incorrect information, e.g. "Good" state for a very old battery. I'm afraid we cannot fix such limitations from our app.