MySQL Bugs: #44255: unhandled win32 exception occured in mysqld.exe

Bug #44255	unhandled win32 exception occured in mysqld.exe
Submitted:	14 Apr 2009 4:46	Modified:	14 May 2009 12:56
Reporter:	sadiqabbas hirani	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Windows	Severity:	S1 (Critical)
Version:	5.1	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any
Tags:	mysqld.exe, Unhandled exception

Description:
actually i m using
xp sp-3 with
vs2005,
photoshop cs2,
and avg 8.5 free

and it happened so that my avg got corrupted

and hdd space for primary drive was low so i uninstalled avg & photoshop cs2

and problem started that service start error: unhandled win32 exception in mysqld.exe

i dont know what to be done with this

How to repeat:
i dont know how this occured

i then again installed avg free and photoshop cs2 but still problem is going on..

please help me with this....

Thank you for the report.

This looks not like MySQL bug, but like problem in your environment.

Which version of MySQL do you use? Have re-installed MySQL after problem occurred? If you haven't please do now and use latest version 5.1.33.

actually i m using 5.1.30 and one more thing that i tried reinstalling it but nothing happened and one more thing that how it could be problem with my environment? as photoshop and avg has no interaction with mysql coz these all the things are different...

i think there might be problem with MS VC++ 8 Redistributable...

before it also happened same and i was forcefully have to format my pc and reinstall windows and other software(s)...

but this time i cant do coz i havent taken backup of my database and now i cant start mysql so i cant format my pc...

and the backup which i am having is very old so i cant try also for doing this...

please revert with a response...

thanks if some one could find me a solution...

Try to start the MySQL server as standalone to see the error message:

mysqld --defaults-file="path_for_my.ini_file" --standalone --console

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".