Well, before I get to the point, I think I'll tell you guys a little background information.
Recently I got the dreaded blue screen of death error on my computer. It moved so fast that I could not read it thoroughly, but it was a crash dump. This happened over and over. I would get the error, the laptop would restart itself, go back JUST before the sign in screen on my User Account, freeze, get the error again, and repeat this endless cycle until I booted it into safe mode. (In safe mode, I decided to uninstall Net Nanny, which I put on my computer earlier. Recently a file in it went corrupt, and I intended to uninstall it in the first place, but never got around to it. I still do not know if this is the source of the problem.) Another thing, when I tried booting it into "Safe Mode with Networking" this gave me the same error as when I tried getting on originally. (Also, I can't access or uninstall Spyware Doctor for some reason. Maybe the system restore interfered with the updates?)
The Net Nanny thing didn't seem to solve it. I kept getting the error, so I finally said "Hell with it." and did a system restore to a couple days back. I rebooted my computer afterward, and I could sign into my user account once again.
But, it wasn't over apparently.
Now when I try to connect to the internet I can't. I cannot use any of my browsers (IE, Chrome, FireFox, Safari), I cannot sign into MSN, can't play Onverse, etc.
(I have a Windows 7, VAIO laptop, 64 bit by the way.)
When I troubleshoot it, I get a DNS error saying,
"Your DNS appears unable to resolve IP addresses."
And I also get a Key Ports error:
"Failed to connect to the service. This could be due to improper proxy or firewall settings. Please review your proxy and firewall settings. Proxy settings can be accessed through Windows Live Messenger Options. For firewall settings, please see the retailer's instructions."
Also, I can access the internet fine from this Mac laptop. I have looked on google but no answers have worked for me so far. I hope that if I get a good answer to this, it will also help many other people in the future.
PS: I tried the troubleshooter, it says it cannot identify the problem.
Edited by Wynnd, 12 July 2010 - 02:59 PM.