"Out Of Memory"- Due to Many States on one entity

[[email protected]]

Has anyone had experience with this message- Unfortunately ATX (even after attaching their software file "Large Address Aware") still unable to accurately process the file.

Keeps shutting Down

[Lee B]

1. Reboot your computer to clear your printer cache.

2. Hold down your ctrl key and press F5 to clear your browser history.

3.  If you have a security suite turn it off, it uses a lot of RAM.

4,  Run CCleaner or a similar program to clear out any garbage

5. Use your task manager to minimize any programs running in the background

Cross your fingers and try again

[Lee B]

You don't say, but if this is happening while trying to efile, not all states have to be piggybacked with the federal return.

Unselect those states that can be efiled independently,

[Pacun]

If the suggestions provided don't help, buy a better computer with 16G or 32G of RAM.

[Jack from Ohio]

4 hours ago, Pacun said:

If the suggestions provided don't help, buy a better computer with 16G or 32G of RAM.

I agree 100%.  My first impression was: "too little RAM."  RAM is cheap.  Nothing less than 16G.

[Lee B]

Perhaps it depends on how many programs you keep running in the background and whether you are using a big security suite.

I have always done well with 8 Gigs of RAM.

[Abby Normal]

Keep Task Manager open and see how much memory it's using. I also have LAA installed and have gotten it up to 4GB before.

Did you remember to add ATX 2018 to LAA? You have to add the new years when you install ATX.

[Wtyler]

I have 64gig of ram and 16 intel 3.2 processors. Still happens to me on 2021 program. Going to try the solution from cbslee

 

[joanmcq]

It happens to me too, especially if I try to open a second return.  I shut down everything and reboot my computer.  Clears out all the crap.  ATX still accumulates RAM usage so if you keep your computer on for days, it adds up and eventually shuts the program down.  A big file can make it happen faster.

[GLJEANNE]

Ugh, I had one of those a few years back.  I forget how many states, but I could work on it, but not print.  Try to print, it crashes.  Sadly, I don't recall for sure my solution, other than making sure everything else was shutdown, and restarting ATX only to work on that return.

My take away was, dump the client (there were other reasons) and never have another one with so many states.