A different cause of BSoD this time?

[etybagem]

In answer to recent my http://www.sevenforums.com/crashes-debugging/50703-repeated-bsod-when-logged-onto-internet.html post KenJ+ kindly told me that the dmp file indicated that a BSoD appeared as though it could have been caused by an HdAudio.sys issue. As Device manager indicated that my High Definition Audio Device (HDAD) had up-to-date drivers and I also had up-to-date drivers for my installed SB X-Fi Xtreme Audio PCI card I hoped to address the issue by disabling the HDAD.
That may have worked but I have just had a BSoD caused by netio.sys, although I'm not quite sure what that is - perhaps the attached dmp file will allow some kind person to give me a clue as to what netio.sys is/does and if there is a potential cure for this particular BSoD - no doubt there will be future BSoD for other reasons, although with XP I never experienced that phenomenon!
From other posts I gather that some posters believe that ZoneAlarm might be the cause of the netio.sys problems but taht is not universal and in any case I am reluctant to dump it as I recently subscribed to it for another year, not having had problems with it under XP; the version I run is ZoneAlarm Extreme Security v. 9.0.114.000 with ZA Forcefield v. 1.5.36.15. (NB in case it is relevant I also run Spyware Doctor v. 7.0.0.508.)
:sarc:

 

[zigzag3143]

In answer to recent my http://www.sevenforums.com/crashes-debugging/50703-repeated-bsod-when-logged-onto-internet.html post KenJ+ kindly told me that the dmp file indicated that a BSoD appeared as though it could have been caused by an HdAudio.sys issue. As Device manager indicated that my High Definition Audio Device (HDAD) had up-to-date drivers and I also had up-to-date drivers for my installed SB X-Fi Xtreme Audio PCI card I hoped to address the issue by disabling the HDAD.
That may have worked but I have just had a BSoD caused by netio.sys, although I'm not quite sure what that is - perhaps the attached dmp file will allow some kind person to give me a clue as to what netio.sys is/does and if there is a potential cure for this particular BSoD - no doubt there will be future BSoD for other reasons, although with XP I never experienced that phenomenon!
From other posts I gather that some posters believe that ZoneAlarm might be the cause of the netio.sys problems but taht is not universal and in any case I am reluctant to dump it as I recently subscribed to it for another year, not having had problems with it under XP; the version I run is ZoneAlarm Extreme Security v. 9.0.114.000 with ZA Forcefield v. 1.5.36.15. (NB in case it is relevant I also run Spyware Doctor v. 7.0.0.508.)
:sarc:

Hi and welcome

wel here is some validation for the zone alarmists. while no smoking gun for sure the fact that it is in the stack and sybols couldnt be loaded is starting to look like it is correct.

BTW thanks for the mention.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\123109-32734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8403f000 PsLoadedModuleList = 0x84187810
Debug session time: Thu Dec 31 05:34:35.560 2009 (GMT-5)
System Uptime: 0 days 1:28:17.951
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8a17701d, 9384b614, 0}

[I][B]Unable to load image \SystemRoot\system32\DRIVERS\vsdatant.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : NETIO.SYS [/B][/I]( NETIO!CalloutStreamDataInit+e )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[B]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8a17701d, The address that the exception occurred at
Arg3: 9384b614, Trap Frame
Arg4: 00000000[/B]

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
NETIO!CalloutStreamDataInit+e
8a17701d 8b5004          mov     edx,dword ptr [eax+4]

TRAP_FRAME:  9384b614 -- (.trap 0xffffffff9384b614)
ErrCode = 00000000
eax=00000000 ebx=897796f8 ecx=00000000 edx=000005b0 esi=9384b798 edi=9384b6d8
eip=8a17701d esp=9384b688 ebp=9384b694 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
NETIO!CalloutStreamDataInit+0xe:
8a17701d 8b5004          mov     edx,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

[B]PROCESS_NAME:  vsmon.exe[/B]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8a1774ea to 8a17701d

STACK_TEXT:  
9384b694 8a1774ea 897796f8 87016ddc 9384b6b4 NETIO!CalloutStreamDataInit+0xe
9384b6dc 8a17789c 9384b778 87016dc0 87016dc0 NETIO!StreamInvokeCalloutAndNormalizeAction+0x2f
9384b70c 8a1779b7 9384b778 87016dc0 87016dc0 NETIO!StreamCalloutProcessData+0x31
9384b74c 8a177e1d 9384b778 87016dc0 87016dc0 NETIO!StreamCalloutProcessingLoop+0x55
9384b7b8 8a165f56 00000014 8f15f2d8 00000000 NETIO!StreamProcessCallout+0x128
9384b81c 8a150334 00000014 89624500 893640e0 NETIO!ProcessCallout+0x120
9384b890 8a14f25c 00000014 89624500 893640e0 NETIO!ArbitrateAndEnforce+0xae
9384b9a0 8a176ab0 00000014 89624500 893640e0 NETIO!KfdClassify+0x1c7
9384ba2c 8a178305 00007533 00000014 89624500 NETIO!StreamInternalClassify+0x84
9384ba88 8a173d2d 00000014 89364008 86d68a68 NETIO!StreamInject+0x13f
9384bacc 8a35cc5b 00000388 00000000 00000100 NETIO!FwppStreamInject+0xde
9384bb04 8f63dbeb 8936d238 00000000 00000000 fwpkclnt!FwpsStreamInjectAsync0+0x93
WARNING: Stack unwind information not available. Following frames may be wrong.
9384bb64 8f63b81d 86d68a68 88deb860 0274e78c vsdatant+0xebeb
9384bb8c 8f64c12d 0274e78c 00000001 88deb860 vsdatant+0xc81d
9384bbb0 8f64c9de 87603038 00000001 0274e78c vsdatant+0x1d12d
9384bbe8 8f64ab69 87307028 88deb848 87307028 vsdatant+0x1d9de
9384bbfc 8407b4bc 87307028 88deb848 88deb848 vsdatant+0x1bb69
9384bc14 8427ceee 87603038 88deb848 88deb8b8 nt!IofCallDriver+0x63
9384bc34 84299cd1 87307028 87603038 00000000 nt!IopSynchronousServiceTail+0x1f8
9384bcd0 8429c4ac 87307028 88deb848 00000000 nt!IopXxxControlFile+0x6aa
9384bd04 8408242a 000003bc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
9384bd04 76ef64f4 000003bc 00000000 00000000 nt!KiFastCallEntry+0x12a
0274e6f4 00000000 00000000 00000000 00000000 0x76ef64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!CalloutStreamDataInit+e
8a17701d 8b5004          mov     edx,dword ptr [eax+4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  NETIO!CalloutStreamDataInit+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf63

FAILURE_BUCKET_ID:  0x8E_NETIO!CalloutStreamDataInit+e

BUCKET_ID:  0x8E_NETIO!CalloutStreamDataInit+e

Followup: MachineOwner
---------

 

[etybagem]

Zone Alarm

On checking the ZA site after the reply I saw that there is a version of ZA Extreme Security to download and install if you have installed a release version of W7 rather than the beta version of W7; there is afree upgrade for subscribers or a free 15-day trial for others. I have now upgraded to the latest ZAES (v. 9.1.008.000) and hope that might resolve issues.
Thanks for the help and advise.
Etybagem.