"Inspector Clay is dead, murdered, and somebody's responsible." (Plan 9 from Outer Space, 1959)
A classic movie example of stating the obvious.
The table gets corrupted and
something is responsible. Equally obvious. But it's easy to just look for a way to relieve the symptom rather than finding the culprit.
Problems don't appear out of nothing. When they start it is because
something has changed. It may not be something we did ourselves. It may be something that we were not aware of. But something did change. And unless we can find out what, we cannot say that we have fixed the problem.
So if the new database removes the symptom, it's more of a band-aid than a cure.
Now I wish that these wise words could be accompanied by some wise advice as to how to find the real problem. Unfortunately I have very little to suggest. I guess it
could be a hardware problem. Seems unlikely, but I would suggest you check for disk or memory problems.
CrystalDiskInfo is pretty good at spotting iffy drives. I haven't used any memory test programs in years, but I know that Windows 10 comes with
Windows Memory Diagnostic. But as I said, this is just a real long shot.
Looking at the event logs with the
Event Viewer can sometimes reveal problems, but it is very much like looking for a needle in a haystack, unless you already know what specific problem you are looking for.