3DMark
Fire Strike Extreme crashing after latest (Steel Nomad) update?
Has anyone noticed any issues with Fire Strike Extreme ever since the latest update? No issues running all the other benchmarks in the suite as well games, just FSX? Would just crash necessitating a reboot. Using a Radeon 6800 with an i7-8700k. Happens regardless whether REBAR is enabled or disabled. Problem doesn't go away either with older versions of the Adrenalin drivers. I know FSX is probably dated now, but I like to keep it running as long as possible just to have historical comparison with older results and HW. Thx.
< >
Menampilkan 1-12 dari 12 komentar
26 Mei 2024 @ 10:59am 
Not having any problems running it myself haven't ran it sense my last cpu but my system is full amd maybe someone will chime in with a mixed intel amd system similar.
UL_Jarnis  [pengembang] 27 Mei 2024 @ 12:58am 
There was no change to this test in the recent updates, so there is some other reason for this. First thing I'd try with a crash like this is to wipe GPU drivers using DDU and reinstalling them.

If problems continue, do they happen on every variant of Fire Strike, or just one of them?

Do you see issues with any other test?
Brian48 28 Mei 2024 @ 4:01pm 
Thanks for the reply. Just Fire Strike and all it's variants seem to be the problem. I assume this might be a Direct X 11 issue of some type? I've tried other DX11 benchmarks like Heaven and some older DX11 games. No issues there. Uninstalled the app, deleted the Steam folder, and reinstalled again, but the same behavior still persists. I used both AMD's driver removal utility as well as DDU, but same results.
UL_Jarnis  [pengembang] 29 Mei 2024 @ 12:40am 
Then my guess would be that this is caused by some background program that specifically interferes in DX11 stuff. If you send a failed result file to us (from Documents/3DMark/) I can try investigate this further. ul.benchmarksupport@ul.com
Brian48 29 Mei 2024 @ 6:08am 
Much appreciated. I just sent you two results files (.ZIP) from my Yahoo account. Please let me know if you don't receive it.
UL_Jarnis  [pengembang] 29 Mei 2024 @ 7:27am 
Try again, the zip was 811 bytes. The data inside was effectively blank.
Tryhard 7 Jul 2024 @ 4:12pm 
I do also have the same symptom. Only Firestrike and it's variants crashes my system and require reboot. ALL other benchmarks runs pretty well.
Terakhir diedit oleh Tryhard; 7 Jul 2024 @ 4:13pm
stahlhart 7 Jul 2024 @ 9:12pm 
Working okay here:

https://www.3dmark.com/3dm/114165982?
https://www.3dmark.com/3dm/114165816?
https://www.3dmark.com/3dm/114166101?

If it were me, I'd cross-verify that the GPU overclock is stable and error-free with the 3D Adaptive test in OCCT.
Tryhard 8 Jul 2024 @ 10:38am 
Got no errors on 3D Adaptive :( nor any other benchmark even directx11 ones
i do have a legion 5i i7 10750h rtx 2060. Stock.
Terakhir diedit oleh Tryhard; 8 Jul 2024 @ 10:44am
Also having the same issue, 6900 xt
UL_Jarnis  [pengembang] 5 Jan @ 2:05am 
Diposting pertama kali oleh SIR Robin:
Also having the same issue, 6900 xt

This is not a benchmark issue, something else is causing this. Background program interference, messed up driver or hardware issue.
Hey, I have the same problem with Time Spy on my RX 6800XT. It's a fresh Windows 11 installation with everything up to date and no additional software or services running. I first got the "Rendering Device Lost" message. Reinstalled the drivers without Adrenalin and the Time Spy Benchmark now just crashes without any message and I have to reboot because 3DMark is still running some processes in the background.

I also tried older drivers but always the same error. Disabled the default overclocking of my GPU (Nitro+) and disabled RAM EXPO profile (so no overclocking here), nothing helped. Steel Nomad and Speed Way both run without problems.

I'm not saying that it's the fault of 3DMark but maybe theres somenthing else in common with those cashes? I was looking for solutions online and found lot's of posts with the same errors.

Last time I run Time Spy on the same hardware was in 2023 so I can't pinpoint what changed since then.

The only thing I can see as "deviation of the norm" is that I run "Windows 11 Pro N" which comes without "Media Feature Pack" and I added it (System -> Optional Features) just to be sure it's not because of that.

You can see my hardware in one of the Steel Nomad results if it helps:
https://www.3dmark.com/sn/3122115
< >
Menampilkan 1-12 dari 12 komentar
Per halaman: 1530 50