-
Posts
11546 -
Joined
-
Last visited
-
Days Won
489
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
fixed: ASRock X299 Taichi XE - CPU Optional fan speed not showing up
Fiery replied to Chris77's topic in Hardware monitoring
Thank you for your feedback -
Thank you for your feedback!
-
2 out of the 3 chassis fans seem to be properly detected by AIDA64. Do you only miss one fan out of three, or you miss more fans?
-
Thank you for checking it out thoroughly. It will be fixed in the next AIDA64 beta update.
- 45 replies
-
- rampage vi extreme encore
- asus
-
(and 1 more)
Tagged with:
-
Bugs with probes reading (Asus Rampage VI Extreme)
Fiery replied to tistou77's topic in Benchmarking, system performance
Please note that when an AIDA64 benchmark is launched, AIDA64 monitoring threads are put to sleep in order to avoid them interfering with the benchmark threads. Otherwise the benchmark results would be lower.- 43 replies
-
Thank you. Please check if the DIMM slots numbering is correct on the Motherboard / SPD page. Maybe it's correct there, and is only wrong on the Computer / Sensor page?
- 45 replies
-
- rampage vi extreme encore
- asus
-
(and 1 more)
Tagged with:
-
Thank you for your feedback. I'd say the values reported by AIDA64 are closer to the truth than SIV's
-
Does AIDA64 report Quad Channel DDR4 on the AIDA64 CPUID Panel? If yes, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). 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
- 45 replies
-
- rampage vi extreme encore
- asus
-
(and 1 more)
Tagged with:
-
Are you sure your DIMM slots are properly populated in order to have all 4 memory channels enabled? If yes, then it means LGA2066 motherboards do not use a single layout for DIMM slots assignment -- in which case we need to implement motherboard specific DIMM slot numbering logic
- 45 replies
-
- rampage vi extreme encore
- asus
-
(and 1 more)
Tagged with:
-
Thank you for the tip and also for your patience about this issue. We've implemented RAID member enumeration, RAID SMART support for LSI "IR" SATA RAID controllers; as well as SMART support for drives connected to LSI "IT" SATA AHCI controllers. 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 how it works.
-
Here's the above mentioned new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
-
fixed: ASRock X299 Taichi XE - CPU Optional fan speed not showing up
Fiery replied to Chris77's topic in Hardware monitoring
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 -
It is Here's the fixed AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
- 45 replies
-
- rampage vi extreme encore
- asus
-
(and 1 more)
Tagged with:
-
Using AIDA64 you can have FPS displayed on an external display as long as the tool (RTSS or Fraps) provides the readings to AIDA64. AIDA64 itself cannot monitor FPS directly.
-
Strange in-game lagging with Odospace LCD and RemoteSensor support enabled
Fiery replied to xcite's topic in Bug reports
I'm afraid we haven't been able to reproduce the issue on our test systems yet. We also haven't found a clear pattern in the various bug reports about slow EC communication issues. -
AIDA64 doesn't monitor mouse activity.
-
As far as I can understand, that picture frame isn't capable of transferring full bitmap frames from a computer to the digital picture frame. So it cannot be supported by AIDA64 or any other monitoring software.
-
fixed: Asus Maximus X Hero not all sensors detected
Fiery replied to facboy's topic in Hardware monitoring
Yes, those spikes are because LiveDash also fiddles around the EC, and switches EC banks back and forth. There's no real solution to that issue I'm afraid. The only "solution" is to disable EC bank switching in AIDA64, that way you won't see any temperature spikes in LiveDash. -
Is your CPU or RAM overclocked, or has specially tuned settings applied in the BIOS Setup? (UEFI Setup)
-
I'm not sure if it's possible. We'll try an older method that worked on previous Asus ROG motherboards, and we'll see A new AIDA64 beta build should be ready sometime tomorrow. I'll post a message into this topic once the new beta build is available for download.
-
The CPU Package value and the other 2 values (CPU VDD power and CPU VDDNB power) are measured using different interfaces of the CPU. Hence their values may not match each other, and one (or both) may well be inaccurate -- we've seen such issues with previous AMD processor generations like Kaveri already. BTW, VDDNB is the north bridge (memory controller and fabric) section of the Ryzen CPU.
-
Detecting IMEI would require our app to request for special permissions. We try to avoid asking for too many permissions, so we skip IMEI detection. Regards, Fiery
-
Some Maximus X Hero motherboards have VRM temperature readout, while others wouldn't. It seems there are multiple versions of seemingly the same motherboard are out there.
-
Corsair decided to discontinue supporting the industry standard synchronization mutexes in the recent updates of their Corsair Link Software. So it may no longer work together with 3rd party monitoring software like AIDA64
-
Thank you for your feedback