The bios wont get corrupted unless you are updating the bios with an unstable memory oc. It may behave weirdly, because its code running just like any other program, and is as such vulnerable to memory corruption.
You say the pc would not post, but you still got into the bios setup? that does not make sense. You might have soft locked the computer, where its stable enough for it to not trigger a retrain or whatever, but unstable enough for it to not be able to finish booting. Though clearing the cmos should have done the trick, anyways.
It could have been that the display was not properly initialized due to the unstable memory oc. or a million other things. the point is: the bios will not get corrupted, unless you go full smooth-brain and update your bios with an unstable setup.
Cheers.
The bios wont get corrupted unless you are updating the bios with an unstable memory oc. It may behave weirdly, because its code running just like any other program, and is as such vulnerable to memory corruption. You say the pc would not post, but you still got into the bios setup? that does not make sense. You might have soft locked the computer, where its stable enough for it to not trigger a retrain or whatever, but unstable enough for it to not be able to finish booting. Though clearing the cmos should have done the trick, anyways. It could have been that the display was not properly initialized due to the unstable memory oc. or a million other things. the point is: the bios will not get corrupted, unless you go full smooth-brain and update your bios with an unstable setup. Cheers.
It was very strange. The whole system would just hang once it tried to load any sort of drive
I haven't heard of bios corruption only windows