# Should We Find A Better Way to Deal With no-boot/crash Questions?

On Raspberry Pi SE I have noticed a ridiculous amount of "Why is my Pi not booting?" or "Pi crashing" questions that are very poorly asked. I understand that a lot of people have this problem, and if they do they should post the output of any files/commands they can still access like dmesg /var/log/messages /var/log/syslog and /var/log/kern.log. Though, most of the time when the Pi won't boot, they have access to none of these files. In that case the op should add what they did to the Pi in the days/hours/minutes leading up to the crash/no boot. The odds of a Pi just dying is pretty slim, so they must have changed something. Also, even if the Pi will not boot at all 99% of people will have access to /boot/config.txt and /boot/cmdline.txt which I assume could contain some very important information in most cases. Is there anything else we should do to help mitigate this problem of almost completely unanswerable questions?

No output of any file/command: Raspberry Pi 2 Boot problem

This contains almost no useful information: raspberry does not start

Examples of good questions:

Contains some good output: My sdcards won't boot

Contains boot messages: My Raspberry Pi won't boot into Raspbian any more?

Contains some useful and very relevant output: Why won't my Raspberry Pi overclock?