[Bug 47731] World of Warcraft BFA Crash with error 132 Memory could not be read.
WineHQ Bugzilla
wine-bugs at winehq.org
Fri Sep 27 17:51:51 CDT 2019
https://bugs.winehq.org/show_bug.cgi?id=47731
--- Comment #15 from Steve Ebey <eaglecomputers.ok at gmail.com> ---
(In reply to Sveinar Søpler from comment #14)
> (In reply to Matteo Bruni from comment #13)
> > FWIW, for WoW you should only need winebuild-Fake_Dlls, ntdll-Builtin_Prot
> > and ntdll-User_Shared_Data staging patchsets.
>
> Nice. I will see if i can get WoW running with only those patches.
>
> Instead of posting a rather detailed explanation to what could be causing
> this error, i fear it would be deemed of topic, so i will just conclude with
> asking the OP - Steve Ebay the following:
>
> 1. Are you using WineD3D or DXVK?
> 2. Is the problem still the same with 4.16? (And possibly upcoming 4.17 this
> weekend).
> 3. In the case of DXVK and "YES" to #2: Are you using a nVidia graphics card?
1. vkd3d (for dx12), and dxvk.
1a. it only appears to crash with retail. I can run the classic version with no
problems.
2. yes, to 4.15 and 4.16.
3. yes, same card I have used for 4 years, GTX 970, with proprietary drivers.
--
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.
More information about the wine-bugs
mailing list