https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #12 from Vasily Galkin galkin-vv@ya.ru --- Also this may be related to the fix that nvidia done in https://bugs.winehq.org/show_bug.cgi?id=49407
The origin of the SIGSEGV is inside NVidia libs. Calling to nullptr-function (according to a stacktrace I presented above) instead of returning an error MAY be a sign of a bug inside nvidia driver.