I went onto a website on Saturday and an avast message popped up for a couple of seconds (too fast to read what it said) something to do with Java started to load and my computer blue screened! It had the error message Stop: 0x0000008E (0xF8461AA2, 0xF8A04925, 0x0000000). I restarted the computer and it loaded up fine but avast couldn't connect to the server and I couldn't connect to the internet. The wireless is telling me there is a good connection and all the other devices in the house that use it are working fine. I did a cmd ipconfig /all and got the message: An internal error occurred: The request is not supported. Please contact Microsoft Product Support Services for further help. Additional information: Unable to query host name. I had a feeling it was a virus or spyware stopping me connecting but a scan with avast and microsoft showed nothing. I'm not very technical so all I can really say about the laptop is that is a Dell Inspiron 1300. If anyone has any ideas how to fix the problem, I would be extremley grateful!! Becky1 person needs an answerI do too

1. Go to Control Panel>Internet Options>Connections tab>LAN button. Make sure that nothing is checked in the "use a proxy" boxes. If it is, clear both of those boxes. 2. Check for malware by doing the preparatory work and running MalwareBytes' Anti-Malware as described here: http://www.elephantboycomputers.com/page2.html#Removing_MalwareMS-MVP - Elephant Boy Computers - Don't Panic!

Checked and both the boxes were clear. I had MalwareBytes installed and had run a scan that showed no infections. I ran it again and it came up with one which I removed and it restarted the computer. Now it has loaded again and I still can't get onto the internet. In Avast, I have a message saying: ATTENTION Your system is not fully protected. Please use the Fix now button to start fully protecting your system. When I click the Fix Now button, nothing happens and I can not turn on the Real-time Shield by clicking the button next to that either! Becky

The Avast error is because you're not online. Make sure the problem isn't with your Internet Service Provider, the modem, the router (whichever you have). The Stop Error can be caused by failed hardware so it you should make sure the hardware is sound, beginning with the RAM. http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot MS-MVP - Elephant Boy Computers - Don't Panic!

I'm going to pick this one up where Becky left off.I'm having the same issue and cannot find a solution.I've tried a lot of different steps...I'll list them as other websites I've browsed have suggested them and it worked for some people. I'm running XP SP3 (installed SP3 post facto)The issue started for me sometime last week. Several shortcuts to crude (because I can't say the P word) sites were placed on the desktop and a fake anti-virus program popped up saying that I needed to purchase the full version. It set the proxy in IE and Firefox to it's website (so it always displayed a local html file showing a message about the fake anti-virus needing to be purchased). It disabled the control panel and almost every .exe in the system32 folder. I had to boot to safe mode to run msconfig and disable many services and start-up programs. Then I booted normally and installed SEP 11 and updated definitions. I ran a scan and had a dozen hits or so for Backdoor.tidserv!inf, Trojan.Zlob, W32.IRCbot, Infostealer.Gampass, Trojan.Zbot (all listed up to this point were in the IPSec.sys file, which is the ultimate problem), Backdoor.Trojan, Trojan Horse (both in DLLs that came from the infection), Hacktool, Trojan.gen, Trojan Horse, Backdoor.Trojan, Infostealer.Bancos, W32.Changeup.C, Trojan.FakeAV (all in the executables for the infection), etc. There are a lot of them.Anyway, I found the files and removed them. Unfortunately for me, I removed the tcpip.sys and ipsec.sys (check your quarantine for these files). I also disabled System Restore, as many of the files were lurking there and the System Volume Information folder. After a restart, I could then get in to my control panel and run my executables from the system32 folder (yay!), so I re-enabled my much-needed start-up services and programs (not all of them [and definitely not the infected ones]).Symantec scans come back clean, but I get the same message when I try ipconfig. Ping localhost returns "Unable to contact IP driver, error code 2,"So I check my services. DHCP is not started. I try to start it. It fails because of a dependency service isn't started. I check the dependencies and it lists the following system components: AFT, NetBios over TCP/IP, and TCP/IP Protocol Driver. (...haha. I think I just figured it out. I'll continue with my troubleshooting steps, though).I tried several repair methods, including "netsh int ip reset resetlog.txt", "netsh winsock reset", and I reinstalled the network card. Nothing worked.I'm working on another angle, though, and I'll post it shortly (whether it works or not).

Hey Becky, Go to your device manager ( Control Panel, Hardware) Find your device and click uninstall, Restart your PC and this should automatically re-install the device , I think the driver is just corrupt I have seen it happen before.. If all else fails, run the system restore wizard, that will fix it. Brett.

It worked.Here's the procedure for XP.Step #1Full uninstall of TCP/IP ... no bullbleep.----------------------------------------------------------------------1. Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad. 2. Locate the [MS_TCPIP.PrimaryInstall] section. 3. Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80. 4. Save the file, and then exit Notepad. 5. In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties. 6. On the General tab, click Install, select Protocol, and then click Add. 7. In the Select Network Protocols window, click Have Disk. 8. In the Copy manufacturer's files from: text box, type c:\windows\inf, and then click OK. 9. Select Internet Protocol (TCP/IP), and then click OK.Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.10. Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes. RESTARTsuccesfull uninstallation of TCP/IP will remove numerous keys from the registry includingHKLM/system/CurrentControlSet/services/tcpipHKLM/system/CurrentControlSet/services/dhcpHKLM/system/CurrentControlSet/services/dnscacheHKLM/system/CurrentControlSet/services/ipsecHKLM/system/CurrentControlSet/services/policyagentHKLM/system/CurrentControlSet/services/atmarpcHKLM/system/CurrentControlSet/services/nlaThese represent various interconnected and interdependant services.For good measure you should delete the following keys before reinstalling TCP/IP in step #2HKLM/system/CurrentControlSet/services/winsockHKLM/system/CurrentControlSet/services/winsock2Step #2Reinstall of TCP/IP----------------------------------------------------------------------Following the above substep #3, replace the 0x80 back to 0xa0, this will eliminate the related "unsigned driver" error that was encountered during the uninstallation phase.Return to "local area connection"> properties > general tab > install > Protocol > TCP/IPYou may receive an "Extended Error" failure upon trying to reinstall the TCP/IP, this is related to the installer sub-system conflicting with the security database status.to check the integrity of the security databaseesentutl /g c:\windows\security\Database\secedit.sdb There may be a message saying database is out of datefirst try the recovery optionesentutl /r c:\windows\security\Database\secedit.sdbthis did not work for me, I needed the repair optionesentutl /p c:\windows\security\Database\secedit.sdbrerun the /g option to ensure that integrity is good and database is up to date.Now return to the "local area network setup" choose install > protocol > tcp/ip and try againReboot. ----------- Okay, it -almost- worked. Run devmgmt.msc. Click View > Show Hidden Devices. AFD still has the ! next to it. I'm going to post a fix for that shortly, as well.When I run an ipconfig now I get 0.0.0.0 and the connection is trying to connect to the router. ipconfig -renew returns "An error occurred while renewing interface Local Area Connection : The RPC server is unavailable."AFD is required for a lot of services to start (including DHCP client!), so that should fix it...Stay tuned!

Okay, I really fixed it this time. Went into %windir%\system32\drivers\ and found my AFD.sys. Next to it was AFD.old.sys. I was going to swap the two as I thought the current AFD.sys was from the previous infection. As soon as I changed AFD.sys to AFD.old2.sys, Windows created a new AFD.sys. I was a little confused for a second because I couldn't change AFD.old.sys to AFD.sys (another file had that name). I hoped I'd find it at the bottom and I did. I restarted the DHCP service and it pulled an IP. My computer is so happy to be looking at Google again... Hope this helps!

HiA better way might be to run WinXP refresh Install.Assuming that the computer is Now Clean.With XP you can do a refresh install without really touching the current applications and data.Refresh XP Installation. Boot from the XP original CD. Skip the first screen that offers Console Repair, and continue as though you install a New XP.After you Agree etc., the new install screen will come on and would detect the current XP installation.Choose the Repair option by Pressing R for Repair.Use it, would take about 45Min. and you will have a Refreshed Installation of XP while keeping all your data and XP configuration.P.S. If previously you made changes to WinXP Security setting (Like Firewall special permission), you have to look over them after the refresh since they might revert to the Default. Jack-MVP Windows Networking. WWW.EZLAN.NET

HiA better way might be to run WinXP refresh Install.Assuming that the computer is Now Clean.With XP you can do a refresh install without really touching the current applications and data.Refresh XP Installation. Boot from the XP original CD. Skip the first screen that offers Console Repair, and continue as though you install a New XP.After you Agree etc., the new install screen will come on and would detect the current XP installation.Choose the Repair option by Pressing R for Repair.Use it, would take about 45Min. and you will have a Refreshed Installation of XP while keeping all your data and XP configuration.P.S. If previously you made changes to WinXP Security setting (Like Firewall special permission), you have to look over them after the refresh since they might revert to the Default. Jack-MVP Windows Networking. WWW.EZLAN.NETThat's the problem with Windows, though. People need to be able to fix this without reloading the entire OS. The entire OS isn't faulty, so why fix what isn't broken? Very soon, I can see a billion people behind computers and none of them will have a clue.Know what you're doing and know it well. If you let the OS call the shots, you haven't learned anything. Your computer isn't smarter than you.