by, 03-24-2012 at 07:33 AM (1720 Views)
Just trying to firm up my "intent".........
My primary purpose/goal is to help users.
There is (IMO) a need for BSOD analysts to help users with their BSOD problems.
This differs from standard BSOD analysis in 2 ways:
- there is little need to disassemble instructions to see where a program/driver went wrong. It's enough (for our purposes) to know that the program was at fault. In most cases we don't even have the skills to repair the problem, relying instead on removal and reinstallation to "repair" the problem.
- There are problems that occur frequently in BSOD situations - but aren't collected anywhere. Things like the ASACPI.sys driver problem, or the Daemon Tools issues. They affect a relatively small proportion of the users of that program - but when they do, they are a real problem. The skills of a user-level BSOD analyst must contain a "record" of these problems.
That being said, there is a need for the user-level BSOD analyst to be familiar with disassembly, as some of it's tools are useful in determining sources of errors.
When I started user-level BSOD analysis, it was primarily guess-work. Reading a memory dump and it's !analyze -v output for clues. And then asking the user to attempt to fix the things associated with the clues.
As I became more familiar with this, I found out a couple of things:
- a consolidated reference for BSOD information was needed. Aumha.org was a good source, but it stopped being updated in 2007. So, in 2009, I created the http://www.carrona.org/bsodindx.html page
Next was the lack of a place to put info about BSOD causes. That was (IMO) a major reason that there weren't many user-level BSOD analysts - too much stuff to remember, and you needed too much experience just to get to the point where you remembered it. So along came the Driver Reference Table (DRT).
Initially it was a simple thing, designed primarily to help users find drivers for their BSOD problems. It's precursor, the Drivers and Downloads page ( http://www.carrona.org/drvrdown.html ) was too limited to be of any significant use. The DRT provided a place where we could link as close as possible to the download site for the program associated with an individual driver.
Early on we saw that there was also a need to store information that would help others research problems - so we added that as a second goal: Helping other user-level BSOD analysts to locate information on needed drivers.
As the project grew, so did the number of people involved. And thanks to jcgriff2, Laxer, and several others the input of drivers to the table (and accessing the data in the table) has become much easier.
But it still remains primarily a resource for users and for those helping users.
2 questions then:
- Where do we go from here with the current projects?
- What other direction(s) are there that we might want to consider going in?