
Quote: Originally Posted by
joodoo

Quote: Originally Posted by
zigzag3143

Quote: Originally Posted by
joodoo
...try deciphering the problem(s) via Event Viewer or with
BlueScreenView.
Just an FYI. Blue screen view often ceremoniously blames OS files. WinDbg is the gold std
Thanks for this.
Although BlueScreenView has been a great boon to me and many others, I will give WinDbg a whirl.
Edit: After installing .net 4 (required) and running the SDK (WinDbg) installer (which failed 3 times), I have decided to stick with BlueScreenView (no installation necessary-just point and click)
for now. I shall try again at a later date....
Final Verdict: SDK is not for the average PC enthusiast-like me.

You dont need SDK to install WinDbg, and many "enthusiasts" are being led astray. With more than 10,000 DMPs under my belt I see them doing useless installs, driver updates, and procedures by its use.
Should you ever want to install WinDBg I would be happy to help you.
WinDbg (when attached to the local machine) runs rings around BSV, who crashed, etc.
It is the gold standard for the serious user.