Massman

Only for real 2 cores (or 2x single core)

Nice! Do you think i3 6320 can beat with the Xeon X5698 with additional tweaking?

Anyone who is having problem with the benchmark on older platforms: can you also check that HPET is enabled in the BIOS?

Thanks for the mention, overlooked this thread. This is indeed the reason why this feature isn't working correctly. The amount links to a search query, which no longer supports "any benchmark" search queries. I'll have a chat with the developers to see if there's a way to get the hardware library search to work without potentially overloading the database with requests.

Ah, yes, thanks for this. Of course it's necessary to indicate the type of memory before it's included in the "different types of memory". :celebration:

Images by Raja (OCN)

I really wish we could but it puts too much strain on the database, causing unwanted outages and lockups.

On a sidenote: if anyone has issues with the XTU benchmark, can you also check that HPET is enabled in the BIOS?

As of now, all hardware that is able to run XTU (Sandy Bridge and up) should be able to get the correct verification. There's been internal testing with Sandy Bridge which is able to run the benchmark. That doesn't mean some people aren't experiencing problems. That's what we're trying to look into. I'm not entirely sure what the course of action may be in the future. It's possible that a newer version of XTU could feature a benchmark 2.0, in which case it would just be a new benchmark application. I don't anticipate hardware support being dropped at the moment.

Yes, working on it. Turns out to be more complicated than anticipated.

Older versions scoring better is something that shouldn't be a problem. Nothing of the XTU updates impacts the benchmark code; it's mostly adding support for overclocking new platforms. Currently XTU versions from v5.1.2 are supported. Older versions are no longer supported because of security updates. Actually, Genieben found some issues that Intel fixed

Just to follow up on this. The newest version of XTU always officially supports three generations prior to the current platform. So for XTU 6.0+ this includes: Skylake, Haswell(-e), and Ivy Bridge(-E). This does not necessarily mean it won't work on older platforms, like Sandy Bridge, it means there is no validation in place. We've been looking at the problem and it appears some users are able to run the benchmark with Sandy Bridge and Ivy Bridge-E. Others can't. Still looking for the problem ...

Man, you're going places with that brain of yours. Awesome stuff, perfect engineering!

Test BBCODE SuperPI 32M Leaderboard HyperX HOT Qualifier HWBOT Prime Leaderboard

Hi Remik88, Can you post a screenshot of the XTU which doesn't show the frequency? Which version of XTU are you using? What are your system specifications?

Do you have a link to the hwbot submission?

There's no "need to guess". On the stage page, click on the stage points next to your country to see which scores count for the country average. Scroll below and apply country filter to see all the results submitted in that particular stage. The rest of the work comes down to planning and communication. I am happy you liked our previous design and I hope you'll get used to the new interface and like it too

Fixed

For the Geekbench stage you need 5 different types of memory. Topdog already submitted using DDR4 and his score is higher than yours. That is why your score is not taken into account for the country average.

Fixed

Canada: "We are the best, sorry guys"

Just a heads-up, we're pin-pointing the problem with Ivy Bridge-E and Sandy Bridge compatibility for XTU 6.0.2.

http://hwbot.org/user/crow Fixed

Can you try to log out and log back in?