https://bugs.winehq.org/show_bug.cgi?id=46416
Bug ID: 46416 Summary: World of Warcraft dx12/vkd3d crashes soon after login Product: vkd3d Version: 1.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs@winehq.org Reporter: zurohki@gmail.com Distribution: ---
Created attachment 63183 --> https://bugs.winehq.org/attachment.cgi?id=63183 WINEDEBUG=+seh,+dxgi,+d3d12 VKD3D_DEBUG=trace log
After logging in and reaching the character select screen, World of Warcraft quickly crashes with an Error #132 exception. It doesn't matter whether you sit on that screen or choose a character and start loading in to the game world.
Slackware64-current Ryzen 2700X Vega 64 wine 4.0rc4 + staging from https://github.com/lutris/wine/commits/tkg Kernel 4.20.0 Mesa master, commit 3453814 LLVM 8.0.0svn, r349003 vkd3d master, commit e13fb13
Vanilla Wine doesn't display any output at all, the screen just freezes. I have to alt-tab to the terminal and ctrl-c to kill Wine, so I can't test with it.
https://bugs.winehq.org/show_bug.cgi?id=46416
Emil Lauridsen mine809@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mine809@gmail.com
--- Comment #1 from Emil Lauridsen mine809@gmail.com --- I can replicate the issue when using the mesa vulkan driver (RADV). It does however not occur when using the AMDVLK driver (which I do not recommend due to poor performance).
https://bugs.winehq.org/show_bug.cgi?id=46416
Emil Lauridsen mine809@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mine809@gmail.com
--- Comment #1 from Emil Lauridsen mine809@gmail.com --- I can replicate the issue when using the mesa vulkan driver (RADV). It does however not occur when using the AMDVLK driver (which I do not recommend due to poor performance).
--- Comment #2 from Emil Lauridsen mine809@gmail.com --- Also, the relavant part of the previous poster's trace appears to be around line 3689700:
trace:d3d12_command_queue_GetPrivateData: iface 0x7cf03dc0, guid {000000f0-0000-000d-e0c5-0db88d7f0000}, data_size 0x23f888, data 0x23f850.
fixme:d3d12_command_queue_Wait: iface 0x7cf03dc0, fence 0x7d1da3b0, value 0x6d1 stub!
trace:d3d12_command_queue_ExecuteCommandLists: iface 0x7cf03dc0, command_list_count 2, command_lists 0x17490a70.
trace:vkd3d_queue_acquire: queue 0x7ceedba0.
0040:fixme:dxgi:dxgi_adapter_QueryVideoMemoryInfo iface 0x3886e00, node_index 0, segment_group 0, memory_info 0x1229fd18 partial stub!
trace:d3d12_fence_Signal: iface 0x7d1da3b0, value 0x6d1.
amdgpu: buffer list creation failed for the chained submission(-2)
vk: error: failed to submit CS 0
https://bugs.winehq.org/show_bug.cgi?id=46416
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|World of Warcraft |World of Warcraft |dx12/vkd3d crashes soon |dx12/vkd3d crashes soon |after login |after login (RADV) CC| |joseph.kucia@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #3 from Józef Kucia joseph.kucia@gmail.com --- Created attachment 63246 --> https://bugs.winehq.org/attachment.cgi?id=63246 vkd3d hacks for radv
It's a known vkd3d bug. The attached hack should fix the problem.
This bug seems to be hard to fix in a reasonable way. It happens because WoW keeps descriptors for destroyed resources in descriptors heaps. It appears to be allowed thing to do in D3D12, but it is invalid usage in Vulkan and radv doesn't handle it well.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #4 from Emil Lauridsen mine809@gmail.com --- The provided patch eliminates the issue in my setup.
That seems like a gnarly issue to fix in a consitent way, yeah. Thanks for the work so far though!
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #5 from zurohki@gmail.com --- The patch fixes the crash for me, too. Played for a few hours and everything worked great.
I can see why Battle for Azeroth uses those performance-wrecking ground effects everywhere now. They aren't anywhere near as bad in DX12 and that's what the art team will be designing for.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #6 from zurohki@gmail.com --- I spoke too soon - sometimes I crash either during login or within a minute of getting in to the game, and sometimes the game runs fine for hours with no issues. There doesn't seem to be a middle ground, it either crashes quickly or it doesn't crash.
Just now I got an amdgpu error in the log and a crash almost as soon as Wow.exe loaded, but sometimes that doesn't appear:
fixme:d3d12_command_queue_Wait: iface 0x7d0ae560, fence 0x7d0f54d0, value 0x4 stub! fixme:d3d12_command_queue_Wait: iface 0x7d0ae560, fence 0x7d0f54d0, value 0x5 stub! amdgpu: buffer list creation failed for the chained submission(-2) vk: error: failed to submit CS 0
0x80000101 (unknown exception) at 00007fb6bbe4f6db : error 132: ERROR #132 (0x85100084) Fatal exception!
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #7 from zurohki@gmail.com --- Wait, that last error was with an older version of vkd3d that got installed when I just ran updates. My mistake.
The crash a few minutes after getting in to the game I've seen on and off for a few days. I'll build the latest vkd3d and see how that goes.
https://bugs.winehq.org/show_bug.cgi?id=46416
sleijeri@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sleijeri@gmail.com
--- Comment #8 from sleijeri@gmail.com --- Confirming same error 132 with dx12. Got generally were only missing --with-vkd3d --with-vulkan config-flag from aur build so could not get it running earlier.
Using latest vkd3d-git with patch and latest of mesa vulkan etc.. Hardware running with RX480 4GB Sapphire nitro+
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #9 from sleijeri@gmail.com --- (In reply to sleijeri from comment #8)
Confirming same error 132 with dx12. Got generally were only missing --with-vkd3d --with-vulkan config-flag from aur build so could not get it running earlier.
Using latest vkd3d-git with patch and latest of mesa vulkan etc.. Hardware running with RX480 4GB Sapphire nitro+
Have also heard by some other users with nvidia + native windows are experiencing Error 132 and getting crash (were using gtx1070 and 2080). So propably there might be issues within wow itself too on dx12 implementation atm.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #10 from zurohki@gmail.com --- (In reply to sleijeri from comment #9)
Have also heard by some other users with nvidia + native windows are experiencing Error 132 and getting crash (were using gtx1070 and 2080). So propably there might be issues within wow itself too on dx12 implementation atm.
I'm sure there are, but it's probably not the same issue.
The frustrating thing is that DirectX 12 mode performs noticeably better than DirectX 11, and it often runs fine for hours. So I'm tempted to use it, but I can't trust it to not crash in the middle of a raid.
Built new kernel, LLVM, mesa, vkd3d+patch and wine-staging. Didn't help. Log in, walk around for a bit and bam:
ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception! The instruction at "0x00007f19b8134141" referenced memory at "0x00007f182c08c010". The memory could not be "read".
https://bugs.winehq.org/show_bug.cgi?id=46416
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #11 from Sveinar Søpler cybermax@dexter.no --- (In reply to zurohki from comment #10)
ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception! The instruction at "0x00007f19b8134141" referenced memory at "0x00007f182c08c010". The memory could not be "read".
This happens randomly with current git and nVidia still. I have not found any consistent way to reproduce this, as sometimes i can play 3-4 hours without issues (did yesterday), but today i crashed twice in 2 hours. (And i changed NOTHING in the meantime).
Doing a tracelog that may risk going for hours is out of the question as this would fill GB's of data + slow the game down considerably when logging.
Hopefully some effect at a certain spot can reproduce this so a useful log can be obtained :) --- This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe ProcessID: 251 Exception: ACCESS_VIOLATION
The instruction at "0x0000000141546b0c" referenced memory at "0x0000000800000038". The memory could not be "read". ---
https://bugs.winehq.org/show_bug.cgi?id=46416
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #12 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Sveinar Søpler from comment #11)
Doing a tracelog that may risk going for hours is out of the question as this would fill GB's of data + slow the game down considerably when logging.
It is also possible that a trace log is not required. It might be enough to try to get the output with VKD3D_DEBUG=err or VKD3D_DEBUG=fixme.
https://bugs.winehq.org/show_bug.cgi?id=46416
themainliner themainliner@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |themainliner@hotmail.com
--- Comment #13 from themainliner themainliner@hotmail.com --- This "looks" much like the behaviour I have encountered. My issue is the the bug title "dx12/vkd3d (RADV)".
Since Wed., patch 8.1.5, I've been unable to play as the game client crashes, "locks up", just after logging in. However, I am using wine-staging 4.13. I have tried with and without DXVK and the results are identical.
THe game client appears to be crashing with wine-staging, which will probably make troubleshooting errors with vkd3d\DXVK more difficult. I also have an nVidia GTX 1050Ti...
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #14 from Sveinar Søpler cybermax@dexter.no --- There is a updated commit for DXVK : https://github.com/doitsujin/dxvk/commit/2d39be4e72aca562f73aa771c27333fd70d... for WoW 8.1.5
Tested latest vkd3d (GIT), and did not experience any lockups yesterday, but did not really have time to test over time. Will probably do some playing tonight.
This is with nVidia binary driver.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #15 from Sveinar Søpler cybermax@dexter.no --- (In reply to Sveinar Søpler from comment #14)
Tested latest vkd3d (GIT), and did not experience any lockups yesterday, but did not really have time to test over time. Will probably do some playing tonight.
This is with nVidia binary driver.
Just played a couple of hours with vkd3d and d3d12 with no issues so far.
Mind you that the graphics settings reset with 8.1.5, so if you have any custom settings other than "recommended" you need to check that.
@Themainliner
I would recommend just to try, to clear out /World of Warcraft/_retail_/Cache folder, aswell as $HOME/.nv/ folder so that no old shader crud is causing a compile error perhaps.
I am using 418.43 driver with nVidia GTX 970.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #16 from themainliner themainliner@hotmail.com --- @Sveinar Søpler I followed your advice...I also upgraded wine-stanging to 4.3 on my Xubuntu 18:04 install..attempting to launch wine with DXVK grinds Xubuntu to a halt, I had to Alt-F1 out to the command line and kill the wine processes...
Launching WoW sans DXK delivered a crash:
"000b:fixme:winediag:start_process Wine Staging 4.3 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 002a:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm 002b:fixme:kernelbase:AppPolicyGetThreadInitializationType 0xfffffffffffffffa, 0x379fdc0 002a:fixme:mpr:WNetGetUniversalNameW (L"Z:\media\Games\World of Warcraft\Data\data", 0x00000001, 0x22c844, 0x22c840): stub 002f:fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform 002f:fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported 002a:fixme:ntdll:EtwEventRegister ({5d8087dd-3a9b-4f56-90df-49196cdc4f11}, 0x180011f80, 0x1801b7940, 0x1801b7940) stub. 002a:fixme:ntdll:EtwEventRegister ({8819ca17-7faa-4184-afb7-a4120ca793cd}, 0x1800eb7e0, 0x1801b9fd0, 0x1801b9fd0) stub. ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception! The instruction at "0x000000018000396a" referenced memory at "0x0000000000000000". The memory could not be "read".
002a:fixme:dbghelp:elf_search_auxv can't find symbol in module ... 002a:fixme:dbghelp:elf_search_auxv can't find symbol in module 003b:fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x32efe4 003b:fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x32efe4 003b:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3 003b:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3 003b:fixme:ver:GetCurrentPackageId (0x32fe14 (nil)): stub
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #17 from Sveinar Søpler cybermax@dexter.no --- @themainliner You did not write that you actually upgraded dxvk to current release 1.0.1 that should have a fix for WoW 8.1.5.
--
Bug fixes and Improvements
Fixed memory allocation failures on Intel Bay Trail (#947) Fixed regression that broke DXGI gamma control (#937) Devil May Cry 5: Enabled d3d11.relaxedBarriers option by default to improve performance Star Wars Battlefront (2015): Report Nvidia GPUs correctly to fix driver version error (#968) Resident Evil 2 and Devil May Cry 5: Work around dark rendering issue on Nvidia GPUs (#956) World of Warcraft: Fixed GPU hangs on Nvidia GPUs since game patch 8.1.5 (#964) -- Just tested with DXVK 1.0.1 now, and had no problems.
If you do not have vkd3d installed/compiled, WoW MIGHT actually try to start up in D3D12 mode unless you either launch it via script and -d3d11 option, or set this option in the battle.net launcher. (8.1.5 resets graphics options to default, and since 8.1 D3D12 is default chosen).
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #18 from themainliner themainliner@hotmail.com --- @Sveinar Søpler I upgraded to DXVK 1.0.1 and WoW runs, and clips, halts momentarily and continues, every second...but it works and doesn't crash. There is a new option in System | Advanced DirectX11 Legacy...not sure what this.
I'm concerned that with DXVK wine-staging cannot launch WoW at all...
https://bugs.winehq.org/show_bug.cgi?id=46416
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #19 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- --- Wow --- This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe ProcessID: 44 Exception: ACCESS_VIOLATION
The instruction at "0x000000018000396a" referenced memory at "0x0000000000000000". The memory could not be "read".
Press OK to terminate the application. --- OK ---
I got this with wine-staging 4.3, before and after update to WoW 8.1.5 (64 bit). I don't even use directx12/vkd3d (not available in Debian 8 jessie), and I have a NVidia GTX 970. This is probably a bug of its own.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #20 from themainliner themainliner@hotmail.com --- Comment 18 should read:
"I'm concerned that *without* DXVK wine-staging cannot launch WoW at all...
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #21 from Sveinar Søpler cybermax@dexter.no --- Perhaps something else is at play here. Atm i use wine-staging-git from yesterday, and i do not experience these problems you describe.
I have tested both with vkd3d/d3d12 and dxvk/d3d11.
The "d3d11 Legacy" is supposed to be "the old engine" or something like that, so you COULD give that a try. Ie. it is d3d11 without multithreading++. Like "legacy" for older cards or something like that.
I did not test d3d11 legacy, so i dunno how that works, and i did not test wined3d/d3d11, but dxvk and vkd3d.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #22 from Sveinar Søpler cybermax@dexter.no --- (In reply to themainliner from comment #20)
Comment 18 should read:
"I'm concerned that *without* DXVK wine-staging cannot launch WoW at all...
I tested WoW with wined3d and d3d11. I used latest wine-staging GIT 65e6bb8111acfc6d7fb08f209bb01348150c14d4 from today, and i would say that you need to use D3D11-Legacy mode in WoW.
I got in with the "new" d3d11, but it was less than a slideshow tbh. Dunno if i would eventually crash if i had hung around long enough? With d3d11-legacy, it was more or less as expected. 20'ish fps in Boralus vs. 80 with d3d12 and 100'ish with DXVK (and the "new" d3d11).
Wine-staging-4.3 crashed with the error you stated bove when i tried D3D11, but worked with D3D12 AND recent dxvk 1.0.1.
So, to reiterate: D3D12 -> Works with wine-staging-4.3+ and recent vkd3d D3D11 -> Works with wine-staging-4.3+ if you use DXVK 1.0.1 D3D11 -> Does NOT work with wined3d AT ALL (Unplayable or crashing). D3D11-Legacy -> Works with wine-staging-git 65e6bb8111acfc6d7fb08f209bb01348150c14d4 D3D11-Legacy -> Does NOT work with wine-staging-4.3 (Crash upon login).
https://bugs.winehq.org/show_bug.cgi?id=46416
Berillions berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |berillions@gmail.com
--- Comment #23 from Berillions berillions@gmail.com --- (In reply to Sveinar Søpler from comment #22)
(In reply to themainliner from comment #20)
Comment 18 should read:
"I'm concerned that *without* DXVK wine-staging cannot launch WoW at all...
I tested WoW with wined3d and d3d11. I used latest wine-staging GIT 65e6bb8111acfc6d7fb08f209bb01348150c14d4 from today, and i would say that you need to use D3D11-Legacy mode in WoW.
I got in with the "new" d3d11, but it was less than a slideshow tbh. Dunno if i would eventually crash if i had hung around long enough? With d3d11-legacy, it was more or less as expected. 20'ish fps in Boralus vs. 80 with d3d12 and 100'ish with DXVK (and the "new" d3d11).
Wine-staging-4.3 crashed with the error you stated bove when i tried D3D11, but worked with D3D12 AND recent dxvk 1.0.1.
So, to reiterate: D3D12 -> Works with wine-staging-4.3+ and recent vkd3d D3D11 -> Works with wine-staging-4.3+ if you use DXVK 1.0.1 D3D11 -> Does NOT work with wined3d AT ALL (Unplayable or crashing). D3D11-Legacy -> Works with wine-staging-git 65e6bb8111acfc6d7fb08f209bb01348150c14d4 D3D11-Legacy -> Does NOT work with wine-staging-4.3 (Crash upon login).
@Sveinar Søpler : I have a different issue with WoW and VKD3D. The login works correctly but i choose a character who is in BFA region like Zul'Dazar, WoW crashes with Error 132. But if i choose a character who is in old region like Orgrimmar/Kalimdor, the game works without issue.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #24 from Sveinar Søpler cybermax@dexter.no --- (In reply to Berillions from comment #23)
@Sveinar Søpler : I have a different issue with WoW and VKD3D. The login works correctly but i choose a character who is in BFA region like Zul'Dazar, WoW crashes with Error 132. But if i choose a character who is in old region like Orgrimmar/Kalimdor, the game works without issue.
This bug kind of reports problems with vkd3d and RADV, and I cant say anything about the state of that really.
If you use nVidia (w/recent driver), i might give you some pointers if you post a wee bit more details about vkd3d versions, wine version++ (Obs: wine-staging-4.9 does NOT work out of the box atm with WoW).
https://bugs.winehq.org/show_bug.cgi?id=46416
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=46416
Yonseca yonseca@posteo.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yonseca@posteo.net
https://bugs.winehq.org/show_bug.cgi?id=46416
jokeyrhyme@jokeyrhy.me changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jokeyrhyme@jokeyrhy.me
https://bugs.winehq.org/show_bug.cgi?id=46416
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #25 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with the latest plain wine. Currently, it is wine-7.0-rc2. And be sure to test in a fresh wineprefix.
https://bugs.winehq.org/show_bug.cgi?id=46416
Márton Szász szaszm01@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |szaszm01@gmail.com
--- Comment #26 from Márton Szász szaszm01@gmail.com --- Created attachment 73258 --> https://bugs.winehq.org/attachment.cgi?id=73258 vkd3d hacks for radv updated to vkd3d 1.4
I've encountered this bug with wine-staging 7.17-1. Wow version is WotLK classic.
Updated the hacks of Jozef to apply to vkd3d 1.4. I'm not familiar with the codebase, so I might have messed up something, but a quick 15 minute test shows no crashes so far. It used to crash within 5 minutes.
https://bugs.winehq.org/show_bug.cgi?id=46416
--- Comment #27 from Márton Szász szaszm01@gmail.com --- (In reply to Márton Szász from comment #26)
Created attachment 73258 [details] vkd3d hacks for radv updated to vkd3d 1.4
I've encountered this bug with wine-staging 7.17-1. Wow version is WotLK classic.
Updated the hacks of Jozef to apply to vkd3d 1.4. I'm not familiar with the codebase, so I might have messed up something, but a quick 15 minute test shows no crashes so far. It used to crash within 5 minutes.
update: longer testing revealed issues, just over a longer timeframe: crashing about every 30m-1h. I'm assuming there are a few other places that would need to be patched in the new version, but I don't understand the code enough to do that.
https://bugs.winehq.org/show_bug.cgi?id=46416
Neko-san nekoNexus@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus@protonmail.ch
-
wine-bugs＠winehq.org -
WineHQ Bugzilla