Fatal Application Exit right after seeking yarrick mission

Moderators: Slitherine Core, BA Moderators, WH40K Armageddon moderators

Post Reply
IG88
Private First Class - Opel Blitz
Private First Class - Opel Blitz
Posts: 3
Joined: Thu May 26, 2016 11:28 pm

Fatal Application Exit right after seeking yarrick mission

Post by IG88 »

The game was running normally. I won the mission on turn 9 and then when the characters got done speaking it started to load the next mission. The Error came up then saying "ERROR Struct exception with code 0xe06d7363". After i press ok or the x it brings up another message saying "Warhammer 40,000 Armageddon: ArmageddonGame.exe-Fatal Application Exit ***Unhandled Exception! ExpCode: 0x80000003 ExpFlags: 0 ExpAdress: 0x00F77E6F Please report!" . After the first time i loaded a save and it brought up the same two messages. Then i restarted the mission and it did the same thing.
zakblood
Most Active User 2017
Most Active User 2017
Posts: 16502
Joined: Thu Jun 12, 2014 6:44 pm

Re: Fatal Application Exit right after seeking yarrick missi

Post by zakblood »

can you zip up and attach the save here for the developers to look at?

thanks
VPaulus
Slitherine
Slitherine
Posts: 8311
Joined: Mon Dec 27, 2010 8:33 pm
Location: Portugal

Re: Fatal Application Exit right after seeking yarrick missi

Post by VPaulus »

IG88
Private First Class - Opel Blitz
Private First Class - Opel Blitz
Posts: 3
Joined: Thu May 26, 2016 11:28 pm

Re: Fatal Application Exit right after seeking yarrick missi

Post by IG88 »

The workaround, worked do you still want me to zip up the file?
zakblood
Most Active User 2017
Most Active User 2017
Posts: 16502
Joined: Thu Jun 12, 2014 6:44 pm

Re: Fatal Application Exit right after seeking yarrick missi

Post by zakblood »

no thanks, that will be fine
IG88
Private First Class - Opel Blitz
Private First Class - Opel Blitz
Posts: 3
Joined: Thu May 26, 2016 11:28 pm

Re: Fatal Application Exit right after seeking yarrick missi

Post by IG88 »

also just saying that the next mission did the same thing but the work around still worked
Post Reply

Return to “Tech Support”