- Joined
- Feb 18, 2005
- Messages
- 5,847 (0.81/day)
- Location
- Ikenai borderline!
System Name | Firelance. |
---|---|
Processor | Threadripper 3960X |
Motherboard | ROG Strix TRX40-E Gaming |
Cooling | IceGem 360 + 6x Arctic Cooling P12 |
Memory | 8x 16GB Patriot Viper DDR4-3200 CL16 |
Video Card(s) | MSI GeForce RTX 4060 Ti Ventus 2X OC |
Storage | 2TB WD SN850X (boot), 4TB Crucial P3 (data) |
Display(s) | 3x AOC Q32E2N (32" 2560x1440 75Hz) |
Case | Enthoo Pro II Server Edition (Closed Panel) + 6 fans |
Power Supply | Fractal Design Ion+ 2 Platinum 760W |
Mouse | Logitech G602 |
Keyboard | Razer Pro Type Ultra |
Software | Windows 10 Professional x64 |
Microsoft will have to determine if the problem is in Haswell (like Opteron/X2 processors) or if it is in their code. If it is in their code, they'll release a hotfix for it. If it is in Haswell, Intel will likely release a hotfix on their end.
Where do you get this being a Haswell problem? According to HWBot,
HWBot said:Sparing you the details of development process, compared to Windows7 and previous versions, Microsoft made changes to how it measures time to be compatible with embedded or low cost PCs that do not have a fixed RTC clock. After all, having a fixed RTC clock adds cost to a platform.
It's an issue with Win8, pure and simple. Not sure why MS didn't simply write code to say
if (system.hasHardwareRtc()) {
useHardwareRtc();
}
else {
useSoftwareEmulatedRtc();
}
I'm sure we will see a fix for this next Patch Tuesday, if not sooner, as an accurate RTC is critical to many applications working correctly, not just benchmarks.