Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

MySQL is crashing frequently and there is no error in the err log file.

The following error message was found in the event viewer:

faulting application mysqld-nt.exe, version, faulting module mysqld-nt.exe, version fault address 0X001176b8

  • MySQL version - 5.0.24
  • OS - Win2003 with 4GB Ram

Is there any problem with combination of MySQL 5.0.24 and Win2003?

share|improve this question
Do you have a good reason for not patching MySQL to 5.0.92? (I'm assuming you can't upgrade) – Jack Douglas Sep 27 '11 at 10:14
+1, without knowing much, I would say upgrade to the highest version you can. – Jonathan Sep 27 '11 at 14:06

I would upgrade away from MySQL 5.0 altogether.

Please note you are using mysqld-nt.exe

It has been a very long (probably over 1.5 yrs) since the NT-featured mysqld was distributed. The only benefit to using mysqld-nt was if you are using shared memory or named pipes, which were just nuances when MySQL 5.0 came out for Windows.

The MFC C++ runtime distributables have been updated several times over the years. If you have been running updates against Win2003, things are probably very different for mysqld-nt.exe now.

Before upgrading, try using mysqld.exe instead of mysqld-nt.exe. If you still get the same crashing behavior, switch out of MySQL 5.0 for Windows and go to MySQL 5.5 because MySQL Support for Windows 2003 went EndOfLife back in April of 2011. I would also think about using a Windows 7 Server instead of Windows 2000/2003/NT.

share|improve this answer
up vote 1 down vote accepted

The problem was not with win2003 and MySQL.

Trend Micro Antivirus was running and was not allowing MySQL temp files to be created/writen.

I added an exception to the MySQL temp directory and from that time, the service has been running properly.

share|improve this answer
Thanks for posting your solution Phanindra - please mark it as the accepted answer so others can find it more easily – Jack Douglas Oct 18 '11 at 10:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.