Have you looked at this resource ? You can double check that you have a specific libmysql.dll (5.2.1) that is not affected by this, and double check if you have any stray mysql libraries that lie around this PHP, instead you can pick up . Or, switch from FastCGI if this is an option for you.
In the interest of interest, the error looks in more detail here . The general idea of the problem (from the mysql bug link) is as follows:
Whenever a new thread is created libmysql is told about that by Windows. It then
increases a thread counter and initializes some data. When libmysql is being unloaded
it checks whether all threads have finished, if not it tries to tell them "close now"
and gives them 5 seconds for that. In general this works in a nice way.
source
share