[Bug 47731] World of Warcraft BFA Crash with error 132 Memory could not be read.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47731

--- Comment #31 from Lunia <LittleLunia94 at Gmail.com> ---
(In reply to Sveinar Søpler from comment #30)
> (In reply to Lunia from comment #29)
> > Currently have this happen constantly on lutris-5.7.5 with DXVK 1.7.
> > 
> > It mostly happens when I take any portal, it will crash on the loading
> > screen and from there on the game will constantly crash more and more often
> > until I delete the GLCache and WoW Cache folders.
> > 
> > From there on it'll be fine again for a while until the next crash occurs
> > and it snowballs into more and more crashes again and I have to delete the
> > folders again.
> 
> What driver are you using?
> 
> The 450.56.02 driver from https://developer.nvidia.com/vulkan-driver seems
> to be working quite well with vkd3d-proton and d3d12 atleast.
> 
> Depending on distro, it can be a slightly scary business to upgrade the
> driver using the nVidia .run version vs. distro package. In the case of
> deb/ubuntu the "official" repo is horribly far behind on the releases me
> thinks.

I'm using 450.57 right now. DX12 with VKD3D works perfectly fine with no error
132 except sometimes when closing the game, however DX12 VKD3D performance is
quite a lot worse than DX11 DXVK for me, so I'd love to get DXVK working. :(

This seems to be some weird issue with DXVK + NVIDIA. Doitsujin said it was
fixed by NVIDIA in like 440.59 but clearly that hasn't really been the case. My
friend using an AMD GPU has no issue whatsoever and whenever I google this
problem every single person seems to have an NVIDIA GPU.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.