Search results

  1. iihavetoes

    The RX Vega 64 Owners Thread

    I'm in the US :)
  2. iihavetoes

    The RX Vega 64 Owners Thread

    "Glad to hear the replacement is working now, the last unit you send back it hang up and crash in windows when we try to run test with it, so we have determine the unit as defective and a replacement card was tested and issue to you." No root cause, but defective nonetheless. New card hasn't...
  3. iihavetoes

    The RX Vega 64 Owners Thread

    I was also using the Majorgeeks version. And at this point the card is in Sapphire's hands for RMA. Fine by me, I still think there was something wrong with it.
  4. iihavetoes

    The RX Vega 64 Owners Thread

    And Sapphire is 2 years for reference liquid. I know that because I think mine is broken :) VRAM has many errors with random blocks on MemtestCL. Occasionally my OS crashes without blue screen, just turns black yet the computer stays on (no the monitors aren't just turning off). Very weird...
  5. iihavetoes

    The RX Vega 64 Owners Thread

    This works for me: https://www.reddit.com/r/DestinyTheGame/comments/6wlg46/destiny_2_beta_fps_limiter_forces_vsync_which/dm92i6k/?context=3
  6. iihavetoes

    The RX Vega 64 Owners Thread

    I see Samsung instead of Micron now
  7. iihavetoes

    The RX Vega 64 Owners Thread

    Sorry, meant that the GPU was stock, but the HBM was not. I manually changed it to [email protected] within Wattman. It does start at 950mV for AIO
  8. iihavetoes

    The RX Vega 64 Owners Thread

    Since my setup is more stable now, I did some benchmarks with 1700x ([email protected]) and RX Vega 64 AIO. My GPU was at stock freq/voltage, which I would expect to be [email protected] (?). HBM was at [email protected]. Power limit +50% through Wattman. https://www.3dmark.com/fs/13469984...
  9. iihavetoes

    The RX Vega 64 Owners Thread

    Wow yeah that was it. Is this documented somewhere? I'm still using Wattman power settings, though closing the program (the monitoring is the issue, I suppose) along with HWinfo worked. Do the monitoring programs need to be closed completely or just not in foreground?
  10. iihavetoes

    The RX Vega 64 Owners Thread

    So I've since went back to 17.8.2. Had some stutters ever 2-3 seconds on those drivers and was able to solve it by disabling Windows Game Mode. Fast forward hours later, I turn on an OC for my 1700x ([email protected]) and now I have the stutters again. Is the OC the cause of this?
  11. iihavetoes

    The RX Vega 64 Owners Thread

    I just joined and I was able to edit my post. I think...
  12. iihavetoes

    The RX Vega 64 Owners Thread

    Stock settings btw. Liquid version
  13. iihavetoes

    The RX Vega 64 Owners Thread

    The default memory voltage is higher on air than water?
  14. iihavetoes

    The RX Vega 64 Owners Thread

    It's two separate 8-pins. On 17.8.2 I'm getting microstuttering every 2 or 3 seconds, with or without FreeSync enabled. The launch beta drivers of 17.8.1 were actually very stable for me
  15. iihavetoes

    The RX Vega 64 Owners Thread

    Had only one black screen tonight for about 6 hours of PUBG, moving between launch drivers and 17.8.2
  16. iihavetoes

    The RX Vega 64 Owners Thread

    Yes. I've tried 17.30.1051-b6-aug7 and 17.8.2 and the PUBG update (17.8.2) performed worse than the beta launch drivers. I'll continue to test, but I was actually getting over 100fps consistently on the launch drivers, but still struggle to hold 60fps with 17.8.2
  17. iihavetoes

    The RX Vega 64 Owners Thread

    Got my RX Vega 64 AIO last night: What I'm using: MSI B350m MORTAR w/ BIOS 7A37v16 Chipset driver 17.10.3401 Stock 1700x Radeon 17.8.2 drivers Stock Radeon Gaming settings Tried Wattman on Power Save, Balanced, and Turbo. I do have Afterburner installed, though I hear that can cause problems...
Back
Top Bottom