it's worth noting that a failing power supply can produce what seem to be ram problems. it happened to me, swapping ram, a motherboard and then a power supply made it clear.
-- Note the right side (his right) of Mr. Trumps face, He's clearly had a major stroke or similar neurological insult. The eye always droops, and that side of his mouth hardly moves when he speaks. I try not to throw stones from inside my glass house, others obviously don't mind hypocrisy. 8. Oct 2017 18:14 by r03...@gmail.com: > On Sun, Oct 8, 2017 at 4:53 PM, Grant Edwards <> grant.b.edwa...@gmail.com> > > wrote: >> On 2017-10-08, R0b0t1 <>> r03...@gmail.com>> > wrote: >> >>> Usually what happens is it will be corrupted in RAM after being >>> verified on disk, and faulty results will be saved to disk from RAM. A >>> user on the forums recently had this issue compiling dev-lang/vala, >>> and I have had related issues. >> >> I've had failing RAM corrupt files and cause compile failures (and >> various other odd problems). But, the exact symptoms tend to be pretty >> random. The chances are infinitesmal that a HW problem would corrupt >> the download (or the compile itself) in an identical manner a second >> time. >> > > Right, redownloading or rerunning the compilation usually fixes such > issues. At the same time, I have seen people hit bad areas of RAM > repeatedly and have it look like other errors. > --------------------------snip > Cheers, > R0b0t1
