search

secondlife / jira-archive

3 stars 0 forks source link

[BUG-8711] Viewer crashes frequently when using Norman Antivirus Security Suite unless HttpPipelining is disabled. #16299

Open sl-service-account opened 9 years ago

sl-service-account commented 9 years ago

This issue is related to the problem with Forticlient+pipelining filed at BUG-8631 but symptoms are different in that there is no obvious visible corruption of mesh & textures and the crash takes longer to reproduce unless you are in a busy area, so I thought it was worth a seperate issue.

Steps To Reproduce

Network Information

Attachments

Links

Related

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-8711 | | Summary | Viewer crashes frequently when using Norman Antivirus Security Suite unless HttpPipelining is disabled. | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Whirly Fizzle (whirly.fizzle) | | Created at | 2015-03-07T22:30:10Z | | Updated at | 2015-03-09T17:32:52Z | ``` { 'Business Unit': ['Platform'], 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': '.', 'What were you doing when it happened?': 'Filling in...', 'What were you expecting to happen instead?': '.', } ```
sl-service-account commented 9 years ago

Whirly Fizzle commented at 2015-03-08T02:19:53Z

Once Norman Antivirus Security Suite was uninstalled and my usual antivirus was reinstalled (AVG), the BSOD's when logging into SL also stopped.

Poking at the BSOD memory.dmp indicates the BSOD was some kind of networking crash - way over my head but seems to be a crash when trying to inject a UDP packet & definitely caused by Norman Antivirus Security Suite.

4: kd> .symfix; .reload
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols

Loading unloaded module list
.....

************* Symbol Loading Error Summary **************
Module name            Error
SharedUserData         No error - symbol load deferred

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800185f1d8, The address that the exception occurred at
Arg3: fffff88004157358, Exception Record Address
Arg4: fffff88004156bb0, Context Record Address

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

*** ERROR: Module load completed but symbols could not be loaded for ale7_nf64.sys

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

FAULTING_IP: 
tcpip!IppJoinPath+328
fffff880`0185f1d8 4c396b10        cmp     qword ptr [rbx+10h],r13

EXCEPTION_RECORD:  fffff88004157358 -- (.exr 0xfffff88004157358)
ExceptionAddress: fffff8800185f1d8 (tcpip!IppJoinPath+0x0000000000000328)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000780010
Attempt to read from address 0000000000780010

CONTEXT:  fffff88004156bb0 -- (.cxr 0xfffff88004156bb0;r)
rax=0000000000000001 rbx=0000000000780000 rcx=fffff88004157590
rdx=fffff88004157760 rsi=0000000000000000 rdi=fffff88004157760
rip=fffff8800185f1d8 rsp=fffff88004157590 rbp=fffff880041577b0
 r8=0000000000000000  r9=0000000000000000 r10=fffff880009b3ac0
r11=fffff880041576c8 r12=fffffa800cdf4b40 r13=0000000000000000
r14=fffff88004157ac0 r15=0000000000000002
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
tcpip!IppJoinPath+0x328:
fffff880`0185f1d8 4c396b10        cmp     qword ptr [rbx+10h],r13 ds:002b:00000000`00780010=????????????????
Last set context:
rax=0000000000000001 rbx=0000000000780000 rcx=fffff88004157590
rdx=fffff88004157760 rsi=0000000000000000 rdi=fffff88004157760
rip=fffff8800185f1d8 rsp=fffff88004157590 rbp=fffff880041577b0
 r8=0000000000000000  r9=0000000000000000 r10=fffff880009b3ac0
r11=fffff880041576c8 r12=fffffa800cdf4b40 r13=0000000000000000
r14=fffff88004157ac0 r15=0000000000000002
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
tcpip!IppJoinPath+0x328:
fffff880`0185f1d8 4c396b10        cmp     qword ptr [rbx+10h],r13 ds:002b:00000000`00780010=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000780010

READ_ADDRESS:  0000000000780010 

FOLLOWUP_IP: 
fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a
fffff880`01a50066 85c0            test    eax,eax

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88001927b15 to fffff8800185f1d8

STACK_TEXT:  
fffff880`04157590 fffff880`01927b15 : 00000000`00000000 fffff880`04157760 fffff880`0196d9a0 00000000`00000011 : tcpip!IppJoinPath+0x328
fffff880`041576d0 fffff880`01a50066 : 00000000`00000000 61626364`00000000 00000000`00000000 00000000`00000000 : tcpip!IppInspectBuildHeaders+0x445
fffff880`041579b0 fffff880`04207fc1 : fffffa80`1373a5a0 fffff880`00000014 00000000`00000000 00000000`00000002 : fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x20a
fffff880`04157a50 fffff800`03128b8a : fffffa80`0d582b50 00000000`00000080 fffffa80`0ca725f0 fffffa80`0d582b50 : ale7_nf64+0x7fc1
fffff880`04157c00 fffff800`02e7b8e6 : fffff880`009b3180 fffffa80`0d582b50 fffff880`009be0c0 fffffa80`0cfa0c60 : nt!PspSystemThreadStartup+0x5a
fffff880`04157c40 00000000`00000000 : fffff880`04158000 fffff880`04152000 fffff880`04157710 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fwpkclnt

IMAGE_NAME:  fwpkclnt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  533f5b09

STACK_COMMAND:  .cxr 0xfffff88004156bb0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

BUCKET_ID:  X64_0x7E_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_fwpkclnt!fwpsconstructipheaderfortransportpacket0+20a

FAILURE_ID_HASH:  {d08c9d47-4138-022d-381f-4ae3456cadf9}

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