Unexpected behavior with low performance MySQL settings

HI!
Recently I had a problem with the configuration of my database parameters that caused it to crash often (the well known "MySQL has gone away" problem). Essentially I had set too low parameter values.
While this is unrelated with Backup and Migrate, I noticed that all scheduled backup files created during the low performance period were corrupted in a very strange way that mislead me into thinking my site was hacked.
Here's a snippet from a backup file:

(...)(`event`,`hostname`,`timestamp`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=28;
DROP TABLE IF EXISTS `frf`;
;
INSERT INTO `frf` VALUES ('sites/all/modules/(...)

The backup files contained almost 100 calls to this unexistent 'frf' table, replacing actual table names thus making the backups unusable.
As soon as I improved the performance, the backups returned back to normal (and working).

I am not sure whether this is a particular problem with my installation (I am momentarily forced to use MySQL 5.0.4 on IIS6) or not, just wanted to report this.

Thanks!