5 ms·
To be fair, it can well be that some sloppy OEM drivers take too many assumptions on reserved bits in registers (which the new microcode may be legitimately cha
by zimmerfrei 9y ago
To be fair, it can well be that some sloppy OEM drivers take too many assumptions on reserved bits in registers (which the new microcode may be legitimately changing) or on undocumented timing side-effects related to some instructions (which the new microcode may affect, being that the root problem in the first place!).
These symptoms are also the classic ones you get when you install an OS on a new-generation, well-functioning CPU.
- joenathanone 9y agoDon't speculate, it adds nothing but confusion.
- zimmerfrei 9y agoMy comment is no more speculative than those blaming the new microcode for causing reboots. The real bad quality, bad update process and unjustified binary nature of OEM firmware is too often overlooked.