HWBOT x265 Benchmark 4k Benchmark Validation Regulations

  • Benchmark Rules
  • 17
  • HWBOT

HWBOT x265 Benchmark 4k Benchmark Validation Regulations

Allowed benchmark versions
Allowed operating systemsAll Windows based (Platform Clock must be enabled for Windows 8/8.1/10)
Default benchmark settings4k
ScoreThe score is the average FPS
Allowed optimisations
  • Run CMD as admin and paste “bcdedit /set useplatformclock yes”
  • Enabling/Disabling HyperThreading
  • Adjust priority and affinity
  • Change benchmark parameters (type, priority, Pmode)
Disallowed tweaks/cheats
  • Altering benchmark files or the rendering
  • Any software or human interaction altering the perceived speed of the benchmark program, tricking it to believe it ran faster
Verification screenshot requirements

All Global Top-20 benchmark results must now include a valid verification screenshot and a system picture showing the benchmarked system in action.

All verification screenshots must show the settings at which the benchmark was completed. This means it is not allowed to decrease the operating frequency for screenshot purposes. In effect, the staff reserves the right to reject a submission that is deemed out of line for the stated system parameters. For XTU specifically, the data file must contain monitoring information (frequency and temperature).

The screenshot must be obtained using the integrated screenshot functionality

  • HWBOT x265 Benchmark window (with all information visible)
  • CPU-Z CPU tab
  • CPU-Z Memory tab
Verification linkNo verification link required
Verification datafileVerification datafile is mandatory
Example screenshot

Red: Mandatory Green: Optional

Additional notesThis page contains the benchmark result regulation specifications for HWBOT x265 Benchmark 4k. The rules as described in our General Rules section are still applicable even if they are not specifically mentioned on this page.

It is your responsibility, and the responsibility of your team captain(s) that these rules are followed properly. Your submission may be blocked by HWBOT moderators without notice if your submission is in violation of one of these rules. Multiple infractions may lead to a warning, and eventually an account ban.

Changelog
  • Nov 1, 2017: several rule adjustments
  • September 18, 2016: link
  • May 1, 2015: clarify version, operating system, and remove GPU-Z requirement
  • November 2, 2015: first draft

Christian Ney says:

Reserved for tweaks and tips

 

Link to support thread

superpatodonaldo says:

just a thought: about the mandatory screenshot, does cpu freq (as shown in cpuz cpu) have to be the same shown in the bench window (core speed)?

If someone changes the core freq later loading the benchmark, cpu speed shown is not updated.

 

Netherlands hidde663 says:

Best\fastest CPU stability test, hands down. Close contenders are Intel-burn-test high-stress x10, Real-bench video-encoding x10.

France bolc says:

hi,

is active HPET mandatory on win8 / 8.1 /10 or the generic rtc is ok for x265 4k ?

++

Belgium leeghoofd says:

Platform clock must be enabled for WIn8 or newer

France bolc says:

11 hours ago, Leeghoofd said:

Platform clock must be enabled for WIn8 or newer

that s what I thought ;)
I asked cause some folk(s) in the comp doesn't have it on on win8.x and I am tired of being the party pooper sending a report :D

it is in div4, in the top 3 scores ;)

many uses win 2012 server r2 for x265 bench, I gonna start as well... hpet is not required on that OS or ...?

United Kingdom Noxinite says:

Server 2012 R2 is a version of Windows 8, so HPET is needed.

websmile says:

I don´t think skylake and newer systems need Hept enabled - these rely on an internal clock and are not vulnerable to the rtc bug. Because of the understandable confusion I think the developper can explain this as well, and please don´t send reports next days until this is cleared :)

 

P.S. And yes, it is really confusing if this is now shown as red "Hept not enabled" on 8700K - that´s why clarification is needed and maybe a fix

Belgium leeghoofd says:

than the old rules need a modification muffin.... contacted Havli

United Kingdom GeorgeStorm says:

My understanding was it wasn't needed on skylake and newer as well.

Belgium leeghoofd says:

yep , but w ehave some 8700K runs with the HPET timer in red on 8700K, hence why we are reinvestigating. Sorry fpr any inconvenience

United States marco.is.not.80 says:

One of my submissions got blocked over this and I've always been under the impression that Skylake and above doesn't need HPET no matter what OS is used and I thought this was discussed with both the x265 and GPUPI authors at length and they both verified that is true AND both released versions that no longer made it a requirement for skylake and above. Maybe I'm not sleeping enough.

Czech Republic PKBO says:

Same here 

says:

Same here, two x265 4k submissions with a 8700K are blocked.

No red timer, only a HPET disabled message.

No problem,  now two new submissons from  me with HPET enabled. 😜

 

Greets

Heinrich

Belgium leeghoofd says:

K to all,  I pulled some X265 benchmarks due to the current rule  (Platform Clock must be enabled for Windows 8/8.1/10)

 

After talking to the developper this will be modified to avoid confusion:

- Skylake and newer Intel CPU subs don't need the platform clock to be enabled

- Pre Skylake CPUs will sport the rule of: Platform Clock must be enabled for Windows 8/8.1/10 and sortlike Server OSses (2012 and newer)

- AMD users will have to enable the platform clock on Win8/8.1/10 and sortlike Server OSses (Server 2012 and newer)

 

in case you run an Intel Skylake or newer generation CPU on a server OS and the HPET timer warning pops up you need to enable the platform clock

 

To those that got their score pulled on Skylake or newer CPUs, plz re-submit, sorry for any inconvenience caused

United States tgurus says:

well this is good news bcuz my i9-7900X drops to about half speed with the HPET timer on so I figured I was out of the running on any competition that included GPUPI.. problem is the current version insisted on changing it for me before it would run..hopefully they will update for this fix?

Austria _mat_ says:

To circumvent HPET in GPUPI use Windows 7 or GPUPI 3.2 + Windows 10 prior to RS4. RS5 changes the QPC timer frequency to 10 MHz and GPUPI currently can't handle that.

Please log in or register to comment.