Fiery

We've implemented preliminary support for H115i Platinum sensor monitoring in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta It may not work reliably while Corsair iCUE is running concurrently with AIDA64. Please let me know how it works on your system.

I may not be able to help you, but I have a quick idea: maybe you can connect the display to a different port on your video card? Maybe even an available DisplayPort output using a DP->HDMI converter? This may not make any difference, but it may worth a try...

I guess the video BIOS (or video driver) controls the fans in a way to make the duty cycle drops or increases smoother than on other video adapters. We've experienced the same behavior on certain video adapters, albeit it wasn't that slow of a process to drop or increase the duty cycle.

1) What kind of HDDs do you have where you can experience this issue? 2) What sort of SATA controller are they connected to? 3) What operating system do you have installed? 4) What motherboard do you have?

Can you see a pattern in the issue? Like it mostly happens when you restart your computer? Or it mostly happens when you shut down your computer? Or maybe it only happens when you put the computer to sleep? Do you use Windows 10 64-bit with the latest patches applied?

It's normal if the drive disappears from the list of ATA drives as it is managed by Windows. You can try enabling the two RAID related options in AIDA64 / main menu / File / Preferences / Stability and restart AIDA64. Let me know if it fixes the issue.

In your dump above I can see the list of video adapters as: ------[ Video Adapters ]------ nVIDIA GeForce GTX 1060 6GB (PG410) [10DE-1C03 / 10DE-11D7] Zotac GeForce GTX 1060 3GB [10DE-1C02 / 19DA-2438] It means at the time AIDA64 started up, it could detect 2 video adapters in your system. "Video adapters" as a technical term in this case includes mining adapters and nVIDIA Tesla accelerators as well. However, in case your mining card was sleeping while AIDA64 was starting up, it could well be invisible on the PCI bus and so not picked up by the GPU detection module of AIDA64. You can try to enable Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability in order to make sure all video cards and mining adapters are "nudged" by AIDA64 at its startup before the actual GPU detection is performed. Please let me know if it helps.

In case you have a low update frequency configured, but the refresh rate is still rather long (over 1 second), it means the Samsung USB protocol is the bottleneck. I'm afraid we cannot fix it from our side. As for the hanging, it could still be due to overheating in case the controller chip inside gets too warm and the heat is not transferred properly out of the frame PCB. Disassembling the frame and directly inspecting the chip's thermal state during operation would be a good idea, but I'm not sure if you can disassemble the frame easily at home...

The blinking is usually caused by an unstable reading that appears and then disappears from the Sensor page. If it's possible, please try to find the reading that gets appearing and disappearing, so we can check its register content.

Thank you for your feedback. Can you please send us a photo of the HW Monitor page of the BIOS Setup (UEFI Setup) where it shows all thermal readings, including the DIMM temps?

Awesome, thank you for your help!

Thank you, but that report doesn't include the 3 necessary dumps that a report submit would automatically send us. If you're hesitant about performing the report submit process, please let me know, and I'll send you special dump requests in private message.

Start AIDA64 first, go to main menu / File / Preferences / Hardware Monitoring / LCD / Samsung. Enable Samsung LCD support there, and it should switch your 800P frame from Mass Storage Mode to Mini Monitor Mode. After that happens, a new device will appear in Device Manager. You need to install the supplied custom driver ... http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip ... then, and restart AIDA64 to start using the frame with AIDA64. Let us know if you get stuck during that process.

The drop in VP8 scores are due to the security patches rolled out in the past 13 or so months.

Purged him. Thank you

Please try it with the latest ForceWare release of 418.81 WHQL.

It could be because the video driver is so busy that it cannot handle the mouse cursor movement

AIDA64 already supports controlling the RGB LEDs of Asus motherboards via the Asus Aura SDK

Using AIDA64 v5.99, please 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. Also 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. Thanks, Fiery

Thank you for your feedback!

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

GPU test is normal to make the mouse cursor sluggish, since the OpenCL driver goes through Direct3D and so it directly affects the smoothness of the video driver. As for the FPU test, it's the most demanding task that our stress test (and also out of many other stress tests) puts on your system. When the FPU test is running, your processor draws the maximum power and generates the most heat. If the PC restarts during the FPU test, especially when it happens immediately after starting the test, it usually means there's a power delivery issue in the system. In most cases it's because the PSU (power supply unit) cannot provide enough power to feed the processor under heavy load and/or the motherboard has a faulty component on it. If you can, try to borrow another, ideally higher specified (more powerful) PSU, and try your system using that. If it makes the FPU test run just fine, your current PSU is the culprit.

It means your system memory is not stable at 3000 MHz setting. You can try to fine-tune the memory timings or adjust the memory voltage to make it stable.

Only the platform developer (ie. the manufacturer of your device) knows what they stand for.

Bars can be rotated by specifying a width that is smaller than the height