Jump to content

The Mac

Members
  • Posts

    93
  • Joined

  • Last visited

  • Days Won

    2

The Mac last won the day on July 16 2016

The Mac had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

The Mac's Achievements

Newbie

Newbie (1/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later

Recent Badges

5

Reputation

  1. It appears to be an issue with free-sync. disabling it, and rebooting fixed the missing sensors. re-enabling after reboot keeps them available. weird.
  2. GPU sensors have disappeared. No Utilization, temps, power, etc Only Memory useage.
  3. Yeah, im aware of that. I am trying to avoid running yet another background process.
  4. Is there any way to get the FPS counter from the adrenalin software as a sensor?
  5. i had this issue in the past. it was sensor collision problem with a Corsair AIO water loop and AIDAs polling module that would randomly shut down the computer with no warning. Try exiting AIDA and see if it contnues.
  6. so im guessing no one has figured out which one to use yet? perhaps a description of the source of the 3 different sensors woulds be helpful...
  7. Which of the 3 CPU sensors is the one i should be watching for throttling (cpu, package or diode)? They all report different temps. None of them seem to match what ryzen master reports. Supposedly thats the one that throttles at 90 degrees. Ryzen 5800x....
  8. similar issue I have the 5800x. None of the 3 cpu temp sensors (cpu, package, or diode) match what ryzen master reports. since that is the temp that throttles the cpu at 90 degrees, its the one we need to monitor.
  9. looks like it reappeared in the new aug18 beta. now its called GPU PowerControl.
  10. R9-290 (SAPPHIRE R9-290 Vapor-X) Crimson 16.8.2
  11. Looks like the AMD Powertune sensor item has gone missing. Although now in Crimson, they call it Power Limit. No sensor for that either. Is it coming back?
  12. i see the latest beta has "improved support" what does that mean exactly? edit: looks like you guys fixed the static duty cycle issue. sweet. Thanx! This kind of support is why i gladly open my wallet every year to you guys...
  13. well, thats certainly good to hear. im guessing you solution involves the corsair driver abstraction layer passing the info rather than trying to read the sensor directly which would obviously only be useful for corsair products..
  14. understood. based on corsair's track record of fixing their own program, im not going to hold my breath. How hard can it be to expose an interface for an external program to passively read values? Their own damn software does it. They make outstanding hardware, but they need to hire some real software engineers, not that group of muppets they have coding for them currently. in the mean time, no monitoring for me.
×
×
  • Create New...