Fiery

Awesome

Sounds great

Thank you. It means your motherboard BIOS fails to provide the T_Sensor thermal reading (as well as the Chipset temperature reading for that matter) due to a BIOS bug.

Thank you for helping us implement support for Z10 RGB.

Please try to perform the dumps that I asked for in my first post in this topic. You can have the debug popup menu pop up if you use the Ctrl + Alt + D key combination. When that menu pops up, select System Debug, then USB Dump to make the USB dump. Then also select Sensor Debug --> Aqua Computer Dump in order to have the other dump.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aqua Computer 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. Also right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

I think we've managed to fix the issue in 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.

No problem. I think we've managed to fix the issue in 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.

Thank you for testing the first beta with Z10 RGB support. I'm glad at least on the USB communication level it worked out okay. We've fixed the LCD preview issue in the following new beta build: https://www.aida64.com/downloads/latesta64xebeta Note that you cannot re-use the old profile for Z10 simply because Z10 and Z10 RGB are way more different about their LCD displays than what at first glance you would think. The old (the original) Z10 has a graphical display with a resolution of 160 x 32 pixels, while the new Z10 RGB steps back quite a lot by having only an alphanumeric display that supports 20 x 4 characters. That's why you cannot change the font on Z10 RGB at all.

Stability issues are not black and white. There are a lot of grey area in there where even the same software could pass 9 out of 10 times. But when only a single software fails only once, it means the system is almost stable. I'm sure what you experience is not due to a bug in AIDA64. But, if you conclude that your system is 100% stable, then you don't need to use AIDA64 System Stability Test actually.

We will fix the issues coming up about Aqua Computer devices due to the latest firmware upgrade in the next AIDA64 beta update. As for power consumption, it is a calculated value (based on the TDP of the video card) and not a measured value as it is displayed in other tools like GPU-Z. If you know the TDP of your video card, you can use the Correction facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction) to apply the TDP as the Ratio to end up having the same calculated value as in other monitoring software.

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Please post a screenshot of the Computer / Sensor page of AIDA64. Also 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, it means your system is not 100% stable.

We've implemented support for EVGA Z10 RGB LCD display in 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.

Which of the sensors do you find inaccurate?

On your motherboard T_Sensor should be listed as Temperature #1.

That's my guess. But it's difficult to tell since it could be a number of other things as well.

This is about downclocking actually Try to set the memory frequency to a conservative setting (e.g. DDR4-2666) where memory timings are less of an issue. Or, you can try asking for proper assistance from overclockers and enthusiasts at such forums like XtremeSystems: http://www.xtremesystems.org/forums/forum.php

You should check sub-3000 MHz memory frequencies as well. In case your system gets stable at e.g. DDR4-2666 setting, it means it's the RAM that has to be carefully tweaked by raising the memory frequency step by step and also adjusting memory timings if necessary. Command Rate can be adjusted in the BIOS Setup (UEFI Setup) on the page where you can manually set DRAM (memory) timings. As for CPU+FPU, that is still a scenario where both the caches and some portion of system memory is still used. The System Memory subtest allocates almost the entire available physical memory, so it can be considered a more thorough test than when you run the AIDA64 System Stability Test without that subtest enabled, but even without it AIDA64 can catch stability issues.

As long as the Commander Pro unit can monitor the thermal sensors, AIDA64 will be able to show you the readings. We cannot guarantee that a certain device will be compatible with another device. All we can assure you is that the Command Pro device is fully supported by AIDA64 as long as you don't try to use it together with Corsair's own monitoring software (iCUE) which is notorious for causing collisions on the hardware communication side.

Awesome, thank you for your help!

Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. 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

Thank you. It must be due to a memory leak on one of the 100+ pages that AIDA64 offers. Problem is: without knowing what exact page causes the issues, it's difficult to dig deeper into it. Please try to narrow it down and try to find the one page that causes the memory leak on your system. My guess is that it will be one of the software-related pages, so I'd start with the Computer group (in the left menu), then Operating System, then Server, Display, Multimedia, Network, DirectX, Software, Security, Config, Database. If none of them causes the memory leak, only then I'd check the hardware-focused groups: Motherboard, Storage and Devices. If you right-click on one of the mentioned page group names, you can make a quick report, so you don't have to hassle with the Report Wizard and can quickly step through all those page groups to find the culprit.

Yes, AMD did contact us to talk about this issue and find a middle ground that would satisfy all users. I'm not sure what that middle ground would eventually be, since only this week we can get a proper Matisse test system to check out the problem in details. We'll do our homework (test runs, research) and will come up with something that hopefully will be useful for you as as well as other owners of this superb CPU by AMD.