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

WineHQ Bugzilla wine-bugs at winehq.org
Sun Sep 29 15:05:48 CDT 2019


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

--- Comment #21 from Steve Ebey <eaglecomputers.ok at gmail.com> ---
(In reply to Sveinar Søpler from comment #20)
> (In reply to Steve Ebey from comment #19)
> > Machine:   Type: Desktop Mobo: ASUSTeK model: M5A97 LE R2.0 v: Rev 1.xx
> > serial: 150954265201367 BIOS: American Megatrends 
> >            v: 2701 date: 03/24/2016 
> 
> I could not find the bios setting i was looking for on that motherboard, so
> it is probably not that.
> 
> Also i can't say i have ever experienced huge issues with vkd3d and this
> error, even when i had GTX970, so i dunno. Well.. Back to the theory
> spinning again :P

Compiled and ran 4.17 and it also crashed on the retail but not on classic. 
Crashed with wined3d, vkd3d, and dxvk. the crashes started back around the 4th
or 5th commit, from the git, in version 4.14.  I have kept a working 4.14
staging, and trying to learn how to bisect the git to see the commit that
caused the problem.

-- 
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