BTW, this is the error message that windows wanted to send to MS C:\DOCUME~1\GARYPA~1\LOCALS~1\Temp\WERd238.dir00\mysqld.exe.mdmp
C:\DOCUME~1\GARYPA~1\LOCALS~1\Temp\WERd238.dir00\appcompat.txt "Carlos Proal" <carlos.pr...@gmail.com> wrote in message news:4a58cb7c.4090...@gmail.com... > > Take a look on the my.ini to see if there is something wrong (maybe a path > pointing to a missing place or memory setting bigger than your actual RAM) > > Carlos > > On 7/11/2009 12:17 PM, Gary wrote: >> Not sure if this is it, it was the only .err file that I have. Also this >> seems to be the latest entry that has a date. >> >> Thanks for your help. >> >> Gary >> >> 090617 21:50:45 - mysqld got exception 0xc0000005 ; >> This could be because you hit a bug. It is also possible that this binary >> or one of the libraries it was linked against is corrupt, improperly >> built, >> or misconfigured. This error can also be caused by malfunctioning >> hardware. >> We will try our best to scrape up some info that will hopefully help >> diagnose >> the problem, but since we have already crashed, something is definitely >> wrong >> and this may fail. >> >> key_buffer_size=16777216 >> read_buffer_size=262144 >> max_used_connections=0 >> max_threads=151 >> threads_connected=0 >> It is possible that mysqld could use up to >> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = >> 133305 K >> bytes of memory >> Hope that's ok; if not, decrease some variables in the equation. >> >> thd: 0x0 >> Attempting backtrace. You can use the following information to find out >> where mysqld died. If you see no messages after this, something went >> terribly wrong... >> 006B8853 mysqld.exe!??? >> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html >> contains >> information that should help you find out what is causing the crash. >> 090627 9:35:07 - mysqld got exception 0xc0000005 ; >> This could be because you hit a bug. It is also possible that this binary >> or one of the libraries it was linked against is corrupt, improperly >> built, >> or misconfigured. This error can also be caused by malfunctioning >> hardware. >> We will try our best to scrape up some info that will hopefully help >> diagnose >> the problem, but since we have already crashed, something is definitely >> wrong >> and this may fail. >> "Carlos Proal" <carlos.pr...@gmail.com> wrote in message >> news:4a58c79b.2090...@gmail.com... >> >>> You have to take a look on the error log, a file named hostname.err >>> (hostname=your machine name) and should be located inside >>> the mysql dir on the xammp dir. >>> That file will give an insight about the problem, or you can post the >>> error here to get help. >>> >>> Carlos >>> >>> >>> On 7/11/2009 11:52 AM, Gary wrote: >>> >>>> I have an issue that Mysql will not start on my local machine. I >>>> noticed a >>>> few days ago on a restart that I got an error saying that Mysqld had >>>> encountered a problem and had to close. I did not pay any attention to >>>> it >>>> because I was not working in it for a bit. >>>> >>>> I then tried to start it today and got the same error message saying >>>> mysqld.exe has encountered a problem and had to close. >>>> >>>> + Apache 2.2.11 >>>> + MySQL 5.1.30 (Community Server) >>>> + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued) >>>> + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main >>>> directory) >>>> + XAMPP Control Version 2.5 from www.nat32.com >>>> + XAMPP Security 1.0 >>>> + SQLite 2.8.15 >>>> + OpenSSL 0.9.8i >>>> + phpMyAdmin 3.1.1 >>>> + ADOdb 4.990 >>>> + Mercury Mail Transport System v4.52 >>>> + FileZilla FTP Server 0.9.29 >>>> + Webalizer 2.01-10 >>>> + Zend Optimizer 3.3.0 >>>> + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the >>>> php.ini) >>>> >>>> Anyone have an idea to where I should start to look? >>>> >>>> Thanks >>>> >>>> Gary >>>> >>>> >>>> >>>> >>>> >> >> >> >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
