It seems that the MC logs are automatically erased when MC is launched. As a result, when there is a crash, either the customer relaunches MC and then calls customer service who says "the logs are erased by your relaunch, it may be difficult to identify the cause" or the customer has to spend time in "run" saving the logs, then in "task manager" stopping all MC processes before relaunching MC.
For a trader, the priority is to have MC up and running, not to waste time with MC closed saving logs in the middle of a trading session.
If the logs were automatically saved for at least 24 hours, the customer would not need to waste time during active trading sessions saving the logs before relaunching MC. In addition, customer service could access the logs when it is open and customers could save and send their logs after their trading session is closed.
This issue is particularly important for customers who live in non-US time zones and trade in local markets which are open during times when when customer service is closed. For these customers, saved logs are the main way to fix issues happening during times when customer service is closed.