To me it appears that your router is not working properly. First, event ID 1002 mentions DCHP server 167.206.3.234 as rejecting a lease for 192.168.1.100. Well, that DHCP request shouldn't reach that DHCP server which probably belongs to your ISP. It would be the router that should answer to such requests, yet it looks like it just forwards them to your ISP (and of course, it gets rejected).

From that error on, everything else is just a logical consequence of not getting an IP from a DHCP server (see Troubleshooting Microsoft Windows Event Logs for comments on each of them). If Windows makes such requests and there is no answer, it will assign the system a random one within that 169.254. subnet (and the reason for that is that computers in the same network, with no DHCP and no Internet are automatically configured so they can communicate with each other without any special configuration from the users).

So, check you router, make sure it is configured to provide IP addresses to internal hosts and not just redirect all the network traffic to the ISP (that would be called bridging and you don't want that).