Some of you probably know my name from elsewhere. It's a nice place, I'm impressed with what's done here, looks swell too. I'm probably going to hang around your offline sections a lot, I hope you don't mind!
Anyway, I'm a strapping young lad with a background in computers and experience with science! I'm a competitive computer gamer, lover, pet enthusiast, livestreamer and more. I don't often join new forums, even less often do I stick with them, so consider yourselves lucky . I work with troubled folks offering real life advice in specific areas where most others have not had success, I'm sort of a professional friend to people, which means I love getting to know others and I'm more than open for people to message me about whatever.
I hope to perhaps learn something from this wonderful site, as learning is most certainly fun!
To add to what Corrine has already said, we have no intention of making a BSOD school here, and I doubt it will ever happen, and certainly not soon. That is not how we do things here. We have all our tutorials available for anyone to read, and you can get access to our private areas and tools simply by asking jcgriff2. Everyone is actively encouraged to ask as many questions as they have, and we will do our best to answer them. Also, anyone may post in the BSOD forum for practice. We don't force everyone through a formal school like malware removal schools do (but they do that for good reason). We just make everything available to all. I hope this helps
I will link some of our introductory stuff below.
If you have never debugged a BSOD before, have no idea where to start, which tools you need, or how to get them set up, see here: BSOD Analysis - Getting Started
Once you have done that, and learned the absolute basics, you should learn a few more of the tricks the tools have to offer. This amazing thread should sort that out: BSOD Methods & Tips
And if you are serious, I strongly recommend that you ask jcgriff2 for access to our tools, although the above tutorials should already be available to you.
This is a complicated subject, and it will take you a while to work through all that, but if you can read and absorb at least a little of the first two linked threads, then you will be well on your way to BSOD debugging greatness
I hope you enjoy your time here, and once again I would like to stress that you should ask any, and as many, questions as you have. Good luck!
It is certainly possible to help users (which usually only involves simple techniques and a bit of trail and error), and to perform the advanced analysis techniques listed here (which is quite honestly most of what you need day to day) without reading that book. However, if you want to foray out into advanced analysis in areas not yet outlined here, pulling apart raw memory, then reading relevant excerts of that book is something close to a must.
To be very honest, very few people are actually able to do the amazing stuff VirGnarus does without him having outlined how to do it already. If you ever need to analyse a particular kernel memory dump, he is usually very willing (or just too polite!) to help us out and show us the way, and then we can all do it in the future.
So in conclusion, you can become not just competent, but extremely highly skilled in BSOD analysis without reading that book, but if you want to become a true master, it is going to be a must.
Addition to above post: In conclusion, Windows Internals is not required reading initially, IMO, but if you get into analysis in a big way, feel held back, or want to progress, then it does become a must.
Others would probably say that it is a must immediately. My opinion that it isn't initially required is probably quite contentious, and may in fact be plain wrong!
I would consider myself fairly knowledgeable in BSOD Kernel Dump Analysis. I've been doing it for what I'd say almost a year now, and I have never read Windows Internals in-depth, just very quick glances... but I do want to, just for the extra knowledge it may offer. All the current knowledge I have was either provided by many people here, or self taught. There are courses and mentors, but those are very expensive. BSOD Analysis is not a secret, but you have to really enjoy helping people and enjoy just the general idea of analyzing a crash dump file. Once you've done that, the rest is just read...read...read...research...research...research
The reason it takes so long also is because you also gain knowledge off of real situations when people BSOD and require assistance. Sure, you can go ahead and read all the books and do all of the research in the world, but the real knowledge comes from actually analyzing that dump file and creating your own process when it comes to analyzing crash dump files