I too have seen that from time to time, but quite rarely.

I attribute it to a slight (but permanent) initialization bug in the boot firmware.

Cheers