The article went on at length about an offending file. Of course, there is no guarantee that your problem is a file or reference problem.
My first suggestion would be that you not bother with debugging if you have no technical experience, or if you aren't technically inclined, or if you can't look up references at the MS site or others. This article, and site in general, is geared toward professionals, so you may get lost if you have no IT background.
Did you try looking up the BSOD code itself? Frequently, that is sufficient, and debugging is just unnecessary work.
"The only thing I got next was another link for hardware disk."
I couldn't make any sort of decent guess without any background or debug data for your problem. Again, just looking up the STOP code is always the best first step.
For further help, open your very own Question, since most folks won't be stopping back at this older article. You can add a link to this article and thread for extra background. Post the STOP code (you could even use it for the post title), and tell us what OS, edition, and service pack level you are using. I'm sure we can point you in the right direction.
Keep Up with TechRepublic