St Augustine Photographers

Fix 3DMark Stuck on Collecting System Info

A quick guide to fixing Futuremark SystemInfo issues so you can get back to benchmarking.

TL;DR — Quick Fixes

  1. Close SignalRGB if you have it running
  2. Disconnect USB audio devices temporarily
  3. Roll back to a previous 3DMark version via Steam
  4. Run the SystemInfo diagnostic tool to disable problematic modules

The Problem

You launch 3DMark, click to run a benchmark, and... it hangs. The status bar says "Collecting System Info" and nothing happens. Maybe it eventually times out, maybe it sits there forever. Either way, you can't run your benchmark.

This is a known issue with Futuremark SystemInfo, the component that gathers your hardware details before running tests. Several things can cause it to hang.

Common Causes

  • SignalRGB conflict — There's an outstanding compatibility issue with SignalRGB. Close it before launching 3DMark.
  • USB audio devices — Some USB speakers, headphones, and amps incorrectly identify themselves as "USB Storage Devices," causing SystemInfo to hang when scanning storage.
  • WMI (Windows Management Interface) issues — Can indicate OS installation problems.
  • Problematic hard drives — Dead or failing drives can cause the storage scan to hang.
  • Bad SystemInfo update — Automatic updates can occasionally introduce bugs.

Fixes to Try

Fix 1: Close SignalRGB Most Common

If you use SignalRGB for RGB lighting control, close it completely before launching 3DMark. There's a known compatibility issue that causes SystemInfo to hang.

Check your system tray—SignalRGB often runs in the background even when the window is closed.

Fix 2: Disconnect USB Audio Devices

Some USB audio devices (speakers, headphones, DACs, amps) incorrectly report themselves as storage devices. When SystemInfo tries to query their "storage capabilities," it hangs.

Quick test: Unplug USB audio devices, run 3DMark, then reconnect them after the benchmark starts.

Permanent fix: In Device Manager, find the problematic device, right-click → Properties → Driver → Disable device. Re-enable after benchmarking.

Fix 3: Roll Back to Previous 3DMark Version (Steam)

If this started after a recent update, try rolling back:

  1. Right-click 3DMark in Steam → Properties
  2. Go to the Betas tab
  3. In the dropdown, select "previous version"
  4. Click OK/Apply and let Steam download the older version

Fix 4: Use the SystemInfo Diagnostic Tool Advanced

Futuremark includes a diagnostic tool that lets you disable specific SystemInfo modules:

C:\Program Files (x86)\Futuremark\SystemInfo\FMSIDiag.exe

Run this tool, go to the second tab, and disable individual scanner modules to isolate the problem. If "WMI Info" is causing the hang, you can disable it—the benchmark will still run, just without some hardware telemetry.

Note: When SystemInfo updates, disabled options may reset. You may need to disable them again.

Fix 5: Reinstall SystemInfo

If nothing else works, try a clean reinstall:

  1. Open Windows Settings → Apps → Installed apps
  2. Find and uninstall Futuremark SystemInfo
  3. Reboot your computer
  4. In Steam, right-click 3DMark → Properties → Local Files → Verify integrity of game files
  5. Steam will reinstall the latest SystemInfo

Fix 6: Nuclear Option — Disable SystemInfo Entirely

If you just need to run a quick benchmark and don't care about hardware telemetry in your results:

  1. Uninstall Futuremark SystemInfo from Windows
  2. Run 3DMark without it

Your benchmark will run, but results won't include detailed hardware information. This is a workaround, not a real fix.

Still Stuck?

If none of these fixes work, there may be a deeper issue with your Windows installation (particularly if WMI queries are failing). Consider:

Did this help? If one of these fixes worked for you, great! If you found a different solution, feel free to let me know and I'll add it to this guide.

Last updated: January 2026