Right after the annexation of YOG the game crashes while I´m trying to save. However, it´s no problem saving during the war between YOG and Axis.
Upvote
0
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Install it in other folder and all your troubles will disappear until gunman fixes this 
In OS up to WinXP/Server 2k3 there's no special protection in c:\program files. If I remember right from the savegames Pang prefers to play in German language, maybe it should be tested in english to rule out a language/translation problem.
Another test option would be to use the 1.08 aodgame.exe in an 1.07 environment to rule out 1.08 data changes.
Another test option would be to use the 1.08 aodgame.exe in an 1.07 environment to rule out 1.08 data changes.
New exe, old problem. A CTD even without saving (happened around Mar 30 1941).
Edit: Gave it another try. This time I was able to save, even after YUG annexation. I saved in 7 days intervals. The game crashed at the end of Jun 1941 (Barbarossa had started on May 22)without saving at that moment.
Edit: Gave it another try. This time I was able to save, even after YUG annexation. I saved in 7 days intervals. The game crashed at the end of Jun 1941 (Barbarossa had started on May 22)without saving at that moment.
Last edited:
just played without the recent hotfix from 36-39 with 2 random crashes, with hotfix from mid 39 to 43 without any crashes. seems to be ok so far?
Started a new game. Everything was fine until YUG war. YUG was annexed (Apr 1941), ITA DOWed GRE and an attempt to save the game led to a CTD.
It is possible. I had no crashes since using the last exe. I just reached the mid of may in 1941 in a game i started using my last set of (softcoded) changes. Saving always takes very long so i always fear a crash but no crash appears. I donnot like to make premature conclusions but i think all relevant hardcoded reasons for known CTDs are solved.
I turned on "showid" because I thought something might be messed up with province id´s. I started saving every day after the YUG war started - and no CTD. ITA DOWed GRE and annexed GRE; YUG had been annexed and CRO formed.
I continued saving daily until May 1, 1941, then I switched to 7 day intervals. After two weeks a message popped up (during gameplay), displaying "critical error - false" and offerd to repeat, ignore etc. I chose "ignore" and had a CTD. There wasn´t any other information provided.
Edit: I can´t reproduce the crash. I reloaded the save (twice, in fact) and it continued well into Aug 1941 without any problems.
I continued saving daily until May 1, 1941, then I switched to 7 day intervals. After two weeks a message popped up (during gameplay), displaying "critical error - false" and offerd to repeat, ignore etc. I chose "ignore" and had a CTD. There wasn´t any other information provided.
Edit: I can´t reproduce the crash. I reloaded the save (twice, in fact) and it continued well into Aug 1941 without any problems.
Last edited:
New exe, same problem after YUG war lasts for some time. This is the message that was displayed (don´t know if it´s anything that might help):
"Problemsignatur:
Problemereignisname: BEX
Anwendungsname: AODGame.exe
Anwendungsversion: 1.0.0.1
Anwendungszeitstempel: 4fd6eb9a
Fehlermodulname: StackHash_0a9e
Fehlermodulversion: 0.0.0.0
Fehlermodulzeitstempel: 00000000
Ausnahmeoffset: e800722e
Ausnahmecode: c0000005
Ausnahmedaten: 00000008
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789"
"Problemsignatur:
Problemereignisname: BEX
Anwendungsname: AODGame.exe
Anwendungsversion: 1.0.0.1
Anwendungszeitstempel: 4fd6eb9a
Fehlermodulname: StackHash_0a9e
Fehlermodulversion: 0.0.0.0
Fehlermodulzeitstempel: 00000000
Ausnahmeoffset: e800722e
Ausnahmecode: c0000005
Ausnahmedaten: 00000008
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789"
I need savegames as close as possible to the moment of crash, weeks but days would be better.
Try to disable DEP (Datenausführungsverhinderung) for Arsenal of Democracy and test if it crashes again. Not the most elegant solution but might help.
http://tdistler.com/2009/04/10/stackhash-and-application-crashes-on-windows
http://tdistler.com/2009/04/10/stackhash-and-application-crashes-on-windows
This one is a day before crash while saving. The crash is reproducable if I start a save from before YUG war.
I don't get crash if I save the next day, or the following day, or the third day with your save...
Anyone else get a crash with the save posted by Blecky?
Anyone else get a crash with the save posted by Blecky?
Try this one. It´s right before the start of YUG war. I´ve started from there three times and got a crash around end of MAR.
I've went into April without crashes. The only time I got a crash is when I was clicking randomly on game window during saving.
Try this: right click on AoDGame.exe, select Properties, then Compatibility and check Run this program as administrator, then click OK.
Try this: right click on AoDGame.exe, select Properties, then Compatibility and check Run this program as administrator, then click OK.
I think I've got it! Caused by death of leaders of expeditionary forces. By the time of YUG invasion, Germany receives a lot of expeditionary forces from Bulgaria, Hungary etc, and with historical leaders deaths option activated, some of those Bulgarian and Hungarian leaders die while being in Exp forces. The situation was very rare before, since a leader had to die in combat.