^ Nonsense.
What the heck does this have to do with script debugging?
If the RAM is messed up, you'd notice that elsewhere (although checking that can't hurt).
AC does not use the registry except for (un)installing.
Please don't copy random stuff you googled somewhere and suggest that to people as a solution.
The thing is that the 1.1.0.4 Windows binaries were compiled without debugging information, so you'll always get 0xc0000005, which I assume is just the entry point. Therefore, that error message is completely meaning- and useless.
"Random" crashes at startup may be caused by quite a few different things. Malware as well as faulty antivirus could be the cause. I'd also check if you have OpenAL installed properly, since that's something AC uses but Sauer doesn't.
Also, when that error message pops up, do you do you get anything in the console other than "pause"?
What the heck does this have to do with script debugging?
If the RAM is messed up, you'd notice that elsewhere (although checking that can't hurt).
AC does not use the registry except for (un)installing.
Please don't copy random stuff you googled somewhere and suggest that to people as a solution.
The thing is that the 1.1.0.4 Windows binaries were compiled without debugging information, so you'll always get 0xc0000005, which I assume is just the entry point. Therefore, that error message is completely meaning- and useless.
"Random" crashes at startup may be caused by quite a few different things. Malware as well as faulty antivirus could be the cause. I'd also check if you have OpenAL installed properly, since that's something AC uses but Sauer doesn't.
Also, when that error message pops up, do you do you get anything in the console other than "pause"?