Toad Applications randomly shut down, even in the middle of a query. (4374989)

Toad Applications randomly shut down, even in the middle of a query.

Toad Applications randomly shut down, even in the middle of a query.  No prompt to save changes or exit gracefully.  It shuts down when minimized,  idle, or in the middle of a query.

Here are the Windows error details.

Event ID 1000
Task Category: Application Crashing Events

Faulting application name: toad.exe, version: 8.0.0.65, time stamp: 0xfb689bbb
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x5d78
Faulting application start time: 0x01da6414a09f2eba
Faulting application path: C:\Program Files\Quest Software\Toad for SQL Server 8.0\toad.exe
Faulting module path: C:\windows\System32\ucrtbase.dll
Report Id: a9ea8e39-99fa-4e0e-8064-0a8cc3d7fa46
Faulting package full name: 
Faulting package-relative application ID: 

The Event ID 1000 application error is included in the Windows Event Viewer log when applications crash.

What causes the application error?

• Malware – The presence of malware or a virus on your machine may also have caused this Event ID. A thorough antivirus software scan usually fixes the issue.
• Older Windows – Having an older version of Windows installed on your PC could cause this issue. Make sure the Windows version is up to date.
• Crashing of a particular application – If you encounter the error message, it could also be because of a specific application crashing on your PC. You can determine it by performing a clean boot or looking at the file path in the event.
• Corrupt system files – The most common reason why you encounter the Event ID 1000 is corrupt system files. Some Windows components may crash and cause problems with the system if you have damaged system files or missing modules.
• .NET Framework improperly installed – Windows and many other apps use.NET framework to function. The Event ID 1000 will appear in the event logs if the framework is wrongly installed or contains faulty files.

Workaround.  

Reinstall Microsoft NET Framework