Hi Kitty,
There is a hotfix available for NETIO.SYS, which corrects a problem in the
ALE (Application Layer Enforcement) component. The problem specifically
corrected by the hotfix does *NOT* exactly match the callstack in your dump
below. However, your dump is clearly referring to ALE (eg the call to
tcpip!WfpAleEndpointTeardownHandler) and Windows Filtering Platform (WFP) -
so, it is somewhat related. You may be seeing a side-effect of the same or
similar problem, which crashes in a slightly different way on your machine.
See:
http://support.microsoft.com/kb/929547/en-us
The first parameter to your STOP message is 0xC0000005, meaning and Access
Violation, aka invalid memory reference. One of the threads running in
NETIO.SYS tried to touch a region of memory it did not have access to - in
this case, address 00000000; so something was passed a NULL pointer. In
kernel mode this is a fatal error and processing cannot continue reliably,
so the machine halts before any damage is done to your data (ie "Blue
screen"). As a rule of thumb, NULL pointers are usually programming bugs
somewhere or other (although maybe not in NETIO.SYS itself - it might just
be the victim of a problem elsewhere in the stack).
As a first step, I'd recommend opening a Service Request with Microsoft
PSS. Get the 929547 hotfix and try it out. If that doesn't fix the problem,
see if they can debug the memory dump, since it looks like you have a pretty
easy-to-reproduce problem scenario, on brand-name hardware. If Microsoft PSS
don't want to debug a dump for a single consumer end-user (possible) maybe
you could hassle Hewlett-Packard support instead - I believe they support
their OEM edition of Vista on their hardware, and they certainly have
engineers who can debug Windows memory dumps.
Good luck with it,
--
Andrew McLaren
amclar (at) optusnet dot com dot au