https://bugs.winehq.org/show_bug.cgi?id=36075
Bug ID: 36075 Summary: Kingdoms of Amalur: Reckoning Crashes on Start Product: Wine Version: 1.7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mattcbro@earthlink.net
In a 32 bit prefix, running on linux mint 16, cinnamon 64 bits, attempting to play Kingdom of Amalur: Reckoning results in a crash prior to game start.
This is occurring in wine-1.7.16 . The exception is, exception: page fault on read access to 0x00000018 in 32-bit code (0x009c54b0).
Others have reported the same problem in ubuntu based systems.
I am using an Nvidia 770 gtx card with proprietary drivers.
http://bugs.winehq.org/show_bug.cgi?id=36075
--- Comment #1 from Matt mattcbro@earthlink.net --- This bug persists in wine 1.7-17, same symptom on start.
http://bugs.winehq.org/show_bug.cgi?id=36075
--- Comment #2 from Matt mattcbro@earthlink.net --- Same bug for a clean 64 bit wine prefix emulating windows 7.
Running mint 16 cinnamon.
https://bugs.winehq.org/show_bug.cgi?id=36075
Goblinstomper@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Goblinstomper@gmail.com
--- Comment #3 from Goblinstomper@gmail.com --- Can confirm with wine 1.7.17 in a 32bit prefix on 64bit OpenSuse 13.1 using fglrx.
https://bugs.winehq.org/show_bug.cgi?id=36075
--- Comment #4 from Goblinstomper@gmail.com --- Created attachment 48446 --> https://bugs.winehq.org/attachment.cgi?id=48446 winegenerated backtrace
http://bugs.winehq.org/show_bug.cgi?id=36075
Eric eric@hellouser.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric@hellouser.net
--- Comment #5 from Eric eric@hellouser.net --- I was also running into the exception: page fault on read access to 0x00000018 in 32-bit code (0x009c54b0) bug but it appeared to go away when I disabled the Steam in-game overlay.
http://bugs.winehq.org/show_bug.cgi?id=36075
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED URL| |http://store.steampowered.c | |om/app/102500/ CC| |focht@gmx.net Resolution|--- |DUPLICATE Summary|Kingdoms of Amalur: |Kingdoms of Amalur: |Reckoning Crashes on Start |Reckoning (Steam) crashes | |on startup
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello folks,
--- quote --- I was also running into the exception: page fault on read access to 0x00000018 in 32-bit code (0x009c54b0) bug but it appeared to go away when I disabled the Steam in-game overlay. --- quote ---
That would be a dupe of bug 35361 then.
--- snip --- Module Address Debug info Name (108 modules) PE 340000- 39f000 Deferred fmod_event PE 3a0000- 3b2000 Deferred xinput1_1 PE 400000- cc5000 Export reckoning PE cd0000- df2000 Deferred fmodex PE e00000- 1060000 Deferred d3dx9_30 PE 1060000- 111b000 Deferred gameoverlayrenderer PE 2a60000- 2b2c000 Deferred steam ... --- snip ---
Regards
*** This bug has been marked as a duplicate of bug 35361 ***
https://bugs.winehq.org/show_bug.cgi?id=36075
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Austin English austinenglish@gmail.com --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=36075
--- Comment #8 from Goblinstomper@gmail.com --- if it was a dupe of 35361 wouldn't disabling the overlay always enable the game to run? The game still does not run for me with the overlay disabled, and as opposed to the times when I've encountered 35361 Amalur does not even get to the creation of a window (or context or w/e it's technically called), whereas other instances of where 35361 occured it has been after the game had started and the overlay was launched.
https://bugs.winehq.org/show_bug.cgi?id=36075
ganbare564@aim.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ganbare564@aim.com
--- Comment #9 from ganbare564@aim.com --- I concur with Goblinstomper's above comment. I've discover a bizarre but so far effective solution to this that works on two of my laptops..namely a Sony Vaio with a Nvidia GT 425M card running on Ubuntu 14.04 (and also Arch Linux 64 bit), and my Samsung Ultra running Ubuntu 14.04 with an integrated HD 4000 graphics unit.
In summary I basically created a bunch of empty numbered folders (i.e. 009, 010, 017 etc) in the "bigs" and "content" folders which are housed underneath the main game folder (where the "reckoning.exe" executable is held)
For more details you can read my test case entry and comments over at WINEHQ:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=25354
I hope this solution works for others and I would love to know what is really happening under the hood here...so to speak.
https://bugs.winehq.org/show_bug.cgi?id=36075
hr450_e@t-online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hr450_e@t-online.de
--- Comment #10 from hr450_e@t-online.de --- This bug is not caused by Steam overlay (my opinion). I have tested all suggested workarounds including disabling overlay, removing/creating directories, ... - none worked for me. Then I came across an assumption made by turboNOMAD (see comment section of game test linked in comment above) - that the crash is triggered by FindFirstFile/FindNextFile implementation. A few hours ago, I realized, that there is a patch addressing this issue (Steam - known bugs):
https://bugs.winehq.org/show_bug.cgi?id=34122
Testing the patch: wine 1.9.7 without patch: crash on startup wine 1.9.7 patched: game starts and seems to run stable
-
wine-bugs＠winehq.org