Leeghoofd

The previous management decided to take UL's direction with the launch of Time Spy, initially they even opted for the option to go without a screenshot, thus just requiring a verification link. Some creative users were able to bench with LOD, while still being able to make the run pop up as VALID. So a nice concept was once more hammered by multiple users for some virtual boints, Anyway there are just too many Firestrike scores with LOD/Tess settings adjusted... tossing them is not an option... Neither is it for Vantage , 3D11 and co scores....

Without ECC we would have bugged outputs all over the place with these RTX cards, especially if the benchmark still VALIDATES on the verification page. There should be an autodetect system monitoring weird outputs that would invalidate the score if eg Scene 3 scores more than 30% faster than scene 7... sadly this is not the case (yet) Now with Pasi from UL monitoring the subs with ECC there are almost no bugged outputs. With UL displaying the ECC enabled and correct memory size we have a double backup layer from the standard HWBOT screenshot requirements. Adding ECC tab is overkill, it has no real added value One member was already creative, making a new screenshot with ECC enabled but with the non ECC save profile loaded in the benchmark. The verification link gave it all away. Can we judge by the displayed frequencies, nope but again we see them in the verification link. Users can downclock or even upclock to make it look more realistic. It's that creativity that leads to so many rules and rule changes... Just wait for the 15th, when we pull all non ECC subs, the dust will settle after a few days... hopefully everybody is satisfied with the new direction... Fingers crossed UL wil pickup the feedback for future benchmark releases, the current verification design has flaws. We saw it already with 6900XT scores and now once more with RTX 4090. Sadly no site is perfect as way too many "tweaked" scores stay under the radar...

Which benchmarks planned for the Apple ?

The value is that it is not a good idea for a broader perspective.... From single user point great idea, however people that bench older hardware will just stop benching as they can't get remotely close the old scores. Also comparing apples and oranges is never a good idea. We have to keep more than one person happy...

Why does one continuously keep on repeating the same thing. All older non ECC scores will be removed on the 15th of this month... So everything will be the same. I can add an ECC easily in the screenshot, no special Photoshop skills required... Doesn't work If Nvidia removes ECC we have a big problem, than it's fully up to UL to impose proper bugged score detection...as users will keep on claiming their score is fully legit and will cry it is labeled Valid by UL. Impossible to moderate with the current graph data we have...

Well its pretty simple: Adjusting LOD/Tess was part of the tweaking culture to boost higher FPS, similar to what we did when we were gaming and had to adjust detail settings in a config file in order to get eg 120FPS so we could do certain trick jumps, move faster or could spot the enemy sooner. Thus adjusting LOD was also allowed for overclocking and it gave the community tremendous fun as it was easy to execute. It also required time to find the right setting per sub benchmark. Nowadays to even get certain benchmarks to properly run and even boost older benchmarks via such software tweaks is one of the reasons OC is less popular (besides ofc the insane hardware prizes) Now as Salty mentioned this is something totally different to what we are experiencing right now with the ECC disabled runs. There users push a bit more memory or GPU clocks and feel totally fine that their air cooled card trumps a score of a person running 300MHz faster on the Graphics Core. Wheres the logic in that? On top of that phenoma the benchmark software VALIDates the run... That would even strenghten the fact to what they did is acceptable. UL is still working on a fix, but it could turn out that they will also accept ECC Enabled onlyon runs for their Hall of Fame in the future The "real" inlogic part is that HWBOT adresses these bugged outputs by imposing the ECC enabled runs only rule for RTX 4090 cards. We can't await a fix any longer as this issue has been reported over 4 months ago... We have proper ECC detection already, enhanced monitoring graphs are on the request list. Otherwise the Fire strike series are still very popular (age 10+) and the benchmark software has nicely aged. Meaning a bugged result can be very easily spotted, similar with as the older legacy 3DMarks via the different subtests. Thanks to its popularity it would be nearly impossible to beat older scores if we would impose from now that no more TESS/LOD could be used. I assume you have no idea of the impact by this standardized ruling that all scores have to be VALID at UL site. Think about the fact that due to software age there are no more updates to the Firestrike benchmark series besides an updated systeminfo. UL is still however updating Port Royal (Age 2+) as with the current line-up of hardware/software inconsistent results are still possible. Another example why it stays as is: When we imposed the new rules layout we decided simultaneously that for the lesser GPU intensive benchmarks from the same 3DMark suite (Cloudgate, SkyDiver and co), to submit only UL VALID runs. Even with the lesser benchmark popularity the amount of negative response was mindblowing. We took away the cherished LOD/TESS tweaking option, till users found out that them particular benchmarks were very heavily influenced by the CPU or the Physx score. In the end it is pretty simple , ECC enabled only runs for RTX4090 users evens the playing field, as bugged outputs have reduced to nearly nill out of over 9000 subs monitored by UL moderators over the last two months. Taking into account that Benchmark software doesn't always get fixed/sorted or supported, especially not if they are already over 5 years or older, this is a wise decision. The real problem is not HWBOT here, we need to ensure competitive benchmarking. New Rules are added in 99% of the cases due to users that found either a way to bend them or discovered a new way to bug outputs. If you want I'll make a poll and will announce that on YOUR request we will impose VALID runs for Firestrike and co, I'll add your email address to the post so you can enjoy the flaming and abusive replies.

done

Both added

done, plz check out the rules and sample screenshots here: https://hwbot.org/benchmarkRules

MOTHERBOARD BIOS for: ASUS: ROG-MAXIMUS-Z790-APEX-ASUS-0021.CAP (GEAR4) ROG-MAXIMUS-Z790-APEX-ASUS-0008.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0008.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0022.CAP (AVX512) ROG-MAXIMUS-Z790-APEX-ASUS-0031.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0031.CAP-ucode15.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0088.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0096.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0601.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0604.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0812.CAP ROG MAXIMUS-Z790-APEX-ASUS-0814.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0902.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0902-ucode15.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0904 CAP ROG-MAXIMUS-Z790-APEX-ASUS-0904-ucode15.CAP ROG-MAXIMUS-Z790-APEX-ASUS-0904-ucode15.CAP(offset fix) ROG-MAXIMUS-Z790-APEX-ASUS-9901-G.SKILL ROG-MAXIMUS-Z690-APEX-ASUS-0021.CAP ROG-MAXIMUS-Z690-APEX-ASUS-2204-ucode15.CAP ROG-MAXIMUS-Z690-APEX-ASUS-0702.CAP ROG-MAXIMUS-Z690-APEX-ASUS-0802.CAP ROG-MAXIMUS-Z690-APEX-ASUS-0803.CAP ROG-MAXIMUS-Z690-APEX-ASUS-0072.CAP ROG-MAXIMUS-Z690-APEX-ASUS-0090.CAP ROG-MAXIMUS-Z690-APEX-ASUS-9901.CAP ROG-MAXIMUS-Z690-APEX-ASUS-9902.CAP ROG STRIX Z690-A Gaming WIFI D4 (0223-0605-0707-0807-0901-1003-1304-1404-1504-1601-1720-2007-2103-2204 ) ROG STRIX Z690-A GAMING WIFI D4 0003.CAP ROG STRIX Z690-A GAMING WIFI D4 1504.CAP ROG STRIX Z790-A GAMING WIFI D4 0814.CAP ROG STRIX Z790-I 0814.CAP eVGA: 1E799111 (Official) Z790 Dark KingPin 1.13 Z790 Dark KingPin 1.14 21220T00 (03-02-23) 30203T00 (20-12-22) EVGA OC Tool Gigabyte: Z790 Tachyon Bios and tools versions ( X4B-X6H-X6K-X6M-X6N-X6O-X4B(AVX) ) Z790 Tachyon X6T (Gear 4 bios) Z790 Tachyon X6U (All Gear bios) Z790 Tachyon X6V Z690 Tachyon X6U (Gear 4 bios) Z690 Tachyon and Tools versions ( X3C-X3G-X3H-X4B-X6F-X6H-X6O-X4B(AVX) ) Flashing these biosses is at own risk!!!

Here's already a taster for those that will battle it out live at the G.Skill booth at Computex 2023 G.Skill Live Stage prize money (Computex 2023 participants) 1st $10000 2nd $6500 3rd $5000 4th $4200 5th $3400 6th $3000 7th $2800 8th $2600 9th $2500 Take note that you will have to arrange flights and hotel accomodation yourselves!

Important links PR link at G.Skill page E-sports page GENERAL RULES ● Participants must use Intel LGA1700 Platforms. ● Participants must use commercial available G.SKILL DDR4/5 memory only. ● Must use commercially available components (ES hardware is not allowed). ● HWBOT and G.SKILL reserve the right to reject any entry. ● HWBOT and G.SKILL have the right to ask for video proof or BenchMate datafile if needed. ● Employees of MB/VGA/MEM/CPU/PSU manufacturers are not allowed to compete. ● No hardware/score sharing is allowed. ● It is not allowed to remove submissions once it has been submitted, or make crucial changes after submission. ● After the end of the competition, no more submissions or rectifications will be allowed. ● All submissions must include a picture of their rig (MB, VGA, MEM, CPU cooler) during use. ● All submissions must include a picture of G.SKILL memory with heatsink and serial number; If the heatsink is removed, the picture must clearly show the PCB and IC. ● We expect fair play from everyone. HWBOT and G.SKILL reserve the right to remove results and/or participants who compete unfairly; The decision is final and will not be discussed afterwards; Examples of unacceptable behaviour: Influence others’ submissions to profit your ranking, Deliberately make a mistake in the submissions process and ask later for change. ● All submissions must include the official OC World Cup 2023 Qualifier desktop wallpaper, available here HARDWARE ● Must use commercially / retail available components. ES hardware is not allowed. ● Participants must use Intel LGA1700 Platforms. ● Participants must use retail G.SKILL DDR4/5 memory. ● 4 processor cores maximum, no Hyper Threading allowed (disabling cores allowed). ● Maximum processor/cache frequency limitation of 5503Mhz for specific stages. SOFTWARE Windows 10 submissions only ( no server OSses ) CPU-Z 2.04 or newer BenchMate 10.12.2 only All published biosses in the Hwbot thread can be used, no date restriction (UPDATE 03/03/2023 by G.Skill judge) STAGES STAGE 1: Memory FREQUENCY March 01 - April 09 12:00 CET Standard HWBOT rules A VALIDATED CPU-Z Verification link is required being ( XOC mode not allowed ) Screenshot with event desktop wallpaper as background: CPU-Z for CPU, memory, and SPD tab. Memory Frequencies showing result not more than 1% lower than validated frequency. STAGE 2: 4-cores 5.5GHz Cinebench R15 by BenchMate March 08 - March 27 12:00 CET Standard HWBOT rules Maximum CPU and Cache frequency of 5503MHz (CPU-Z and BenchMate result tab) A VALIDATED CPU-Z Verification link is required being ( XOC mode not allowed ) Screenshot made by BenchMate tool with event desktop wallpaper: BenchMate result tab, CPU-Z for CPU, memory and SPD tabs. STAGE 3: 4-cores 5.5GHz Y-Cruncher 2.5B by BenchMate March 15 - April 06 12:00 CET Standard HWBOT rules Maximum CPU and Cache frequency of 5503MHz (CPU-Z and BenchMate result tab) A VALIDATED CPU-Z Verification link is required being ( XOC mode not allowed ) Screenshot made by BenchMate tool with event desktop wallpaper: Including BenchMate result tab , CPU-Z CPU, memory and SPD tabs. STAGE 4: 5.5GHz SuperPi32M by BenchMate March 22 - April 10 12:00 CET Standard HWBOT rules Maximum CPU and Cache frequency of 5503MHz (CPU-Z and BenchMate result tab) A VALIDATED CPU-Z Verification link is required being ( XOC mode not allowed ) Screenshot made by BenchMate tool with event desktop wallpaper: Including BenchMate result tab , CPU-Z CPU, memory and SPD tabs. Example of a valid screenshot: CPU-Z tab for CPU CPU-Z tab for memory CPU-Z tabs for SPD for both sticks CB R15 Rendered screen and Benchmate score window (take note this is not the official wallpaper) HARDWARE PRIZES Each of the top-9 of the online qualifier will receive a G.Skill DDR5-7800 2x16GB memory kit 3 x Lucky draw winners using DDR4/5 will receive a G.Skill DDR5-7200 2x16GB memory kit (must participate in all stages) : 2 x for DDR5 and one kit for a DDR4 participant G.Skill is looking for 9 participants to display their overclocking skill at the Live event held during Computex 2023 (Taiwan). Participants for the live stage will need to take care of transportation and accomodation themselves to Computex 2023 In the case that any of the top-9 qualified overclockers cannot attend the Live Qualifier at Computex 2023, their spot will be made available to subsequent runner- ups of the Online Qualifier (e.g. 10th, 11th, 12th, etc. places). More details soon...

https://hwbot.org/newsflash/5407_the_countdown_has_begun...

Maybe because you submit twice the same score while already having a faster one...

No eVGA scores to my knowing upped to HWBOT from them limited edition cards

Just compare the top scores, them screenshots already give away a lot.

You need to build a reputation, like eg at least a dozen of comments before you can get access.. Otherwise everybody can chime in and sell stuff...

Since the RTX 4090 ECC drama has reached intergallactic levels. HWBOT will take a decision at the 15th of February with or without a fix from the benchmark developers. The only possible option to ensure competitive benchmarking will be to remove all ECC disabled scores. As usual we will get a lot of flaming and other love mail or even multi page PMs from the ones that feel now discriminated as they either no longer have the card and their score seems perfectly legit plus has been stamped as VALID at UL Benchmarks. Well we can't moderate properly with ECC disabled, some scores are legit some are obviously bugged, but many will remain below the radar... Thus I'm already emptying my mail box. Enjoy and let the hatred flow...

Forum login is via Email address now, not username

Read first, flame later

K ladies all in your corner and moan, thread locked

ECC NOT ON, BLOCKED and a solid explenation is required why your screenshot shows it enabled, while your verification link tells 24GB is available... interesting to say the least

UL is still on it... we are awaiting their final call to either remove all ECC disabled scores or to allow them if they can provide a solid fix.... Last mail I received below Everyone involved in this thread know exactly what they did and are curently doing... Just look in the mirror and maybe have a moment of self reflection... I'll have a look at the scores as Salty seems to be busy elsewhere Interesting score here: https://hwbot.org/submission/5186983

Not bad

test