A bit more information would be useful - including whether resetting a users' layout profile helped (deleting the relevant CONSOLEUSER_IDN user entry from the LAYOUT table -- AFTER you made a backup obviously). *could* be that one particular tool / section is causing you trouble.
I've used the console across various enterprise accounts (including some that handle 50,000+ devices on a single Core) and haven't had any stability issues.
You might want to get in touch with support here to begin with. Here's ONE possibility that I've unearthed for instance that has nothing to do with us:
You can increase the loggging of the Console to debug level with the following (Support will request that most likely anyway in an attempt to trace down what might be going on):
(Feel free to have a look at the debug log, but it may not be the most "normal mortal human" readable thing in there, depending).
Support *MIGHT* request a backup of your database in to help duplicate (and then diagnose the issue) if need be.
Hope this helps.
In addition to the replies above, there have also been issues with running the Console when FIPS is enabled, causing various display, resizing, windowing issues, crashing, etc.
Also - there's a big difference between "it crashes" and "it doesn't respond".
If it crashes, there'll be exit codes & various things (including log entries that support will want to know about).
If it's "NOT RESPONDING* ... it could be either some .NET method that's having a fit, the DB back-end that's having to do something or similar. But if you leave it the time it needs to finish whatever, and then works just fine ... that's not the console crashing. That's "something going on in the background".
That's an important difference. I've not had the console crash on me in years.
It becoming unresponsive *could* be the more likely scenario - and we'd need to know what your console is loading up / trying to load up as a result. Hence - again - a lot of the advice above, about debug-logging and having a DB-backup to give to support for troubleshooting .