SystemInfo Issues

[Uroke]

Hi, I seem to having some issues with 3DMark and not being able to run a proper benchmark. This is on a new build (12700k, 3080ti, win 11). Firstly, the program itself takes like 5 minutes to initialize, first hanging on "collecting system info" and then "loading GUI"

Secondly, While attempting to run a benchmark, the run hangs on "collecting system info" and then eventually starts. This results in either a failed run or a run with no system info data stating "SystemInfo data is incomplete. (Some of the data could not be parsed)"

Killing the multiple Futuremark SystemInfo in task manager causes the run to start and then end up with just a score and no extra data

Anyone able to offer some guidance on this issue?

[UL_Jarnis]

To figure out what is going on, I'd need some logs.

Go to SystemInfo install folder at C:\Program Files (x86)\Futuremark\SystemInfo

Run FMSIdiag.exe

Enable "redirect output" in the second (advanced) tab.

Run scan (collect) from the first tab, send the .txt log files that appear in the SystemInfo install folder (client and scanner, there may be more than one)

(email logs to [e-mail] )

If one or more steps in the scan takes very long, you can also try disabling them in the Advanced tab. We've had two recent reports that on some systems "WMI Info" component causes a hang. Most likely this is an indication that something is wrong with the OS install as this bit queries Windows Management Interface bits, but as this data is currently not used for result validation, disabling it may allow you to work around the hang. But it could also be some other component, would need to see the logs to figure out which one.

[DroptheHammer]

Originally posted by UL_Jarnis:

To figure out what is going on, I'd need some logs.

Go to SystemInfo install folder at C:\Program Files (x86)\Futuremark\SystemInfo

Run FMSIdiag.exe

Enable "redirect output" in the second (advanced) tab.

Run scan (collect) from the first tab, send the .txt log files that appear in the SystemInfo install folder (client and scanner, there may be more than one)

(email logs to [e-mail])

If one or more steps in the scan takes very long, you can also try disabling them in the Advanced tab. We've had two recent reports that on some systems "WMI Info" component causes a hang. Most likely this is an indication that something is wrong with the OS install as this bit queries Windows Management Interface bits, but as this data is currently not used for result validation, disabling it may allow you to work around the hang. But it could also be some other component, would need to see the logs to figure out which one.

I've been trying to perform these steps since I had the same problem as the OP. Collecting just seems to take hours and never finishes. Any idea if/when we'll get some patches around this? For comparison, i'm 12900KS on a 4090 and Z690.

[UL_Jarnis]

If it takes a long time, the scanner is hanging at some point.

The incomplete log may still tell us where. Alternatively the Advanced tab of FMSIDiag.exe allows enabling and disabling individual components to find out which component is breaking. Ones I'd check first are WMI Info and anything related to Storage. Contact us via email and I'll walk you thru the process of determining what is going wrong.

Historically following reasons have been seen to break SystemInfo. All are fairly rare, but PCs these days are complex things:

- Faulty or non-formatted hard disk attached to the system (Breaking Storage component)

- Third party monitoring/system scanning utility in the background conflicting with the scan. Try closing all background programs that do system hardware monitoring

- Outdated/buggy motherboard BIOS hanging when querying some specific hardware detail

- Something broken in the Windows installation that causes WMI Info (querying Windows Management Interface) to break

[mir ist langweilig @ mp3]

I have the same problem since 2 weeks.

It looks, like it has something to do with CPUID Info, because after disabling this check, it starts perfectly fine! Standalone CPU-Z works as expected.
I'll send you my logs via email.

Greetings from Germany

[UL_Jarnis]

Do you happen to have SignalRGB on your system? That one has been seen breaking CPUID info and we're working on solving it.

If not, ensure that motherboard BIOS is up to date.

[mir ist langweilig @ mp3]

Originally posted by UL_Jarnis:

Do you happen to have SignalRGB on your system? That one has been seen breaking CPUID info and we're working on solving it.

If not, ensure that motherboard BIOS is up to date.

Yes, I'm using SignalRGB and closing it makes the magic happen.
Thanks for your help. Please let me know, if you solve the problem completely.

[peaceofday]

I know how to fix this PROBLEM. but right now Im at work, I can't reach to my computer. When I get home, I will get you out.

Originally posted by mir ist langweilig @ mp3:

Originally posted by UL_Jarnis:

Do you happen to have SignalRGB on your system? That one has been seen breaking CPUID info and we're working on solving it.

If not, ensure that motherboard BIOS is up to date.

Yes, I'm using SignalRGB and closing it makes the magic happen.
Thanks for your help. Please let me know, if you solve the problem completely.

[peaceofday]

Originally posted by peaceofday:

I know how to fix this PROBLEM. but right now Im at work, I can't reach to my computer. When I get home, I will get you out.

Originally posted by mir ist langweilig @ mp3:

Yes, I'm using SignalRGB and closing it makes the magic happen.
Thanks for your help. Please let me know, if you solve the problem completely.

You should try this way to see it works with your system or no.

1, Uninstall software Futuremark systeminfo from Programs and features, them restart your windows.
2, Open steam, right click on 3Dmark --> Properties --> Local files tab --> verify integrity of software files, then waiting a little bit for running.
3. Reopen your steam, then launch 3Dmark, and it will detect and install Futuremark again. Then all done!

[mir ist langweilig @ mp3]

I tried this before i wrote here, but sadly this didn't work on my system.

I also tried uninstalling 3dmark completely and installed it again, but this didn't helped me either.

So I'll wait until there is an official solution from Jarnis...

But thanks for your advice!

[Whiny Anakin]

Closing CPUID instantly let me pass the "starting ui" page, it's really weird

[UL_Jarnis]

We have a new SystemInfo coming out tomorrow that has some bugfixes related to CPUID component that may help.

Also note that there is an outstanding compatibility issue with SignalRGB - if you have that on your system, try closing it before starting 3DMark.

[Derk Ironwulf]

brand new PC Build; AMD 79503DX 6600 DDR 5 RAM 4090 FE Crucial NVME SSD Gen 5 Drie.... 3d mark takes fooooorrrrrreeeevvvvveeeeeerrrr to collect system info.

[siortuth]

Dear Peaceofday,
Thank you for your input on solving this problem with 3DMark TimeSpy benchmarks. I had uninstalled and reinstalled the software several times to no avail. After each reinstall of the software the "SystemInfo data is incomplete. (Some of the data could not be parsed)" message would always comeback. It was that way until i found your message that suggested to uninstall 3dMark benchmark from the Steam Menu then REBOOT the computer. After the reboot compleated I started Steam Engine and reinstalled all of the files associated with my 3DMark subscription and low and behold my system info was found, my games benchmark fields were now activated and my benchmarking works as it should. Thank you ever so much.

System Specs:
i9 13900KS.
Asus ROG Maximus Z790 Hero MB bios ver. 1801.
Patriot memory 7600Mhz, running 4 sets of memtest86 v10 stable at 7200Mhz.
2 Samsung NVME 990 pro 2Tb in Bios setup Raid for a 4 Tbyte boot drive.
AsRock 7900 XTX Phantom Gaming 24 Gbyte Video Card.
Razer Chroma Black Widow Keyboard.
Razer Basilisk v3 wired mouse.
Acer 38 inch wide screen curved monito 3840x1600 model XR382CQK
Logitech 5.1 surround speakers with powered subwoofer on MB realtek audio.

[Tibbles McCumsies]

Having the same issue. 3D Mark takes about 15 minutes to "initialize" then brings up zero system info when it does. I have uninstalled and reinstalled SystemInfo from their website via the latest link. I have uninstalled and reinstalled FutureMark. I have uninstalled and reinstalled 3D Mark more times than I can count. I have verified files many times. At a loss for words as to how bad this is. Any help would be appreciated.

[cozval]

Originally posted by Tibbles McCumsies:

Having the same issue. 3D Mark takes about 15 minutes to "initialize" then brings up zero system info when it does. I have uninstalled and reinstalled SystemInfo from their website via the latest link. I have uninstalled and reinstalled FutureMark. I have uninstalled and reinstalled 3D Mark more times than I can count. I have verified files many times. At a loss for words as to how bad this is. Any help would be appreciated.

same problem here with a rtx 4080 and a 7800x3d