Which motherboard manufacturers have bundled Intel’s latest 0x12F microcode into public BIOS releases and when?
Executive summary
Intel published microcode 0x12F in early May 2025 to address a lingering Vmin‑shift instability on 13th‑ and 14th‑Gen Intel Core CPUs, and motherboard makers began integrating that microcode into BIOS releases almost immediately, with ASRock documented as the first to post BIOS images; other major vendors (ASUS, MSI, Gigabyte) were reported to follow in the ensuing weeks though their public release dates vary by board and region [1] [2] [3].
1. Which vendors have publicly bundled 0x12F: ASRock first, others followed
Multiple independent outlets and community threads identify ASRock as the earliest vendor to post BIOS images containing microcode 0x12F—reports from Tom’s Hardware, Guru3D and Club386 all say ASRock had BIOSes with 0x12F available in early May 2025 [1] [2] [3], and community discussion confirms users saw 0x12F in BIOS updates [4]. ASUS users and the Republic of Gamers forum reported ASUS releases that include 0x12F as well, with community posts explicitly noting a new ASUS BIOS containing 0x12F [5]. Press and community reporting also list MSI and Gigabyte as vendors expected to roll out or already rolling out updated BIOSes in the weeks after Intel’s announcement, though coverage mostly frames those as “following suit” rather than pinpointing a single universal release date [2] [1].
2. Timeline: Intel’s May microcode and a rolling vendor rollout
Intel published microcode 0x12F in a public update in early May 2025; Tom’s Hardware and Club386 covered that release on May 7–8, 2025 [1] [3]. ASRock had beta BIOS images incorporating 0x12F available immediately after Intel’s disclosure, with trade press and community posts dated the first week of May citing ASRock’s availability [2] [1]. Coverage then describes a rolling timetable—vendors validated and distributed their own BIOS packages over the following weeks, so end users saw vendor-specific BIOSes arrive at different times depending on model and region; Intel community threads from mid‑May through July show users asking when particular motherboard models would receive official vendor‑validated 0x12F BIOSes [4] [6] [7].
3. What the sources document precisely (and what they don’t)
The cited sources clearly document ASRock posting BIOSes with 0x12F early in the May 2025 window and community reports that ASUS has published BIOS containing 0x12F [2] [5]. They consistently indicate MSI, Gigabyte and other major vendors planned or began releasing updates shortly after [2] [1]. What the sources do not provide is a comprehensive, model-by-model manifest: there is no single consolidated list or uniform calendar in these reports of every motherboard model and the exact public release date for each vendor’s BIOS that carries 0x12F; community threads and press reporting instead show a staggered, model‑dependent rollout [4] [6].
4. Real‑world uptake and post‑release reports
Community and game‑forum reports document users who flashed vendor BIOSes containing 0x12F and in some cases later reverted to previous microcode due to game crashes, stuttering, or compatibility issues with anticheat systems—posts on Steam and other forums reference ROG, Gigabyte/AORUS and MSI boards where users tied new stutters or GameGuard errors to 0x12F‑inclusive BIOS updates [8] [9]. Intel and reporting note Intel’s testing showed no measurable performance impact for 0x12F and that the update targets a specific low‑load, long‑uptime instability; nevertheless, these community reports show that vendor validation and user experience can vary and that some users found stability differences that led them to roll back BIOS versions [1] [9].
5. Bottom line — who and when, with a caution
Concisely: ASRock publicly posted BIOS images with microcode 0x12F immediately after Intel’s May 2025 release (documented by press and community posts) and ASUS has publicly released BIOSes containing 0x12F per user reports; MSI, Gigabyte and other major vendors were widely reported to have followed in the weeks after, though exact dates are model‑specific and not exhaustively listed in the available reporting [2] [5] [1]. Users and system administrators should check their specific motherboard vendor’s support page and changelogs for the precise BIOS version and release date that includes 0x12F, and weigh community reports of rare post‑update issues when deciding whether to update immediately or wait for a vendor‑validated stable build [6] [9].