Whether you’re using MyISAM or InnoDB, repetitive crashes relate to unstable hosting.
Your first question then becomes, “Is this a hobby project or a money project?”
For Hobby sites, ignore the problem. For Money sites, move to fast stable hosting.
What I do for my clients, to maintain stable database system is…
Use MariaDB rather than MySQL. It’s faster + more stable + recovers faster when problems occur.
Run mysqltuner + mysql-tuning-primer, retuning database every day for first week of hosting, then once a week thereafter, till no tuning suggestions are presented.
Track database error log + slow query log + /tmp usage (used when SELECTs exceed memory buffers) + resolve all problems as they arise.
Reasons for repeat table crashes include…
Interrupted long queries, or updates which will show up in one of the database logs, if correct logging is enabled.
Incorrect configuration/use of BINARY LOGs.
/tmp filing up
Database disk filing up
Connections broken during database transaction
And the list goes on…
Only way to know for sure is have access to all system logs + database logs + have correct database logging enabled.
If this is a Money site, likely best you hire an expert to fix your site.
Also likely you’ll require changing hosting companies.