>>Some more ideas:
>>
>>1. Could a stored procedure or something else be triggered by the INSERT into the ErrorLog table - and might there be a problem in that?
>>
>
>No stored procedures. No DBC because there's FP2x compatibility.

Do FP2x (or Excel etc.) and VFP open the same table? Could there be an issue with VFP writing a code page mark or something else that FP2x doesn't like or understand (or vice versa)?

You could try some basic Windows (not hardware) troubleshooting:

1. From an elevated CMD prompt, run CHKDSK on all of the physical drives on your computer which could be involved: your system (usually C:) drive plus separate VFP table or temp file drives (if present)

2. From an elevated CMD prompt, run the Windows System File Checker:

sfc /scannow

3. After you get a crash, take a look at your Windows System and Application Event Logs and see if any errors or warnings were logged at the time of the crash