Jump to content
HWBOT Community Forums

_mat_

Members
  • Content Count

    734
  • Joined

  • Last visited

  • Days Won

    22

_mat_ last won the day on September 20

_mat_ had the most liked content!

Community Reputation

324 Excellent

About _mat_

Converted

  • Location
    AUSTRIA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you want texture and model verification, please use BenchMate 0.9.3. There will be another File Hash entry right below the executable. The number will always be the same unless something was tampered. Edit: Please don't use any NVIDIA resolution trickery with BenchMate, Windows native functions won't detect it and BenchMate will capture a wrong screenshot. I will look into it though, it's on my list. The real solution here is to make CPU-Z optional with BenchMate. It doesn't add anything that's not already on there (and much better because it's captured during the run). Unless SPD info is necessary, but that would be a single additional CPU-Z window (for now).
  2. Are you raising the bclock after the OS has booted?
  3. I've setup a Win 7 OS for old Intel platforms yesterday and it was nothing but trouble. Since this month a fresh SP1 install can't even check for Windows Updates without having the latest SHA256 update patches included. More of the same hassle when switching an existing W7 install from an old Intel platform to a new one. It doesn't work because of missing xHCI USB drivers. Same thing with Ryzen I guess, because last time I checked the mouse and keyboard didn't work and I couldn't log in. CINEBENCH R20 for example needs two additional patches to work on Windows 7 and doesn't work out-of-the-box either. Ryzen 3000 on Windows 7 is another topic. Multiple people tried and it's not only not officially supported (fixes and speed improvements won't happen on Windows 7), but it seems to be not as stable and slower. So in the end it's either a struggle to get it working on modern platforms or not the best choice anyways. And at some point in the future it might not be possible at all to go back to Windows 7. What happens then? Also don't forget that we want new people to come into the community. Most of the new guys start with Windows 10 on a modern platform and if they can't participate with that and their first score gets removed instantly, they will never get into competitive overclocking on HWBOT.
  4. Some hair turned gray already, so I guess I will go for the Sean Connery look when BenchMate has its first production release. I have "fixed" this bug by not touching the 32 bit mode configuration for HPET's Timer0 on Windows 7 anymore, even if a 64 bit main counter is available. It seems to be a hardware bug I could not get rid of, even when I disable the interrupts and the main counter. Some internal flaw in the Intel implementation I guess, that was never revealed because the OS always sets up the HPET timer properly before the first rollover happens. I have no clue why this doesn't happen on Windows 10 though. In any case, I've read over on OSR that a Windows kernel dev recommended to always use HPET in 32 bit mode, especially on 32 bit systems. There is also the problem of the main counter possibly not being latched correctly when it's 64 bit on a 32 bit platform, because reading 8 bytes is not atomic for 32 bit architecture. So the counter has to be read multiple times and checked for validity, which makes the already slow HPET even slower. Of course a 32 bit implementation has to handle the rollover that happens about every 5 minutes, so there are more instructions involved to make it work. For 64 bit I don't do rollover checks because it needs 9 million days with a 24 MHz frequency until that happens. I would call that safe for non-server/workstation applications. So consider the HPET64 implementation as faster, which is another reason to use Windows 10 if you can.
  5. I had a gook look at this and BenchMate 0.10 will work correctly on Windows 7 with 32 bit. It doesn't support kernel code integrity checks and there were other minor bugs that needed to be addressed. It should work with the next release and I hope you will have the time to take another look.
  6. Yes, BenchMate 0.10 will NOT support Geekbench. It will come with new benchmarks though like pifast. All integrations are in agreement with their respective developers. I will not throw days of work into the garbage anymore.
  7. You can download BenchMate 0.9.3 and add the manually installed Geekbench to the launcher. Just start BenchMate and click the + button below the application list. Select the executable of Geekbench (Geekbench 4.exe) and it will be added to the list.
  8. The rules would stay exactly as they are now for everything that is not supported or when BenchMate is not used.
  9. I think that and even more information should be available on a validation page for each result, just like CPU-Z has it. So we have to define: What needs to be on the screen? This should be only the most important information to get a quick look of what's going on here. What needs to be available on the validation page? This should be the place to show everything. Maybe some information is withheld and only available for moderators.
  10. That's a great idea! Will be available in BenchMate 0.10, you can find an ES marking right next to the CPU name:
  11. I have found a workaround for using Realtime priority on CINEBENCH and still have perfectly validated scores. ❤️ Bugfix will come with BenchMate 0.10 as soon as possible.
  12. Ah yes, I see that now. I am so deep into bugfixing anything that comes along, I might go crazy at some point.
  13. What happens exactly? Are you using Ryzen 3000 on Windows 7? In any case, I need more information to reproduce and fix any possible errors. Can you submit a bug report? You'll find it in the BenchMate menu or if the application can't start, please use bugreport.exe in the BenchMate directory to submit a report.
×
×
  • Create New...