Occasional crash in 4.2.6 on Windows 10

I'm using this by talking directly to the pipe. Most of the time it's fine, but I have seen an "IPC client ReadFile failed, error: 109" error and a crash.

The last time it happened during a "MANUAL HUB ADD", but I have seen it with "LIST" as well. Here's two entries in the syslog from last time:

11/12/2017 03:40:47 AM
LogName=Application
SourceName=Application Error
EventCode=1000
EventType=2
Type=Error
ComputerName=bat960194win64.mathworks.com
TaskCategory=Application Crashing Events
OpCode=Info
RecordNumber=10839
Keywords=Classic
Message=Faulting application name: vhui64.exe, version: 4.2.6.0, time stamp: 0x59c8b00e
Faulting module name: ntdll.dll, version: 10.0.14393.1715, time stamp: 0x59b0d03e
Exception code: 0xc0000374
Fault offset: 0x00000000000f8363
Faulting process id: 0x8b0
Faulting application start time: 0x01d35b9150562a1a
Faulting application path: C:\VirtualHere\vhui64.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 5cc02dc8-9aa8-4c8b-9266-e84ca7b8bfd2
Faulting package full name:
Faulting package-relative application ID:

11/12/2017 03:40:47 AM
LogName=Application
SourceName=Windows Error Reporting
EventCode=1001
EventType=4
Type=Information
ComputerName=bat960194win64.mathworks.com
TaskCategory=None
OpCode=Info
RecordNumber=10840
Keywords=Classic
Message=Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: vhui64.exe
P2: 4.2.6.0
P3: 59c8b00e
P4: StackHash_1a97
P5: 10.0.14393.1715
P6: 59b0d03e
P7: c0000374
P8: PCH_A6_FROM_ntdll+0x00000000000A6BF4
P9:
P10:

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: 5cc02dc8-9aa8-4c8b-9266-e84ca7b8bfd2
Report Status: 0
Hashed bucket:

In this "session", I had previously sent the command "HELP" and two other "MANUAL HUB ADD"s that were all OK.

Any ideas?

#2

Is there a file 20171112034047.txt (or a similar name) in the %TEMP% directory?, if so can you email me that.

Also can you download the latest client 4.3.4 use that.

If it crashes again can you take a look in %TEMP% and see if there is a file called yyyymmddhhmmss.txt where the yyyy stands for the current year. The file time should correspond to the crash time in windows.

My guess at the moment is a parsing issue with the IPC command.

#3

I haven't seem this since upgrading to 4.3.5. If I do, I will grab that file and send it along.

Thanks!