"I had to unplug it to do it, so yes it powercylced."
Not the PC, the modem itself - what is the make and model of your modem? And you also mention a router, if your on some sort of dsl based connection I would guess your "modem" is not really just a modem but a gateway (modem/router combo) And you could be double natting for starters - should work, but can be flaking - especially if you for example have same network on both sides of your router.
Taking the router of the equation couldn't hurt for testing, but if its an actual "modem" then yes quite often you have to power cycle when you change the device connected to it, be it a router or pc, etc.
As to this info
"should be an interent IP it should not be starting with 192"
This a bit lacking. There are plenty of pubic IPs that can start with 192.
NetRange: 18.104.22.168 - 22.214.171.124
OrgName: BBN Communications
NetRange: 126.96.36.199 - 188.8.131.52
OrgName: Level 3 Communications, Inc.
NetRange: 184.108.40.206 - 220.127.116.11
OrgName: Group Health Cooperative
Its quite possible his ISP uses 192.x.x.x, the private address space is 192.168.x.x, 10.x.x.x, 172.16-31.x.x so if your directly connected to the public net and not behind a NAT, then your IP should be something other than those. If you fail to get an IP from a dhcp server, then your IP could be 169.254.x.x which is APIPA and just means some random IP your machine gave itself when a dhcp server didn't answer - this will not be routable on the public net, etc.
If you get an IP other than in the ranges listed, this should be from your ISP when directly connected to your "modem" and lets see if you still have the issue.
While your directly connected to your "modem" and working, ping your gateway - you can find this from ipconfig /all -- also look to see what your dns servers are. If your internet stops working, ping the gateway address - does it respond? Are you getting packet loss? Ping it it with
ping ipaddressofgatewway -t
and let it run for awhile, do some pings not answer -- after about 100 or so, hit cntrl+C what does it show you for amount lost (% loss) if this not zero it points to issue with your ISP.
If that is working great and still internet problems, test your dns -- do a nslookup to something, does it respond? Flush your dns, ipconfig /flushdns Do queries with nslookup, do they respond or timeout? If they timeout, then you have issue with dns if your ping test to gateway showed no loss, etc.