Jump to content
HWBOT Community Forums

Recommended Posts

Posted
4 hours ago, Fasttrack said:

No one cares to reply ?

How nice.

Yes, this really needs to be addressed please. @Leeghoofd Did the programmer have a look at the server logs? What was changed on the new server?

  • Crew
Posted
8 hours ago, Fasttrack said:

No one cares to reply ?

How nice.

you can always submit by using the datafile at hwbot itself

CBR15.png

 

Laura, the network specialist is still on holiday,... so we have to wait till she's back

Posted
2 hours ago, Leeghoofd said:

you can always submit by using the datafile at hwbot itself

CBR15.png

 

Laura, the network specialist is still on holiday,... so we have to wait till she's back

Yes Alby, I found out later this option. Thanks.

  • 3 weeks later...
Posted

Hello,  I'm unable to run benchmate.          I got init error, tried many reinstallation.      this is the log report:

LOG START at 2022-12-13 11:55:51 ----------------------
BenchMate 10.12.2.0
DPI Awareness used: System
Could not load font, falling back to Arial!
Could not load font, falling back to Arial!
Init Status: VERIFYING INSTALLATION
Could query crypt object signature of executable: C:\BM\bin\client64.exe (Error: Invalid signature or no signature at all)
Failed to load certificate: C:\BM\bin\client64.exe
Installation invalid!
Init Error: The verification of BenchMate's files has failed.

 

Hardware:  Gigabyte X570 UD & Ryen 4100, WINDOWS 10.

 

any suggestion?     (I have already tried the suggested solution, I have also tried to manual install the certificate include into the directory, but it doesn't solve.

Posted (edited)

Please don't install the certificate manually. It's done by the BM installer automatically.

It's best to remove the manually added certificates. They can cause problems if not done right.

"Could not query crypt object" is the culprit here. Please check that the file bin\client64.exe is available, readable and not corrupt. If you post a file hash of the file (like CRC32), I can help you to verify that.

Edited by _mat_
Posted

Reinstalled benchmate on the secondary hard drive, but I still get the same error.                    

I hve moved the entire disk with windows 10 system to another PC with similar specs (X370 wirh Ryzen 4600G instead of X570 and Ryzen 4100) and it works.           So it is hardware problem?   But both platform was ad default.. no OC.

  • 4 weeks later...
Posted (edited)

bad_module_info error was maybe first one after this stopped working

 

 LOG START at 2023-01-08 14:45:17 ----------------------
BenchMate 10.12.2 
Initializing components:
 => DPI Awareness
DPI Awareness used: System
 => QPC timestamp
 => Fonts
 => Adjusting window style
 => Benchmark factory
 => WMI
 => Query system data
 => cURL
 => Timer object
 => Submission object
 => CPU affinity map
 => Preset UI
 => Single node found: 1
 => Single node found: 1
 => Loading client config file: client.json
Could not load client configuration data from file: client.json
 => Loading apps config file: apps.json
Could not load apps configuration data from file: apps.json
 => Loading result meta files
 => Sensor thread
 => Process thread
 => Timer Skew Test thread
 => Init thread
Theme selected: BenchMate
Init thread running: 0x0000000000000374
New initialization update status: Installing driver
Initializing Reliable Benchmark Timer driver
Reliable Benchmark Timer successfully initialized.
HPET Mode: HPET32
HPET Frequency: 14.32 MHz
Resuming timer skew test thread
New initialization update status: Resuming process thread
Configured system timers for skew test:
New initialization update status: Initializing HWiNFO
 => HPET32, 14.32 MHz
 => ACPI PM, 3.58 MHz
Initializing HWiNFO in sensor thread
Process thread running: 0x000000000000035C
 => QPC HPET, 14.32 MHz
Sensor thread running: 0x0000000000000350
 => Hotkeys
4 hotkeys successfully registered!
Skew Test:
Components successfully initialized.

Edited by Janne77
Posted
8 hours ago, Janne77 said:

bad_module_info error was maybe first one after this stopped working

 

 LOG START at 2023-01-08 14:45:17 ----------------------
BenchMate 10.12.2 
Initializing components:
 => DPI Awareness
DPI Awareness used: System
 => QPC timestamp
 => Fonts
 => Adjusting window style
 => Benchmark factory
 => WMI
 => Query system data
 => cURL
 => Timer object
 => Submission object
 => CPU affinity map
 => Preset UI
 => Single node found: 1
 => Single node found: 1
 => Loading client config file: client.json
Could not load client configuration data from file: client.json
 => Loading apps config file: apps.json
Could not load apps configuration data from file: apps.json
 => Loading result meta files
 => Sensor thread
 => Process thread
 => Timer Skew Test thread
 => Init thread
Theme selected: BenchMate
Init thread running: 0x0000000000000374
New initialization update status: Installing driver
Initializing Reliable Benchmark Timer driver
Reliable Benchmark Timer successfully initialized.
HPET Mode: HPET32
HPET Frequency: 14.32 MHz
Resuming timer skew test thread
New initialization update status: Resuming process thread
Configured system timers for skew test:
New initialization update status: Initializing HWiNFO
 => HPET32, 14.32 MHz
 => ACPI PM, 3.58 MHz
Initializing HWiNFO in sensor thread
Process thread running: 0x000000000000035C
 => QPC HPET, 14.32 MHz
Sensor thread running: 0x0000000000000350
 => Hotkeys
4 hotkeys successfully registered!
Skew Test:
Components successfully initialized.

System information? It looks like HWiNFO doesn't start. Please download HWiNFO and check if it's working.

  • 4 weeks later...
Posted

IMHO, actual version of benchmate is not working on old (for example s775) with windows10.

Actual versions of Win10 allows me to see benchamate windows for few seckonds, but 1st build of win10 (from 2015) made a different UX :)
 



It is possible to run client and it is possible to run hwifo (no examples on video) and some tests, but BenchMate is actually broken.

Posted (edited)

Yes, Socket 775 is not officially supported and untested. Some people could run these old platforms, but the timers are unreliable, so it's pure luck.

Starting with the upcoming version 10.13, I will not allow unsupported platforms. Support starts with Nehalem, Westmere and Sandy Bridge.

On AMD I will support Bulldozer/Bobcat onwards. Maybe I can add some K10 CPUs later on, but let's face it: That's not the target audience of BM.

Edited by _mat_
Posted

One more case. I will give an example with 775, but it is not principial.


I have a celeron 430 (775? 200*9) and Benchmate. Benchmate shows me a valid cpu name, but i see a "celeron M 430" on hwbot result. Also, i see a lot of wrong hardware points or even global cups. So, i made a lot of editions of all results, but season points was wrong anout 12 hours. It is not a good practice, i think.

Posted
13 hours ago, _mat_ said:

Yes, Socket 775 is not officially supported and untested. Some people could run these old platforms, but the timers are unreliable, so it's pure luck.

Starting with the upcoming version 10.13, I will not allow unsupported platforms. Support starts with Nehalem, Westmere and Sandy Bridge.

On AMD I will support Bulldozer/Bobcat onwards. Maybe I can add some K10 CPUs later on, but let's face it: That's not the target audience of BM.

May be, it will be a good idea to make some exclusions for "win 7 only" systems and benchmate 10.8 or 775/754/939 systems and benchmate 10.11?

IMHO, 7zip results of old systems are interesting.

  • Like 1
  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...