So, was doing some work from home today and did a couple ping and tracert's to office machines and saw some weird numbers.
I noticed the following when I did a tracert to Dell.com:
Tracing route to dell.com [143.166.224.244]
over a maximum of 30 hops:
1 4294967291 ms 4294967290 ms 4294967290 ms 192.168.x.x
2 <1 ms <1 ms 1 ms 73.157.32.1
3 <1 ms 4294967295 ms * 68.86.230.17
4 6 ms <1 ms <1 ms 68.86.230.253
5 1 ms 1 ms 1 ms 10g-9-1-ur01.westhaven.ct.hartford.comcast.net [
68.87
Then I did a ping to my firewall and got this:
Pinging 192.168.x.x with 32 bytes of data:
Reply from 192.168.x.x: bytes=32 time=-5ms TTL=64
Reply from 192.168.x.x: bytes=32 time=-6ms TTL=64
Reply from 192.168.x.x: bytes=32 time=-6ms TTL=64
Reply from 192.168.x.x: bytes=32 time=-6ms TTL=64
Ping statistics for 192.168.x.x:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = -6ms, Maximum = -5ms, Average = 1073741818ms
As you can see I got some astronomical times in the trace and negative times in the ping
Did some google searches and found a post talking about this problem with a quad core proc. I then tested this on each of my cores and found that Core0 will produce the above results but Core1 will not.
Im curious if this may show a bad core or not?
I noticed the following when I did a tracert to Dell.com:
Tracing route to dell.com [143.166.224.244]
over a maximum of 30 hops:
1 4294967291 ms 4294967290 ms 4294967290 ms 192.168.x.x
2 <1 ms <1 ms 1 ms 73.157.32.1
3 <1 ms 4294967295 ms * 68.86.230.17
4 6 ms <1 ms <1 ms 68.86.230.253
5 1 ms 1 ms 1 ms 10g-9-1-ur01.westhaven.ct.hartford.comcast.net [
68.87
Then I did a ping to my firewall and got this:
Pinging 192.168.x.x with 32 bytes of data:
Reply from 192.168.x.x: bytes=32 time=-5ms TTL=64
Reply from 192.168.x.x: bytes=32 time=-6ms TTL=64
Reply from 192.168.x.x: bytes=32 time=-6ms TTL=64
Reply from 192.168.x.x: bytes=32 time=-6ms TTL=64
Ping statistics for 192.168.x.x:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = -6ms, Maximum = -5ms, Average = 1073741818ms
As you can see I got some astronomical times in the trace and negative times in the ping
Did some google searches and found a post talking about this problem with a quad core proc. I then tested this on each of my cores and found that Core0 will produce the above results but Core1 will not.
Im curious if this may show a bad core or not?
Last edited: