Are blue screens Windows 7 black magic?

Nobody seems to provide straight answers to the regrettable and common stop errors in some Windows 7 configurations. Let's make a quick review. 1) DELL. One of the "Resolution Expert Center" experts, after different exchanges both by e-mail and via chat, and after having received a copy of one of my dump files and other useful information, he concluded: "In order to correct the issue with a corrupt ntoskrnl file, the operating system will need to either be repaired or reinstalled." Corrupt kernel file? How about being able to watch videos, movies, etc.? Totally clueless? If that was the case my computer would not start in the first place (!) Just following a script, not providing actual customer service. 2) Microsoft. I'm sure the information is there in their huge knowledge bases, but is not easy to come by; besides you have to know what to look for. Their debugging tools seem to be, from my view point of a IT generalist, very good, but it's not for regular folks. Finally, 3) Web forums. Most of the times, the contributors seem to be as clueless as the people longing for answers. Apparently there is no exact science when it comes to figuring out these "stop errors" or "BSODs." But the process is illuminating; at least it has been for me.