Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

genghisquan

Member
  • Content Count

    160
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About genghisquan

  • Title
    Junior Member
  • Birthday May 26, 1988

Contact Methods

Profile Information

  • Gender
    Not Telling
  • Biography
    Artist, graphic designer, beer enthusiast.
  • Occupation
    Graphic Designer

Recent Profile Visitors

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

  1. Yes, 5700XT is your best bet, but, for the love of all that is cool, please look at tear-down videos. I can't believe that we still have to deal with poor memory and VRM cooling in 2020, but that's totally a thing with some cards.
  2. Yeah, I definitely think the 5700XT is worth it for 1440p. I don't think it'll give you 120+ FPS at max settings, but nobody should expect that kind of FPS outside of e-sports titles. If you're not afraid, then get a 5700 with good cooling and dual BIOS and then flash an XT bios onto it.
  3. Not to resurrect an old thread, but I just wanted to give an update for anyone who might be experiencing similar RAM issues. After upping the SOC voltage, the system seemed to boot more consistently, but a few days later, I was still getting random BSODs during web browsing and watching videos on YouTube. Once again, I ran MemTest and came up with multiple errors. I got an RMA from G. Skill after citing MemTest errors. I haven't gotten any issues with the new RAM kit since.
  4. Sorry, not sure if this belongs in General Discussion or another section, but I just have a question about RMA: Do all companies make you (the consumer) pay for any return costs for an RMA? I only ask because I've only had to RMA two things in my life, a Corsair PSU and recently a G.Skill RAM kit, and both companies didn't cover the return costs. In contrast, I've made returns to retailers, and they've always covered the return costs (shipping, restocking, recycling fees, etc). It's odd to me that the consumer has to pay more money on top of the original cost when th
  5. Yeah, I figured it wasn't reporting it correctly at all. And yeah, I did look at HWinfo at first, but there's no label for VDDP, so I wasn't sure which one I was supposed to look at.
  6. I've tried to Google what exactly VDDP voltage is, and I don't really understand it from the descriptions. Can someone help me understand what this voltage is? And more importantly, why is mine 0.0V?
  7. I currently have my system on "Auto" vcore as suggested by a few people early in the thread. I went thru a full day of work with no performance issues, thermal issues, or BSODs (I mean...not that graphic design on Adobe apps would ever be super heavy workloads or anything). It's reaching 1.33-1.36V during load. Should I still be concerned?
  8. I could've sworn I quoted you in my screenshot earlier today. But yeah, I misquoted the video—it said 1.35V, not 1.36V. Regardless, I think there should be an updated Zen 2 architecture overview video for people like me.
  9. Ah, good. A 3600X owner. Thanks for the relevant comment. So that's weird that you can get a higher core frequency while using a lower vcore. This boggles my mind.
  10. For sure. I never apply constant voltage to anything 24/7, but I wanted to apply a constant voltage because I erroneously thought that the voltage fluctuation was causing consistent performance.
  11. OH, BTW, I'm not running PBO, which is why the 1.36V on all-core load is concerning me.
  12. Ok, that's sorta good to hear. I find the GUI of Ryzen Master too cluttered and confusing. I'll stick to adjustments in UEFI/BIOS.
  13. I don't even know what's the proper method for voltage control at this point. People recommend Ryzen Master, but others say it's too complicated / unnecessary. Albeit, Cinebench is an extremely stressful program, and I don't think I ever hit my CPU that hard during gaming / Adobe app usage.
  14. God damn it. Now I'm worried that the auto setting is pumping too high of a vcore during all-core load!
×