Share via

NETIO.SYS BSOD - Help Needed

Anonymous
2010-03-09T03:24:34+00:00

I have recently upgraded to Windows 7 64-bit and have since been getting the BSOD fairly frequently.

Here is the contents of one of the DMP files:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800142558d, fffff88002984150, 0}

Unable to load image 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 ( NETIO!CalloutStreamDataInit+1d )

Followup: MachineOwner


0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the bugcheck

Arg2: fffff8800142558d, Address of the instruction which caused the bugcheck

Arg3: fffff88002984150, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

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+1d

fffff880`0142558d 488b5808        mov     rbx,qword ptr [rax+8]

CONTEXT:  fffff88002984150 -- (.cxr 0xfffff88002984150)

rax=0000000000000000 rbx=fffff88002984d50 rcx=fffffa8004069810

rdx=fffffa8004737040 rsi=fffff88002984bb0 rdi=00000000000005b4

rip=fffff8800142558d rsp=fffff88002984b30 rbp=fffffa8004737010

 r8=fffff88002984bb0  r9=0000000000000000 r10=0000000000000000

r11=fffffffffffffa4c r12=fffffa8004737010 r13=fffff88002984d00

r14=fffffa8004737010 r15=fffffa8004737010

iopl=0         nv up ei ng nz na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286

NETIO!CalloutStreamDataInit+0x1d:

fffff8800142558d 488b5808        mov     rbx,qword ptr [rax+8] ds:002b:0000000000000008=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  vsmon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800142ec94 to fffff8800142558d

STACK_TEXT: 

fffff88002984b30 fffff8800142ec94 : fffff88002984d50 fffff88002984d50 fffff88002984f50 fffffa80062408c0 : NETIO!CalloutStreamDataInit+0x1d

fffff88002984b70 fffff8800143aa38 : 0000000000000000 fffff88002984f50 fffff88002984d00 fffff88002984d88 : NETIO!StreamInvokeCalloutAndNormalizeAction+0x54

fffff88002984c10 fffff8800143ba31 : fffffa8004737010 fffff88002984f50 fffff88002984d50 fffff880029853a0 : NETIO!StreamCalloutProcessData+0x48

fffff88002984c60 fffff8800143ca68 : fffff88002984d50 fffff880029853a0 fffff88002984f01 fffffa8004737010 : NETIO!StreamCalloutProcessingLoop+0xa1

fffff88002984cf0 fffff8800141d4fa : fffff88002984f50 fffff880038b399c fffffa8000000000 fffffa8004ba0014 : NETIO!StreamProcessCallout+0x1e8

fffff88002984de0 fffff88001406619 : fffff88002980014 fffffa800429ebd0 fffffa8007ef6ac8 fffff880029853a0 : NETIO! ?? ::FNODOBFM::`string'+0x71e2

fffff88002984f00 fffff88001407bb1 : fffff88002980014 fffffa800429ebd0 fffffa8004ba4450 fffff88000000000 : NETIO!ArbitrateAndEnforce+0x2a9

fffff88002984fd0 fffff8800143ef33 : fffff88002985474 fffffa800429ebd0 0000001400000001 fffff880029853a0 : NETIO!KfdClassify+0x934

fffff88002985340 fffff8800143f51a : 0000000000000000 0000000000000001 0000000000107fc1 fffffa8004ba42e0 : NETIO!StreamInternalClassify+0xf3

fffff88002985410 fffff8800143f90e : 0000000000000014 0000000000000100 0000000000000000 fffffa800471dad0 : NETIO!StreamInject+0x1ca

fffff880029854e0 fffff88001494dd7 : fffffa8004ba42e0 0000000000000100 fffffa8004a37bc0 fffff88002ccfe00 : NETIO!FwppStreamInject+0x12e

fffff88002985570 fffff88002cc5f27 : 0000000000000000 fffffa8004a37bc0 fffffa800512d250 0000000000000000 : fwpkclnt!FwpsStreamInjectAsync0+0xcf

fffff880029855d0 0000000000000000 : fffffa8004a37bc0 fffffa800512d250 0000000000000000 0000000000000100 : vsdatant+0xcf27

FOLLOWUP_IP:

NETIO!CalloutStreamDataInit+1d

fffff880`0142558d 488b5808        mov     rbx,qword ptr [rax+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  NETIO!CalloutStreamDataInit+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

STACK_COMMAND:  .cxr 0xfffff88002984150 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_NETIO!CalloutStreamDataInit+1d

BUCKET_ID:  X64_0x3B_NETIO!CalloutStreamDataInit+1d

Followup: MachineOwner


Can anyone decypher this for me?

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2010-03-09T16:37:16+00:00

The ZoneAlarm driver the vsdatant.sys is on the stack:

STACK_TEXT: 

fffff88002984b30 fffff8800142ec94 : fffff88002984d50 fffff88002984d50 fffff88002984f50 fffffa80062408c0 : NETIO!CalloutStreamDataInit+0x1d

fffff88002984b70 fffff8800143aa38 : 0000000000000000 fffff88002984f50 fffff88002984d00 fffff88002984d88 : NETIO!StreamInvokeCalloutAndNormalizeAction+0x54

fffff88002984c10 fffff8800143ba31 : fffffa8004737010 fffff88002984f50 fffff88002984d50 fffff880029853a0 : NETIO!StreamCalloutProcessData+0x48

fffff88002984c60 fffff8800143ca68 : fffff88002984d50 fffff880029853a0 fffff88002984f01 fffffa8004737010 : NETIO!StreamCalloutProcessingLoop+0xa1

fffff88002984cf0 fffff8800141d4fa : fffff88002984f50 fffff880038b399c fffffa8000000000 fffffa8004ba0014 : NETIO!StreamProcessCallout+0x1e8

fffff88002984de0 fffff88001406619 : fffff88002980014 fffffa800429ebd0 fffffa8007ef6ac8 fffff880029853a0 : NETIO! ?? ::FNODOBFM::`string'+0x71e2

fffff88002984f00 fffff88001407bb1 : fffff88002980014 fffffa800429ebd0 fffffa8004ba4450 fffff88000000000 : NETIO!ArbitrateAndEnforce+0x2a9

fffff88002984fd0 fffff8800143ef33 : fffff88002985474 fffffa800429ebd0 0000001400000001 fffff880029853a0 : NETIO!KfdClassify+0x934

fffff88002985340 fffff8800143f51a : 0000000000000000 0000000000000001 0000000000107fc1 fffffa8004ba42e0 : NETIO!StreamInternalClassify+0xf3

fffff88002985410 fffff8800143f90e : 0000000000000014 0000000000000100 0000000000000000 fffffa800471dad0 : NETIO!StreamInject+0x1ca

fffff880029854e0 fffff88001494dd7 : fffffa8004ba42e0 0000000000000100 fffffa8004a37bc0 fffff88002ccfe00 : NETIO!FwppStreamInject+0x12e

fffff88002985570 fffff88002cc5f27 : 0000000000000000 fffffa8004a37bc0 fffffa800512d250 0000000000000000 : fwpkclnt!FwpsStreamInjectAsync0+0xcf

fffff880029855d0 0000000000000000 : fffffa8004a37bc0 fffffa800512d250 0000000000000000 0000000000000100 : vsdatant+0xcf27

Your problem is probably similar to what was experienced in the following thread:

http://social.answers.microsoft.com/Forums/en-US/w7hardware/thread/a93e141e-556c-4a9f-9ea4-2809002c9593

Either disable NetBIOS over TCP/IP or uninstall ZonaAlarm.

Was this answer helpful?

0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2010-03-11T04:13:27+00:00

    You're welcome. Good luck!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2010-03-10T22:44:52+00:00

    Thanks for that auggy. Your help is greatly appreciated.

    I contacted ZoneAlarm's technical support and they weren't much help.

    What I have done is start with uninstalling the ZoneAlarm Anti-Phishing/Site Status Toolbar, which seems to have stopped the BSODs so far (fingers crossed).

    Cheers.

    Was this answer helpful?

    0 comments No comments