23 Incredibly Helpful Crash Reports

It must blow to be the dude who has to read these.

1. Be as detailed as possible.

ID: 1053890

2. Try to avoid comparisons to competing products.

ID: 1053898

3. Remember: The report concerns the status of your software, not your furniture.

ID: 1053925

4. Try to remain positive.

ID: 1053950

5. Be succinct.

ID: 1053901

6. Focus on one issue at a time.

ID: 1053949

7. Focus on the important things.

ID: 1053924

8. Look for workarounds.

ID: 1053903

9. Be honest.

ID: 1053944

10. Try to avoid speaking in metaphors.

ID: 1053960

11. Report any previous errors of the same nature.

ID: 1053920

12. Keep a clear head.

ID: 1053952

13. If it helps describe the problem, drop a graphic into the error report screen.

ID: 1053922

14. Try to isolate any environmental issues that may have caused the problem.

ID: 1053923

15. Don’t ramble.

ID: 1053954

16. Give a second-by-second recap of the moments leading up to the crash.

ID: 1053928

17. Write the report as though it’s going to read by a dog or small monkey.

ID: 1053959

18. Try to express your emotional state at the time of the crash.

ID: 1053929

19. Always report errors, even if the crash occurs when the program is closing.

ID: 1053956

20. Check your privilege.

ID: 1053935

21. Try to be non-threatening.

ID: 1053938

22. It’s okay to get a little poetic.

ID: 1053948

23. Avoid making the same mistakes over and over again.

ID: 1053955

Check out more articles on!

Deputy Editorial Director, Iron Fist of BuzzFeed
Contact Tanner Greenring at

More News

More News

Now Buzzing