Results are somewhat finicky. At first, I thought you might be onto something... now I see that everything is just in the same general window of performance. Enabling/disabling HPET timer in windows (bcdedit /set useplatformclock true/false) seems to have a larger impact.
On an interesting side note, I'm having pretty high DPC latency - but it's the standard Microsoft driver culprits (USB, HDAUDIO, and SATA). Going to try manually forcing to use AMD drivers (the ones a fscking slipstreamed, Microsoft!). I know they were in use originally, but I guess updating to Build 1607 overrode those. Fortunately, most of my storage testing was done before hand (and it's all REALLY good).
In fact, aside from some weird scheduling issues that only occur with SMT enabled on Windows 10, Ryzen is behaving wonderfully... as long as you know that it has a crazy many-stage error correction protocol built in...
Power on -> off -> on -> off -> on -> off -> on -> off -> on -> warm reboot -> pause -> warm reboot -> pause -> warm reboot -> reset at BIOS screen -> normal boot
Kind of disconcerting when that behavior, in the past, was indicative of a stability setting you had to manually correct. The system will learn the DDR itself and try various configurations, and it will reset platform errors after only so many power cycles (hence all the power cycling). I have yet to do much testing on the exposed bits related to this logic.
For now, I'm reinstalling AMD drivers onto Windows 10 and validating a few results don't change, then doing BF1 testing all over again... VSync on is not so good for benchmarking