Hi. I'm running the latest VH Client and VH Server (from MSStore) on Windows 11 24H2. I connect 3 devices (Jabra Speaker, Logitech C922 Camera, and a Blue Microphone). Within the first 10 minutes, the VH Server crashes. I restart it, and typically, it's fine after that but there have been times when it crashes again, and I need to restart it. After this, it usually works for the rest of the day without issue. I have a dmp file and analyzed it with Windows Debugger which is pointing to a memory access violation.
Your application (vhusbdwinw64.exe
) crashed due to an Access Violation (0xC0000005) in ucrtbase.dll
, specifically in the memcpy function. This suggests that the program attempted to read from an invalid memory address (00000211c80fcff8
).
Below is the full dmp analysis:
0:028> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 671
Key : Analysis.Elapsed.mSec
Value: 4736
Key : Analysis.IO.Other.Mb
Value: 8
Key : Analysis.IO.Read.Mb
Value: 92
Key : Analysis.IO.Write.Mb
Value: 38
Key : Analysis.Init.CPU.mSec
Value: 15421
Key : Analysis.Init.Elapsed.mSec
Value: 75969
Key : Analysis.Memory.CommitPeak.Mb
Value: 286
Key : Failure.Bucket
Value: INVALID_POINTER_READ_c0000005_ucrtbase.dll!memcpy
Key : Failure.Hash
Value: {731a66c7-6985-15fa-895b-5aa953069a01}
Key : Timeline.OS.Boot.DeltaSec
Value: 3661
Key : Timeline.Process.Start.DeltaSec
Value: 1294
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
Key : WER.Process.Version
Value: 4.7.2.0
FILE_IN_CAB: vhusbdwinw64.exe.22968.dmp
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
rax=00000211c41f21d0 rbx=0000000000000000 rcx=00000211c41f21d0
rdx=00000211c80fcff8 rsi=00000211c4e282b0 rdi=0000000000000001
rip=00007fff4edede6d rsp=000000553ccffc38 rbp=00000211c80fcff8
r8=00000000000000b2 r9=00000211c41f21d0 r10=00007fff4ed00000
r11=000000553ccffbe0 r12=00000211c41f21d0 r13=00000211c418fc40
r14=00000211c4ecf1a0 r15=00000000000000b2
iopl=0 nv up ei ng nz na po cy
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010287
ucrtbase!memcpy+0x17d:
00007fff`4edede6d c5fe6f02 vmovdqu ymm0,ymmword ptr [rdx] ds:00000211`c80fcff8=??
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007fff4edede6d (ucrtbase!memcpy+0x000000000000017d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000211c80fcff8
Attempt to read from address 00000211c80fcff8
PROCESS_NAME: vhusbdwinw64.exe
READ_ADDRESS: 00000211c80fcff8
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000211c80fcff8
STACK_TEXT:
00000055`3ccffc38 00007ff7`9ea08a9e : 00000000`00000000 00007fff`00000000 00000000`00000008 00000000`00000018 : ucrtbase!memcpy+0x17d
00000055`3ccffc40 00007ff7`9e36495c : 00000000`00000000 00007fff`4ed174bf 00000000`00000000 00000000`00000000 : vhusbdwinw64+0x6a8a9e
00000055`3ccffd10 00007fff`4ed037b0 : 00000211`c41aed50 00000000`00000000 00000000`00000000 00000000`00000000 : vhusbdwinw64+0x495c
00000055`3ccffd60 00007fff`504fe8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x30
00000055`3ccffd90 00007fff`5151bf2c : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000055`3ccffdc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c
SYMBOL_NAME: ucrtbase!memcpy+17d
MODULE_NAME: ucrtbase
IMAGE_NAME: ucrtbase.dll
STACK_COMMAND: ~28s; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_ucrtbase.dll!memcpy
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 10.0.26100.3037
FAILURE_ID_HASH: {731a66c7-6985-15fa-895b-5aa953069a01}
Followup: MachineOwner
---------
Please let me know if I can provide any additional information on this. Thanks!
.
Thanks, that's helpful.
Run that and when it crashes it will popup a stacktrace in drmingw. Can you email me that stack trace
.
Hi Michael.
I have been running the debug version for a few days now without any issues. I'm curious if it has something to do with running the VH Server from the Windows Store versus running the standalone version?
.
The server i sent in the link above is identical to the windows store version.