vmconnect (Hyper-V Virtual Machine Connection) dies every time I try to connect to a running VM. Got a dump, but I get wrong symbols despite having _NT_SYMBOL_PATH set to symsrv*symsrv.dll*C:\symbols*http://msdl.microsoft.com/download/symbols.

No idea where to go from here other than to switch to VMWare. We were looking at virtualizing five servers, but from what I've seen so far, Hyper-V is a complete bust.

*** WARNING: Unable to verify checksum for mscorlib.ni.dll

FAULTING_IP:
+0
00000000`00000000 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  000000000000092c

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

PROCESS_NAME:  vmconnect.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG:  2000000

APPLICATION_VERIFIER_FLAGS:  8000

APP:  vmconnect.exe

MANAGED_STACK: !dumpstack -EE
OS Thread Id: 0x92c (0)
Current frame:
Child-SP         RetAddr          Caller, Callee

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS

LAST_CONTROL_TRANSFER:  from 000007fb124c12d2 to 000007fb1548319b

STACK_TEXT:  
000000fb`3f35f6f8 000007fb`124c12d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtWaitForMultipleObjects+0xa
000000fb`3f35f700 000007fa`fbd1d9da : 00000000`00000000 000007f5`ff4b5000 00000000`00000000 00000000`00000000 : KERNELBASE!WaitForMultipleObjectsEx+0xe5
000000fb`3f35f9e0 000007fb`14a51832 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!W32ProcObj::ObjectWorkerThread+0x8a
000000fb`3f35fa30 000007fb`154dd609 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
000000fb`3f35fa60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP:
mstscax!W32ProcObj::ObjectWorkerThread+8a
000007fa`fbd1d9da 83f8ff          cmp     eax,0FFFFFFFFh

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  mstscax!W32ProcObj::ObjectWorkerThread+8a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mstscax

IMAGE_NAME:  mstscax.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  513011e5

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_80000003_mstscax.dll!W32ProcObj::ObjectWorkerThread

BUCKET_ID:  APPLICATION_FAULT_WRONG_SYMBOLS_mstscax!W32ProcObj::ObjectWorkerThread+8a

There is actually nothing useful here.

Can you describe in gory detail what your configuration is and what you are attempting to do?

I think the community can be far more helpful with that.

I have not seen anyone report issues when attempting to open the console of a VM from Hyper-V Manager when it is local.

Also, what do you see in the Hyper-V Event logs?  (under applications and Services, Microsoft, Windows, Hyper-V *

Dell T7500: single Xeon 5650 6 core, 96GB ram, Win 8 Pro x64 w/Hyper-V enabled. One Win 2003EE SP2 x32 VM: 2 proc, 8GB ram. One external virtual switch. Hyper-V integration installed in guest.

Created the VM last night and was able to connect to it fine. Ran windows update on host, rebooted, could not connect to it afterwards. Removed Hyper-V role and reinstalled. Updates installed:

    KB2855336 July rollup
    KB2756872 GA rollup
    KB2770917 update rollup
    KB2267602 Windows Defender 1.155.1705.0
    KB2859541 Camera Codec pack
    KB2785094 Jan rollup
    KB2779768 Dec rollup

Only non-info msgs in Hyper-V* logs are from the missing virtual switch when I re-enabled Hyper-V. Everything else is routine info. App error is:

Faulting application name: vmconnect.exe, version: 6.2.9200.16384, time stamp: 0x50107744
Faulting module name: ntdll.dll, version: 6.2.9200.16579, time stamp: 0x51637f77
Exception code: 0xc0000374
Fault offset: 0x00000000000ebd59
Faulting process id: 0x12a8
Faulting application start time: 0x01ce938ef5fc152b
Faulting application path: C:\Windows\system32\vmconnect.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 524d7613-ff82-11e2-be79-bc305bb090be

Offset is consistent in every failure

Able to start and stop VM from Hyper-V manager without any problems and ping the VM.

Thanks for any and all help.

Actually, despite having the wrong symbols, the dump was helpful. In trying to figure out why the symbols were missing, I noticed that one of the files that it wasn't able to verify the checksum for was aticfx64. On I hunch, I uninstalled the video driver (because it was an ATI/AMD card), rebooted, then updated it through Windows update. Voila. It worked again.

If this were in production, though, however, this would mean that a single bad driver or update on the client running SCC would mean losing access to every VM.

Glad to hear you found the root cause and fixed the issue.