MSI Announces X79 BIOS Updates For Ivy Bridge-E




/ 11 years ago

MSIX79Board2

MSI has just announced that all its X79 motherboards are now ready for Intel’s Ivy Bridge-E processors. Intel’s Ivy Bridge-E retains the same socket and chipset as Sandy Bridge-E so users can just drop the new CPU in an updated motherboard and everything should work just fine. Users will have to update the BIOS of their motherboards first using the latest BIOS versions from MSI’s website, specified below.

MSI claims all consumers with X79 motherboards will have no trouble running these latest processors and overclocking them to their max. Of course these new CPUs are more power efficient so will put less strain on the motherboard’s VRM implementation than the Sandy Bridge-E processors did previously. MSI claims that its Military Class III components combined with its Click BIOS II should give you a flawless overclocking experience. If you’re opting for a Core i7 4960X then you should be able to grab yourself a decent overclock in the 4.4-4.8GHz range depending on the quality of your chip and what voltages you choose.

msi_ibe_bios_updates

Be sure to check out our review of the Core i7 4960X right here if you are interested.

Images courtesy of MSI


Topics: , , , , ,

Support eTeknix.com

By supporting eTeknix, you help us grow and continue to bring you the latest newsreviews, and competitions. Follow us on FacebookTwitter and Instagram to keep up with the latest technology news, reviews and more. Share your favourite articles, chat with the team and more. Also check out eTeknix YouTube, where you'll find our latest video reviews, event coverage and features in 4K!

Looking for more exciting features on the latest technology? Check out our What We Know So Far section or our Fun Reads for some interesting original features.

eTeknix Facebook eTeknix Twitter eTeknix Instagram eTeknix Instagram
  • Be Social With eTeknix

    Facebook Twitter YouTube Instagram Reddit RSS Discord Patreon TikTok Twitch
  • Features


Send this to a friend
})