start up crashes would never make it past release window, this is a user problem, not a dev problem.
and 0x0000... looks more like a memory error, you might want to run a memory diagnostic to see if one of your ram sticks is going bad, or simply take the sticks out and put them back in, could just be loose.
0x00000... = null address AKA doesn't really tell us what the problem is.
if your memory is okay and passes windows memory diagnostics, update everything below:
it would also be very helpful if you can locate the full crash dump and upload it here.
(probably found under AppData\Local\WilfLifeC
Bullshit. Access to zero address is obviously access using uninitialized pointer. There are many ways how this can happen, even randomly. For example program requested something, didn't tested request return code and started using that. The reason why it would pass tests is that the requested thing was always granted on tester computers.
Everyone who has programmed anything, knows that writing a code so safe to handle every possible case correctly is quite annoying. So no one really does that, unless it's something critical. It's even possible that the bug is in some library function they are calling.
I can upload the error log and memory dump, but this is not the right site for that. I know Steve reads this board now and then, but his programmers have their support site elsewhere if any. I guess for paying customers only. I would also have to redact user name from file paths in those files.
Basically the log says that the game run time is zero, there is plenty of memory available and zero memory is used. It does not say which module/function crashed. Maybe it could be found in the memory dump. It crashes even before loading screen appears.