Fiery
-
Posts
12008 -
Joined
-
Last visited
-
Days Won
525
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
We've just rolled out the first AIDA64 beta that includes the new update "what's new" information link. You'll need to wait for the next beta though to first have the information shown.
-
Not yet. If you don't want to use a beta build, then please wait for the next stable build which we currently have scheduled for next month. -
Thank you. In your Registry, at least by looking at its current state, there should be no problem determining (in AIDA64) that you have no paging files configured.
-
Thank you for your feedback and kind words
-
Please avoid posting a single issue into multiple topics. I've replied you in your other topic.
-
Please let us know more about your hardware configuration. Motherboard model, CPU type, video card(s) model, HDDs/SSDs.
-
We're currently investigating this issue. It seems to be due to the performance drawback of one or more of the recent security patches (Spectre, Meltdown, etc).
-
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. If it doesn't help, then 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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
-
No, that's a separate issue that we expect nVIDIA to fix in a future ForceWare update.
-
Detecting sensor information... (Asus ROG Strix B450-F Gaming)
Fiery replied to lukebro's topic in Hardware monitoring
Thank you. Go to AIDA64 / main menu / File / Preferences / Stability, disable (uncheck) the option called Asus WMI sensor support, and restart AIDA64. -
We've presented our arguments, and also asked fellow developers (of CPU-Z, HWiNFO, HWMonitor, SIV, etc) to join in our efforts, but it didn't go through just yet. You as owners of Corsair hardware may need to put more pressure on Corsair to force them to find a proper resolution to this issue.
-
Try to lower the DRAM frequency slightly. It may just help to stabilize your system.
-
I don't think it's possible to pull the calculated efficiency data from Corsair Link Software or iCUE.
-
Thank you. The issue has already been fixed in the latest AIDA64 Extreme update: https://www.aida64.com/downloads/latesta64xe
-
AIDA64 uses the Windows default date format to display the date. I suppose you can alter the date format in Windows Regional Settings to achieve the date display you're looking for.
-
about the unit of Netspeed, better to add the option of "Mbps"
Fiery replied to zhuoziqiang's topic in Brainstorming
No, because AIDA64 doesn't support dynamic measurement units. -
That would still provide virtualized values and not the real values for the underlying hardware, wouldn't it?
-
We've tried to reproduce the issue on various Win7 64-bit machines of ours, but with no luck so far. If you still experience the issue, then please open Registry Editor (by running REGEDIT.EXE), navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management And export the Memory Management section by right-clicking on Memory Management in the tree --> Export. Please rename the resulting file to MEM.TXT and attach it to your forum post. If you have difficulties doing that, please contact me in private message.
-
fixed: NVMe SSD no longer reporting temp (Z170 NVMe RAID0 array)
Fiery replied to Arctucas's topic in Bug reports
Thank you for your feedback -
That's most likely because of a collision between AIDA64 and Corsair iCUE. In iCUE Corsair decided to remove the synchronization mutexes that ensured that previous Corsair Link Software worked great together with 3rd party monitoring applications like AIDA64, HWiNFO, HWMonitor, SIV, etc. We're in conversation with Corsair and try to convince them to put the mutexes back again. Until then the collision can only be avoided by using only iCUE or only AIDA64, but not the two together in the same time.
-
Please contact our international distributor Abseira for details on that: https://www.aida64.co.uk/support-request
-
Thank you. IMHO no matter what component of the SSD the thermal reading is coming from, if it's higher than the rest, that's the one that is the critical temperature reading and so it should be considered the drive temperature.
-
From where did you gather the info on the meaning of Drive Temperature 1 and 2?
-
Thank you for your feedback, I'm glad it works now. Corsair Commander Pro should work already, as long as you have Corsair Link sensor support enabled in AIDA64 Preferences / Stability.
-
Close AIDA64, download the ZIP package, extract its contents into your existing AIDA64 installation folder, and let it overwrite any existing files. Don't worry, your existing settings and your license will both be retained. Just make sure not to delete any files during the process.
