How to find out what is causing a Blue Screen of Death (BSOD) by using the kernel debugger tools

phpinfo()

phpinfo() — Thu, 23 Mar 2023 19:24:21 GMT

Pingback from phpinfo()

How To Find Out What Is Causing Bsod | Information

How To Find Out What Is Causing Bsod | Information — Fri, 14 Oct 2016 03:30:48 GMT

Pingback from How To Find Out What Is Causing Bsod | Information

Blue screen after ~24 hours of folding - Overclock.net - Overclocking.net

Blue screen after ~24 hours of folding - Overclock.net - Overclocking.net — Fri, 11 Jun 2010 12:52:02 GMT

Pingback from Blue screen after ~24 hours of folding - Overclock.net - Overclocking.net

TParker.net » Post Topic » DriveImage XML - Awesome Drive Imaging Tool

TParker.net » Post Topic » DriveImage XML - Awesome Drive Imaging Tool — Mon, 10 Dec 2007 15:45:59 GMT

Pingback from TParker.net » Post Topic » DriveImage XML - Awesome Drive Imaging Tool

re: How to find out what is causing a Blue Screen of Death (BSOD) by using the kernel debugger tools

Alchemist — Mon, 11 Jun 2007 06:56:07 GMT

Hi David, I appreciate your help and your concern,ithanks a lot.Could you please tell me whethere following error message is normal or do we have to do something to fix this. Thanks again Best Regards, Alchemist *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** ***

re: How to find out what is causing a Blue Screen of Death (BSOD) by using the kernel debugger tools

Bob S. — Tue, 05 Jun 2007 19:59:45 GMT

You people probably already know this and may have already discussed it, but Vista and Windows XP Pro x64 and probably other OS's are having issues with running greater than 4GB. I'm running XP Pro x64 and have been seeing the BSOD with various reasons identified. I ran some of the Memory Tests from The Ultimate Boot CD. When I had 4GBs installed, 1 GB (DDR2) per DIMM slot, two slots failed some test. I would switch slots, but as long as I had 4GBs, two out of 4 sticks always indicated a problem. Different slots and different sticks each time after a swap. Finally, I ran the tests with just 2 slots occupied and eventually verified that all 4 sticks were good. My system is working for the moment and recognizes the full 4GBs, but tomorrow when I boot it up again, I may have to boot several times before the OS is up and running or it may go great and crash later or it may run well all day.

re: How to find out what is causing a Blue Screen of Death (BSOD) by using the kernel debugger tools

David Overton — Sun, 06 May 2007 06:09:12 GMT

Michael,

take several crash dumps and see if each one is happening in the same place - if it is, then it is consistent. What often happens if memory is bad is that the dumps show failures all over the place.

Also, what error code is it in the dump - it could be showing something like a memory checksum error, which again points to memory.

If the crash is happening in TCPIP.SYS it does not necessarily point to that file being at fault since th TCP/IP stack works very closely with network drivers it might also be worth updating the network drivers on that box too and making sure that they are certified.

Finally, have you run the Memory Diagnosis tool? Go to oca.microsoft.com/.../windiag.asp and burn the ISO there to a CD and run that for a couple of hours. If you do have faulty memory it should show it up.

thanks

David

re: How to find out what is causing a Blue Screen of Death (BSOD) by using the kernel debugger tools

Michael Carney — Sat, 05 May 2007 22:36:32 GMT

Your blog is fascinating. I just used your "How to find out what is causing a Blue Screen of Death (BSOD)" post, and discovered that my recurring BSOD in Vista Ultimate 32-bit is caused by tcpip.sys . . . Microsoft tech support has said it was the memory, however, not the network . . . do you have any thoughts as to why?

re: How to find out what is causing a Blue Screen of Death (BSOD) by using the kernel debugger tools

Michaele Hicks — Wed, 12 Jul 2006 17:21:47 GMT

Thanx for the info. I've sent it off to the rest of my IT guys.

http://forums.windowsforum.org/index.php?s=e769661e6c0f5c6796c62205046a330b&showtopic=25714&pid=198221&st=0&#entry198221

TrackBack — Sun, 09 Jul 2006 19:42:51 GMT

re: How to find out what is causing a Blue Screen of Death (BSOD) by using the kernel debugger tools

David Overton — Fri, 16 Jun 2006 10:32:52 GMT

So, there I was glad that I had produced this and then read Susan's blog entry at http://msmvps.com/blogs/bradley/archive/2006/06/15/101628.aspx and realised I had carefully re-created the blog entry from http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx. Ho hum, oh well.

ttfn

David