When a new monitor thread fails to create and returns the `EAGAIN` error, we incorrectly assume it has been created. Then when attempting to shutdown the thread later on, we cause an Access Violation in the client application. Some details:

`thread_create` doesn't check if the creation succeeds or not.

When we attempt to stop the server monitor thread, it is assumed that it was already running. The call on `thread_join stop` will crash

It would be nice if C driver could handle this situation gracefully to avoid crashes.