VPX crash report
What it means
A Visual Pinball X crash report is in this folder. It describes the context of the crash, not its cause.
Why it happens
VPX writes "crash.txt" in its working directory; loading or playing a table sets that working directory to the table's folder. The scan looks in the tables folder, beside each detected VPX executable and in each table's folder. It reads the date, the VPX revision, the exception and the first entry of the Call stack. The Call stack gives context, it does not establish the cause of the crash; a third-party module that appears in it is not named as the cause. A report whose readable date is more than 30 days old is classed as Info, the others as Note.
How to fix it
If VPX still crashes, note the table, the module shown and the date from the report, and give them when asking for help (forum, table author or module author).
How Pincab Toolbox detects it
A "crash.txt" file in the tables folder, in a table's folder or in the folder of a detected VPX executable starts with the header "Crash report VPX". The scan deleted and changed nothing.
Check your own pincab
Pincab Toolbox is a free Windows scanner for Visual Pinball X and PinUP Popper. It finds and explains problems like this one. No account, no telemetry.
Download for freeCovered: Visual Pinball X (10.x) and PinUP Popper. Partly covered, read only: PinballX and PinballY (their settings and game lists). Not covered: Future Pinball, Pinball FX, Visual Pinball 9 and the other frontends.