Systeminfo takes forever again after the laest update

[Del_Pierro]

A problem from the past - now it frustrates me again. Systeminfo hangs in the task manager forever and the program does not start. I don't know why you break that function on a frequent basis.

[UL_Jarnis]

SystemInfo has not changed for over a month. So whatever is causing this is caused by something else. Most commonly if you have another hardware monitoring utility running when SystemInfo scan starts and both try to access same low level hardware bits simultaneously, a hang could occur.

The "program does not start" is bit unclear, does the UI open or not? Can you email to [e-mail] with more detail what exactly is happening and what programs you have running in the background?

[DLB]

No problems here after update

[HateCult]

Me too , system info takes forever. Not normal.

[¤ 31 Bit ¤]

took time 10-15 seconds for my pc

[Lucille]

After installing new CPU benchmark it loops in Systeminfo forever. After deinstalling CPU benchmark I can use VRMark again.

[UL_Jarnis]

That makes no sense whatsoever. CPU benchmark and VRMark have nothing to do with each other and uninstalling CPU benchmark changes nothing related to SystemInfo.

We've seen some cases where updating SystemInfo requires a reboot to work normally, tho even in this case it is unclear why. After a system reboot there should be no issues.

[MaCK0y]

After installing the CPU benchmark it gets stuck on Scanning System Info for me.

Edit: nevermind. Force closed javaw.exe, restarted Steam and now working.

[El Jefe]

Now none of the benchmarks work at all. I get the same error for all of them.
Window/swapchain initialization failed: DXGI call IDXGISwapChain::SetFullscreenState failed [0X80004005]

Edit: Ok so 3dmark doesn't like high refresh rates so I put it at 60 and it loaded but the cpu test rebooted my pc after a few seconds of testing. I really don't need this software since everything else works fine. Uninstalled.

[UL_Jarnis]

Display panel overclocks won't work with 3DMark.

(Normal high refresh panels work just fine, the issue only comes if you tweak 60hz panel to be something other than 60hz)

CPU test causing system to reboot suggests hardware problems - too weak PSU or problems with motherboard BIOS settings (usually too low Load Line Calibration setting, ie. motherboard "brownouts" when CPU load switches between "none" and "100%" very fast, causing major switch in power demand)

[El Jefe]

Originally posted by UL_Jarnis:

Display panel overclocks won't work with 3DMark.

(Normal high refresh panels work just fine, the issue only comes if you tweak 60hz panel to be something other than 60hz)

CPU test causing system to reboot suggests hardware problems - too weak PSU or problems with motherboard BIOS settings (usually too low Load Line Calibration setting, ie. motherboard "brownouts" when CPU load switches between "none" and "100%" very fast, causing major switch in power demand)

Gotcha. I select 120hz because it's an option in windows display settings. I don't know anything about tweaking unless that's just what it's called nowadays.

Everything in my system is adjusted to idle and automatically increases fan speeds, voltages and mhz. All my lights go from blue to red when stuff heats up. I don't want to undo all that just for a benchmark that is picky, no offense, but there are other benchmarks that work fine with the way my system is set up, and I don't consider it hacking or cheating. Thanks for the reply.

[UL_Jarnis]

Selecting higher refresh rate from Windows display options is perfectly fine. Panel overclocking is different, it is modifying otherwise capped-to-60hz panel to run at say 75hz via unofficial tricks.

Reboot during run is an indication your system is not 100% stable.

[Raiden85OCUK]

Same issue as MaCK0y above, after installing the CPU benchmark it got stuck on scanning system info, I closed javaw.exe with the task manger and it started ok the second time.

No other hardware monitoring tool was open at the time.

Windows 10 21H1 (19043.1081)
5950X

[rckrz6]

i have same issue as OP, systeminfo now takes a long time

[UL_Jarnis]

First thing to check if the scan takes exceedingly long is to see if your Windows Event Viewer has any disk errors (indicating that one of your disks is failing) - that could stall the scan.

If there are no such errors, you can run FMSIDiag.exe from C:\Program Files (x86)\Futuremark\Systeminfo\ and in second tab, enable redirect, then scan from first tab and send the client and scanner logs that appear in SystemInfo folder to [e-mail] and we'll take a look what could be causing this.

[Del_Pierro]

I can use the tool when I kill the systeminfo scanning in the task manager, then deavtivate it in the tool. The annoying thing ist that after every update the system scan is back to activated so I need to do it all over again. Any chance of keeping the setting with an update?