Search results

  1. S

    Enabling ADL makes the AMD Fury crash

    1: It works better with 5.20+ADL, definetly less stutters and the VRM power in shows 4-5x more as it should. 2: The VRAM current and power shows 0.0 instantly at start but other sensors are showing correct values longer. 3: first time It happened when the PC was left idle on desktop I would say...
  2. S

    Enabling ADL makes the AMD Fury crash

    Ok, I will test the new beta to see if it crashes. With ADL enabled in the new beta the performance is bad in 3D applications. I get stutters and I can see the GPU indicator LEDs on the card are lighting up from half to maxed constantly. Also in Furmark the GPU VRM Power in/out should be above...
  3. S

    Enabling ADL makes the AMD Fury crash

    Just tried the latest version and it's stable, but there are some incorrect readings (negative/too high values for voltages, current and power) and hwinfo starts a little slower at the first time but that's a minor issue: Screenshot and debug file attached. Edit: After a few minutes the same...
  4. S

    Enabling ADL makes the AMD Fury crash

    Attached the logs - one is with ADL and possibly incomplete due to the crash but the other one should be fine.
  5. S

    Enabling ADL makes the AMD Fury crash

    I only get these without ADL: [attachment=1784] And here is a fast capture with ADL [attachment=1785] (there are more sensors but they appearing later and the crash happens almost instantly so I can't take a screenshot)
  6. S

    Enabling ADL makes the AMD Fury crash

    Ok, thanks. Not sure how but MSI AB or GPU-Z can read the GPU VDDC but not the rest of VRM related informations.
  7. S

    Enabling ADL makes the AMD Fury crash

    AMD Fiji Pro (Sapphire Fury OC).
  8. S

    Enabling ADL makes the AMD Fury crash

    Hi! Just noticed that enabling the ADL support  shows additional information like VRM temperature, voltage and VRM currents, but a few seconds later the card switches to black screen and the fan runs at max speed. Latest HWINFO stable version and AMD Crimson 16.1 The crash is almost...
  9. S

    Sapphire R9 Fury - missing/incorrect sensor reading

    Ok, I attached the HWINFO64.DBG to the first post - I alsi changed the fan speed during the debug mode. No, in AIDA is also missing, only GPU-Z shows. SMBUS: ------[ Microsoft Windows 10 Professional 10.0.10240.16463 (64-bit) ]------ ------[ Video Adapters ]------ Sapphire Radeon...
  10. S

    Sapphire R9 Fury - missing/incorrect sensor reading

    Hi! I noticed that HWINFO doesn't detect the voltage sensor and the GPU fan speed is bugged on the Sapphire card. The voltage sensor is being detected by GPU-Z (VDDC) but the fan reading is also buggy. I guess it's because Sapphire set the fans to stop bellow a certain temperature - HWINFO...
  11. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    Works fine, now shows the sensors default value, and appears even after shutdown. Thx.
  12. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    It happens even when GPU Tweak is not running. Just for 1 sec drops to 0 V. Also I noticed that if I shutdown the computer next boot the SET sensor disappears and won't show until I start GPU Tweak and load default settings or set the voltage. Made a debug file with HWiNFO and also with AIDA:
  13. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    Sometimes minimum voltage column shows 0 V even without sleep mode. I was able to capture Voltage Set but happens with current too.
  14. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    With ADL Enabled the voltage sometimes drops to 0 V I can see it in minimum column, withoud ADL works fine here is the sleep dump:
  15. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    No the 0 V / sensor disappear bug after sleep happens anyway doesn't matter if ADL is enabled/disabled.
  16. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    Noticed a minor issue: When the monitor goes to sleep the GPU turns off thanks to AMD ZeroCore technology. After waking up the current voltage keeps showing correctly but Voltage Set stays 0 V. If I restart HWiNFO the sensor disappears, the only way to bring it back to change something with ASUS...
  17. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    This last build works for me: both set & current with lower,default and higher voltages! :) I hope there will not be more issues. Thank you!
  18. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    Current seems to display the current voltage so that's okay :) The Voltage set however displays 2.025 at startup when the voltage is set to 1.225 V. If I set to 1.194 or 1.188 it displays correctly, if I set to 1.275 displays 1.975, 1.3 V -> 1.950 V. So it seems lower voltages are fine, but...
  19. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    Yes 1.225V is the default. Great! Thank you for your time.
  20. S

    ASUS R7 260X DirectCU II OC - Missing sensors

    Well I tried to make some, but with default settings the voltage ranges are much wider... Also it seems dumping the SMBus interferes with GPU Tweak's Monitor because after the dump created it jumped to 250 mV which would be impossible the GPU can't operate with such a low voltage. def1-3: 250...
Back
Top