Every day I need to power cycle my TP-LINK TD-W8960N modem/router because my PC, upon turning on, fails to secure an IP.  The IP of the router is 192.168.1.1/24 and has a DHCP range of .100 to .200.  I've set up a static IP for my PC of 30, which doesn't affect it (same behaviour whether the static IP is set or not).  After the power cycle, everything works perfectly until the next day (more specifically, I assume until the DHCP lease ends?).

Ipconfig when it's acting up, note the completely incorrect IP range and subnet mask:
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::98ea:2e7a:9b77:101e%10
   Autoconfiguration IPv4 Address. . : 169.254.16.30
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

The awesome unidentified network:


My router's LAN+DHCP settings:


And ipconfig again, after a power cycle with things working dandy
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::98ea:2e7a:9b77:101e%10
   IPv4 Address. . . . . . . . . . . : 192.168.1.30
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

My google-fu failed to return any fixes in this case. :(  Speaking with my flatmates, my PC is not the only one affected by this.  Removing my static IP (as shown above) does not fix this.  Manually setting an IP rather than relying on DHCP also does not fix this, surprisingly, indicating that it may not even be a DHCP problem?

Help me geeki wan zoneabi, you're my only hope!

edit: fixed images and code tags