As you said that the DB goes to suspect now and then and also the h/w check came clean.

Only thing I can think of right now is disk controller.

Refer this KB which briefs about the impact of disk controller caching on SQL Server .

http://support.microsoft.com/kb/86903