Fiery

Something between 12 and 24 hours is best.

I'm sorry, but the crash is due to ULPS, so there's nothing to log about that. We could log all GPU register readouts to see which register reading causes the crash, but since ULPS crashes on any registers you try to read when the GPU is asleep, having a register index wouldn't help at all. As I've previously mentioned, to assure 100% stability when ULPS is enabled, we would have to check GPU sleep state before reading or writing each GPU register. And that would make GPU polling very slow, so it wouldn't be any better than the other workarounds. As for the 30 seconds issue, that could be caused by many things. It may or may not be related to GPU polling. What you can try is right-clicking on the bottom status bar of AIDA64 main window --> HWMon Modules, and disable those modules one by one, by removing the ticks next to them. Start with HDD, then disable GPU, and then go on until you find the culprit. You may need to enable status bar in AIDA64 / main menu / View first.

Thank you for your feedback It wasn't easy to solve the USB protocol AXi PSUs use, it was full of tricks and pitfalls. But I'm glad it works now. Regards, Fiery

Interesting... But it shouldn't be a problem, since Afterburner is synchronized with AIDA64 and other monitoring software.

While waking up, Catalyst may have reported that the GPU is not sleeping anymore, but the GPU was still not ready to accept GPU register readouts properly. As you can see, it's still a messy situation. I'm not sure what HWiNFO64 does differently, but I'm pretty sure ULPS will not work with it 100% reliable either, at least if you let it run for a few hours. We and also the authors of several other 3rd party applications have been nagging AMD for years to solve the ULPS issue. But for some reason they don't listen and just keep pushing their solution as is. It's a lot like how Asus refuses to fix AI Suite, so AMD is not alone at being hard-headed

Yes, it's normal. All measured values, including GPU and GPU memory clock, GPU temperature, GPU voltages, GPU fan RPM will turn to zero when the GPU in question goes to sleep.

Thank you, I hope we can continue working together Quite frankly, I have no idea what that option does. The problem with ULPS is that there's no 100% sure way to avoid having issues when it is active. The way it works is: when you try to read a GPU register, like the one used to calculate GPU clock, or another one used for measuring GPU temperature (etc), and the GPU in question is asleep (due to ULPS previously put it to sleep), the system will throw a fatal error. What we do now is try to detect if the GPU is asleep before reading out GPU properties and before polling GPU sensors. In theory that should help to avoid issues, but there's a slim chance that the GPU is not asleep when we check the sleep state but goes to sleep right after it -- but before we actually start reading various GPU registers. Or it could go to sleep between reading two GPU registers, etc. It would be the safest to check GPU sleep state before every GPU register readouts, but that would make polling GPU properties and especially GPU sensors a lot slower than now. The performance of that solution would be abysmal, and that's why we still stick to our previous stance: you need to disable ULPS or disable polling non-primary GPUs to make it 100% stable. BTW, when the whole issue of ULPS was first introduced, back in the Radeon HD 5970 days, we hoped AMD would solve this quickly. By simply patching Catalyst drivers it would be very easy to solve this, and there could be multiple ways to achieve the goal. For example, a software could request Catalyst for a temporary wakeup of GPUs for the time of polling GPU registers. Or, a software could request Catalyst to initiate a GPU register readout while retaining the sleep state but not ending the register readout in a fatal error (sort of a "safe GPU register readout" -- which is now not available). Sadly, so far AMD didn't implement any of such tricks to let 3rd party applications handle ULPS properly

According to our tests, Samsung NVMe SSDs work at quite high temperatures, especially under heavy load. We can rarely see anything under 40 Celsius when they are working, so I'd say 60 Celsius is definitely more realistic than 14C And yes, if you touch them, they don't feel anything cool, so it's not a temperature measurement issue. Quote from a 950 Pro review: And another 950 Pro review:

Thank you for the feedback Happy New Year!

Thank you for the feedback Happy New Year!

We've implemented support for Corsair Link sensor devices (including Link Commander, Commander Mini, H80, H80i, H100, H100i, H100i GT, H110i, H110i GT, and various Corsair Link capable PSU models) in the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that since Corsair's own Corsair Link software is not synchronized with any other monitoring software, it is very important to make sure it is closed, and also that its background service is not running. It's best if you completely uninstall the Corsair Link software. Due to the special precautions required to use the new Corsair Link feature of AIDA64, it is disabled by default. You have to go to AIDA64 / main menu / File / Preferences / Stability, and enable (check) Corsair Link sensor support to activate the new feature. Let us know how it works on your system. If you find any issues, please 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. 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 --> USB PSU Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

We've implemented support for Corsair Link sensor devices (including Link Commander, Commander Mini, H80, H80i, H100, H100i, H100i GT, H110i, H110i GT, and various Corsair Link capable PSU models) in the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that since Corsair's own Corsair Link software is not synchronized with any other monitoring software, it is very important to make sure it is closed, and also that its background service is not running. It's best if you completely uninstall the Corsair Link software. Due to the special precautions required to use the new Corsair Link feature of AIDA64, it is disabled by default. You have to go to AIDA64 / main menu / File / Preferences / Stability, and enable (check) Corsair Link sensor support to activate the new feature. Let us know how it works on your system. If you find any issues, please 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. 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 --> USB PSU Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

We've implemented support for Corsair Link sensor devices (including Link Commander, Commander Mini, H80, H80i, H100, H100i, H100i GT, H110i, H110i GT, and various Corsair Link capable PSU models) in the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that since Corsair's own Corsair Link software is not synchronized with any other monitoring software, it is very important to make sure it is closed, and also that its background service is not running. It's best if you completely uninstall the Corsair Link software. Due to the special precautions required to use the new Corsair Link feature of AIDA64, it is disabled by default. You have to go to AIDA64 / main menu / File / Preferences / Stability, and enable (check) Corsair Link sensor support to activate the new feature. Let us know how it works on your system. If you find any issues, please 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. 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 --> USB PSU Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

We've implemented support for Corsair Link sensor devices (including Link Commander, Commander Mini, H80, H80i, H100, H100i, H100i GT, H110i, H110i GT, and various Corsair Link capable PSU models) in the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that since Corsair's own Corsair Link software is not synchronized with any other monitoring software, it is very important to make sure it is closed, and also that its background service is not running. It's best if you completely uninstall the Corsair Link software. Due to the special precautions required to use the new Corsair Link feature of AIDA64, it is disabled by default. You have to go to AIDA64 / main menu / File / Preferences / Stability, and enable (check) Corsair Link sensor support to activate the new feature. Let us know how it works on your system. If you find any issues, please 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. 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 --> USB PSU Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

AXi PSUs are now supported both when connected via the USB dongle, or via a Link Commander unit: http://www.aida64.com/downloads/latesta64xebeta Let us know how it works on your AXi PSU

We've fixed it up in 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 Thanks, Fiery

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 if it helps. Thanks, Fiery

We've further improved the ULPS workarounds in the following new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works

It's not possible to pinpoint exactly which component failed. But based on your system description, it may just be too overclocked. Your CPU may be stable at 4.8 or 4.7 GHz though

Are you sure 14 Celsius is a real value for your SSD? Is your computer water cooled?

Can you please check if the battery voltage is reported by the BIOS Setup? What value can you see there? Maybe what AIDA64 calls battery voltage is actually the +3.3V voltage rail or the 3VSB (+3.3V Standby) voltage rail coming from your PSU (Power Supply Unit) ? Thanks, Fiery

Thank you for your feedback. I've also sent you a private message

Yes, I am one of them

Thank you Let's also hope a very Happy New Year for all of us!

Maybe