Jump to content
HWBOT Community Forums

hidde663

Members
  • Posts

    120
  • Joined

  • Last visited

Converted

  • Location
    Netherlands

Recent Profile Visitors

495 profile views

hidde663's Achievements

Newbie

Newbie (1/14)

16

Reputation

  1. "Your chip died because 1.55v is way too fucking much for daily" I tried to kill it, that was the idea, to see the degradation process. anyways hopefully someone will read this who is new to OC and wont try such a high vcore as a daily driver.
  2. Too much? I don't know. The chip was delidded, resealed, 85C@155 watt. did not gain anything past ~1.536v on air, the extra is just for the droop. So i set 1.55v, did a few x265 4k benches in a row, which was the hardest test to pass in my book, stabalized the highest freq. without destabalising the mem. It ran fine for a few weeks, then suddenly after i came back from work and it wouldnt POST no more. (i did shut it down myself, so no crashes) Thats why i think it died due to a voltage spike at startup. (similar to how Jayztwocents 7700k died, cant remember for certain) I was hoping the degradation experiment would have lasted a little longer, but oh well got a 5800x now, which is quite a jump in performance. I will wait for de8auer's degradation vid before trying anything "un-safe" on this one ;)
  3. random info: i killed this chip last month, with only 1.55v (AVX stable@4.924), no degradation - just instant failure. Boot voltage spike maby?
  4. I'm sorry to say but, version 3.3.3 is not allowed: https://hwbot.org/news/11973_application_145_rules/ You can probably just re-submit as gpupi 3.3.3 1B
  5. Benchmark tessellation load modified by AMD Catalyst driver, result invalid. Check your video driver settings.
  6. im not gonna lie, it took me multiple days just to tune the GDDR5, without it randomly spitting errors after an hour
×
×
  • Create New...