benchmark 5 doesn't start

[Jiri.Matys]

Hi,

welcome screen shows up, but after a while disappear and thats all. Benchmark 4.1 works fine.

[daniel.taskoff]

Hi,

Thanks for the report!

Does the same happen with the CLI version of the application?
Can you send us the log file, if there’s any? It’s located in %TEMP%/V-Ray Benchmark/logs/.

Best regards,
Daniel

[Jiri.Matys]

CLI doesnt work either.
Sure, here it is.

[daniel.taskoff]

Thank you for your time!

Could you please share the output from the following powershell commands:

Get-WmiObject -Query "select maxclockspeed from win32_processor" | Format-List -Property maxclockspeed

Get-WmiObject -Query "select percentprocessorperformance from win32_perfformatteddata_counters_processorinformation where name='_Total'" | Format-List -Property percentprocessorperformance

[Jiri.Matys]

Not sure if I am doing this right.

[GARY_ROYLANCE]

Same here, Benchmark 5 doesn't start. 1950X Threadripper | RTX 3090 | RTX 2060 Super | 128GB RAM

[daniel.taskoff]

Jiri.Matys , you have to open Windows PowerShell first. This can be done by either entering "powershell" in the search (next to Windows's start button), or writing it in Command Prompt (where you executed the previous commands).

GARY_ROYLANCE , may I ask you for your log file, as well? It's in %TEMP%/V-Ray Benchmark/logs

[Jiri.Matys]

Ok, so here it is.

[GARY_ROYLANCE]

Jiri.Matys , you have to open Windows PowerShell first. This can be done by either entering "powershell" in the search (next to Windows's start button), or writing it in Command Prompt (where you executed the previous commands).

GARY_ROYLANCE , may I ask you for your log file, as well? It's in %TEMP%/V-Ray Benchmark/logs

[benchmark] got args:
[warning] Couldn't get information about hardware-accelerated GPU scheduling
[benchmark] Couldn't get frequency
V-Ray Benchmark: FatalError "Couldn't get frequency"
V-Ray Benchmark: exit(1)
TypeError: Cannot read property 'emit' of undefined
at ChildProcess._0x283a00 (C:\Users\GARYRO~1\AppData\Local\Temp\V-Ray Benchmark\resources\app\src\main.js:1:7629)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:962:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)

[daniel.taskoff]

An update:
Since we're using Windows' performance counters in the application, some modifications of the counters might crash it.
As GARY_ROYLANCE pointed out, resetting the performance counters by executing

lodctr /r

from a Command Prompt with administrator privileges fixes such crashes.
Jiri.Matys , please confirm if this fixes your issue, as well.

Thanks to both of you for the cooperation!

EDIT: In order to use the correct ldoctr executable, you might have to run a slightly modified version of the command above.

%windir%\SysWOW64\lodctr /r

[Shusen.ZHAO]

I also encountered the same problem.
CPU: AMD 3900X
Memory: 64G
GPU: RTX 3090 24G

[Alex_M]

Same problem here. Everything was working great when I had my GTX 1080 Ti. The problem started after I installed an RTX 3090 graphics card. When I start Vray Benchmark 5, I briefly get the splash screen and then the process dies. I can run Vray Benchmark 4.10.07 fine.

[JezUK]

Just to chime in, I was having this problem whilst I still had the same old GTX 1080 ti's in - and now I've got an RTX 3090 as well and the Bench Mark software (which ever 5xxx version I use) still doesn't work... (4.xx works).

[Alex_M]

An update:
Since we're using Windows' performance counters in the application, some modifications of the counters might crash it.
As GARY_ROYLANCE pointed out, resetting the performance counters by executing

lodctr /r

from a Command Prompt with administrator privileges fixes such crashes.
Jiri.Matys , please confirm if this fixes your issue, as well.

Thanks to both of you for the cooperation!

EDIT: In order to use the correct ldoctr executable, you might have to run a slightly modified version of the command above.

%windir%\SysWOW64\lodctr /r

Thanks, Daniel. This worked!!!

[Jiri.Matys]

An update:
Since we're using Windows' performance counters in the application, some modifications of the counters might crash it.
As GARY_ROYLANCE pointed out, resetting the performance counters by executing

lodctr /r

from a Command Prompt with administrator privileges fixes such crashes.
Jiri.Matys , please confirm if this fixes your issue, as well.

Thanks to both of you for the cooperation!

EDIT: In order to use the correct ldoctr executable, you might have to run a slightly modified version of the command above.

%windir%\SysWOW64\lodctr /r

Yes, as I said in our chat, it helped, benchmark is working fine Thank you.