Whilst trying to wrap my head around what is involved in trying to learn
how to analyze BSOD's, and furthermore analyze and make sense of data generated by Windows event logs (see Event Viewer), I have come
across a series of tutorials, articles and websites which may assist anyone
else looking to learn more about the procedures to take.
This for myself, was after spending several hours trying to learn by way of Instant Messenger which is not really a viable option apparently (thanks for the time anyway zigzag). I am also not the type of person who will allow access to my computer at will so I can sit there and watch as someone else shows an on screen demonstration either, so to state the obvious, the following information is for newcomers like myself who might like to learn more about their machines and the errors which they may be reporting.
The following information is from my favourite on line friend (and the people who put the info there!) who I refer to in many of my posts as Dr Google. Some or maybe even all of these sites have more than likely already been explored by the advanced users of this site, but here are my findings anyway for all us noobies.
1) Troubleshooting Microsoft Windows Event Logs
This is a well layed out website where you can enter the Event ID and Event Source reported by a log from Event Viewer. Various reasons for the event will be returned and many are source specific meaning that if there are 3 or 4 possible causes for example, you will be able to narrow the problem to the specific source error message you can see in the event log.
The majority of services on this site are free however there are fees applicable in relation to viewing advanced solutions which I could see the benefit of if you were say a systems admin or couldn't afford the time to Google around for problem specific info.
2) Troubleshooting Windows STOP Messages
This site actually had the link which led to the above site. Lots of good info here.
3) Windows Debuggers: Part 1: A WinDbg Tutorial - CodeProject®
WinDbg (Windows Debugger) tutorial written by Saikat Sen. Apparently this tutorial is one of the old time staples. There are heaps of other good links at this site to. I was a little disappointed that the tutorial was labelled as Part 1 and there were no futher parts to it but hey........
4) Win XP - BSOD ~ How to use Debugging Tools For Windows - PC Perspective Forums
WinDbg tutorial which refers to Windows XP but this one has some nice step through piccies.
5) Debugging In Progress... - Site Home - TechNet Blogs
Technet blog - obviously!
6) FaultWire Fatal BSoD Solutions
Faultwire - this site is AWESOME!!! - woot woot
7) Maximum PC | Blue Screen of Death Survival Guide: Every Error Explained - Page 1
Maximum PC 4 page article explaining the frequently seen error messages relating to BSOD's
Edit: I forgot to also mention that this forum has some information on BSOD's which can be found at the top of the Crashes and Debugging section, and also, as recommended by various members here, check out these links at carrona.org (with SF contributing members jcgriff2 and Jonathan_King providing valuable input)
Driver reference table for if the WinDbg software can give a good indication of a "Probably caused by"
For driver and download links to various manufacturer sites and software providers
For a comprehensive link list to various antivirus uninstallers should the BSOD team advise that the antivirus be un-installed for running of MalwareBytes and MSE (Microsoft Security Essentials)
And after writing all of that edit I noticed that Anak had mentioned it!!! Thanks Anak
So there it is - in the 2 days I have for the majority been offline here at SF's I have managed to come across a plethora of information. I was told that it was a learn as you go thing and that I wouldn't find anything tutorial like (no offense Ken) out there in the big wide web, but I guess if you seek, you shall find.
I don't profess to know how to solve some/ any/ or all of these problems yet and maybe I never will, but this information certainly won't hurt the cause that's for sure.
I'm not giving up yet!