MySQL 5

here is the log file.

nnoDB: Last MySQL binlog file position 0 98, file name E:\Mysqllogs\mylogs.000034
111005 19:45:51  InnoDB: Started; log sequence number 86 3756766005
111005 19:45:51 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.67-community-nt-log'  socket: ''  port: 3307  MySQL Community Edition (GPL)
111007  6:14:03 - 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=268435456
read_buffer_size=65536
max_used_connections=289
max_connections=1000
threads_connected=59
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2374144 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=31612F08
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...
7C82A081    ntdll.dll!RtlRestoreLastWin32Error()
7C82A1E1    ntdll.dll!RtlRestoreLastWin32Error()
006DC834    mysqld-nt.exe!???
006DC856    mysqld-nt.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 1D03E018=select `SPECIFIC_NAME` from `INFORMATION_SCHEMA`.`ROUTINES` where `ROUTINE_SCHEMA` = 'mydb' and ROUTINE_TYPE = 'PROCEDURE'
thd->thread_id=89483
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.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
111007  6:15:54  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 98, file name E:\Mysqllogs\mylogs.000034
111007  6:15:55  InnoDB: Started; log sequence number 87 2501999354
111007  6:15:55 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.67-community-nt-log'  socket: ''  port: 3307  MySQL Community Edition (GPL)
111007  7:09:21 - 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.

Hi there,

Did this error occur all of a sudden on a server that has been running fine with no issues up until now or is it in a new server and has just been installed? If it is on a old server perhaps it has developed a RAM issue or a HDD issue. Run a full disk check on the drive to make sure that there are no problems and then run a RAM test using  something like Memtest. If it is on a new server perhaps try a latest version of Mysql or even go back to a slightly older release.

Let us know

maybe the problem is your computer. Did u try to format your computer and install fresh windows os

it was running fine, but suddenly this program starts coming and MySQL service starts automatically