Before you can attempt to resolve a problem, you have to know what's causing the problem in the first place, or at least have a good idea of what's causing the problem. Otherwise, how will you know what procedure(s) to follow?
The alternative, often suggested here, is to work a through a long list of generic tests that may or may not have anything to do with solving the problem, and then try to figure out what the results mean, or to throw everything at the problem that you think
might work. In my view, not only is this a waste of time, you could end up making things worse. Even if you're lucky enough to hit on something that appears to work, you still won't know what caused the problem in the first place and how to prevent it from
coming back.
Unfortunately, there are no shortcuts here - not if you're looking for a real solution that won't cause trouble for you down the road, like when the next update is released. You have to understand the cause of something before you can address it.
Most people hardly ever see a BSOD and never have to reset their computer. If that's something that happens to you often - as it did to me - you really have to step back and figure out 'what am I doing wrong?'
