Database Error in Blog Page

My bx_blogs_views_track' is marked as crashed and last (automatic?) repair failed

I went to phpMyAdmin open table bx_blogs_views_track and repair it, after repair its  ok. but after 1 days same error occur. I repaired again and its ok again. then after 1 days same error.

My question is repair is working just for 1 day not permanently. Kindly tell me what to do i have to repair my table again n again.

First of all, make sure you have enough drive space and memory for mySQL

You are probably not going to get much help on this.  I had a table from a third party module that kept crashing.  Hard drive space and memory were not the issue, the database engine was not shutting; just that one table.  The developer rewrote some of the db routines and I think we ended up not using the table and removing it; we never actually found out why it kept crashing.  Since this is a Boonex module maybe Boonex will respond as well.

Here is some background information I copied from the net.

MyISAM tables are very easy to crash. There is header info in each table that keeps track of how many open file handles a MyISAM table has.

If mysqld crashes, any MyISAM table that had open file handles to it never had the opportunity to decrement the file handle count upon each file handle closing. Thus, if a new file handle opens a MyISAM table (.MYD file) and mysqld discovers a mismatch between the number of file handles a MyISAM table believes is open and the the number of file handles the MyISAM table actually has open, the table is declared crashed.

There are four(4) methods for handling this:

METHOD #1 : Setup automatic MyISAM repair

See my post http://dba.stackexchange.com/a/15079/877 on how to set this up upon a MySQL restart (Mar 15, 2012)

METHOD #2 : Use InnoDB instead of MyISAM

InnoDB has crash recovery built into the Storage Engine's initialization. MyISAM does not

METHOD #3 : Use Aria instead of MyISAM

Aria is MariaDB's drop-in replacement for MyISAM. It features crash recovery mechanisms for individual tables.

METHOD #4 : Don't kill -9 on mysqld

If mysqld crashes, deliberately or involuntarily, header info for all open MyISAM tables will get them into a crashed state.