Well, if you deactivate the plug-ins, then the project affected by the crashes should not cause any problems afterwards. And that at every start and no matter how often. Then we know that the crashes are really caused by a plug-in. (You don’t have to wait until the next crash to test this either. You can press CTRL + Shift + Alt at startup to launch the safe mode dialog.)
Because Cubase only crashes on certain projects (and there only occasionally), it can take some time and patience to find the cause of the crashes. There are many ways to get to the desired goal. My way is only a suggestion. It is important that you proceed systematically. That’s why I suggested a simple way first. This way you can narrow down the problem directly to the plug-ins. (Or exclude them as the cause.)
But if you are absolutely sure that it is a plug-in, then you can also deactivate/remove each plug-in in your project step by step and see if or when Cubase runs stable. This way you will find the culprit immediately. (You should definitely make a backup before you start troubleshooting.)
But of course there can be other reasons for the crashes. Therefore I come back to your question from your initial post:
Yes, this can be a help and speed up the search for the cause. Therefore you should take a look at this thread:
There it is explained how you can read the dump files.