What do people do to solve a total system lock up? By this, I mean
that nothing responds, except the Reset button. Mouse does not move, and
most of all - I cannot use Ctrl+D for SoftICE.
To date, I just used to revert to an older version of the tested
driver which didn’t lock up.
Before everyone suggests WinDBG, let me just say that I could not
get it to work (tried the latest version in March 2002, gave up after
that), and I cannot get a NULL modem cable here:-)
–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers.
Alfa File Protector - File protection and hiding library for Win32
developers.
If you can’t break into SoftIce (never had this happen with a filesystem
filter, maybe you corrupted some memory that caused a hardware driver to
lock up with interrupts off?), then you can try manually generating a
crashdump file like this (from the WinDbg docs):
“In the registry path
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters
, create a key named CrashOnCtrlScroll, and set it equal to REG_DWORD
0x1 (or any nonzero value). The system must be rebooted before these
changes will take effect. After this has been done, the keyboard crash
can be initiated as follows. Hold down the rightmost CTRL key, and press
the SCROLL LOCK key twice. It is possible for a system to freeze in such
a way that this CTRL+SCROLL LOCK+SCROLL LOCK sequence will not work.
However, this should be a very rare occurrence. The CTRL+SCROLL
LOCK+SCROLL LOCK crash initiation will work even in many instances where
CTRL+ALT+DEL does not work.”
You don’t have to set up the null-modem cable to debug a crashdump file
using WinDbg. You just need to set the source paths correctly. I’ve
debugged many hangs this way on machines where I didn’t want to install
SoftIce.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dejan Maksimovic
Sent: Saturday, November 23, 2002 2:32 AM
To: File Systems Developers
Subject: [ntfsd] Solving total system lock up
What do people do to solve a total system lock up? By
this, I mean that nothing responds, except the Reset button.
Mouse does not move, and most of all - I cannot use Ctrl+D
for SoftICE.
To date, I just used to revert to an older version of the
tested driver which didn’t lock up.
Before everyone suggests WinDBG, let me just say that I
could not get it to work (tried the latest version in March
2002, gave up after that), and I cannot get a NULL modem cable here:-)
–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32
developers. Alfa File Protector - File protection and hiding
library for Win32 developers.
You are currently subscribed to ntfsd as: xxxxx@nryan.com
To unsubscribe send a blank email to %%email.unsub%%
Good suggestion. Unfortunately, this didn’t work either:-(
Nicholas Ryan wrote:
If you can’t break into SoftIce (never had this happen with a filesystem
filter, maybe you corrupted some memory that caused a hardware driver to
lock up with interrupts off?), then you can try manually generating a
crashdump file like this (from the WinDbg docs):
“In the registry path
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters
, create a key named CrashOnCtrlScroll, and set it equal to REG_DWORD
0x1 (or any nonzero value). The system must be rebooted before these
changes will take effect. After this has been done, the keyboard crash
can be initiated as follows. Hold down the rightmost CTRL key, and press
the SCROLL LOCK key twice. It is possible for a system to freeze in such
a way that this CTRL+SCROLL LOCK+SCROLL LOCK sequence will not work.
However, this should be a very rare occurrence. The CTRL+SCROLL
LOCK+SCROLL LOCK crash initiation will work even in many instances where
CTRL+ALT+DEL does not work.”
You don’t have to set up the null-modem cable to debug a crashdump file
using WinDbg. You just need to set the source paths correctly. I’ve
debugged many hangs this way on machines where I didn’t want to install
SoftIce.
–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers.
Alfa File Protector - File protection and hiding library for Win32
developers.
I remember the old Macs had a ‘debug switch’ you could install on the
side to force a break into MacsBug when all else fails. 
Maybe there’s
something like this for the PC that doesn’t involve installing something
between the CPU and the motherboard… Anybody know?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dejan Maksimovic
Sent: Sunday, November 24, 2002 11:42 AM
To: File Systems Developers
Subject: [ntfsd] RE: Solving total system lock up
Good suggestion. Unfortunately, this didn’t work either:-(
Nicholas Ryan wrote:
> If you can’t break into SoftIce (never had this happen with a
> filesystem filter, maybe you corrupted some memory that caused a
> hardware driver to lock up with interrupts off?), then you can try
> manually generating a crashdump file like this (from the
WinDbg docs):
>
> “In the registry path
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Paramete
> rs
> , create a key named CrashOnCtrlScroll, and set it equal to
REG_DWORD
> 0x1 (or any nonzero value). The system must be rebooted before these
> changes will take effect. After this has been done, the
keyboard crash
> can be initiated as follows. Hold down the rightmost CTRL
key, and press
> the SCROLL LOCK key twice. It is possible for a system to
freeze in such
> a way that this CTRL+SCROLL LOCK+SCROLL LOCK sequence will not work.
> However, this should be a very rare occurrence. The CTRL+SCROLL
> LOCK+SCROLL LOCK crash initiation will work even in many instances
> LOCK+where
> CTRL+ALT+DEL does not work.”
>
> You don’t have to set up the null-modem cable to debug a crashdump
> file using WinDbg. You just need to set the source paths correctly.
> I’ve debugged many hangs this way on machines where I
didn’t want to
> install SoftIce.
–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32
developers. Alfa File Protector - File protection and hiding
library for Win32 developers.
You are currently subscribed to ntfsd as: xxxxx@nryan.com
To unsubscribe send a blank email to %%email.unsub%%
The old Periscope software package had a switch that connected from the case
to pin one of the ISA bus. This triggered a NMI which could not be disabled
except with a special command to external (not in the CPU) hardware. CLI
still won’t inhibit NMI, but the chipsets have to have the capability as
dynamic ram generates NMIs until it has been written to several times during
POST. I am sure it still exists, but you would need to know which pin in
the PCI bus is NMI. The Periscope Model 1 had the switch connected to that
card with a RCA jack. Someone could create a simple PCI card with the NMI
activated by an external switch. SoftIce can be told to look for INT 1,
which is where NMI is routed. For most of my driver debugging, I use INT 1
because on 9x INT 3 is used by too many other components of the OS.
----- Original Message -----
From: “Nicholas Ryan”
To: “File Systems Developers”
Sent: Sunday, November 24, 2002 3:43 PM
Subject: [ntfsd] RE: Solving total system lock up
> I remember the old Macs had a ‘debug switch’ you could install on the
> side to force a break into MacsBug when all else fails. Maybe there’s
> something like this for the PC that doesn’t involve installing something
> between the CPU and the motherboard… Anybody know?
>
> - Nicholas Ryan
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Dejan Maksimovic
> > Sent: Sunday, November 24, 2002 11:42 AM
> > To: File Systems Developers
> > Subject: [ntfsd] RE: Solving total system lock up
> >
> >
> >
> > Good suggestion. Unfortunately, this didn’t work either:-(
> >
> > Nicholas Ryan wrote:
> >
> > > If you can’t break into SoftIce (never had this happen with a
> > > filesystem filter, maybe you corrupted some memory that caused a
> > > hardware driver to lock up with interrupts off?), then you can try
> > > manually generating a crashdump file like this (from the
> > WinDbg docs):
> > >
> > > “In the registry path
> > >
> > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Paramete
> > > rs
> > > , create a key named CrashOnCtrlScroll, and set it equal to
> > REG_DWORD
> > > 0x1 (or any nonzero value). The system must be rebooted before these
> > > changes will take effect. After this has been done, the
> > keyboard crash
> > > can be initiated as follows. Hold down the rightmost CTRL
> > key, and press
> > > the SCROLL LOCK key twice. It is possible for a system to
> > freeze in such
> > > a way that this CTRL+SCROLL LOCK+SCROLL LOCK sequence will not work.
> > > However, this should be a very rare occurrence. The CTRL+SCROLL
> > > LOCK+SCROLL LOCK crash initiation will work even in many instances
> > > LOCK+where
> > > CTRL+ALT+DEL does not work.”
> > >
> > > You don’t have to set up the null-modem cable to debug a crashdump
> > > file using WinDbg. You just need to set the source paths correctly.
> > > I’ve debugged many hangs this way on machines where I
> > didn’t want to
> > > install SoftIce.
> >
> > –
> > Kind regards, Dejan M. www.alfasp.com
> > E-mail: xxxxx@alfasp.com ICQ#: 56570367
> > Alfa File Monitor - File monitoring library for Win32
> > developers. Alfa File Protector - File protection and hiding
> > library for Win32 developers.
> >
> >
> >
> >
> > —
> > You are currently subscribed to ntfsd as: xxxxx@nryan.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to %%email.unsub%%
A couple of months ago I was dealing with frozen system problem. The only
way to get into system was WinDbg. We tried to use some BSOD generating
tools (e.g BANG), but it didn’t work because IRQL were masked. So the only
way was /DEBUG and WindDbg. In our case we had 2 RUNNING threads (on 2 CPU
system) that were running around Spin Locks and so masking other lower IRQs.
You can find some more info about this problem, if you search for “frozen
system” in NTDEV list.
WBR Primoz
-----Original Message-----
From: Dejan Maksimovic [mailto:xxxxx@alfasp.com]
Sent: Saturday, November 23, 2002 11:32 AM
To: File Systems Developers
Subject: [ntfsd] Solving total system lock up
What do people do to solve a total system lock up? By this, I mean that
nothing responds, except the Reset button. Mouse does not move, and most of
all - I cannot use Ctrl+D for SoftICE.
To date, I just used to revert to an older version of the tested driver
which didn’t lock up.
Before everyone suggests WinDBG, let me just say that I could not get it
to work (tried the latest version in March 2002, gave up after that), and I
cannot get a NULL modem cable here:-)
–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers. Alfa File
Protector - File protection and hiding library for Win32 developers.
You are currently subscribed to ntfsd as: xxxxx@hermes.si To
unsubscribe send a blank email to %%email.unsub%%