-
Posts
11334 -
Joined
-
Last visited
-
Days Won
476
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
Not at all, we don't have a problem with Corsair products. What we do have is constant issues and headaches about Corsair's policy of blocking out 3rd party software developers from accessing their hardware concurrently with their own software (iCUE). Another issue is the firmware stability problems of AXi Series PSU's, as well as the market availability of certain 2nd generation lower priced AXi PSU's. Since we have to pay out of pocket for each of those Corsair products that we need to work on, we simply can't afford to purchase the highest-end and most expensive model. Sadly nothing else seems to be available on the market than AX1600i which is bleeding expensive. We'd be happy to continue investigating the issues related to 2nd generation AXi PSU's in case we could get our hands on one.
-
Hello i tried to run AIDA64 (ASRock B460M Pro4)
Fiery replied to Akani's topic in General Discussion
Yes, it's actually normal: on modern PC's using just one memory module per memory channel could help to stabilize an otherwise problemous configuration since it puts less stress on the memory controller. -
I'm afraid it's not possible to access DAC chips in Android devices.
- 1 reply
-
- sonido
- dispositivos
-
(and 1 more)
Tagged with:
-
Your motherboard isn't capable of monitoring those readings.
-
No Fan Speed Reading in Sesnsor Data with Schenker Notebooks
Fiery replied to FuglyOtherMucker's topic in Hardware monitoring
Thank you for the data! I'm afraid we cannot find any sensor readings among those registers. This sadly is the case with most laptops, so it's not just yours but most of them out there. Only Clevo (the original manufacturer of your laptop) would know what registers can be used for fan monitoring, but usually those companies wouldn't reveal such technical details with anyone. -
AIDA64 x OpenRGB for system monitoring with expressive RGB?
Fiery replied to daneeh777's topic in 3rd party solutions
Asus RGB devices are currently supported through the Aura SDK. We do have direct support (that doesn't require Aura SDK) for Claymore keyboard and Gladius II mouse. If you have other Asus products than these two, please let us know and we'll check if we can implement direct support for them. -
The best place to look for those is:
-
Hello i tried to run AIDA64 (ASRock B460M Pro4)
Fiery replied to Akani's topic in General Discussion
Try to lower memory frequency and/or set the memory modules to work at 2T Command Rate (tCR or tCMD). -
No problem at all, AIDA64 quite a complex piece of kit. Some call it a Swiss Army Knife for your PC
-
You can see a more precise and dynamically updated BCLK reading on the Computer / Overclock page. You can adjust the number of decimal digits for clock frequency readings at AIDA64 / main menu / File / Preferences / Hardware Monitoring / Decimal digits for clock speeds.
-
Every AIDA64 Extreme version after 5.99 causes BSoD on Asus P4B533
Fiery replied to Buhntz's topic in Bug reports
We've tested it with Catalyst 12.4 WHQL + Windows 7 32-bit + HD4670, and it worked flawlessly for us. Have you tried to re-install your video driver and update the motherboard BIOS? -
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
-
You can use the Registry for that purpose. Put your values into the following Registry path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues Name them as Str1, Str2,... Str10 to have 10 string values imported to AIDA64. Name them as DW1, DW2,... DW10 to have 10 integer (DoubleWord) values imported to AIDA64. If you place a value to one or more of those Registry entries, the values will get listed among the other sensor items for LCD, OSD Panel, SensorPanel, etc.
-
Thank you! Please post 2 further dumps: Disk Debug / Disk Controllers Dump and Disk Debug / NVMe Dump.
-
We've been notified today that fan#2 and fan#3 are coupled together on Aorus RTX 3000 Series video cards and so they will spin at the same RPM and use the same duty cycle setting (fan speed %). Hence what AIDA64 measures as GPU2 Fan will apply to fan#3 too.
-
AIDA64 v6.32.5609: GPU Diode Temperature no longer exported?
Fiery replied to Grestorn's topic in Hardware monitoring
I suppose Aquasuite relies on the External Applications feature of AIDA64. So you should check if all the necessary sensors are ticked (enabled) on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications page. Support for High Flow Next has been added to the latest beta release: https://www.aida64.com/downloads/latesta64xebeta -
fixed: Support for 3 GPU fans (EVGA RTX 3080 FTW - iCX3)
Fiery replied to schrutic's topic in General Discussion
Awesome, thanks a lot for your help! -
fixed: RTX 3080 GPU Temperature Sensor 2 Degrees Off
Fiery replied to schrutic's topic in Bug reports
Thank you for your feedback! -
fixed: RTX 3080 GPU Temperature Sensor 2 Degrees Off
Fiery replied to schrutic's topic in Bug reports
Both And in theory, they should match -- in which case only one should be kept by AIDA64. And that's usually the case. -
AIDA64 v6.32.5609: GPU Diode Temperature no longer exported?
Fiery replied to Grestorn's topic in Hardware monitoring
Ah I see. Are you sure it's due to an issue with AIDA64? -
I'm puzzled, since our Android app (AIDA64 for Android) doesn't interact with anything running on a PC Maybe you mean Odospace? Or Logitech Arx? Or running browsers on the Android devices with RemoteSensor?
-
fixed: Translate bug (Sensor page dynamic update)
Fiery replied to tistou77's topic in Localization, language modules
Thank you! -
Thank you for your feedback!