search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.15k stars 1.06k forks source link

Forza Motorsport (2440510) #7151

Open robotman40 opened 1 year ago

robotman40 commented 1 year ago

Compatibility Report

System Information

I confirm:

[ ] that I haven't found an existing compatibility report for this game. [ ] that I have checked whether there are updates for my system available.

Symptoms

Game crashes on launch, supposedly due to this in the Proton log

19625.840:00e8:01b0:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
19625.859:0030:01b4:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
19625.859:0030:01b8:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
19625.859:0030:01bc:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
19625.860:0030:01c0:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
19625.860:0030:01c4:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 69674 != 69673, skipping destruction (fork without exec?)

I've noticed many warnings related to NtSetInformationThread throughout the log and a couple fixme errors like 19619.029:0064:0070:fixme:hid:handle_IRP_MN_QUERY_ID and 19619.971:0110:0114:fixme:uiautomation:msaa_provider_GetPropertyValue.

Here is the full Proton log

https://drive.google.com/file/d/1UWI7cHhhP9cLCMnP7rqm1btflvKbjRh_/view?usp=sharing

Reproduction

Launch the game and observe it show the splash screen and then crash

nyannyankas commented 1 year ago

The same issue seems to occur on Steam Deck. Edit: Also happens on my Desktop using an nvidia card.

Here's my Proton log: steam-2440510.log

AhmetTumis commented 1 year ago

Seems as if there is something wrong with a specific DLL file provided by the game. Gotta check it out in my spare time

der-eismann commented 1 year ago

Don't think it'll add something new, but crashes for me as well.

System Information

steam-2440510-proton-experimental.log steam-2440510-proton-8.log

robotman40 commented 1 year ago

Seems as if there is something wrong with a specific DLL file provided by the game. Gotta check it out in my spare time

Could you tell us more on what makes you suspect that and what specific DLL?

LeonardoWL037 commented 1 year ago

This error happens on Windows too. It Happens because of when you first launch the game, it tries to install xbox gaming services(exclusive to windows from what i know) through an .exe on game folder; gamingrepair.exe, located on Forza Motorsport\gamingservices\gamingrepair. I think we would not be able to play on proton, unless Turn 10 removes this requirement and do just like Playground games does on Forza Horizon 4 and 5.

Some links: https://steamcommunity.com/app/2440510/discussions/0/3881597531957253090/

and

https://support.xbox.com/en-US/help/games-apps/troubleshooting/gaming-services-repair-tool

robotman40 commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/7151#issuecomment-1749580185

When I get home, I'll see if I can somehow force it to run and install

For now, best bet is to let your voice be heard and let the Turn 10 developers know of this issue on the Steam discussion in the quote.

anliec commented 1 year ago

This thread was created by turn 10 (notice the T10 in the username), it's under their radar, but that don't mean they will solve it for us

robotman40 commented 1 year ago

I ran gamingrepair.exe via Proton and I got this log:

https://drive.google.com/file/d/1SPPtF_U7F64Vsh478rwwc2tSdU_gdgUG/view?usp=sharing

I think this will narrow down the problem since we already knew that gamingrepair.exe was the culprit. Now we just need to see what's going on in gamingrepair.exe. These are likely lines of interest.

171.970:0130:0134:err:module:import_dll Library drvstore.dll (which is needed by L"Z:\\home\\user\\Drive2\\SteamLibrary\\steamapps\\common\\Forza Motorsport\\gamingservices\\gamingrepair\\gamingrepair.exe") not found
171.972:0130:0134:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\setupapi.dll" at 000000036D860000: builtin
171.972:0130:0134:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\newdev.dll" at 0000000202880000: builtin
171.972:0130:0134:err:module:LdrInitializeThunk Importing dlls for L"Z:\\home\\user\\Drive2\\SteamLibrary\\steamapps\\common\\Forza Motorsport\\gamingservices\\gamingrepair\\gamingrepair.exe" failed, status c0000135
logos128 commented 1 year ago

The game seems to need WINEDLLOVERRIDES="amd_ags_x64=b", since it loads the native version of that dll. Try the following command prompt: WINEDLLOVERRIDES="amd_ags_x64=b" %command% At least that should help go further and hopefully reach the graphical screen.

der-eismann commented 1 year ago

Try the following command prompt: WINEDLLOVERRIDES="amd_ags_x64=b" %command%

Unfortunately this didn't help in my case, I guess this gamingrepair.exe issue needs solving first.

logos128 commented 1 year ago

Unfortunately this didn't help in my case, I guess this gamingrepair.exe issue needs solving first.

Thanks. Can you post a new log with WINEDLLOVERRIDES included. The initial logs don't seem to show anything related to gaming services. PROTON_LOG=1 WINEDLLOVERRIDES="amd_ags_x64=b" %command%

robotman40 commented 1 year ago

Unfortunately this didn't help in my case, I guess this gamingrepair.exe issue needs solving first.

Thanks. Can you post a new log with WINEDLLOVERRIDES included. The initial logs don't seem to show anything related to gaming services. PROTON_LOG=1 WINEDLLOVERRIDES="amd_ags_x64=b" %command%

To note, I did notice some of the warnings/errors/fixmes being shared between both Forza Motorsport and gamingrepair.exe

mohamadaljaf commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/7151#issuecomment-1749761401

I added a stub drvstore dll and it got to the next step, but as expected it failed to fix anything:

0174:fixme:combase:RoGetActivationFactory (L"Windows.ApplicationModel.Store.Preview.InstallControl.AppInstallManager", {00000035-0000-0000-c000-000000000046}, 0000000000C8FCA8): semi-stub
0174:err:combase:RoGetActivationFactory Failed to find library for L"Windows.ApplicationModel.Store.Preview.InstallControl.AppInstallManager"
0150:fixme:eventlog:ControlTraceW (0, L"GamingRepair_979701AE", 00000000006B9E70, 3) stub
0150:fixme:eventlog:ControlTraceW (0, L"GamingRepair_979701AE", 00000000006B9E70, 1) stub
0150:err:module:DelayLoadFailureHook failed to delay load ext-ms-win-wer-reporting-l1-1-0.dll.WerReportCreate
wine: Call from 0000000174013C17 to unimplemented function ext-ms-win-wer-reporting-l1-1-0.dll.WerReportCreate, aborting
wine: Unimplemented function ext-ms-win-wer-reporting-l1-1-0.dll.WerReportCreate called at address 0000000174013C17 (thread 0150), starting debugger...

It looks like it needs Windows.ApplicationModel.Store.Preview.InstallControl.AppInstallManager. The native drvstore wasn't any different.

LeonardoWL037 commented 1 year ago

Yeah, did this just now too, came to say the same thing, as expected, gamingrepair is trying to open microsoft store and download xbox game services, just as xbox app on windows do. I think we are done, unless they really remove this thing. Hope they do because of a lot of people on windows is having the same problem too

robotman40 commented 1 year ago

Well, it was worth a try.

Until Turn 10/Microsoft accommodates for Proton players (or for everyone's best, removes this requirement all togehter), just play another racing game like Assetto Corsa (which requires some tweaking and is a bit buggy, but looks better [with mods] and has modding).

With that said, should we close this issue since there's nothing we can really do on our end? Our best bet is to try to let Turn 10/Microsoft hear our voices.

Also, I think the Steam Deck verification should (obviously) be marked as "unsupported," but with a unique reason detailing about gaming services not available on Steam Deck/Proton.

SPL0T commented 1 year ago

Game doesn't crash for me anymore but doesn't go further than it did while still crashing so I let it run for about 10min to see if it would start. It didn't.

System Information

GPU: AMD RX 6900 XT Video driver version: Mesa-git 23.3.0_devel.178631.0c10cbff558.d41d8cd-1 Kernel version: 6.5.5 Link to full system information report as Gist: https://gist.github.com/SPL0T/e3ab0d76b9297e1168a0f8db75295896 Proton version: Experimental [bleeding-edge]

https://drive.google.com/file/d/1LVoFVHSBJq5lRmcu065G6vPkOmjES0Cy/view?usp=drive_link

robotman40 commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/7151#issuecomment-1751642504

As previously stated, the game needs to open the Microsoft Store and download some Xbox services, which is, unfortunately, impossible under Proton since we don't have any sort of access to Microsoft Store APIs.

logos128 commented 1 year ago

I've just installed successfully the gamingrepairtool.exe on a Windows 10 LTSC (21H2) VM. This is an enterprise edition without the Microsoft Store and a few other components, which makes it closer to a wineprefix. The tool installed Gaming Services, Microsoft GameInput and Microsoft Edge WebView2 Runtime. The Gaming Services settings screen functioned properly as well. Also the tool didn't install Microsoft Store during the update.

I don't have the game, so can't test if it works. But if it doesn't require Microsoft Store, then running on Wine seems more possible. It'll likely require a lot of development work, though.

Anyway, let's hope Turn 10 will rethink this and use the Steam Cloud to store the online profiles, since that's the right way to do on Steam (as Playground Games did).

robotman40 commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/7151#issuecomment-1751762086

If you do happen to get the game, could you copy over the installed files over into the game's Wine prefix and see what happens?

logos128 commented 12 months ago

If you do happen to get the game, could you copy over the installed files over into the game's Wine prefix and see what happens?

They are not simple dlls. There are assemblies and other executables, that need to be properly registered with the system. The Gaming Services looks like a UWP app. It also seems to require Win 10 version 19041 (21H2), as it failed to install on Win 10 LTSC (2019).

The good news is that the needed components are installed directly by this tool, outside of the Microsoft Store. I'll get the game, when the things start moving here, and will try to contribute of course.

eVen-gits commented 12 months ago

Trying today on launch day. Seems to get to the splash screen, but no further. image

Using Proton Experimental, I get the splash screen, using GE-Proton, I crash after splash. Using EndeavourOS (arch) with kernel 6.5.6.zen2-1

I'll repurchase once it's at least known to be runnable. Looking forward to it.

System info: ``` Computer Information: Manufacturer: ASUSTeK COMPUTER INC. Model: TUF GAMING X570-PLUS (WI-FI) Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD Ryzen 7 3700X 8-Core Processor CPU Family: 0x17 CPU Model: 0x71 CPU Stepping: 0x0 CPU Type: 0x0 Speed: 4050 MHz 16 logical processors 8 physical processors Hyper-threading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Supported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Supported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: "EndeavourOS Linux" (64 bit) Kernel Name: Linux Kernel Version: 6.5.6-arch2-1 X Server Vendor: The X.Org Foundation X Server Release: 12101008 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20230919.60656 Video Card: Driver: AMD AMD Radeon RX 5700 XT (navi10, LLVM 16.0.6, DRM 3.54, 6.5.6-arch2-1) Driver Version: 4.6 (Compatibility Profile) Mesa 23.2.1-arch1.2 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 164 Hz VendorID: 0x1002 DeviceID: 0x731f Revision Not Detected Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 2560 x 1440 Desktop Resolution: 5120 x 1440 Primary Display Size: 23.50" x 13.23" (26.97" diag), 59.7cm x 33.6cm (68.5cm diag) Primary VRAM: 8192 MB Sound card: Audio device: ATI R6xx HDMI Memory: RAM: 32002 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 466924 MB Largest Free Hard Disk Block: 106624 MB Storage: Number of SSDs: 4 SSD sizes: 1000G,500G,500G,256G Number of HDDs: 0 Number of removable drives: 0 ```
fastoslinux commented 12 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7151#issuecomment-1755431757

the same with FH5 in today's update

nebadon2025 commented 12 months ago

Replying to #7151 (comment)

the same with FH5 in today's update

I can confirm that Forza Horizon 5 no longer runs in Linux or Steam Deck same as above just a splash screen and immediate exit back to steam.

Mario-119 commented 12 months ago

Might be old news to some here, but it seems like Valve is aware and is looking to push a fix eventually for Forza Motorsport (and FH5 as well I imagine)

robotman40 commented 12 months ago

Now, until Microsoft either brings them over to Linux or accommodates for us, I'll be playing Assetto Corsa (which I highly recommend due to the modding and it looks better than Forza games with CSP as well)

1basti1 commented 11 months ago

I've heard (or more like read in the steam forums) with proton experimental bleeding edge Forza horizon 5 works again. Anyone tried that? maybe Forza motorsport will work too now..?

Edit: Ok, just tested Forza Horizon 5 myself. Works again with Proton Experimental Bleeding Edge!

LeonardoWL037 commented 11 months ago

Just tested both, FH5 and FM FH5: Really works again FM: Hangs on splash screen now, just like those with problems on windows. Seems to have something to do with admnistrator rights, cant remember correctly

robotman40 commented 11 months ago

Just tested both, FH5 and FM FH5: Really works again FM: Hangs on splash screen now, just like those with problems on windows. Seems to have something to do with admnistrator rights, cant remember correctly

Could you give us a Proton log for Forza Motorsport?

LeonardoWL037 commented 11 months ago

Sure, here it is:

Log: https://drive.google.com/file/d/1W-Xp1z2H28RwlI_AFl3aPFavF0il48aH/view?usp=drive_link

Had to force close it.

robotman40 commented 11 months ago

Sure, here it is:

Log: https://drive.google.com/file/d/1W-Xp1z2H28RwlI_AFl3aPFavF0il48aH/view?usp=drive_link

Had to force close it.

Also, is there a way to confirm if the game isn't attempting to install gamingservices?

LeonardoWL037 commented 11 months ago

I dont think it is trying anymore. I am testing on steam deck. Before, i launched the game, it appeared to me in the bottom of screen, "executing steps of instalattion ("\gamingservices.exe") the splash screen appeared over it and then closed.

Now it passes from the installing proccess, just hangs on the splash alone

SLI0095 commented 11 months ago

I tried launching using Proton Experimental and can confirm that it hangs on the splash screen without crashing. When launching the game on Windows 11, I get this warning every time (using RX 7900 XTX). It needs to be closed or I have to click "Ignore Warning" to boot into the game. Is it possible that it hangs due to this warning that is somehow not visible when launching through Proton?

Screenshot 2023-10-14 100333

LeonardoWL037 commented 11 months ago

I will try on desktop mode, I have windows on my steam deck too, it really gives me this error

LeonardoWL037 commented 11 months ago

It really just hangs, no error.

kadardar commented 11 months ago

I don't own Forze Motorsport. But i do have FH5 and it works on proton hotfix. Forza Motorsport maybe works aswell. Can someone give it a try and report the outcome?

Iam looking to buy this game, but protondb and this github issue holds me back.

kadardar commented 11 months ago

Got impatient and decided if it didn't work i will just play on Windows.

Proton Hotfix also hangs on splash screen. Whatever makes FH5 work with hotfix doesn't do so for FM.

fastoslinux commented 11 months ago

TKG-proton-experimental.bleeding.edge.8.0.59260.20231013 worked for FH5 successfully, can you confirm if it works for Motorsport? (I used ProtonUp-qt to install TKG..)

LeonardoWL037 commented 11 months ago

TKG-proton-experimental.bleeding.edge.8.0.59260.20231013 worked for FH5 successfully, can you confirm if it works for Motorsport? (I used ProtonUp-qt to install TKG..)

Tested with Ge 8-18 and TKG TKG-proton-experimental.bleeding.edge.8.0.59260.20231013

GE : Same as experimental, loop on splash screen, let for 3 hours, had to force stop TKG: Crashes instantly and returns to Steam library

LeonardoWL037 commented 11 months ago

Just tested the new update with GE, Experimental Bleeding edge and TKG, still the same as before

Mario-119 commented 11 months ago

Any updates on this out of curiosity?

robotman40 commented 11 months ago

Any updates on this out of curiosity?

Not from what I've heard.

It seems to be an issue that, unfortunately, Microsoft would only be able to fix, since this game requires a service that cannot be installed or run through WINE.

anliec commented 11 months ago

In addition to that there seems to have some memory allocation issue, they are using undocumented flag in VirtualAlloc

robotman40 commented 11 months ago

In addition to that there seems to have some memory allocation issue, they are using undocumented flag in VirtualAlloc

Could you give us a log and give us an excerpt showing us the unimplemented flag?

anliec commented 11 months ago

The game call VirtualAlloc with flags 0x00002000 (MEM_RESERVE), 0x20000000 (MEM_LARGE_PAGES) and 0x00400000 (MEM_PHYSICAL). Ignoring the two last flags let the call succeed, but encounter a memory error later down the line. I'm not into memory allocation enough to understand what is needed here...

robotman40 commented 9 months ago

Is there any news on whether the apparent memory allocation bug has been fixed?

Sure, this game is a dumpster fire, but it wouldn't hurt to solve a bug like this since it may as well have the domino effect of fixing other games.

Could we also consider the possibility that while the game does install Gaming Services on first run, it might not be actually working?

robotman40 commented 9 months ago

UPDATE: The undocumented flags seem to actually be documented. Perhaps we can work on implementing those?

https://learn.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-virtualalloc#parameters

lilmike commented 9 months ago

Has anyone gotten motorsport working?

-Michael.

LeonardoWL037 commented 9 months ago

I still have not managed to get it working, but i found it after anliec said. Still didnt test as it will "manipulate" the game and can result on ban or something.

https://gist.github.com/Allavaz/23bb92ec4a69fa74f01088cb846b3029

robotman40 commented 9 months ago

I still have not managed to get it working, but i found it after anliec said. Still didnt test as it will "manipulate" the game and can result on ban or something.

https://gist.github.com/Allavaz/23bb92ec4a69fa74f01088cb846b3029

In that case, could we just use what the vague documentation tells us to create the flags and hope they work? Also, I'm not sure if the game would even detect the debugger at this point if it can't even get past the splash screen.

NTMan commented 9 months ago

After launching the game I see only splash screen and hear howl of CPU fan which did not disappear until I stop the game. Screenshot from 2024-01-02 02-21-22

Nothing happened within half an hour.

Proton logs: steam-2440510.zip steam-2440510-with-WINEDLLOVERRIDES="amd_ags_x64=b".zip

In proton log I see cycling messages:

12233.494:012c:0130:warn:seh:dispatch_exception backtrace: --- Exception 0xc000001d.
12233.494:012c:0130:trace:seh:dispatch_exception code=c000001d flags=0 addr=00000001414B2614 ip=1414b2614
12233.494:012c:0130:warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised
12233.494:012c:0130:trace:seh:dispatch_exception  rax=0000000002990001 rbx=000000000011e840 rcx=0000000002f97b89 rdx=0000000000000354
12233.494:012c:0130:trace:seh:dispatch_exception  rsi=0000000002356880 rdi=00000000023508f0 rbp=000000000011e0e9 rsp=000000000011e038
12233.494:012c:0130:trace:seh:dispatch_exception   r8=0000000000000012  r9=000000000011e0d8 r10=000000000011e840 r11=000000000011e090
12233.494:012c:0130:trace:seh:dispatch_exception  r12=0000000000000000 r13=00000000023508f8 r14=0000000000000000 r15=ffffffffffffffff
12233.494:012c:0130:trace:seh:call_vectored_handlers calling handler at 000000014144637C code=c000001d flags=0
12233.494:012c:0130:trace:seh:sigsys_handler SIGSYS, rax 0x73, rip 0x1415afad1.
12233.494:012c:0130:trace:seh:call_vectored_handlers handler at 000000014144637C returned ffffffff
12233.494:012c:0130:warn:seh:dispatch_exception backtrace: --- Exception 0xc000001d.
12233.494:012c:0130:trace:seh:dispatch_exception code=c000001d flags=0 addr=00000001414B26B7 ip=1414b26b7
12233.494:012c:0130:warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised
12233.494:012c:0130:trace:seh:dispatch_exception  rax=0000000000000001 rbx=000000000011e840 rcx=0000000000000000 rdx=000000017006e6f0
12233.494:012c:0130:trace:seh:dispatch_exception  rsi=0000000002356880 rdi=00000000023508f0 rbp=000000000011e0e9 rsp=000000000011e038
12233.494:012c:0130:trace:seh:dispatch_exception   r8=0000000000000092  r9=000000017006d940 r10=00000000036f9955 r11=0000000000000000
12233.494:012c:0130:trace:seh:dispatch_exception  r12=0000000000000000 r13=00000000023508f8 r14=0000000000000000 r15=ffffffffffffffff
12233.494:012c:0130:trace:seh:call_vectored_handlers calling handler at 000000014144637C code=c000001d flags=0
12233.494:012c:0130:trace:seh:call_vectored_handlers handler at 000000014144637C returned ffffffff
12233.494:012c:0130:warn:seh:dispatch_exception backtrace: --- Exception 0xc000001d.
12233.494:012c:0130:trace:seh:dispatch_exception code=c000001d flags=0 addr=00000001414B2428 ip=1414b2428
12233.494:012c:0130:warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised
12233.494:012c:0130:trace:seh:dispatch_exception  rax=0000000002990001 rbx=000000000011e840 rcx=0000000002f9831f rdx=0000000000002d90
12233.494:012c:0130:trace:seh:dispatch_exception  rsi=0000000002356880 rdi=00000000023508f0 rbp=000000000011e0e9 rsp=000000000011e038
12233.494:012c:0130:trace:seh:dispatch_exception   r8=0000000000000018  r9=000000000011e0e0 r10=000000000011e840 r11=000000000011e098
12233.494:012c:0130:trace:seh:dispatch_exception  r12=0000000000000000 r13=00000000023508f8 r14=0000000000000000 r15=ffffffffffffffff
12233.494:012c:0130:trace:seh:call_vectored_handlers calling handler at 000000014144637C code=c000001d flags=0
12233.494:012c:0130:trace:seh:sigsys_handler SIGSYS, rax 0x73, rip 0x1415afad1.
12233.494:012c:0130:trace:seh:call_vectored_handlers handler at 000000014144637C returned ffffffff
12233.494:012c:0130:warn:seh:dispatch_exception backtrace: --- Exception 0xc000001d.
12233.494:012c:0130:trace:seh:dispatch_exception code=c000001d flags=0 addr=00000001414B24CB ip=1414b24cb
12233.494:012c:0130:warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised
12233.494:012c:0130:trace:seh:dispatch_exception  rax=0000000000000001 rbx=000000000011e840 rcx=0000000000000000 rdx=000000017006dd60
12233.494:012c:0130:trace:seh:dispatch_exception  rsi=0000000002356880 rdi=00000000023508f0 rbp=000000000011e0e9 rsp=000000000011e038
12233.494:012c:0130:trace:seh:dispatch_exception   r8=000000000000002c  r9=000000017006d940 r10=00000000036fc711 r11=0000000000000000
12233.494:012c:0130:trace:seh:dispatch_exception  r12=0000000000000000 r13=00000000023508f8 r14=0000000000000000 r15=ffffffffffffffff
12233.494:012c:0130:trace:seh:call_vectored_handlers calling handler at 000000014144637C code=c000001d flags=0
12233.494:012c:0130:trace:seh:call_vectored_handlers handler at 000000014144637C returned ffffffff

Adding parameter WINEDLLOVERRIDES="amd_ags_x64=b" nothing change.

Link to full system information report as gist