Times not matching Server? Any idea how, why etc..?

Asterix

500RPM
Original poster
Apr 19, 2015
532
237
Not often Google draws a total blank but I've had this message on a couple of servers in the last two days.

'Warning: your times do not match the server's. If the issue persists, please check your CPU clock.'

This is on servers with the nanny state stuff that charges you pretend money for crossing lines and whatnot. Not seen it on other servers.

Game plays fine, as do all others - no issues anywhere else.

Any idea what it is?
 

Asterix

500RPM
Original poster
Apr 19, 2015
532
237
Thanks for the posts.

Very odd. My CPU isn't OC'd other than the standard 'turbo' thing when it's working hard. Also, only just started happening, not had anyone in servers mention weird timings or improper behaviour and I'm normally running competitively so I'm sure something would have been said.

Odd.

I've a new MoBo and CPU to go in anyway when the RAM turns up, maybe that'll sort it as there's not much else I can do with the current set up as it's in standard settings.
 
  • Like
Reactions: Andy-R

Andy-R

1000RPM
Jul 23, 2016
1,206
973
Perhaps it was that specific server then, have you tried another nanny state server?

I don't really know much about it just remember that thread from ages ago in the official forum.
 

Asterix

500RPM
Original poster
Apr 19, 2015
532
237
Trying some more now - nothing as yet.

Had a try on servers with the same monitoring and nothing out of the ordinary - weird.

Anyway - thanks for your info.
 
Last edited:
  • Like
Reactions: Andy-R
Dec 12, 2018
2
2
32
Hi. I´m having the exact same issue.And I think my times are not correct. I onc had a lap with a guy and I was faster than him and he beat me like for 10 sec.its very wierd.
In qualy i am always very slow and I know my times are better..
Have you found any solution??
 

Asterix

500RPM
Original poster
Apr 19, 2015
532
237
No, well, not really - I've replaced the MoBo and CPU - no issues since.

That said, there wasn't any other issues beforehand so maybe it was a server specific problem.

Hope you get it sorted.