https://bugs.winehq.org/show_bug.cgi?id=40979
--- Comment #5 from Henri Verbeet hverbeet@gmail.com --- (In reply to Roland Vet from comment #4)
GFX 17:06:49.594 <Exe.Architecture> x86_64
You're using the 64-bit client, is that intentional? Do you know if the issue also happens with the 32-bit client?
GFX 17:06:49.880 Adapter [0]: NVIDIA GeForce GTX 470 (VendorID 0x10de DeviceID 0x6cd)
Is that from the same machine as the previous log? The earlier log seemed to suggest an Intel Haswell based GPU.
GFX 17:07:32.964 DirectX call m_device->TestCooperativeLevel() failed with error code D3DERR_DEVICENOTRESET GFX 17:07:32.964 DirectX call failed with error code D3DERR_DEVICENOTRESET GFX 17:07:32.964 Lost D3D9 device GFX 17:07:32.996 GFX 17:07:32.996 D3D9 Device Reset from ::OnRender returned e_errorKindGfx(0)
Does this match the time of the crash/hang? It implies the device getting lost, for example because of the window getting minimised, and then failing to recover. There's a chance that happens only after the crash though. Does it make a difference if you run the game windowed?
In the "GameLogs" directory, there should be a crash directory corresponding to the crash, and in there should be a .dmp file containing a minidump. Could you open that with winedbg and get a backtrace?
Are there any obvious differences between the terminal output when it works and when it doesn't?