Re: Lockup debugging

From: Doron Holan [MS] (doronh_at_nospam.microsoft.com)
Date: 12/09/04 

Date: Thu, 9 Dec 2004 08:36:18 -0800

if crash on control + scroll lock doesn't work, either you have not set the
setting properly (have you verified this crashes the machine when it is
running?), or the keyboard interrupt isn't running when the machine locks up
(which means spinning at high irql or a hw lockup). in these cases, getting
the debugger to break in can sometimes be impossible.

d 

-- 
Please do not send e-mail directly to this alias. this alias is for 
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Pete Johnston" <anonymous@discussions.microsoft.com> wrote in message 
news:ujPg8zY3EHA.2540@TK2MSFTNGP09.phx.gbl...
> I've got a dual Xeon W2k3 box that locks up intermittently. I'd like to 
> debug
> or crash it when it stops responding. Ctrl + double ScrollLock doesn't 
> work.
> It's not convenient to have a debugger attached all the time. I wonder if
> the following will work.
>
> - I set /debug /debugport=1394 in boot.ini and boot the box
> - Once the box has locked up, I connect a 1394 cable to a laptop with 
> WinDbg
> - I use WinDbg to debug or crash the box
>
> What are my chances to have WinDbg connected to the target machine when 
> the latter is stuck - ie spinning at a high IRQL?
>
> Can anyone suggest hardware-based solutions to crash a PC with memory 
> dump? Like a cheap PCI card, NIC or whatever, with two wires and a red 
> button soldered to it? Though I am afraid the problem is in video drivers, 
> so even if I managed to crash the computer, I won't get the memory dump 
> anyway.
>
> Thanks
> Pete
>
> -- 
>
>
>
>