We've seen this exception as well. It happens very rarely but I'd say that I see it at least a few times a week in normal development.
We try not to load too much data at once (mostly because we continually ran into StackOverflowExceptions during serialization - but we are on an older version before you guys introduced the alternate serialization method). I know in a few cases, our app will load a relatively large amount of data and I think (this is all based on memory....I'll try to pay more attention to what I was doing next time I see this) that is when I've seen this CRC error.
In the worst case scenario, we have 5 parallel InvokeServerMethod calls that return between 300k and 2mb of data each (with a total size of 4.5mb). (note: these are the numbers I see reported by Fiddler....I believe those sizes are after the gzip compression takes place? In which case, the actual data was likely much bigger).
As for the type of data that gets loaded, I can't think of anything special. It's mostly just text and numeric fields.
If you'd like any more info from me, let me know.