Jump to content
froggyluv

0xC0000409 - STATUS_STACK_BUFFER_OVERRUN

Recommended Posts

 On latest Dev been getting this CTD upon trying to launch with seemingly too many mods -is there a weight limit to hefty mods that can be loaded? If I add a new one and erase an old equally large one it seems ok but if not....ctd

  • Like 2

Share this post


Link to post
Share on other sites

 On latest Dev been getting this CTD upon trying to launch with seemingly too many mods -is there a weight limit to hefty mods that can be loaded? If I add a new one and erase an old equally large one it seems ok but if not....ctd

Same problem on the last dev udpate. Wasn't on the RC

Share this post


Link to post
Share on other sites

I'm getting error 0xC0000417 on both dev and RC

Share this post


Link to post
Share on other sites

Seems to appear with more than 17 mods in the list. Very annoying !

Share this post


Link to post
Share on other sites

Yep, came here to search this issue.  Tested on RC.

 

Another issue i just found out (I've been outta the loop for a little over a month now) is a lot of my STEAM MODs are being loaded into a Content folder now instead of the ROOT like previous with @MODNAME.  Now the MODNAME is numbers.  Is this a STEAM issue, or ARMA?  My guess is this is how ARMA is handling MODS now with their launcher?  IF so this has borken the way i use to run a 3rd party MOD handler....

Share this post


Link to post
Share on other sites

Yo buddy... yeah.. steam now references the workshop content folder so it doesn't double the file size by having one in arma root and one in workshop content... I noticed this messed up my install and they didn't show up if I didn't run the launcher way...

My fix was to manually move the folders over and rename... and then I unsubscribed from the workshop mods and will have to do manually now..

The actual crash is caused by the parser apparently and how many mods are in the command line... fix for that is combining mods into less folders to reduce command line size...

Pita but works for now

Share this post


Link to post
Share on other sites

Yo buddy... yeah.. steam now references the workshop content folder so it doesn't double the file size by having one in arma root and one in workshop content... I noticed this messed up my install and they didn't show up if I didn't run the launcher way...

My fix was to manually move the folders over and rename... and then I unsubscribed from the workshop mods and will have to do manually now..

The actual crash is caused by the parser apparently and how many mods are in the command line... fix for that is combining mods into less folders to reduce command line size...

Pita but works for now

Hey dude, hope all is well.  Yes i came across this post: https://forums.bistudio.com/topic/185298-the-mod-subscribed-from-steam-workshop-leaves-2-copies-in-my-disks-it-is-waste-of-my-disk-space/page-2

 

I figured reducing the folders would do the trick, but thinking BIS should and will fix it instead.  But thats for the temp workaround for now if i decide to go that route.  I did make a post on the other topic to hopefully give us the option to go back so we dont have to manually manage the folders/files.  I get thier approach though since this is really a STEAM issue....

 

Oh well always something  ;)

Share this post


Link to post
Share on other sites

Hello guys,

would be any use to use if there would be a special folder in Arma dir, that would contain read-only link to Steam mods? E.g. <Arma 3 dir>\Steam mods\@modFolderName

 

Possibly Yes?  Well so the benefit i see is finding the folder easily without using the default Arma Launcher.  Right now per my last comments the folders contain the numbers which mean nothing when trying to determine the MODs.  I think if 3rd party apps can use these read-only/shortcut folders to load the original MOD, then yes this would be great, but this may not be the case?

 

Either way i think it would be helpful just for the ease of finding the MOD folder.  But since i know the ARMA launcher can do this as well, not sure if the effort is worth it. 

 

I need to play with the default launcher some more, but one thing i struggle with is the speed of it.  It's a very slow/painful process of selecting/deselecting the mods.  I have a good half second or so delay after each click of a MOD, and i can't quickly make these changes.  I think this happens because it moves it to the "LOADED" section of the list.  Of course once i create multiple profiles, then maybe it won't be so bad...  Another nice feature would be to export the MOD command line of the current selected MODS.  This can be helpful if you wanted to load that into a different launcher, or use it for the SERVER MOD list.  Right now it seems the only way to do this is export the entire LOG batch which takes more time and space then a quick copy of the MOD command line.  With this said, are you guys looking into this limited MOD selection issue?  Should we open a ticket or something else?  It's not the launcher it's ARMA in general as it crashes without the launcher as well.

 

 

With my feedback above, i hope you take it as suggestions and not complaints.  I love everything you guys have been doing and love your games.  As always, thanks for everything!  :)

  • Like 1

Share this post


Link to post
Share on other sites

bumping a very very old post because its happening again as of latest updated and been happening alot with very little mods loaded (like 5...)

 

ie. the problem has been revived

 

had to stop using the default memory manager and use window's version now.

Edited by Sycholic

Share this post


Link to post
Share on other sites

I'm getting the same error message, no mods installed. It happens only when I'm flying in a jet or helicopter, and happens consistently enough that it's pretty much guaranteed if I spend 30 mins or so flying around over Altis.

 

I've tried all 3 different memory allocators, a clean install of the game (including deleting Arma files located in "%appdata%" and "Documents\Arma3".

 

I'd really like to find a solution to this, currently unable to play due to this issue...

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×