https://bugs.winehq.org/show_bug.cgi?id=44480 --- Comment #8 from Aru <nieve.aru(a)gmail.com> --- It might be something different then. I tested some more on each combination along with apitrace. This is how I ran apitrace (32-bit version): apitrace32 trace wine Steam.exe And then collected the wine-preloader.trace file on Rabi-Ribi directory. To replay the apitrace I used (x86_64 version): apitrace replay wine-preloader.trace Test cases: 1) Arch Linux, Kernel 4.14.15, NVIDIA 387.34-21: a) Game works fine. b) apitrace generated fine: apitrace_rabiribi_linux.4.14_nvidia_387.34.trace c) apitrace works fine on all test cases 1, 2 and 3. 2) Arch Linux, Kernel 4.15.3, NVIDIA 387.34-1: a) Game works fine. b) apitrace generated fine: apitrace_rabiribi_linux.4.15_nvidia_387.34.trace c) apitrace works fine on all test cases 1, 2 and 3. 3) Arch Linux, Kernel 4.15.3, NVIDIA 390.25-11: a) Game crashes. b) apitrace generated fine: apitrace_rabiribi_linux.4.15_nvidia_390.25.trace c) apitrace works fine on all test cases 1, 2 and 3, there are no crashes and apitrace exits nicely: output similar to the others and exit code 0. So, I can still run the game if I use the latest kernel on repository if I patch NVIDIA 387.34-1 to be able to be compiled on 4.15 kernel. This is my current setup now. Is there anything else I can test or any more information I can try to find? I hope this is helpful. Sorry for taking long to report the tests. -- 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.