All Activity

Poderia compartilhar?

Both 32-bit and 64-bit versions of sens_oal.dll are located in de Bin.cab file of the original installer after extraction. But only one of them gets installed in both 32-bit and 64-bit system folders during installation. Can't remember which one though 😷 My workaround is to extract Bin.cab and put both sens_oal.dll files in both appropriate system folders.

here 😁

Thank you! Please also post a screenshot of the Computer / Sensor page of AIDA64, showing all fans listed there.

Hello Fiery I have attached the file ecdump.txt isasensordump.txt

I also noticed yesterday while gaming that the AIDA FPS sensor shows 0.

Thank you for your feedback!

AIDA64 v8.40 (latest version) should be able to read all the fans you've listed. If that's not the case, then please post a screenshot of the Computer / Sensor page of AIDA64 (showing all fans listed there) as well as an ISA Sensor Dump and an Embedded Controller Dump. To create an ISA Sensor Dump: in AIDA64 please press Ctrl+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. To create an Embedded Controller Dump: in AIDA64 please press Ctrl+D --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Where does that installer place the 64-bit DLL module?

Hello @Fiery, I’ve run into another issue. The AIDA64 FPS sensor isn’t working either, so I’m stuck reverting to RTSS. Please look into the GPU Hotspot and AIDA64 sensor. Thank you.

Creative uses the Creative OpenAL 1.1 installer on all products to place the OpenAL32 dlls, and this does not do what you claim, What you're recollecting is on XFI where the 64bit CT_OAL file is placed in both the 64 and 32bit system32 locations due to a flawed inf configuration.

has stuff all to do with OSD, this issue has been reported countless times, even by yourself 6 years ago the only way to run 8.x on many 10 and 11 systems is by replacing the kernel driver with the 5.99.4800 one, 5.99.49xx and later affected instead of feeding it the driver files, give it the dump file as well

Could depend on if you added m.2 to the slot right above the graphics card and how many pcie lanes your board and cpu support. The wrong combo of things on the board can cause bifurcation. I would suggest reading the board manual on this.

I’m having exactly the same problem with this version of AIDA64 8.35.8400 with NVIDIA GeForce RTX 5090FE.

1280 x 800. TURZX 8 inch. No AIDA 64 AMD.zip

Hello Is it possible to add the motherboard fan headers shown in the attached image to AIDA64?

so the problem devolved until it was exhibiting symptoms regardless of toggling LCD. 10/9/26 3:15 PM Fresh boot, AIDA 64 launched at boot with LCD Support Enabled, All Sensor items removed and ALL stability options disabled. This test is to try and see if it is LCD and LCD support alone (which i suspect) that is causing the issue we should know in about 48 hours. and LCD update frequency is set to 100ms. Had to restart at some point to reinstall armory crate going to have to re run this test. Have been on a day or so at this time and i just set LCD update frequency to 100ms it defaulted back to 5,000 ms. It is now 11/12/26 12:00 PM

While in this particular session for what ever reason, the symptoms disappear when i disable LCD display, and re appear when the LCD display is enabled (as opposed to another fresh boot and 2 day test). Having this opportunity while i can observe this i tried some things. Right now i confirmed that with ALL sensor items removed, AND all stability options disabled, with LCD support enabled Symptoms are present. Symptoms go away when LCD support is disabled. This suggests a general leak of some kind that pertains directly to AIDA 64 LCD support on the ASUS Ryujin III Extreme.

GREAT!!!!!! It works! I see Temp, Fan Speed, Voltage, Current and Power Values. Good for my rainmeter monitoring widget It took a long time, but better late than never THX YOU

Please post this in https://forums.aida64.com/forum/8-bug-reports/ or submit a support ticket at aida64.com

Call of Duty MW4 arrive a grand pas

I've sent you a private message. We currently have no plans to offer an "eternal" license.

Also interested in discount season to start using the Extreme version. When will it start? Also extremely interested in one-time purchased eternal license (for let's say x5 times of one-year price) with any updates available ever. Yearly subscription motivates to cancel it at some point.

Hello, I have a 7-inch 1024x600 USB display sold as "compatible with AIDA64", and I would like to know if there are any plans to add native support for this type of display in AIDA64. The device uses the following USB ID: VID: 345F PID: 9132 REV: 0110 Windows enumerates it as a composite USB device with at least these interfaces: USB\VID_345F&PID_9132 MI_00: USB Input Device HID-compliant vendor-defined device MI_03: MS USB Display USB\VID_345F&PID_9132&MI_03 The display currently requires WinUsbDisplay.exe to remain running in Windows. If I terminate WinUsbDisplay.exe, the LCD remains powered on and keeps displaying the last frame, but the image freezes and no longer receives updates. The manufacturer provides the software/drivers and information for this 7-inch display here: http://www.lcdwiki.com/7inch_PC_Sub_Display My goal would be to use this LCD directly with AIDA64, if technically possible, without having to keep WinUsbDisplay.exe running as an additional process. I understand that simply replacing the current USB driver with WinUSB/libusb would not necessarily make the display compatible with AIDA64, since AIDA64 would also need support for the device/protocol. So I would like to ask: Is VID_345F / PID_9132 (MS USB Display / MS9132) currently supported by AIDA64 in any form? If not, are there any plans or ongoing work to support this controller directly? Would implementing native support for this type of USB display be technically feasible in AIDA64? Would the official driver/software package linked above be useful for investigating the communication protocol? I have the physical device available and would be happy to help with testing or provide additional technical information, such as USB descriptors, hardware IDs, driver files/information, screenshots, or USB traffic captures, if that would help with implementing support. Thank you.