Fiery

Thank you for the feedback

There's definitely an issue about using high BCLK setting on MSI and Asus motherboards. It's not about the benchmarks working off, they do work well actually. The benchmark results however are scaled by the CPU core clock value, and that's where there's a glitch. We have to check the CPU registers to see where does AIDA64 go wrong about calculating the CPU core clock. Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic. If it's possible, please do that for both clock settings of 46x100 and 23x200.

Here's the first AIDA64 beta with the new RGB LED module working: http://www.aida64.com/downloads/latesta64xebeta You can enable it from AIDA64 / main menu / File / Preferences / Hardware Monitoring / RGB LED. The new module is designed to be used on per-key RGB LED keyboards. It currently supports Razer BlackWidow Chroma and Logitech G910 keyboards only. We're planning to implement support for Corsair RGB keyboards in the next AIDA64 beta update. For Razer keyboards the currently beta state Razer Chroma SDK has to be installed. IMPORTANT: In order for the beta Chroma SDK to work properly, Synapse has to be closed! Hopefully the stable build of Chroma SDK will eliminate this limitation. For Logitech G910 the latest version of Logitech Gaming Software has to be installed. It's also recommended to update the keyboard's firmware to the latest version. We've basically implemented 3 out of the 4 proposed ideas, and a variant of idea #3. So, you can use the RGB LED module in 4 ways right now: 1) Single Key: You can display a temperature, voltage, fan speed or other monitored value on a single key of the keyboard, by altering the colour of the key based on the actual value. You can set the limits in the same way that you set the limits for bars on the SensorPanel or LCD. 2) Row of Keys: You can use a row of keys, like Function Keys or Numbers to make a bar that changes its length and colour as well, based on the actual value of the monitored item. Due to different localized keyboard layouts, we had to define a larger set of rows than the usual 5 rows of Function Keys, Numbers, QWERTY..., ASDFG... and ZXCVB... 3) 2 Digits: By using the Functions Keys and Numbers rows, you can display a value using 2 digits. The first digit will be displayed on the Functions Keys row, and the second digit will be displayed on the Numbers row. However, in order to enable quicker readout, AIDA64 will try to display both digits on the Numbers row whenever it's possible. 12, 35, 79 and other numbers will be displayed that way, but 54, 82, 97 (etc) will be displayed by using both the Function Keys and Numbers row. There's also a setting to let you divide down the measured values by a factor. So, e.g. by using a divisor of 100, you can display fan RPM by having just 2 digits. 1820RPM will then be displayed as "18". 4) 3 Digits: A variant of the 2 Digits solution, by also using the Numeric Keypad (NumPad) for the 3rd digit. Just as with 2 Digits, this feature will also try to display as much digits as possible by using only the Function Keys and Numbers rows. Please let us know what you think. By using this feature you will quickly realize that it is more basic and more limited than other monitoring modules of AIDA64, but keep in mind that this is only a start. If there's a considerable interest in this feature, we'll improve and extend it to make it more practical and also more fun to use it

Sounds great, thank you It could be because in your case we're using an exact multiply of 64KB. Let's see how it goes with other frames

Yes, we've just added a new, hidden option that you can use to tweak the JPEG limiter by yourself, and so try multiple values without us having to alter the main AIDA64 code base. Download the new AIDA64 beta from: http://www.aida64.com/downloads/latesta64xebeta Go to AIDA64 / main menu / File / Preferences, and simply press the OK button. Close AIDA64, go to AIDA64 installation folder, and open the AIDA64.INI file in a text editor (e.g. Notepad). Find the following line in there: HWMonSPLCDJPEGLimit=0 And change it to a value below 500, e.g.: HWMonSPLCDJPEGLimit=490 That will effectively limit the JPEG frame size to 490KB. I think the actual limit will always be an exact multiply of 64KB, but it's just a theory that has to be verified. If my hunch is right, you will still experience issues at 490KB, 480KB, 470KB, etc, and it will only work reliably when you set it to 448KB (7x64KB). Please let me know how it goes. What sort of hardware monitor value type are you thinking of? The colour of a Simple Sensor Item label?

We've just rolled out the mentioned new AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta

Try to enable the option Prevent SensorPanel from being minimized in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel.

AIDA64 main window can remember its size if you enable that in AIDA64 / main menu / File / Preferences / Layout. The Preferences panel will also remember its size. We've just tried, and importing SensorPanel layouts into a RemoteSensor layout works fine, including all graphs. If you have difficulties importing your SensorPanel layout, then please open your .sensorpanel file in Notepad, find the entry that is imported incorrectly, and copy-paste that line into this topic. Or, you can attach the whole file to your post if you want.

Yes. Previously, swap space incorrectly included the physical memory, and we've added up physical memory and swap space to form virtual memory, which again was incorrect. We had to remove virtual memory and rename swap space to virtual memory to make it right.

You're good to go. Go to the next page in the AIDA64 Preferences called LCD Items, and start building your own LCD layout. As for resizing, the whole window should fit in the Windows Desktop area, even when it is resized automatically to fit the RemoteSensor LCD layout builder. When you use RemoteSensor, Logitech Arx or other high-resolution LCD, the Preferences window will have to be adjusted to a minimum width and height to make sure the layout editor fits properly. If you then resize the window, the window size will of course be remembered.

Yes, it is, but it's not all that simple There used to be virtual memory reading on the Motherboard / Memory page which we've removed, and then renamed swap space to virtual memory there. So the "new" virtual memory is not the old virtual memory, but equals to the old swap space. I admit, this change is a bit confusing, but we've had to do this because the old method didn't provide correct values.

No, I'm afraid it's not possible with AIDA64.

No problem BTW, you can find the full list of values in the AIDA64 user's manual, on the External Applications page.

We've fixed it up, thank you for reporting the issue to us.

Does AIDA64 appear in the list of apps in the menu of the LCD display?

Thank you for the report. Fan #1 should belong to one of the Kraken devices there. Do you have one fan connected to each Kraken, so 2 fans for the 2 Krakens?

Then please upgrade to the latest beta version of AIDA64 Extreme available at: http://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

What LCD device do you have? Is it Logitech G19?

CAM and AIDA64 will collide, so you have to keep only one of the running. Even if it's running in the background CAM would talk to your Krakens and that traffic will collide with AIDA64 Kraken fan RPMs should be reported by AIDA64. Please copy-paste the full content of the Computer / Sensor page into this topic, or post a screen shot. If you do a screen shot, please make sure to keep as much content (of the Sensor page) on the shot as possible.

1) Before we've implemented support for Kraken devices, did AIDA64 work well on your system? 2) Do you have NZXT's own CAM software installed? If yes, then is it running in the background? 3) Do you have any other software running in the background that may poll the Kraken devices concurrently with AIDA64?

Do you mean that if on your system AIDA64 starts up before Razer Synapse, then Synapse will kill the AIDA64 process when it starts up? Why would it do that? Or maybe it's a mixup inside Synapse, so the Razer DLL that AIDA64 uses would crash and it would pull AIDA64 main process with itself?

Thank you. Please avoid posting a single issue into multiple topics. This topic is closed.

I've just tried to register a new user to this forum, and the email with the subject "New Registration at AIDA64 Discussion Forum" came from the email address: forums AT finalwire.com If you received the email message from somewhere else, then please forward that email to the email address I've sent you in private message, so we can check it out. Thanks, Fiery

We implement hot-plug support for LCD devices on a case-by-case basis. Please let us know what LCD do you have, and in what situation does AIDA64 lose connection to your device. Do you disconnect the device sometimes? Is it due to an intermittent communication issue between the LCD and AIDA64? Thanks, Fiery

Why would it be scary? I work for FinalWire, the company that sold you that AIDA64 license I simply took your email address that you used to register into this forum, and searched for it in our customers database. Quite usual stuff, although mostly we do that when a customer loses his license key and wants to recover it.