Issues with 3DMark and Steel Nomad

[IronMaaasel]

I have a few problems with the last update. The start of 3DMark disrupts my entire OpenRGB and also Corsair's RGB control. It also intervenes briefly in the control of FanControl. Why is this happening? This does not require 3DMark to read/change this data.

The benchmark still hangs in "Collecting System Info". Nothing just happens there. It's only been like this since the update with Steel Nomad.

[UL_Jarnis]

OpenRGB is not very nice when accessing low level motherboard functions. It can conflict with SystemInfo (SystemInfo will hang for a long time waiting for OpenRGB to release their lock on the hardware bits accessed by CPUID component). I have no solution other than to close OpenRGB before running 3DMark, or reporting the issue to them. They would need to discuss this with the developer of CPUID/CPU-Z to solve the conflict.

Corsair iCUE also had the same issue but it should be fixed by their latest update as they already worked the issue out with CPUID/CPU-Z developer. Ensure that Corsair iCUE is up to date (released couple of weeks ago)

[CaptnDanLKW]

Just an additional item to note - sometimes the test finishes, but when we would expect the results to fade in, the main window just remains at 'Running benchmark'. Moving mouse over the 'Running benchmark' text it highlights Orange as if its a hyperlink but non-interactable. The rest of the Top row functions (home, benchmark, stress test, results, options) don't respond either. Close closes the window but steam and task manager show it's still running.

[stahlhart]

Originally posted by UL_Jarnis:

I have no solution other than to close OpenRGB before running 3DMark, or reporting the issue to them.

I customarily shut down all unnecessary background processes before running 3DMark (RGB, Defender, etc.), not in my case to avoid conflicts, as I'm not having any, but just to keep them from consuming resources that the benchmark could be using. Every little bit helps.

[UL_Jarnis]

Originally posted by CaptnDanLKW:

Just an additional item to note - sometimes the test finishes, but when we would expect the results to fade in, the main window just remains at 'Running benchmark'. Moving mouse over the 'Running benchmark' text it highlights Orange as if its a hyperlink but non-interactable. The rest of the Top row functions (home, benchmark, stress test, results, options) don't respond either. Close closes the window but steam and task manager show it's still running.

Hmm, not seen this in our test lab. Would be very interested to seeing trace logs from such a scenario if you can reproduce it. Please contact us at [e-mail] if you can reliably somehow make this happen on demand.

[IronMaaasel]

Originally posted by UL_Jarnis:

OpenRGB is not very nice when accessing low level motherboard functions. It can conflict with SystemInfo (SystemInfo will hang for a long time waiting for OpenRGB to release their lock on the hardware bits accessed by CPUID component). I have no solution other than to close OpenRGB before running 3DMark, or reporting the issue to them. They would need to discuss this with the developer of CPUID/CPU-Z to solve the conflict.

Corsair iCUE also had the same issue but it should be fixed by their latest update as they already worked the issue out with CPUID/CPU-Z developer. Ensure that Corsair iCUE is up to date (released couple of weeks ago)

Hi and thanks for your Information. Deactivating the Effects Plug-In in OpenRGB helped ;)

But it´s still causing some weird FAN Controlling with the Programm "Fan Control" running for my CaseFans.

[HSken]

Same issue here, every benchmark was stuck at " Please Wait Collecting System info" closing openRGB solved it :) HWMonitor was also very slow at booting