Microsoft

Video: Troubleshoot Windows blue screen of death (BSOD) with WinDbg

Bill Detwiler shows you how to troubleshoot Windows blue screen of death (BSOD) errors using Microsoft's own WinDbg debugger tool.

Few things are more infamous in the Windows world than the dreaded Blue Screen of Death. They can strike without warning. And, troubleshooting them is often a combination of knowledge, skill, and lots of trial and error. During this TR Dojo episode, I show you a slightly more methodical blue screen troubleshooting approach using Microsoft's own WinDbg debugger tool.

For those who prefer text to video, you can click the Transcript link that appears below the video player window or read Jacky Howe's article, "How do I use WinDBG Debugger to troubleshoot a Blue Screen of Death?"

You'll find the WinDbg debugger tool and related resources on the following Microsoft Web pages:

You can also sign up to receive the latest TR Dojo lessons through one or more of the following methods:

About

Bill Detwiler is Managing Editor of TechRepublic and Tech Pro Research and the host of Cracking Open, CNET and TechRepublic's popular online show. Prior to joining TechRepublic in 2000, Bill was an IT manager, database administrator, and desktop supp...

39 comments
JamesMathewJJ
JamesMathewJJ

Troubleshooting the BSOD error is quite hard as it totally depends on the type of problem. I am using windows 7 and inspite of  using the PC cleaner, I could not be able to resolve the issue. Then after searching on google, I called on the toll-free number of AskPCTechies and they had resolved the issue completely. 

jnager
jnager

It is because your windows has invalid or obsolete items. You need to remove them. I use Digeus Registry Cleaner for this purpose.

asolomon
asolomon

Will this only work with the minidump? Does this utility work on server versions of Windows?

rickclark9
rickclark9

Bill, As always I like Bill's style. This subject and the use of WinDbg is however beyond your average PC user. There are times when a competent computer professional is required. Much simpler methods of basic troubleshooting should be attempted first. What was I doing when I got the BSOD? Was there something new that was installed either application or hardware with drivers? Did I do any critical updates just before this started?

203T
203T

Part II would be GREAT! I've been through this material and managed over the years but would love to see a concise and probably conceptual 'how to'. (part III?)

g.ferguson
g.ferguson

Hi, This looks very useful. Can you please verify the symbols path. It looks like SRV"c:\symbols"http://madl.microsoft.com/download/symbols but that http address cannot be browsed to?? Alternatively, can you tell me how I know which .pdb file will have the symbols I require. I'm looking at a W2008 32-bit dump. Many thanks, Garry

techrepubliclist
techrepubliclist

Since switching to Win7 Ultimate, commercial version, I'm seeing about one (1) per month. Since the beta & RTM versions, I've accrued 25 blue screen mini-dumps.

NickNielsen
NickNielsen

A decade ago, I would see multiples in a day. I've seen one this year so far.

Bill Detwiler
Bill Detwiler

In the above TR Dojo post, I show you how to troubleshoot Windows blue screen of death (BSOD) errors using Microsoft's own WinDbg debugger tool. But, I'm curious to know if BSOD errors are as prevalent today as they were five years ago. Take the poll and in the post above, and let me know. Original post and poll: http://blogs.techrepublic.com.com/itdojo/?p=1682

Editor's Picks