Bought an Intel for the first time in over a decade. Patched in the TSC frequency fix that should be used after the PmTimer is patched
With CPUz started and WinTimerTester running a test I see the known clock drift problem. Ryzen does not have the issue so I wasnt able to test it until now.
I'm assuming still no fix with windows patch or BIOS?
For now, I use classic XP era Dimension4 time to keep sync.
Like with XP, add shr to shift right, value is 0A hex or 10 decimal, so 2^10=1024
https://msfn.org/board/topic/183489-windows-xp2003-x32-on-modern-hardware-faq/page/4/#findComment-1235566
x64 hal.dll 5.2.3790.6912
https://ufile.io/j28adslm
PmTimer
@38881 73 -> EB
@40186 73 -> EB
TSC frequency
@F890 74 0C 65 48 8B 04 25 C0 00 00 00 48 89 01 0F 31 48 C1 E2 20 48 0B C2 C3 CC CC CC CC CC CC CC CC
-> 74 10 65 48 8B 04 25 C0 00 00 00 48 C1 E8 0A 48 89 01 0F 31 48 C1 E2 20 48 0B C2 48 C1 E8 0A C3
in KeQueryPerformanceCounter
=========================================
74 0C jz short loc_XXX
65 48 8B 04 25 C0 00 00 00 mov rax, gs:0C0h
48 89 01 mov [rcx], rax
0F 31 rdtsc ;loc_XXX
48 C1 E2 20 shl rdx, 20h
48 0B C2 or rax, rdx
C3 retn
change to
=========================================
74 10 jz short loc_XXX
65 48 8B 04 25 C0 00 00 00 mov rax, gs:0C0h
48 C1 E8 0A shr rax, 0Ah <---------
48 89 01 mov [rcx], rax
0F 31 rdtsc ;loc_XXX
48 C1 E2 20 shl rdx, 20h
48 0B C2 or rax, rdx
48 C1 E8 0A shr rax, 0Ah <---------
C3 retn