AGEOD Forums

Version 1.05 Steam
CTD Application error during turn processing
Playing the Union during the April 61 campaign

My comp: Win 8.1 16GB ram 1TB HD 4GB NVIDA card

I took backup1 and processed the turn without issue, I guess this was the previous turn that crashed for you? Did you retry processing it?

It was the last turn that CTD. I replayed that turn and it was ok...odd. Sorry I did not remember to write what the error said.

[ATTACH]33388[/ATTACH][ATTACH]33387[/ATTACH]

Not sure if this is a same bug but happened to me today. Using the new exe. file. Before it did not happen.

Yes thats it. I got it a few times before the new EXE and before 1.05 also. But upon reload the turn processed.

Yeah keeps happening to me since fixed exe.
Two more crash files from yesterday, same thing happened.
[ATTACH]33414[/ATTACH][ATTACH]33415[/ATTACH]

Happens to me also with 1.05 both in steam and in AGEOD installation. Played Gettysburg scenario and CTD on first turn processing. Reloaded and played out turn then another CTD on 2nd turn

can you keep the logs please? We will first start inspecting Smitzer saves.

I got it again, only this time when I started up the game this popped
up before the play/update/etc screen showed. Here's the log: [ATTACH]33417[/ATTACH]

[ATTACH]33418[/ATTACH]

More input from my side:
Error first appeared when I used exe. from forum and applied it in steam folder. But when steam was updated yesterday and I did a complete reinstall + installed the game to HDD not an SSD drive the CTD stopped. Then I played 5 turns with no crash (same save).

So for anyone having the same CTD problem, maybe it will work to completely uninstall and reinstall. In my case I had to change a hardrive too. Also before I did that I verified files though steam and it didn´t help.
Hope this helps, since there is an possibility of an error on my side here. (corrupt file, admin rights or whatnot)

DrPostman wrote:I got it again, only this time when I started up the game this popped
up before the play/update/etc screen showed. Here's the log: [ATTACH]33417[/ATTACH]

[ATTACH]33418[/ATTACH]

It seems to have been triggered by a write operation on the disk. I remember you had some of these before, perhaps linked to admin rights, an AV, the UAC, the location where your game is?

Pocus wrote:It seems to have been triggered by a write operation on the disk. I remember you had some of these before, perhaps linked to admin rights, an AV, the UAC, the location where your game is?

That's probably it. Until I get my disability raised I'm having to deal with a wonky
computer. If you say it's likely due to that I can't argue with it.

Try the next public beta but I got no issue with Smitzer saves either.