Sometimes the best answer to your PC problems is right in front of your face.–PC Pitstop.
Better PC Answers In Front of Your Face
Get Better, Faster Answers by Reading What’s in Front of You
By Leo Notenboom
I vent a little about people missing what’s right in front of them (including myself), and then discuss why taking the time to read what your machine is telling you is so important to a less frustrating experience with your technology.
One of the things that frustrates me occasionally in the questions that I’m asked is something I’m also guilty of myself: not reading what’s right in front of my face.
Rather than only venting about it, I want to talk a little bit about why it’s so important to read and follow instructions.
Because it’s obvious that so many people do not. (And, yeah, like I said, sometimes that includes me.)
The question that started this
This morning as I was reviewing questions in the Ask Leo! question queue, I came across this one:
How i solve this problem sir pls! I use windows 7!-
A problem has
been detected and windows has
been shut down to prevent
damage to your computer.
If this is the first time you’ve seen
this stop error screen, restart your
computer. If this screen appears
again. Follow these steps: _ _ _
That was the entire question. (I did not respond, for reasons that will become apparent.)
We’ve all seen these types of error messages at one time or another. Messages that, essentially tell you exactly what to do next.
My assistant’s proposed response was spot on: “I’d follow the steps described in the error message”.
So why didn’t the questioner do that?
And if he did, why didn’t he include that information? After all, the Ask Leo! question form does also include the following instructions:
BE COMPLETE: I require the version of all software involved (particularly Windows), the full text of any error messages, the specific make and model of computer and detailed steps to reproduce the problem you’re seeing. Without enough information you won’t get an answer. Period.
This excerpt appears with permission from Leo Notenboom.