- Joined
- Aug 20, 2007
- Messages
- 21,572 (3.40/day)
System Name | Pioneer |
---|---|
Processor | Ryzen R9 9950X |
Motherboard | GIGABYTE Aorus Elite X670 AX |
Cooling | Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans... |
Memory | 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30 |
Video Card(s) | XFX RX 7900 XTX Speedster Merc 310 |
Storage | Intel 5800X Optane 800GB boot, +2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs |
Display(s) | 55" LG 55" B9 OLED 4K Display |
Case | Thermaltake Core X31 |
Audio Device(s) | TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED |
Power Supply | FSP Hydro Ti Pro 850W |
Mouse | Logitech G305 Lightspeed Wireless |
Keyboard | WASD Code v3 with Cherry Green keyswitches + PBT DS keycaps |
Software | Gentoo Linux x64 / Windows 11 Enterprise IoT 2024 |
AMD has acknowledged an issue in which applications utilizing FMA3 code (basically compute and floating point heavy applications) can freeze Ryzen-based desktops. According to AMD, a fix is already on the way in the form of a basic bios update that will be issued to motherboard vendors, who will then most assuredly update their boards with the fix. If you want to be sure your Ryzen based system is not affected by this or numerous other teething issues, making sure you are running the latest BIOS will go a long way towards easing your experience with your new platform.
AMD has not commented on the specifics of the bug itself, only saying they have "identified the root cause." Wherever the bug originates, it is likely a simple microcode patch that fixes the issue. Microcode has existed as a method to "patch" processor bugs since the infamous Pentium FDIV bug, when Intel decided it might just be smart to have a way to update the processor's running firmware with workarounds for newly discovered errata rather than just assuming it perfect on launch day. AMD and Intel both have microcode update methods now, and microcode can be updated via the bios. If this reported had to guess (and it might be worth noting that this reported has dabbled in bios-modding, so he's not clueless here), that would be my guess as to how they are addressing it.
View at TechPowerUp Main Site
AMD has not commented on the specifics of the bug itself, only saying they have "identified the root cause." Wherever the bug originates, it is likely a simple microcode patch that fixes the issue. Microcode has existed as a method to "patch" processor bugs since the infamous Pentium FDIV bug, when Intel decided it might just be smart to have a way to update the processor's running firmware with workarounds for newly discovered errata rather than just assuming it perfect on launch day. AMD and Intel both have microcode update methods now, and microcode can be updated via the bios. If this reported had to guess (and it might be worth noting that this reported has dabbled in bios-modding, so he's not clueless here), that would be my guess as to how they are addressing it.
View at TechPowerUp Main Site