Do you know what line is causing the crash? Are you logging?
You need to find out what line of code is causing the crash, you need to be 100% certain what the cause of errors are.
If you did install Matrix1 then you can use the log commands and write out the progress of your process. Logging is saved to disk while the program is running before it closes.
The last output into the report reveals where the problem is. If you do not feel comfortable using log files, try message boxes or text on the screen; give yourself feedback to work with.
Log example code:
Open Log "MyLog.txt"
WriteLn Log 0, "Starting dynamix"
Dyn Start
WriteLn Log 0, "Loading level"
LoadEntities()
LoadMap()
` etc etc
WriteLn Log 0, "Level loaded"
You do it between major parts of the process, when you find out the problematic section of the code, you narrow it down by adding more log statements in high frequency between every few lines of code. It's down to your judgement to decide what commands are worth logging.
If it crashes on various unrelated lines; it is more likely an external software issue or hardware conflict.