You don't actually have any packet loss. Packet loss is only realized if you have loss at the destination. Being that you don't, all the hops in between are simply ignoring your ping request basically.
I've found the source of the "packet loss". I recently installed Bitdefender Total Security. By default, it sets up the firewall to block all incoming ICMP requests. When I changed the setting from Deny to Allow, PingPlotter once again showed information for each of the hops along the route.
As moldypickle stated, you're not having any actual packet-loss since you have 0 packet-loss to your destination. In my experience, what you're seeing is caused by a firewall blocking some of the trace packets. As a test, try bypassing your router and connect your computer directly to your cable modem and perform another trace.
As I mentioned in my reply just above yours, I discovered the problem was being caused by the Firewall within Bitdefender blocking all incoming ICMP requests.
