Futuremark Systemscanner keep crashing

[blubberandy]

as it says. This thing keeps crashing and i cannot record any clocks or temperatures in any benchmark. Does someone else have this Problem?

[UL_Jarnis]

Do you have Corsair iCUE? The latest version of it is known to break SystemInfo at this time.

Also any other hardware monitoring utility is potentially able to cause monitoring to fail. Depends on the exact hardware config. Try closing anything nonessential (which is good idea before benchmarking anyway, to minimize background process overhead).

[blubberandy]

"Name der fehlerhaften Anwendung: FMSIScan.exe, Version: 5.69.1204.0, Zeitstempel: 0x6568626c
Name des fehlerhaften Moduls: atiadlxx.dll, Version: 31.0.23013.1023, Zeitstempel: 0x65666e09
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000d6d2b
ID des fehlerhaften Prozesses: 0x0x1838
Startzeit der fehlerhaften Anwendung: 0x0x1DA2E4CB55B703C
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Futuremark\SystemInfo\FMSIScan.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\atiadlxx.dll
Berichtskennung: a4da12b3-9118-4026-a9b9-266ee08ede3e
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: "

this is german. it seems to have a conflict with my gpu driver

[UL_Jarnis]

First thing to try would be to wipe drivers using Display Driver Uninstaller and then reinstall latest driver for you hardware.

But this could also be a background program related issue. There is no general issue with this driver - all AMD setups in our test lab complete a systeminfo scan with latest AMD drivers just fine.

[blubberandy]

well i try and report. thx so far

[sblantipodi]

I agree, if you close icue it works.

[UL_Jarnis]

iCUE has a known bug that can cause this. Corsair is aware, but no idea how soon they can fix it.

[sblantipodi]

nice to know that Corsair knows about it. thanks for informing us.
I use your benchmarks since the first releases and I still love them.