Quote:
Originally Posted by chiefblackhammer  Can we stay on topic, offer help to the user or go else where. |
I can see your point, but jeez...that's some tough love. Someone woke up on the wrong side of the bed today.
I don't know about the others, but I was interested in the response to your request for more information. BSOD's are caused by literally hundreds of reasons, so its kind of pointless to guess unless you have more information first.
Your suggestion was the best advice so far, but I also believe that correcting misleading information should be seen as equally valuable to someone trying to understand their OS related issue.
I would add to your suggestion to OP to either write down or take a photo of the actual BSOD so everyone here can see the error code details. It would beat looking for errors in such a round-about way as going through the prompt to the error log, if it turned out to be an issue with a driver listed as the stop error on the BSOD in the first place.