AMD Radeon RX 6800: Port Royal demo crashes

[myna]

I have a new system with a RX 6800 that is very stable (99,3% in stress test and no incidents beside this). I can run the Port Royal benchmark, but the demo crashes after around three seconds.

System: X570 with Ryzen 5800, Radeon RX 6800 & 32GB RAM DDR 3866MHz,
Windows 19042.662, Adrenalin 20.11.3 & latest 3DMark.
For now everything is stock.

[Seamus]

Might want to include your log file about the crash for whenever Jarnis happens to notice this thread.

[myna]

Not really helpful, I think. I deleted the Steam key, custom run without graphics test and demo activated.

08:27:55.439 INFO _____ ____ __ __ _
08:27:55.440 INFO |___ /| _ \| \/ | __ _ _ __| | __
08:27:55.440 INFO |_ \| | | | |\/| |/ _` | '__| |/ /
08:27:55.440 INFO ___) | |_| | | | | (_| | | | <
08:27:55.440 INFO |____/|____/|_| |_|\__,_|_| |_|\_\
08:27:55.440 INFO Starting 3DMark v2.16.7113 s64
08:27:55.806 INFO initializing Steam service
08:27:56.162 WARN failed to read application settings, reverting to default.
08:27:58.161 WARN failed to read application settings, reverting to default.
08:28:11.424 WARN failed to read application settings, reverting to default.
08:28:29.661 WARN failed to read application settings, reverting to default.
08:28:30.577 INFO starting benchmark PORT_ROYAL_CUSTOM
08:28:42.413 INFO Fetching Port Royal key at result creation
08:28:42.448 INFO got Steam authentication ticket
08:28:44.135 INFO Running benchmark, system scan included, and monitoring included
08:28:55.302 INFO Begin workload set Port Royal Demo Custom
08:28:55.309 INFO launch command is "D:\Games\Steam\steamapps\common\3DMark\dlc\port-royal-test\bin\x64\3DMarkPortRoyal.exe" --in "C:\ProgramData\UL\3DMark\tmp\fm-workload-11770276889703215495.json" --out "C:\ProgramData\UL\3DMark\tmp\fm-result-1964544799339433874.json"
08:29:16.754 ERROR workload produced no result
08:29:16.758 INFO End workload set Port Royal Demo Custom
08:29:18.105 INFO Benchmark completed.

[UL_Jarnis]

Demo has some effects that are not present in the benchmark. I would venture a guess this might be a driver problem.

[myna]

I thought that it could be something like this, but I have asked other owners of the RX 6800 and they don't have problems with the demo. More or less similar systems like me, new Ryzen CPU with X570 chipset.

The benchmark is running just fine, over and over again. Control is running with RT enabled, too. I could test Death Stranding, but haven't installed it yet.

[UL_Jarnis]

Well, when running into any strange stuff like this, first thing I'd try is Display Driver Uninstaller nuke of graphics drivers and reinstall latest drivers. Very often that can magically fix things that are otherwise inexplicable.

[myna]

I tried a lot now. Uninstalled with DDU in secure mode. After reinstall I saw the first driver hang since I installed the system in Port Royal benchmark. Demo showed same behaviour as before. I tested other benchmarks from the suite and had problems there as well.

Uninstalled everything with the AMD uninstaller. Reinstalled and the demo did run a second longer than ever before, but the systems wasn't rock stable.

Uninstalled AMD graphics and chipset driver completely with DDU in secure mode. Now it seems to work as before the whole process.

Demo doesn't run, but benchmarks where fine and on the same level as the first runs last week. The scores aren't validated and I'm not sure why. Maybe the 20.11.3 isn't allowed yet. The only difference I see to the validated results with 20.11.2 is the CPU where all cores were listed and now I only see one entry.

22:31:25.754 INFO _____ ____ __ __ _
22:31:25.756 INFO |___ /| _ \| \/ | __ _ _ __| | __
22:31:25.756 INFO |_ \| | | | |\/| |/ _` | '__| |/ /
22:31:25.756 INFO ___) | |_| | | | | (_| | | | <
22:31:25.756 INFO |____/|____/|_| |_|\__,_|_| |_|\_\
22:31:25.756 INFO Starting 3DMark v2.16.7113 s64
22:31:26.059 INFO initializing Steam service
22:31:26.391 WARN failed to read application settings, reverting to default.
22:31:28.283 WARN failed to read application settings, reverting to default.
22:31:41.077 WARN failed to read application settings, reverting to default.
22:32:39.102 WARN failed to read application settings, reverting to default.
22:32:40.013 INFO starting benchmark PORT_ROYAL_PERFORMANCE
22:32:51.872 INFO Fetching Port Royal key at result creation
22:32:52.149 INFO got Steam authentication ticket
22:32:53.419 INFO Running benchmark, system scan included, and monitoring included
22:33:04.553 INFO Begin workload set Port Royal Demo Performance
22:33:04.560 INFO launch command is "D:\Games\Steam\steamapps\common\3DMark\dlc\port-royal-test\bin\x64\3DMarkPortRoyal.exe" --in "C:\ProgramData\UL\3DMark\tmp\fm-workload-4022753873477886667.json" --out "C:\ProgramData\UL\3DMark\tmp\fm-result-5792993214644422209.json"
22:33:24.428 ERROR workload produced no result
22:33:24.431 INFO End workload set Port Royal Demo Performance
22:33:24.433 INFO Begin workload set Port Royal Graphics Test 1 Performance
22:33:24.436 INFO launch command is "D:\Games\Steam\steamapps\common\3DMark\dlc\port-royal-test\bin\x64\3DMarkPortRoyal.exe" --in "C:\ProgramData\UL\3DMark\tmp\fm-workload-3566720546781203609.json" --out "C:\ProgramData\UL\3DMark\tmp\fm-result-8854478033935148443.json"
22:34:33.432 ERROR workload produced no result
22:34:33.432 INFO End workload set Port Royal Graphics Test 1 Performance
22:34:35.563 INFO Benchmark completed.

[HELLR4ZOR]

You have to think that the drivers are still raw, let some time pass. Something similar happened to me only with the Unigine Superposition. However the 3D Mark works perfect. You will have to wait for optimizations and bug fixes from AMD.

* I use nVIDIA 3070

[myna]

I played around with the options. In Full HD the demo did run once until the large ship enters the hangar and then the driver did hang. I switched off every feature, but no difference.

Actually I wouldn't bother if Port Royal wasn't more or less the only test I have for raytracing. And 3DMark is usually the tool that is optimized as possible from the driver teams. Therefore, I fear I may have some kind of hardware problem.

[myna]

Update: After a lot of testing it is clear that the frequency my card is boosting to is too high. I have to limit it to 2.200MHz for Port Royal demo and 2.100MHz in Control to stabilize it. Funny enough, I can push the card to 8080 points in the benchmark which is quite high, and this is running over and over again without problems.