appearing on many machines would appear to indicate a flaw in the compiler code, possibly platform dependent. If there where a hardware problem then... 1) The timing and location of the error would be somewhat random. 2) There would be other symptoms of instability on the computers in question. 3) The error would likely be different sometimes. 4) Copying large files on the computer in question would sometimes result in a corrupt copy of the file.
If there is an intermittant flaw in the compiler, depending how long it takes the gcc devs to fix, it might be wise to implement a temporary work around (if one can be found that consistantly avoids the error). ?