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

WineHQ Bugzilla wine-bugs at winehq.org
Mon Sep 30 07:30:23 CDT 2019


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

--- Comment #23 from Steve Ebey <eaglecomputers.ok at gmail.com> ---
(In reply to Sveinar Søpler from comment #22)
> (In reply to Steve Ebey from comment #21)
> > 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.
> 
> I had no such problems with wine-staging-4.17.
> 
> Did you try to clear out WoW caches, DXVK caches and nVidia caches?
> 
> ~/.nv/GLCache (Unless you use custom folder)
> c/Program Files (x86)/World of Warcraft/_retail_/Cache (delete everything)
> c/Program Files (x86)/World of Warcraft/_retail_/Wow.dxvk-cache
> 
> World of Warcraft ofc residing inside the wineprefix you use.

Still crashed. Not sure what else to try.

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