I did a quick google search and it seems to be a common bug on 1st gen Intel. Over at TomsHardware someone got it fixed by resetting the CMOS of the Motherboard. But they dont really know why this happens - seems to be a bug
I would recommend updating your motherboard BIOS and resetting the CMOS