Yes, I'm leaning toward motherboard issues also. It looks like my wife is going to get a pretty robust (though slightly used) gaming machine. Time for me to go shopping again. I always get the new computer
if the time sample is always off by a consistent amount, try setting the BIOS time forwards/backwards to compensate for it. In your case, try setting it back 38941 minutes.
It's not consistent. It appears to be reading a time that is frozen on or about May 20th, but it sometimes only reads it for a couple of random minutes before it finds the correct time somewhere. Even changing the BIOS way off and back doesn't make the problem go away. Even when I find the right time on May 20th, within 5 minutes of setting the time, I'm back looking at the message as the world turns under my stuck in time computer. The only thing that confuses me, is why the bitcoin client is the only program that is reading a bad date/time. My BIOS is right, my Windows is right. I wrote a little c# program that loops around and displays DateTime.Now and never see anything but the correct time. It's got to be a hardware issue, but not like anyone I've ever seen before.