LAST_CONTROL_TRANSFER: from 00007ffd1bf428c5 to 00007ffd1bf41d9aĪDDITIONAL_DEBUG_TEXT: Followup set based on attribute from Frame: on thread: Followup set based on attribute from Frame: on thread: Followup set based on attribute from Frame: on thread: Followup set based on attribute from Frame: on thread:īUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ_CALL_LEAK The memory could not be "%s".ĮXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". Some info from the dump:Ġ0007ffd`1bf41d9a ff5010 call qword ptr ĮXCEPTION_RECORD: ffffffffffffffff - (.exr 0xffffffffffffffff)ĮxceptionAddress: 00007ffd1bf41d9a (vmStatsProvider+0x0000000000001d9a)ĮxceptionCode: c0000005 (Access violation)Īttempt to read from address 00007ffd241fe520ĮRROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". I've tried to look at procdump, however I don't have any experience with windbg therefore I'm unable to conclude anything from the output.
Server has latest security and feature updates, also. Tried different vmtools versions including newest 10.1.7, still the same problem. We have faulting application errors every ~5-10 minutes on our 2016 servers with vm tools:įaulting application name: WmiApSrv.exe, version: 3.0, time stamp: 0x57899ac8įaulting module name: vmStatsProvider.dll, version: 10.2, time stamp: 0x57426effįaulting application start time: 0x01d2f499b7b2dbdeįaulting application path: C:\WINDOWS\system32\wbem\WmiApSrv.exeįaulting module path: C:\Program Files\VMware\VMware Tools\vmStatsProvider\win64\vmStatsProvider.dll
0 kommentar(er)
