Examining the diagnostic report, we that the failure is not caused by a deadlock condition as indicated by the dump file. Although there is one thread initiating the shutdown and dump after waiting eight minutes for a resource already held by another thread (which is normally triggered by a thread deadlock condition), that thread is not waiting for another resource, which would be held by the previous one or some other thread in case of a deadlock. The thread blocking the resource is instead waiting for a database table to be deleted. We think, that it takes so long, because some NSM processes are taking most of the computational power on that machine at a given time after restart. This is unfortunate althou not entirely unnecessary. There is a paragraph in the Install Guide section labeled as Server Requirements describing that while small volume Automation Point could run on single 2GHz processor, a high load system or system running NSM has to have two 2.4GHz processors. You happen to have one 2.4GHz processor running on this system.