Posted February 15, 20169 yr The pink elephant in the room needs to be addressed. (Even if 99% of the people dont even know what it is) There are some nefarious tweaks in XTU that make it unfair to the layman bencher. Here is a 4770k on air for example. 10ghz why not? Same can be easily achieved on x99. And here is a step by step way to do it. 1. Download process lasso 2. Open 3. Disable Pro balance garbage File->Pro Balance 4. Next you are going to go to default process priorities 5. Type in p95-bench.exe and select realtime from the drop down and add to list 6. Loop XTU till you get a WR. You'll notice that the rotation above the XTU process bar will be glitchy fast then slow etc that's how you know its working. Also the Mhz will be super high but you can make them look more normal by under clocking or even using slow mode to get a nice round ln2 able figure. Better yet you dont need a screen shot so who cares if it says 10 GHZ, your validation file will work just fine. I can confirm working on z77/z87-z97/x79/x99 in my short testing of this "tweak" The ones that use this dont even feel shame for they arent doing anything that is classified as a hack, they arent touching files, they arent changing files, they arent even tricking the timer etc. And I wouldnt classify it as a bug as its reproducible easily. So I think XTU needs an overhaul....maybe now that some smart people know this tweak, they can figure out what causes this to work and help it to be closed. But if you were to ask me I feel all XTU results should loose points for now and if and when its fixed, start fresh with the newest version and require Screenshots as well.
February 15, 20169 yr Administrators It was time to adress issues on XTU, but this will now bring on some fun It would be helpful if you can send pm perhaps to christian ney to confirm if new XTU versions are hit by this still Edited February 15, 20169 yr by websmile
February 15, 20169 yr So many points on hwbot so dam easy. Good work big guy. Best reconfigure hwbot algorithm to accommodate this....junk bench most points .. I wonder why? Hey you try ragging the monitor out on the run for a boost? Edited February 15, 20169 yr by 8 Pack
February 15, 20169 yr TThe ones that use this dont even feel shame for they arent doing anything that is classified as a hack, they arent touching files, they arent changing files, they arent even tricking the timer etc. And I wouldnt classify it as a bug as its reproducible easily. NAME AND SHAME BABY
February 15, 20169 yr Wow, all those global and hardware points gone! Or maybe if there is enough complaining from top overclockers it will stay and use the honor system to govern it. Sounds great!
February 15, 20169 yr Wow, all those global and hardware points gone! Or maybe if there is enough complaining from top overclockers it will stay and use the honor system to govern it. Sounds great! Pardon me for laughing long and loud.
February 15, 20169 yr What's XTU? It's this benchmark that Intel made that calculates your score based on your frequencies and then runs Prime 95 for a minute or so.
February 15, 20169 yr It's this benchmark that Intel made that calculates your score based on your frequencies and then runs Prime 95 for a minute or so. You forgot in an effort to kill your nice CPU
February 16, 20169 yr I demonstrated this "tweak" at AOOC qualifier to der8auer a year ago. Thought this was fixed(( http://forum.hwbot.org/showpost.php?p=328647&postcount=73
February 16, 20169 yr [joking mode on] At this point , i believe it's the perfect time to say , that XTU has given a lot to the overclocking community ... and it should be awarded with even more points , here at Hwbot. More points to XTU !!! Hip-hip Hurray ... [/joking mode on]
February 17, 20169 yr Some initial feedback on this topic. This issue was highlighted to the XTU development team on May 7, 2015. Our report was based on findings of user @henkenator68NL who provided us with the test data via @HiVizMan. Based on the findings, the XTU development team added a fix in v6.0.2.8 which prevents a user from changing the priority of the benchmark process or any other XTU related processes. This version was released in October 2015. Based on this thread we'll check if this issue is still present on the latest XTU release and if so, check with the XTU development team for more information.
February 17, 20169 yr Oh man, I thought I was so smart when I found this out during CC. 62.55ghz, who can do better?
February 17, 20169 yr I mentioned something similar in Apr 2015 http://forum.hwbot.org/showpost.php?p=369447&postcount=6 Never had the audacity to try and validate it though.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.