Hi,
First of all I do not wanna point the thing that my D7000 v2 is freezing/locking up every 2-3 days as it has become a common issue for many users. I suppose there is still no fix for this and only reboot seems to "fix" it?
I've noticed that when I ping a host using cmd -> ping -4 xx.xx.xx -t, the 1st value seems to be 18-19ms higher than the rest of responses (I highlighted it). Note it always is 18-19ms and it is not due to ping variation of my network. I've also noticed that happens only when pinging using IPv4, it seems to be normal on IPv6, same happens in trace route - some pings are just 18-19ms higher than the rest. Even more strange is, it happens every time I close cmd and reopen it, when I ping a host the 1st value is higher but when I ping it again without closing cmd the responses are normal. I haven't noticed any issues in gaming but I am just curious why is that happening? Is it some kind of bug or possibly hardware issue? It never happened to me when tested different router though.
C:\Users\N0STIE>ping -4 bbc.co.uk -t
Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data
Reply from 151.101.0.81: bytes=32 time=29ms TTL=60
Reply from 151.101.0.81: bytes=32 time=11ms TTL=60
Reply from 151.101.0.81: bytes=32 time=10ms TTL=60
Reply from 151.101.0.81: bytes=32 time=11ms TTL=60
Reply from 151.101.0.81: bytes=32 time=10ms TTL=60
Reply from 151.101.0.81: bytes=32 time=11ms TTL=60
Reply from 151.101.0.81: bytes=32 time=10ms TTL=60
Reply from 151.101.0.81: bytes=32 time=11ms TTL=60
Reply from 151.101.0.81: bytes=32 time=11ms TTL=60
Reply from 151.101.0.81: bytes=32 time=11ms TTL=60
Reply from 151.101.0.81: bytes=32 time=11ms TTL=60
Reply from 151.101.0.81: bytes=32 time=10ms TTL=60
Reply from 151.101.0.81: bytes=32 time=10ms TTL=60
Reply from 151.101.0.81: bytes=32 time=10ms TTL=60
Reply from 151.101.0.81: bytes=32 time=10ms TTL=60
