Chris Lo <cklo @
>I have just encounter VERY similar crash yesterday, also pointing to
>fw.sys and a IRQL_NOT_LESS_OR_EQUAL thing.
>I've a rule filtering/blacking Java/ActiveX, turn it off and **SEEM* to
>run ok so far.
>Just an experience.
So NT insists on having ActiveX enabled or else it crashes FW1? - scary
There's a /CRASHDEBUG switch which you can use (change boot.ini) to boot the
NT kernel in a debug mode. I think it writes all debug data to one of the
com ports, but I've never used this option myself. You can also config NT to
create a core dump if it crashes, but I have absolutely no idea how one goes
about analysing it.
IMHO, the IRQL error is usually related to some h/w problem, and sometimes
to a low level driver that's not fully compatible, or a bug in the kernel.
Another thing to keep in mind is never to aply a NT Service Patch unless
it's recommended for that h/w platform, or to fix a specific NT bug that
your software on the box runs into. IOW, if the FW1 people do not
specifically recommend using a specific SP then don't install it. SP's are
notorious for introducing a couple of new bugs every time... <sigh>