Jump to content
HWBOT Community Forums

Bilko

Crew
  • Posts

    283
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Bilko

  1. After a quick look this is happening on my team as well, I wouldn't expect that to be normal behavior.
  2. Most of my boards don't have batteries tbh, It's a saving grace in case I forgot to clear CMOS after benching cold then boot it up on ambient again later (we learn from mistakes). So the board not having a CMOS battery really is not a big deal at all, at least not as big a deal as some think it is.
  3. You need to run Physics and Combined to get a Valid link (Along with WHQL driver) anyway so I assumed it'd be overall score that counted and not just the GTs but looks like that isn't the case here. Long time no see btw
  4. I haven't tried as yet but if I get it running I'll let you know
  5. From how I understand it atm Raven Ridge and Picasso are fine on 10 but Matisse isn't (outside of the usual 3DMark, x265, Benchmate) So Matisse, Pinnacle Ridge and Summit Ridge are all in the same boat.
  6. Hey I like those movies, don't you ruin them for me now....
  7. Give me a background and I'll get to benching ?
  8. New version of Benchmate cleared this up for me, was the same issue @keeph8n had. Thanks @_mat_!! ?
  9. I was having this issue as well on my TR4 system (X399 Gaming 7 + 2920X) and enabling the disabling HPET seemed to fix it but now it's back again. Almost exactly the same process, Benchmate cmd windows pops up, loads then vanishes leaving benchmate client as a background task in task manager and that's where it ends. About 15 minutes prior this was all working perfectly, Only thing that were changed was the desktop background and memory strap. video-1562991520.mp4
  10. You do your thing mate, Really appreciate the work you've been putting in for this and whenever you get that donate button setup let us know!
  11. Better to report now so the people have a chance to rebench before the end.
  12. Count me in as well, I've got both AM4 and TR4 so can give this a real good workout
  13. Either way sounds pretty cool, I think that Idea #2 is a little easier to get sorted (potentially) and I'm also in favour of Idea #3
  14. Might need to change the wording around to reflect this. Currently the way this reads is the CPU is limited to positive temps but the GPU isn't. Also no mention of highlighting GPU temps viz GPU-Z as well. Just don't want people potentially misunderstanding
  15. CPU limited to positive temps in Div I-V as well? I'd assume Div VI-VII would be positive temps regardless as they were in Round 1
  16. With us needing to use HWiNFO64 or HWMonitor and the like already I think a +15/20c minimum for GPU temp is best. I understand the rationale behind Stock coolers only but with there being (sometimes large) variations in the capabilities of GPU air coolers it could be just as unbalanced as allowing H2O mixed in anyway. Capping CPU freq is fine by me and also ties in with still needing monitoring software. Can't speak for Div VII but for Div VI it'd make sense to have the top end GPU used to be the same time period as the top end platform (990FX = HD 7970) Looking forward to Round 2 ?
×
×
  • Create New...