Steve Jones - Editor (12/10/2008)
You might want to call MS support and work through this, checking to see if you might have hardware issues.
Not much point - they're not going to say anything different or have any better insight than what's been said on the thread so far - and it will cost $250+ for the extra non-advice.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005