Endpoint V10 (1000) closes itself (BurnIn V11.0)

[DUTtester]

Hi,

im using BurnIn V11.0 (Build 1016) and the Endpoint version which is available after installing BurnIn V11.

While testing the advanced Network the Endpoint closes itself after a while.

The Endpoint is running in Win10, also the client.
BurnIn is configured to run for 5min with the advanced network function, than BurnIn ends, exits and a restart script is called, the client will shutdown and restart after few minutes and BurnInV11 starts testing again after the reboot -> loop.

I observed that the endpoint closes itself and the advanced network test is failed because of the closed endpoint.

debug output of the endpoint is attached.

This issue was also seen in BurnInV10 but it seems that when using BurnInV11 the endpoint crashes more faster (after the first or second reboot).
To Fix this, i was using the endpoint in Linux (V5), this was running very stable and without issue, but i want to use the endpoint on windows to be able to use the endpointserver for other things too.

IPs/Subnetmaks are set correctly in my opinion, also all firewalls are completely disabled (im not testing on a complex network, its just a connection between the two PCs), drivers are also up to date.

also when using BurnInV11, i can see the following information in the logfile:

but im using the endpoint version that is delivered with BurnInV11.


Am i doing somthing wrong or is it a bug?

Thanks in advance
BR DUTtester =)

[Richard (PassMark)]

It looks like we forgot to update the hardcoded version number in the Endpoint.exe. We'll fix that in the next build release.

Can you provide more details of your testing setup?
How many systems are running Endpoint.exe?
How are the systems connected, e.g. through a switch?

Also make sure, that only one BurnInTest/Advanced Network Test should be running on the network.

Can you start both BurnInTest and the EndPoint in debug mode at the same time? Run the tests and once you have reproduced the issue, send in the all logs and we can take a look. To start BurnInTest in debug mode, use the command line parameter -u.

[DUTtester]

The testsetup is like following:

one machine is running the endpoint, a second one is running BurnIn with Advanced Networktest (+ maybe some disk tests and USBtest with PM loopbacks)
both are connected directly via ethernetcable.
only one network port is tested at a time and just one endpoint.exe is running on this testsetup

i can do a retest with EndPoint+BurnIn in debug mode, ill be able to do this next week.

thanks and BR =)

[DUTtester]

When Burnin is started in debug mode (-u), the following query appears:



I have to click away this message twice before Burnin starts. Unfortunately, this message also appears when it is started with a script (automatically). This means that I have to click away this message manually after every reboot. I assume that it is not possible to bypass this message.

I'll try to reproduce it and send in the logs. Depending on how much time I have and how quickly the endpoint closes, I'll get back to you afterwards.

thanks and BR =)

[DUTtester]

the endpoint crashed quite fast,
I send you the debug logs (endpoint+BurnIn) via private message Richard (PassMark) , as I do not want our system information to be publicly accessible.

thanks and BR =)

[Richard (PassMark)]

I have to click away this message twice before Burnin starts. Unfortunately, this message also appears when it is started with a script (automatically). This means that I have to click away this message manually after every reboot. I assume that it is not possible to bypass this message.

Currently, cannot be bypassed. The message is displayed to show the user where the debug logs are saved to so the user can send them to us. Debug mode is typically only used to for debugging and not in normal testing, so not normally an issue in production.

the endpoint crashed quite fast, I send you the debug logs (endpoint+BurnIn)

I have received the logs, but nothing stands out as to why the endpoint crashed. BurnInTest looks to have correctly close the connection after the auto stop time of 5 minutes. The endpoint log error of 10054 is Connection reset by peer (i.e. BurnInTest closing the sockets).

2025-09-05 123656: TestThread2_rec socket error (1) 10054 (bytes rec'd) (rec)
2025-09-05 123656: TestThread2_Send socket error (on send) 10054
2025-09-05 123656: TestThread2_rec exiting receive test thread loop 10.11.13.100<->10.11.13.200 [10054]
2025-09-05 123656: TestThread2_Send exiting send test thread loop 10.11.13.100<->10.11.13.200 [10054]
2025-09-05 123656: TestThread2_Send finished
2025-09-05 123656: ServerBroadcastThread UDP Data received (12 bytes)
2025-09-05 123656: ServerBroadcastThread UDP Data received (12 bytes)
2025-09-05 123656: ServerBroadcastThread MSG_EP_RESET recv
2025-09-05 123656: ServerBroadcastThread MSG_EP_RESET recv​​

However, the endpoint log does looks like it abruptly cuts off (possibly when it crashed). Normal exit of Endpoint application would have entries at the end of "ServerBroadcastThread Stop listening", "ServerBroadcastThread Exiting server broadcast thread" and "Main Closing".

Can you send email into our email support and provide your configuration/script files you are using? We will try to replicate the setup and see if we can get the same behavior. This may also require us sending debug builds to you for testing and email would be the easiest way to conduct further communication.

[DUTtester]

ok, ill contact your email support.
thanks in advance and BR =)