.net framework wmi crash problem
- From: adriantar <adriantar@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 9 May 2006 07:24:02 -0700
Hello,
We made a windows service that expose instance of a class to WMI, using .NET
1.1 System.Management. We made also a WMI reader in C++ that reads the
exposed values using WMI queries.
The problem is that after a time of normal functioning (sometimes days), the
exposed wmi instances become unreachable when I query with wbemtest.exe, the
WMI service is scrambled and finally the test service will crash.
In event log a record is written with: “The TestWMIService is terminated
unexpectedly” and “.NET Runtime version 1.1.4322.2300- testwmiservice.exe -
Common Language Runtime Debugging Services: Application has generated an
exception that could not be handled. Process id=0x488 (1160), Thread
id=0x14c0 (5312)”
If the test service is not yet down and if I restart the WMI service,
without restarting my service, all came back to normal. Because my
application is so simple with no threads, synchronization etc and still
crashing; I suspect that an unhandled exception is thrown from WMI dynamic
provider that .NET automatically generate.
We attached an adplus in crash mode to the our test service and to the
svchost.exe. After a while the service has thrown multiple 1 chance “Access
violation - code c0000005” that shown problems with fastprox or mscorwks.
The test server is Windows 2003 Server with SP1, but the same thing happens
on multiple WindowsXP Pro with SP2.
(the strange thing is that on the 2003 Server boxes it crash more rapidly
that on XP stations).
Thank you.
Some memory dumps:
PID-3248__TESTWMISERVICE.EXE__1st_chance_AccessViolation__mini_08D4_2006-05-08_12-37-43-365_0CB0.dmp
Comment: '1st_chance_AccessViolation_exception_in_TESTWMISERVICE.EXE_running'
Windows Server 2003 Version 3790 (Service Pack 1) MP (2 procs) Free x86
compatible
(cb0.cbc): Access violation - code c0000005 (first/second chance not
available)
eax=0369e008 ebx=00000000 ecx=0369e4d0 edx=00000000 esi=001555c0 edi=0369e4d0
eip=755516a0 esp=00bffd10 ebp=00bffd3c iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
fastprox!CWbemInstance::`vftable':
755516a0 858855759488 test [eax+0x88947555],ecx ds:0023:8bfe555d=????????
0:002> !analyze -v
FAULTING_IP:
fastprox!CWbemInstance::`vftable'+0
755516a0 858855759488 test [eax+0x88947555],ecx
EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: 755516a0 (fastprox!CWbemInstance::`vftable')
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 8bfe555d
Attempt to read from address 8bfe555d
DEFAULT_BUCKET_ID: APPLICATION_FAULT
PROCESS_NAME: testwmiservice.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced
memory at "0x%08lx". The memory could not be "%s".
READ_ADDRESS: 8bfe555d
BUGCHECK_STR: ACCESS_VIOLATION
MANAGED_STACK: !dumpstack -EE
No export dumpstack found
LAST_CONTROL_TRANSFER: from 79201887 to 755516a0
STACK_TEXT:
00bffd3c 79201887 00000001 00bffd74 00bffda4 fastprox!CWbemInstance::`vftable'
00bffd4c 00cc0406 00bffd58 0369e4d0 00000000 mscorwks!Interop::Release+0x1d
WARNING: Frame IP not in any known module. Following frames may be wrong.
00bffda4 79232abb 00bffe20 7921a9c6 ffffffff 0xcc0406
00bffe30 79232b7d 011cfcf0 001555c0 00159ac8
mscorwks!MethodTable::CallFinalizer+0xee
00bffe44 79240302 011cfcf0 77e670b2 00000000 mscorwks!CallFinalizer+0x84
00bffedc 791b989e 011cfcf0 00000000 00000000 mscorwks!CallFinalizer+0x255
00bfff24 791cede0 00000000 80915714 7ffdc000
mscorwks!GCHeap::FinalizerThreadStart+0xc2
00bfffb8 77e66063 00155778 00000000 00000000
mscorwks!Thread::intermediateThreadProc+0x44
00bfffec 00000000 791ced9f 00155778 00000000 kernel32!BaseThreadStart+0x34
STACK_COMMAND: ~2s; .ecxr ; kb
FOLLOWUP_IP:
fastprox!CWbemInstance::`vftable'+0
755516a0 858855759488 test [eax+0x88947555],ecx
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: fastprox!CWbemInstance::`vftable'+0
MODULE_NAME: fastprox
IMAGE_NAME: fastprox.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 424377ac
FAILURE_BUCKET_ID: ACCESS_VIOLATION_fastprox!CWbemInstance::_vftable_+0
BUCKET_ID: ACCESS_VIOLATION_fastprox!CWbemInstance::_vftable_+0
Followup: MachineOwner
.
- Follow-Ups:
- RE: .net framework wmi crash problem
- From: adriantar
- RE: .net framework wmi crash problem
- Prev by Date: Re: Bus Speed/HTT
- Next by Date: VBS: Using SystemUpTime from Win32_PerfFormattedData_PerfOS_System effectively
- Previous by thread: Simple WMI provider crashing.
- Next by thread: RE: .net framework wmi crash problem
- Index(es):
Relevant Pages
|