ok, in order to diagnose the problem we need to know everything possible about the problem. We can't just figure out what the issue is by saying "oh, it says runtime error". That's not helpful. We need things like error logs, system specs, model numbers, etc. Until then we won't be able to solve the issue.
Save the file, open it with Notepad (or similar) and check to see if it contains any private data (in the first few lines), then copy and paste it here.
My Windows machine dxdiag produced a large mount of data.