Comments on: Help Troubleshoot the Blue Screen of Death by Preventing Automatic Reboot http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/ Computer Help from your Friendly How-To Geek Sun, 08 Nov 2009 07:56:33 -0600 http://wordpress.org/?v=2.8.5 hourly 1 By: Erik http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/comment-page-1/#comment-74784 Erik Wed, 29 Jul 2009 21:42:37 +0000 http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/#comment-74784 Ok, so i froze the blue screen and wrote down the error code...now how do i find and fix the error? Ok, so i froze the blue screen and wrote down the error code…now how do i find and fix the error?

]]> By: bob http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/comment-page-1/#comment-68291 bob Sat, 07 Mar 2009 21:50:04 +0000 http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/#comment-68291 hi. a curly one.how can we convert flv and wmv downloaded medical clips to mpeg2?.this according to panasonic is required,to enable us (national digestive disorders trust,reg. no ak/1295197)to view the dvd-rw on a panasonic dmr-es15 video recorder/player.we hope you will respond personally,(or steer us in the right direction) to the above email address,thanks in advance,bob tasman. hi. a curly one.how can we convert flv and wmv downloaded medical clips to mpeg2?.this according to panasonic is required,to enable us (national digestive disorders trust,reg. no ak/1295197)to view the dvd-rw on a panasonic dmr-es15 video recorder/player.we hope you will respond personally,(or steer us in the right direction) to the above email address,thanks in advance,bob tasman.

]]> By: Lara W. http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/comment-page-1/#comment-56477 Lara W. Sat, 23 Aug 2008 14:05:43 +0000 http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/#comment-56477 Ah, you're the best! Marry me? ;-) Ah, you’re the best! Marry me? ;-)

]]> By: Mihai Criveti http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/comment-page-1/#comment-30856 Mihai Criveti Mon, 24 Dec 2007 16:41:18 +0000 http://www.howtogeek.com/howto/windows-vista/help-troubleshoot-the-blue-screen-of-death-by-preventing-automatic-reboot/#comment-30856 Hi. Nice blog by the way. Here's a couple more ways to get even more details from a Windows system crash: I should point out that the errors will show up in Windows Event Viewer and, of course, in the kernel memory dump or minidumps if you have WinDbg. Start - run - eventvwr.msc to start the Windows Event Viewer. Vista has an interesting tool called the "Reliability Monitor" which monitors various crashes also. Start - run - perfmon.msc Anyway, if you install Microsoft Windows Debugging Tools (WinDbg and the Debugging Symbols) you can perform very simple analysis on the memory dumps (it's as simple as loading the memory dump in WinDbg and typing "!analyze -v" and maybe looking at the list of loaded drivers (lm kv), running the deadlock verifier (!deadlock), listing memory usage (!vm) and examine the current thread (!thread) and process list (!process 0 0). I've done something a bit more advanced here using Windows Driver Verifier (helps pinpoint faulty drivers) and WinDbg: http://unixsadm.blogspot.com/2007/10/windows-crash-dump-analysis-pinpointing.html I'm simply pointing out that even regular home users can look at the output and get a general idea on what could be wrong with their system. As it turns out, most crashes are caused by bad hardware (a simple memtest86+, sensors and S.M.A.R.T. tests should point that out fairly quickly) and, of course, faulty drivers (usually solved by updating to the latest and greatest version available). With the right tools and a bit of reading, it's simple enough to fix most computer issues :-). Hi. Nice blog by the way. Here’s a couple more ways to get even more details from a Windows system crash:

I should point out that the errors will show up in Windows Event Viewer and, of course, in the kernel memory dump or minidumps if you have WinDbg.

Start – run – eventvwr.msc to start the Windows Event Viewer. Vista has an interesting tool called the “Reliability Monitor” which monitors various crashes also. Start – run – perfmon.msc

Anyway, if you install Microsoft Windows Debugging Tools (WinDbg and the Debugging Symbols) you can perform very simple analysis on the memory dumps (it’s as simple as loading the memory dump in WinDbg and typing “!analyze -v” and maybe looking at the list of loaded drivers (lm kv), running the deadlock verifier (!deadlock), listing memory usage (!vm) and examine the current thread (!thread) and process list (!process 0 0).

I’ve done something a bit more advanced here using Windows Driver Verifier (helps pinpoint faulty drivers) and WinDbg:
http://unixsadm.blogspot.com/2.....nting.html

I’m simply pointing out that even regular home users can look at the output and get a general idea on what could be wrong with their system. As it turns out, most crashes are caused by bad hardware (a simple memtest86+, sensors and S.M.A.R.T. tests should point that out fairly quickly) and, of course, faulty drivers (usually solved by updating to the latest and greatest version available).

With the right tools and a bit of reading, it’s simple enough to fix most computer issues :-) .

]]>