this seems to be a Microsoft defect. Are you using Windows 10 Pro? I ask because the only other report so far was from a user using that.
Although it is not recommended, you can start WSJT-X by using "Run as Administrator", I have no idea why that is necessary. The error is a memory access violation and should not be happening.
I suggest you report the issue to Microsoft as there is not much we can do to diagnose or resolve this issue.