http://bugs.winehq.org/show_bug.cgi?id=18040 --- Comment #17 from Stefan Dösinger <stefandoesinger(a)gmx.at> 2009-04-18 07:35:27 --- Thanks for the log. winedbg parses the wined3d debug symbols, which suggests that the crash occurs inside wined3d or the opengl driver. However, the backtrace is not very conclusive: Backtrace: =>0 0x023cf9e0 (0x0052d07c) 1 0x10d94b16 in masseffect (+0x494b16) (0x0052d0a0) 2 0x10db2f40 in masseffect (+0x4b2f40) (0x0052fcd8) 3 0x00000000 (0x00000000) Can you see if the game writes a minidump file or something similar? I suspect the backtrace we see here is from a follow-up exception, not the original issue. The D3D log up to the crash doesn't ring any bells so far. Can you add +d3d_draw,+d3d9 to the log? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.