https://bugs.winehq.org/show_bug.cgi?id=49896
--- Comment #9 from Esme Povirk madewokherd@gmail.com --- Calling through kernelbase to ntdll is expected.
The address of the crashing instruction appears to be on the stack.
So this is most likely a case of stack misalignment, where a function pops a different number of bytes than expected, and a pointer on the stack is treated as a return address. We're lucky the stack trace has any useful information.
It might be worth checking whether any compiler/optimization flags in your build are contributing to this.