Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Infected with the Google Redirect Virus.


  • Please log in to reply
26 replies to this topic

#1 AndyGarr

AndyGarr

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 16 June 2011 - 10:29 PM

I have the Google redirect virus, and most of the time, my google searches are redirected to Scour, Lab-Search, etc. I've trid using Mbam, Avg, and TDSSKiller, but none of those have worked. What should I do? I am running on Winodws 7.

Edited by AndyGarr, 16 June 2011 - 10:29 PM.


BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:29 AM

Posted 16 June 2011 - 10:46 PM

Hello you did use the latest version of TDSSKiller?

Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.5.4.0) from Kaspersky's website and not TDSSKiller.zip which appears to be an older version 2.3.2.2 of the tool.
  • Double-click on TDSSKiller.exe to run the tool for known TDSS variants.
    Vista/Windows 7 users right-click and select Run As Administrator.
  • If TDSSKiller does not run, try renaming it.
  • To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to How to change the file extension.
  • Click the Start Scan button.
  • Do not use the computer during the scan
  • If the scan completes with nothing found, click Close to exit.
  • If malicious objects are found, they will show in the Scan results - Select action for found objects and offer three options.
  • Ensure Cure (default) is selected, then click Continue > Reboot now to finish the cleaning process.
  • A log file named TDSSKiller_version_date_time_log.txt (i.e. TDSSKiller.2.4.0.0_27.07.2010_09.o7.26_log.txt) will be created and saved to the root directory (usually Local Disk C:).
  • Copy and paste the contents of that file in your next reply.


Then run
Please download GooredFix from one of the locations below and save it to your Desktop
Download Mirror #1
Download Mirror #2
  • Ensure all Firefox windows are closed.
  • To run the tool, double-click it (XP), or right-click and select Run As Administrator (Vista).
  • When prompted to run the scan, click Yes.
  • GooredFix will check for infections, and then a log will appear. Please post the contents of that log in your next reply (it can also be found on your desktop, called GooredFix.txt).



If still redirecting>>>
Change your DNS Servers:
  • Go to Posted Image > Run... and in the open box, type: cmd
  • Press OK or Hit Enter.
  • At the command prompt, type or copy/paste: ipconfig /flushdns
  • Hit Enter.
  • You will get a confirmation that the flush was successful.
  • Close the command box.
If the above commands did not resolve the problem, the next thing to try is to reset your network settings and Configure TCP/IP to use DNS.
  • Go to Posted Image > Control Panel, and choose Network Connections.
  • Right-click on your default connection, usually Local Area Connection or Dial-up Connection if you are using Dial-up, and and choose Properties.
  • Double-click on Internet Protocol (TCP/IP) or highlight it and select Properties.
  • Under the General tab, write down any settings in case you should need to change them back.
  • Select the button that says "Obtain an IP address automatically" or make sure the DNS server IP address is the same as provided by your ISP.
  • Select the button that says "Obtain DNS servers automatically".
  • If unknown Preferred or Alternate DNS servers are listed, uncheck the box that says "Use the following DNS server address".
  • Click OK twice to get out of the properties screen and restart your computer. If not prompted to reboot go ahead and reboot manually.
-- Vista users can refer to How to Change TCP/IP settings

CAUTION: It's possible that your ISP (Internet Service Provider) requires specific DNS settings here. Make sure you know if you need these settings or not BEFORE you make any changes or you may lose your Internet connection. If you're sure you do not need a specific DNS address,
then you may proceed.


I have to leave now but will look in again.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#3 AndyGarr

AndyGarr
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 17 June 2011 - 12:52 AM

I have tried everything, but I am still redirecting. I wasn't really able to "reset your network settings and Configure TCP/IP to use DNS", because I am using a laptop with wireless internet on windows 7, and the steps didn't seem to match with what I saw.

Here are the two logs. Thanks so far!

Here is the TDSSKiller Log:

2011/06/16 22:35:09.0775 3328 TDSS rootkit removing tool 2.5.5.0 Jun 16 2011 15:25:15
2011/06/16 22:35:10.0251 3328 ================================================================================
2011/06/16 22:35:10.0251 3328 SystemInfo:
2011/06/16 22:35:10.0252 3328
2011/06/16 22:35:10.0252 3328 OS Version: 6.1.7600 ServicePack: 0.0
2011/06/16 22:35:10.0252 3328 Product type: Workstation
2011/06/16 22:35:10.0252 3328 ComputerName: GATEWAY-ID5822U
2011/06/16 22:35:10.0252 3328 UserName: Andy Gar
2011/06/16 22:35:10.0252 3328 Windows directory: C:\Windows
2011/06/16 22:35:10.0252 3328 System windows directory: C:\Windows
2011/06/16 22:35:10.0252 3328 Processor architecture: Intel x86
2011/06/16 22:35:10.0252 3328 Number of processors: 2
2011/06/16 22:35:10.0252 3328 Page size: 0x1000
2011/06/16 22:35:10.0252 3328 Boot type: Normal boot
2011/06/16 22:35:10.0252 3328 ================================================================================
2011/06/16 22:35:11.0698 3328 Initialize success
2011/06/16 22:35:21.0830 4124 ================================================================================
2011/06/16 22:35:21.0830 4124 Scan started
2011/06/16 22:35:21.0830 4124 Mode: Manual;
2011/06/16 22:35:21.0830 4124 ================================================================================
2011/06/16 22:35:22.0743 4124 1394ohci (6d2aca41739bfe8cb86ee8e85f29697d) C:\Windows\system32\DRIVERS\1394ohci.sys
2011/06/16 22:35:22.0790 4124 ACPI (f0e07d144c8685b8774bc32fc8da4df0) C:\Windows\system32\DRIVERS\ACPI.sys
2011/06/16 22:35:22.0809 4124 AcpiPmi (98d81ca942d19f7d9153b095162ac013) C:\Windows\system32\DRIVERS\acpipmi.sys
2011/06/16 22:35:22.0847 4124 adp94xx (21e785ebd7dc90a06391141aac7892fb) C:\Windows\system32\DRIVERS\adp94xx.sys
2011/06/16 22:35:22.0920 4124 adpahci (0c676bc278d5b59ff5abd57bbe9123f2) C:\Windows\system32\DRIVERS\adpahci.sys
2011/06/16 22:35:23.0030 4124 adpu320 (7c7b5ee4b7b822ec85321fe23a27db33) C:\Windows\system32\DRIVERS\adpu320.sys
2011/06/16 22:35:23.0076 4124 AFD (ddc040fdb01ef1712a6b13e52afb104c) C:\Windows\system32\drivers\afd.sys
2011/06/16 22:35:23.0100 4124 agp440 (507812c3054c21cef746b6ee3d04dd6e) C:\Windows\system32\DRIVERS\agp440.sys
2011/06/16 22:35:23.0139 4124 aic78xx (8b30250d573a8f6b4bd23195160d8707) C:\Windows\system32\DRIVERS\djsvs.sys
2011/06/16 22:35:23.0287 4124 aliide (0d40bcf52ea90fc7df2aeab6503dea44) C:\Windows\system32\DRIVERS\aliide.sys
2011/06/16 22:35:23.0304 4124 amdagp (3c6600a0696e90a463771c7422e23ab5) C:\Windows\system32\DRIVERS\amdagp.sys
2011/06/16 22:35:23.0325 4124 amdide (cd5914170297126b6266860198d1d4f0) C:\Windows\system32\DRIVERS\amdide.sys
2011/06/16 22:35:23.0345 4124 AmdK8 (00dda200d71bac534bf56a9db5dfd666) C:\Windows\system32\DRIVERS\amdk8.sys
2011/06/16 22:35:23.0368 4124 AmdPPM (3cbf30f5370fda40dd3e87df38ea53b6) C:\Windows\system32\DRIVERS\amdppm.sys
2011/06/16 22:35:23.0387 4124 amdsata (2101a86c25c154f8314b24ef49d7fbc2) C:\Windows\system32\DRIVERS\amdsata.sys
2011/06/16 22:35:23.0410 4124 amdsbs (ea43af0c423ff267355f74e7a53bdaba) C:\Windows\system32\DRIVERS\amdsbs.sys
2011/06/16 22:35:23.0479 4124 amdxata (b81c2b5616f6420a9941ea093a92b150) C:\Windows\system32\DRIVERS\amdxata.sys
2011/06/16 22:35:23.0799 4124 AppID (feb834c02ce1e84b6a38f953ca067706) C:\Windows\system32\drivers\appid.sys
2011/06/16 22:35:24.0111 4124 arc (2932004f49677bd84dbc72edb754ffb3) C:\Windows\system32\DRIVERS\arc.sys
2011/06/16 22:35:24.0209 4124 arcsas (5d6f36c46fd283ae1b57bd2e9feb0bc7) C:\Windows\system32\DRIVERS\arcsas.sys
2011/06/16 22:35:24.0256 4124 AsyncMac (add2ade1c2b285ab8378d2daaf991481) C:\Windows\system32\DRIVERS\asyncmac.sys
2011/06/16 22:35:24.0284 4124 atapi (338c86357871c167a96ab976519bf59e) C:\Windows\system32\DRIVERS\atapi.sys
2011/06/16 22:35:24.0610 4124 AVGIDSDriver (2177e7448c1ecfb35a5db417603d205a) C:\Windows\system32\DRIVERS\AVGIDSDriver.Sys
2011/06/16 22:35:24.0847 4124 AVGIDSEH (13256fc72fa5b3f6d6e8c5957e579b7c) C:\Windows\system32\DRIVERS\AVGIDSEH.Sys
2011/06/16 22:35:24.0947 4124 AVGIDSFilter (fa0685cc51de5cfd804e7deaa6488e0e) C:\Windows\system32\DRIVERS\AVGIDSFilter.Sys
2011/06/16 22:35:25.0036 4124 AVGIDSShim (f788b51100d0f40ea176798cce954a1a) C:\Windows\system32\DRIVERS\AVGIDSShim.Sys
2011/06/16 22:35:25.0232 4124 Avgldx86 (4e796d3d2c3182b13b3e3b5a2ad4ef0a) C:\Windows\system32\DRIVERS\avgldx86.sys
2011/06/16 22:35:25.0515 4124 Avgmfx86 (5639de66b37d02bd22df4cf3155fba60) C:\Windows\system32\DRIVERS\avgmfx86.sys
2011/06/16 22:35:25.0725 4124 Avgrkx86 (d1baf652eda0ae70896276a1fb32c2d4) C:\Windows\system32\DRIVERS\avgrkx86.sys
2011/06/16 22:35:25.0781 4124 Avgtdix (aaf0ebcad95f2164cffb544e00392498) C:\Windows\system32\DRIVERS\avgtdix.sys
2011/06/16 22:35:25.0945 4124 b06bdrv (1a231abec60fd316ec54c66715543cec) C:\Windows\system32\DRIVERS\bxvbdx.sys
2011/06/16 22:35:26.0107 4124 b57nd60x (bd8869eb9cde6bbe4508d869929869ee) C:\Windows\system32\DRIVERS\b57nd60x.sys
2011/06/16 22:35:26.0214 4124 Beep (505506526a9d467307b3c393dedaf858) C:\Windows\system32\drivers\Beep.sys
2011/06/16 22:35:26.0262 4124 blbdrive (2287078ed48fcfc477b05b20cf38f36f) C:\Windows\system32\DRIVERS\blbdrive.sys
2011/06/16 22:35:26.0474 4124 bowser (fcafaef6798d7b51ff029f99a9898961) C:\Windows\system32\DRIVERS\bowser.sys
2011/06/16 22:35:26.0512 4124 BrFiltLo (9f9acc7f7ccde8a15c282d3f88b43309) C:\Windows\system32\DRIVERS\BrFiltLo.sys
2011/06/16 22:35:26.0697 4124 BrFiltUp (56801ad62213a41f6497f96dee83755a) C:\Windows\system32\DRIVERS\BrFiltUp.sys
2011/06/16 22:35:26.0826 4124 Brserid (845b8ce732e67f3b4133164868c666ea) C:\Windows\System32\Drivers\Brserid.sys
2011/06/16 22:35:26.0854 4124 BrSerWdm (203f0b1e73adadbbb7b7b1fabd901f6b) C:\Windows\System32\Drivers\BrSerWdm.sys
2011/06/16 22:35:26.0891 4124 BrUsbMdm (bd456606156ba17e60a04e18016ae54b) C:\Windows\System32\Drivers\BrUsbMdm.sys
2011/06/16 22:35:27.0052 4124 BrUsbSer (af72ed54503f717a43268b3cc5faec2e) C:\Windows\System32\Drivers\BrUsbSer.sys
2011/06/16 22:35:27.0408 4124 BTHMODEM (ed3df7c56ce0084eb2034432fc56565a) C:\Windows\system32\DRIVERS\bthmodem.sys
2011/06/16 22:35:27.0518 4124 cdfs (77ea11b065e0a8ab902d78145ca51e10) C:\Windows\system32\DRIVERS\cdfs.sys
2011/06/16 22:35:27.0566 4124 cdrom (ba6e70aa0e6091bc39de29477d866a77) C:\Windows\system32\DRIVERS\cdrom.sys
2011/06/16 22:35:27.0599 4124 circlass (3fe3fe94a34df6fb06e6418d0f6a0060) C:\Windows\system32\DRIVERS\circlass.sys
2011/06/16 22:35:27.0650 4124 CLFS (635181e0e9bbf16871bf5380d71db02d) C:\Windows\system32\CLFS.sys
2011/06/16 22:35:27.0785 4124 CmBatt (dea805815e587dad1dd2c502220b5616) C:\Windows\system32\DRIVERS\CmBatt.sys
2011/06/16 22:35:27.0811 4124 cmdide (c537b1db64d495b9b4717b4d6d9edbf2) C:\Windows\system32\DRIVERS\cmdide.sys
2011/06/16 22:35:27.0849 4124 CNG (1b675691ed940766149c93e8f4488d68) C:\Windows\system32\Drivers\cng.sys
2011/06/16 22:35:28.0013 4124 Compbatt (a6023d3823c37043986713f118a89bee) C:\Windows\system32\DRIVERS\compbatt.sys
2011/06/16 22:35:28.0035 4124 CompositeBus (f1724ba27e97d627f808fb0ba77a28a6) C:\Windows\system32\DRIVERS\CompositeBus.sys
2011/06/16 22:35:28.0165 4124 cpudrv (d01f685f8b4598d144b0cce9ff95d8d5) C:\Program Files\SystemRequirementsLab\cpudrv.sys
2011/06/16 22:35:28.0245 4124 crcdisk (2c4ebcfc84a9b44f209dff6c6e6c61d1) C:\Windows\system32\DRIVERS\crcdisk.sys
2011/06/16 22:35:28.0309 4124 CSC (27c9490bdd0ae48911ab8cf1932591ed) C:\Windows\system32\drivers\csc.sys
2011/06/16 22:35:28.0362 4124 DfsC (8e09e52ee2e3ceb199ef3dd99cf9e3fb) C:\Windows\system32\Drivers\dfsc.sys
2011/06/16 22:35:28.0442 4124 discache (1a050b0274bfb3890703d490f330c0da) C:\Windows\system32\drivers\discache.sys
2011/06/16 22:35:28.0474 4124 Disk (565003f326f99802e68ca78f2a68e9ff) C:\Windows\system32\DRIVERS\disk.sys
2011/06/16 22:35:28.0537 4124 drmkaud (b918e7c5f9bf77202f89e1a9539f2eb4) C:\Windows\system32\drivers\drmkaud.sys
2011/06/16 22:35:28.0661 4124 dtsoftbus01 (555e54ac2f601a8821cef58961653991) C:\Windows\system32\DRIVERS\dtsoftbus01.sys
2011/06/16 22:35:28.0740 4124 DXGKrnl (8b6c3464d7fac176500061dbfff42ad4) C:\Windows\System32\drivers\dxgkrnl.sys
2011/06/16 22:35:29.0069 4124 ebdrv (024e1b5cac09731e4d868e64dbfb4ab0) C:\Windows\system32\DRIVERS\evbdx.sys
2011/06/16 22:35:29.0504 4124 elxstor (0ed67910c8c326796faa00b2bf6d9d3c) C:\Windows\system32\DRIVERS\elxstor.sys
2011/06/16 22:35:29.0678 4124 ErrDev (8fc3208352dd3912c94367a206ab3f11) C:\Windows\system32\DRIVERS\errdev.sys
2011/06/16 22:35:29.0763 4124 exfat (2dc9108d74081149cc8b651d3a26207f) C:\Windows\system32\drivers\exfat.sys
2011/06/16 22:35:29.0826 4124 fastfat (7e0ab74553476622fb6ae36f73d97d35) C:\Windows\system32\drivers\fastfat.sys
2011/06/16 22:35:29.0901 4124 fdc (e817a017f82df2a1f8cfdbda29388b29) C:\Windows\system32\DRIVERS\fdc.sys
2011/06/16 22:35:29.0968 4124 FileInfo (6cf00369c97f3cf563be99be983d13d8) C:\Windows\system32\drivers\fileinfo.sys
2011/06/16 22:35:29.0997 4124 Filetrace (42c51dc94c91da21cb9196eb64c45db9) C:\Windows\system32\drivers\filetrace.sys
2011/06/16 22:35:30.0108 4124 flpydisk (87907aa70cb3c56600f1c2fb8841579b) C:\Windows\system32\DRIVERS\flpydisk.sys
2011/06/16 22:35:30.0166 4124 FltMgr (7520ec808e0c35e0ee6f841294316653) C:\Windows\system32\drivers\fltmgr.sys
2011/06/16 22:35:30.0204 4124 FsDepends (1a16b57943853e598cff37fe2b8cbf1d) C:\Windows\system32\drivers\FsDepends.sys
2011/06/16 22:35:30.0272 4124 Fs_Rec (a574b4360e438977038aae4bf60d79a2) C:\Windows\system32\drivers\Fs_Rec.sys
2011/06/16 22:35:30.0318 4124 fvevol (5592f5dba26282d24d2b080eb438a4d7) C:\Windows\system32\DRIVERS\fvevol.sys
2011/06/16 22:35:30.0346 4124 gagp30kx (65ee0c7a58b65e74ae05637418153938) C:\Windows\system32\DRIVERS\gagp30kx.sys
2011/06/16 22:35:30.0479 4124 GEARAspiWDM (8182ff89c65e4d38b2de4bb0fb18564e) C:\Windows\system32\DRIVERS\GEARAspiWDM.sys
2011/06/16 22:35:30.0560 4124 hcw85cir (c44e3c2bab6837db337ddee7544736db) C:\Windows\system32\drivers\hcw85cir.sys
2011/06/16 22:35:30.0642 4124 HdAudAddService (3530cad25deba7dc7de8bb51632cbc5f) C:\Windows\system32\drivers\HdAudio.sys
2011/06/16 22:35:30.0709 4124 HDAudBus (717a2207fd6f13ad3e664c7d5a43c7bf) C:\Windows\system32\DRIVERS\HDAudBus.sys
2011/06/16 22:35:30.0752 4124 HidBatt (1d58a7f3e11a9731d0eaaaa8405acc36) C:\Windows\system32\DRIVERS\HidBatt.sys
2011/06/16 22:35:30.0832 4124 HidBth (89448f40e6df260c206a193a4683ba78) C:\Windows\system32\DRIVERS\hidbth.sys
2011/06/16 22:35:30.0883 4124 HidIr (cf50b4cf4a4f229b9f3c08351f99ca5e) C:\Windows\system32\DRIVERS\hidir.sys
2011/06/16 22:35:30.0954 4124 HidUsb (25072fb35ac90b25f9e4e3bacf774102) C:\Windows\system32\DRIVERS\hidusb.sys
2011/06/16 22:35:31.0040 4124 HpSAMD (295fdc419039090eb8b49ffdbb374549) C:\Windows\system32\DRIVERS\HpSAMD.sys
2011/06/16 22:35:31.0136 4124 HSF_DPV (227c3ba25012752bb7450235392c719f) C:\Windows\system32\DRIVERS\HSX_DPV.sys
2011/06/16 22:35:31.0322 4124 HSXHWAZL (4df5c76302dc2f8f3465966c8426a292) C:\Windows\system32\DRIVERS\HSXHWAZL.sys
2011/06/16 22:35:31.0392 4124 HTTP (c531c7fd9e8b62021112787c4e2c5a5a) C:\Windows\system32\drivers\HTTP.sys
2011/06/16 22:35:31.0495 4124 hwpolicy (8305f33cde89ad6c7a0763ed0b5a8d42) C:\Windows\system32\drivers\hwpolicy.sys
2011/06/16 22:35:31.0588 4124 i8042prt (f151f0bdc47f4a28b1b20a0818ea36d6) C:\Windows\system32\DRIVERS\i8042prt.sys
2011/06/16 22:35:31.0625 4124 iaStorV (934af4d7c5f457b9f0743f4299b77b67) C:\Windows\system32\DRIVERS\iaStorV.sys
2011/06/16 22:35:31.0893 4124 igfx (ad626f6964f4d364d226c39e06872dd3) C:\Windows\system32\DRIVERS\igdkmd32.sys
2011/06/16 22:35:32.0099 4124 iirsp (4173ff5708f3236cf25195fecd742915) C:\Windows\system32\DRIVERS\iirsp.sys
2011/06/16 22:35:32.0184 4124 IntcHdmiAddService (81486f0eb4238b65c317f97de246c4ac) C:\Windows\system32\drivers\IntcHdmi.sys
2011/06/16 22:35:32.0353 4124 intelide (a0f12f2c9ba6c72f3987ce780e77c130) C:\Windows\system32\DRIVERS\intelide.sys
2011/06/16 22:35:32.0378 4124 intelppm (3b514d27bfc4accb4037bc6685f766e0) C:\Windows\system32\DRIVERS\intelppm.sys
2011/06/16 22:35:32.0429 4124 IpFilterDriver (709d1761d3b19a932ff0238ea6d50200) C:\Windows\system32\DRIVERS\ipfltdrv.sys
2011/06/16 22:35:32.0466 4124 IPMIDRV (e4454b6c37d7ffd5649611f6496308a7) C:\Windows\system32\DRIVERS\IPMIDrv.sys
2011/06/16 22:35:32.0550 4124 IPNAT (a5fa468d67abcdaa36264e463a7bb0cd) C:\Windows\system32\drivers\ipnat.sys
2011/06/16 22:35:32.0578 4124 IRENUM (42996cff20a3084a56017b7902307e9f) C:\Windows\system32\drivers\irenum.sys
2011/06/16 22:35:32.0604 4124 isapnp (1f32bb6b38f62f7df1a7ab7292638a35) C:\Windows\system32\DRIVERS\isapnp.sys
2011/06/16 22:35:32.0636 4124 iScsiPrt (ed46c223ae46c6866ab77cdc41c404b7) C:\Windows\system32\DRIVERS\msiscsi.sys
2011/06/16 22:35:32.0683 4124 k57nd60x (c4c95805b85bce1eb9d20f4a02fc5f9b) C:\Windows\system32\DRIVERS\k57nd60x.sys
2011/06/16 22:35:32.0791 4124 kbdclass (adef52ca1aeae82b50df86b56413107e) C:\Windows\system32\DRIVERS\kbdclass.sys
2011/06/16 22:35:32.0818 4124 kbdhid (3d9f0ebf350edcfd6498057301455964) C:\Windows\system32\DRIVERS\kbdhid.sys
2011/06/16 22:35:32.0849 4124 KSecDD (e36a061ec11b373826905b21be10948f) C:\Windows\system32\Drivers\ksecdd.sys
2011/06/16 22:35:32.0887 4124 KSecPkg (365c6154bbbc5377173f1ca7bfb6cc59) C:\Windows\system32\Drivers\ksecpkg.sys
2011/06/16 22:35:33.0039 4124 lltdio (f7611ec07349979da9b0ae1f18ccc7a6) C:\Windows\system32\DRIVERS\lltdio.sys
2011/06/16 22:35:33.0108 4124 LSI_FC (eb119a53ccf2acc000ac71b065b78fef) C:\Windows\system32\DRIVERS\lsi_fc.sys
2011/06/16 22:35:33.0163 4124 LSI_SAS (8ade1c877256a22e49b75d1cc9161f9c) C:\Windows\system32\DRIVERS\lsi_sas.sys
2011/06/16 22:35:33.0302 4124 LSI_SAS2 (dc9dc3d3daa0e276fd2ec262e38b11e9) C:\Windows\system32\DRIVERS\lsi_sas2.sys
2011/06/16 22:35:33.0328 4124 LSI_SCSI (0a036c7d7cab643a7f07135ac47e0524) C:\Windows\system32\DRIVERS\lsi_scsi.sys
2011/06/16 22:35:33.0362 4124 luafv (6703e366cc18d3b6e534f5cf7df39cee) C:\Windows\system32\drivers\luafv.sys
2011/06/16 22:35:33.0494 4124 mdmxsdk (0cea2d0d3fa284b85ed5b68365114f76) C:\Windows\system32\DRIVERS\mdmxsdk.sys
2011/06/16 22:35:33.0531 4124 megasas (0fff5b045293002ab38eb1fd1fc2fb74) C:\Windows\system32\DRIVERS\megasas.sys
2011/06/16 22:35:33.0600 4124 MegaSR (dcbab2920c75f390caf1d29f675d03d6) C:\Windows\system32\DRIVERS\MegaSR.sys
2011/06/16 22:35:33.0712 4124 Modem (f001861e5700ee84e2d4e52c712f4964) C:\Windows\system32\drivers\modem.sys
2011/06/16 22:35:33.0733 4124 monitor (79d10964de86b292320e9dfe02282a23) C:\Windows\system32\DRIVERS\monitor.sys
2011/06/16 22:35:33.0765 4124 mouclass (fb18cc1d4c2e716b6b903b0ac0cc0609) C:\Windows\system32\DRIVERS\mouclass.sys
2011/06/16 22:35:33.0920 4124 mouhid (2c388d2cd01c9042596cf3c8f3c7b24d) C:\Windows\system32\DRIVERS\mouhid.sys
2011/06/16 22:35:34.0006 4124 mountmgr (921c18727c5920d6c0300736646931c2) C:\Windows\system32\drivers\mountmgr.sys
2011/06/16 22:35:34.0034 4124 mpio (2af5997438c55fb79d33d015c30e1974) C:\Windows\system32\DRIVERS\mpio.sys
2011/06/16 22:35:34.0068 4124 mpsdrv (ad2723a7b53dd1aacae6ad8c0bfbf4d0) C:\Windows\system32\drivers\mpsdrv.sys
2011/06/16 22:35:34.0096 4124 MRxDAV (b1be47008d20e43da3adc37c24cdb89d) C:\Windows\system32\drivers\mrxdav.sys
2011/06/16 22:35:34.0129 4124 mrxsmb (f1b6aa08497ea86ca6ef6f7a08b0bfb8) C:\Windows\system32\DRIVERS\mrxsmb.sys
2011/06/16 22:35:34.0271 4124 mrxsmb10 (5613358b4050f46f5a9832da8050d6e4) C:\Windows\system32\DRIVERS\mrxsmb10.sys
2011/06/16 22:35:34.0308 4124 mrxsmb20 (25c9792778d80feb4c8201e62281bfdf) C:\Windows\system32\DRIVERS\mrxsmb20.sys
2011/06/16 22:35:34.0340 4124 msahci (4326d168944123f38dd3b2d9c37a0b12) C:\Windows\system32\DRIVERS\msahci.sys
2011/06/16 22:35:34.0459 4124 msdsm (455029c7174a2dbb03dba8a0d8bddd9a) C:\Windows\system32\DRIVERS\msdsm.sys
2011/06/16 22:35:34.0500 4124 Msfs (daefb28e3af5a76abcc2c3078c07327f) C:\Windows\system32\drivers\Msfs.sys
2011/06/16 22:35:34.0536 4124 mshidkmdf (3e1e5767043c5af9367f0056295e9f84) C:\Windows\System32\drivers\mshidkmdf.sys
2011/06/16 22:35:34.0617 4124 msisadrv (0a4e5757ae09fa9622e3158cc1aef114) C:\Windows\system32\DRIVERS\msisadrv.sys
2011/06/16 22:35:34.0665 4124 MSKSSRV (8c0860d6366aaffb6c5bb9df9448e631) C:\Windows\system32\drivers\MSKSSRV.sys
2011/06/16 22:35:34.0696 4124 MSPCLOCK (3ea8b949f963562cedbb549eac0c11ce) C:\Windows\system32\drivers\MSPCLOCK.sys
2011/06/16 22:35:34.0754 4124 MSPQM (f456e973590d663b1073e9c463b40932) C:\Windows\system32\drivers\MSPQM.sys
2011/06/16 22:35:34.0856 4124 MsRPC (0e008fc4819d238c51d7c93e7b41e560) C:\Windows\system32\drivers\MsRPC.sys
2011/06/16 22:35:34.0887 4124 mssmbios (fc6b9ff600cc585ea38b12589bd4e246) C:\Windows\system32\DRIVERS\mssmbios.sys
2011/06/16 22:35:34.0915 4124 MSTEE (b42c6b921f61a6e55159b8be6cd54a36) C:\Windows\system32\drivers\MSTEE.sys
2011/06/16 22:35:34.0939 4124 MTConfig (33599130f44e1f34631cea241de8ac84) C:\Windows\system32\DRIVERS\MTConfig.sys
2011/06/16 22:35:35.0067 4124 Mup (159fad02f64e6381758c990f753bcc80) C:\Windows\system32\Drivers\mup.sys
2011/06/16 22:35:35.0214 4124 NativeWifiP (26384429fcd85d83746f63e798ab1480) C:\Windows\system32\DRIVERS\nwifi.sys
2011/06/16 22:35:35.0256 4124 NDIS (23759d175a0a9baaf04d05047bc135a8) C:\Windows\system32\drivers\ndis.sys
2011/06/16 22:35:35.0412 4124 NdisCap (0e1787aa6c9191d3d319e8bafe86f80c) C:\Windows\system32\DRIVERS\ndiscap.sys
2011/06/16 22:35:35.0441 4124 NdisTapi (e4a8aec125a2e43a9e32afeea7c9c888) C:\Windows\system32\DRIVERS\ndistapi.sys
2011/06/16 22:35:35.0460 4124 Ndisuio (b30ae7f2b6d7e343b0df32e6c08fce75) C:\Windows\system32\DRIVERS\ndisuio.sys
2011/06/16 22:35:35.0486 4124 NdisWan (267c415eadcbe53c9ca873dee39cf3a4) C:\Windows\system32\DRIVERS\ndiswan.sys
2011/06/16 22:35:35.0577 4124 NDProxy (af7e7c63dcef3f8772726f86039d6eb4) C:\Windows\system32\drivers\NDProxy.sys
2011/06/16 22:35:35.0603 4124 NetBIOS (80b275b1ce3b0e79909db7b39af74d51) C:\Windows\system32\DRIVERS\netbios.sys
2011/06/16 22:35:35.0656 4124 NetBT (dd52a733bf4ca5af84562a5e2f963b91) C:\Windows\system32\DRIVERS\netbt.sys
2011/06/16 22:35:36.0020 4124 NETw5s32 (5b2dfa9c5c02ddf2a113cc0f551b59df) C:\Windows\system32\DRIVERS\NETw5s32.sys
2011/06/16 22:35:36.0427 4124 netw5v32 (58218ec6b61b1169cf54aab0d00f5fe2) C:\Windows\system32\DRIVERS\netw5v32.sys
2011/06/16 22:35:36.0608 4124 nfrd960 (1d85c4b390b0ee09c7a46b91efb2c097) C:\Windows\system32\DRIVERS\nfrd960.sys
2011/06/16 22:35:36.0644 4124 Npfs (1db262a9f8c087e8153d89bef3d2235f) C:\Windows\system32\drivers\Npfs.sys
2011/06/16 22:35:36.0687 4124 nsiproxy (e9a0a4d07e53d8fea2bb8387a3293c58) C:\Windows\system32\drivers\nsiproxy.sys
2011/06/16 22:35:36.0739 4124 Ntfs (3795dcd21f740ee799fb7223234215af) C:\Windows\system32\drivers\Ntfs.sys
2011/06/16 22:35:36.0870 4124 Null (f9756a98d69098dca8945d62858a812c) C:\Windows\system32\drivers\Null.sys
2011/06/16 22:35:36.0904 4124 nvraid (3f3d04b1d08d43c16ea7963954ec768d) C:\Windows\system32\DRIVERS\nvraid.sys
2011/06/16 22:35:36.0936 4124 nvstor (c99f251a5de63c6f129cf71933aced0f) C:\Windows\system32\DRIVERS\nvstor.sys
2011/06/16 22:35:36.0961 4124 nv_agp (5a0983915f02bae73267cc2a041f717d) C:\Windows\system32\DRIVERS\nv_agp.sys
2011/06/16 22:35:37.0056 4124 ohci1394 (08a70a1f2cdde9bb49b885cb817a66eb) C:\Windows\system32\DRIVERS\ohci1394.sys
2011/06/16 22:35:37.0106 4124 Parport (2ea877ed5dd9713c5ac74e8ea7348d14) C:\Windows\system32\DRIVERS\parport.sys
2011/06/16 22:35:37.0132 4124 partmgr (ff4218952b51de44fe910953a3e686b9) C:\Windows\system32\drivers\partmgr.sys
2011/06/16 22:35:37.0164 4124 Parvdm (eb0a59f29c19b86479d36b35983daadc) C:\Windows\system32\DRIVERS\parvdm.sys
2011/06/16 22:35:37.0290 4124 pci (c858cb77c577780ecc456a892e7e7d0f) C:\Windows\system32\DRIVERS\pci.sys
2011/06/16 22:35:37.0326 4124 pciide (afe86f419014db4e5593f69ffe26ce0a) C:\Windows\system32\DRIVERS\pciide.sys
2011/06/16 22:35:37.0366 4124 pcmcia (f396431b31693e71e8a80687ef523506) C:\Windows\system32\DRIVERS\pcmcia.sys
2011/06/16 22:35:37.0491 4124 PCTCore (6ef125721a9f1f7dbf3229786f7decd0) C:\Windows\system32\drivers\PCTCore.sys
2011/06/16 22:35:37.0543 4124 pctDS (f820b4c61d1e591325b679d479d4eea4) C:\Windows\system32\drivers\pctDS.sys
2011/06/16 22:35:37.0609 4124 pctEFA (acc8c15f3d59f17c5d903ff1de3b43d3) C:\Windows\system32\drivers\pctEFA.sys
2011/06/16 22:35:37.0765 4124 pctgntdi (b76c829f00b9b534405b4ed5f58b8f52) C:\Windows\System32\drivers\pctgntdi.sys
2011/06/16 22:35:37.0836 4124 pctplsg (c5c488e6232b29f5744b8f7988a20730) C:\Windows\System32\drivers\pctplsg.sys
2011/06/16 22:35:37.0951 4124 pcw (250f6b43d2b613172035c6747aeeb19f) C:\Windows\system32\drivers\pcw.sys
2011/06/16 22:35:37.0996 4124 PEAUTH (9e0104ba49f4e6973749a02bf41344ed) C:\Windows\system32\drivers\peauth.sys
2011/06/16 22:35:38.0177 4124 PptpMiniport (631e3e205ad6d86f2aed6a4a8e69f2db) C:\Windows\system32\DRIVERS\raspptp.sys
2011/06/16 22:35:38.0251 4124 Processor (85b1e3a0c7585bc4aae6899ec6fcf011) C:\Windows\system32\DRIVERS\processr.sys
2011/06/16 22:35:38.0307 4124 Psched (6270ccae2a86de6d146529fe55b3246a) C:\Windows\system32\DRIVERS\pacer.sys
2011/06/16 22:35:38.0363 4124 ql2300 (ab95ecf1f6659a60ddc166d8315b0751) C:\Windows\system32\DRIVERS\ql2300.sys
2011/06/16 22:35:38.0499 4124 ql40xx (b4dd51dd25182244b86737dc51af2270) C:\Windows\system32\DRIVERS\ql40xx.sys
2011/06/16 22:35:38.0537 4124 QWAVEdrv (584078ca1b95ca72df2a27c336f9719d) C:\Windows\system32\drivers\qwavedrv.sys
2011/06/16 22:35:38.0569 4124 RasAcd (30a81b53c766d0133bb86d234e5556ab) C:\Windows\system32\DRIVERS\rasacd.sys
2011/06/16 22:35:38.0601 4124 RasAgileVpn (57ec4aef73660166074d8f7f31c0d4fd) C:\Windows\system32\DRIVERS\AgileVpn.sys
2011/06/16 22:35:38.0719 4124 Rasl2tp (d9f91eafec2815365cbe6d167e4e332a) C:\Windows\system32\DRIVERS\rasl2tp.sys
2011/06/16 22:35:38.0774 4124 RasPppoe (0fe8b15916307a6ac12bfb6a63e45507) C:\Windows\system32\DRIVERS\raspppoe.sys
2011/06/16 22:35:38.0805 4124 RasSstp (44101f495a83ea6401d886e7fd70096b) C:\Windows\system32\DRIVERS\rassstp.sys
2011/06/16 22:35:38.0837 4124 rdbss (835d7e81bf517a3b72384bdcc85e1ce6) C:\Windows\system32\DRIVERS\rdbss.sys
2011/06/16 22:35:38.0940 4124 rdpbus (0d8f05481cb76e70e1da06ee9f0da9df) C:\Windows\system32\DRIVERS\rdpbus.sys
2011/06/16 22:35:38.0965 4124 RDPCDD (1e016846895b15a99f9a176a05029075) C:\Windows\system32\DRIVERS\RDPCDD.sys
2011/06/16 22:35:39.0009 4124 RDPDR (c5ff95883ffef704d50c40d21cfb3ab5) C:\Windows\system32\drivers\rdpdr.sys
2011/06/16 22:35:39.0054 4124 RDPENCDD (5a53ca1598dd4156d44196d200c94b8a) C:\Windows\system32\drivers\rdpencdd.sys
2011/06/16 22:35:39.0175 4124 RDPREFMP (44b0a53cd4f27d50ed461dae0c0b4e1f) C:\Windows\system32\drivers\rdprefmp.sys
2011/06/16 22:35:39.0234 4124 RDPWD (801371ba9782282892d00aadb08ee367) C:\Windows\system32\drivers\RDPWD.sys
2011/06/16 22:35:39.0278 4124 rdyboost (4ea225bf1cf05e158853f30a99ca29a7) C:\Windows\system32\drivers\rdyboost.sys
2011/06/16 22:35:39.0421 4124 rkhdrv40 (ba96e9fc124585f4cbec11416d85dc1e) C:\Windows\system32\drivers\rkhdrv40.sys
2011/06/16 22:35:39.0496 4124 rspndr (032b0d36ad92b582d869879f5af5b928) C:\Windows\system32\DRIVERS\rspndr.sys
2011/06/16 22:35:39.0626 4124 RSUSBSTOR (434dcf7ae4300c876aa40873e3113983) C:\Windows\system32\Drivers\RtsUStor.sys
2011/06/16 22:35:40.0018 4124 s3cap (5423d8437051e89dd34749f242c98648) C:\Windows\system32\DRIVERS\vms3cap.sys
2011/06/16 22:35:40.0078 4124 sbp2port (34ee0c44b724e3e4ce2eff29126de5b5) C:\Windows\system32\DRIVERS\sbp2port.sys
2011/06/16 22:35:40.0121 4124 scfilter (a95c54b2ac3cc9c73fcdf9e51a1d6b51) C:\Windows\system32\DRIVERS\scfilter.sys
2011/06/16 22:35:40.0298 4124 Serenum (9ad8b8b515e3df6acd4212ef465de2d1) C:\Windows\system32\DRIVERS\serenum.sys
2011/06/16 22:35:40.0412 4124 Serial (5fb7fcea0490d821f26f39cc5ea3d1e2) C:\Windows\system32\DRIVERS\serial.sys
2011/06/16 22:35:40.0462 4124 sermouse (79bffb520327ff916a582dfea17aa813) C:\Windows\system32\DRIVERS\sermouse.sys
2011/06/16 22:35:40.0609 4124 sffdisk (9f976e1eb233df46fce808d9dea3eb9c) C:\Windows\system32\DRIVERS\sffdisk.sys
2011/06/16 22:35:40.0703 4124 sffp_mmc (932a68ee27833cfd57c1639d375f2731) C:\Windows\system32\DRIVERS\sffp_mmc.sys
2011/06/16 22:35:40.0750 4124 sffp_sd (a0708bbd07d245c06ff9de549ca47185) C:\Windows\system32\DRIVERS\sffp_sd.sys
2011/06/16 22:35:40.0780 4124 sfloppy (db96666cc8312ebc45032f30b007a547) C:\Windows\system32\DRIVERS\sfloppy.sys
2011/06/16 22:35:40.0941 4124 sisagp (2565cac0dc9fe0371bdce60832582b2e) C:\Windows\system32\DRIVERS\sisagp.sys
2011/06/16 22:35:40.0973 4124 SiSRaid2 (a9f0486851becb6dda1d89d381e71055) C:\Windows\system32\DRIVERS\SiSRaid2.sys
2011/06/16 22:35:41.0009 4124 SiSRaid4 (3727097b55738e2f554972c3be5bc1aa) C:\Windows\system32\DRIVERS\sisraid4.sys
2011/06/16 22:35:41.0041 4124 Smb (3e21c083b8a01cb70ba1f09303010fce) C:\Windows\system32\DRIVERS\smb.sys
2011/06/16 22:35:41.0185 4124 spldr (95cf1ae7527fb70f7816563cbc09d942) C:\Windows\system32\drivers\spldr.sys
2011/06/16 22:35:41.0238 4124 srv (50a83ca406c808bd35ac9141a0c7618f) C:\Windows\system32\DRIVERS\srv.sys
2011/06/16 22:35:41.0290 4124 srv2 (dce7e10feaabd4cae95948b3de5340bb) C:\Windows\system32\DRIVERS\srv2.sys
2011/06/16 22:35:41.0388 4124 SrvHsfHDA (e00fdfaff025e94f9821153750c35a6d) C:\Windows\system32\DRIVERS\VSTAZL3.SYS
2011/06/16 22:35:41.0484 4124 SrvHsfV92 (ceb4e3b6890e1e42dca6694d9e59e1a0) C:\Windows\system32\DRIVERS\VSTDPV3.SYS
2011/06/16 22:35:41.0605 4124 SrvHsfWinac (bc0c7ea89194c299f051c24119000e17) C:\Windows\system32\DRIVERS\VSTCNXT3.SYS
2011/06/16 22:35:41.0716 4124 srvnet (bd1433a32792fd0dc450479094fc435a) C:\Windows\system32\DRIVERS\srvnet.sys
2011/06/16 22:35:41.0792 4124 stexstor (db32d325c192b801df274bfd12a7e72b) C:\Windows\system32\DRIVERS\stexstor.sys
2011/06/16 22:35:41.0829 4124 storflt (957e346ca948668f2496a6ccf6ff82cc) C:\Windows\system32\DRIVERS\vmstorfl.sys
2011/06/16 22:35:41.0866 4124 storvsc (d5751969dc3e4b88bf482ac8ec9fe019) C:\Windows\system32\DRIVERS\storvsc.sys
2011/06/16 22:35:41.0981 4124 swenum (e58c78a848add9610a4db6d214af5224) C:\Windows\system32\DRIVERS\swenum.sys
2011/06/16 22:35:42.0124 4124 SynTP (47183e3520c88fadd5b0c87d57040da5) C:\Windows\system32\DRIVERS\SynTP.sys
2011/06/16 22:35:42.0218 4124 Tcpip (2cc3d75488abd3ec628bbb9a4fc84efc) C:\Windows\system32\drivers\tcpip.sys
2011/06/16 22:35:42.0362 4124 TCPIP6 (2cc3d75488abd3ec628bbb9a4fc84efc) C:\Windows\system32\DRIVERS\tcpip.sys
2011/06/16 22:35:42.0467 4124 tcpipreg (e64444523add154f86567c469bc0b17f) C:\Windows\system32\drivers\tcpipreg.sys
2011/06/16 22:35:42.0498 4124 TDPIPE (1875c1490d99e70e449e3afae9fcbadf) C:\Windows\system32\drivers\tdpipe.sys
2011/06/16 22:35:42.0529 4124 TDTCP (7551e91ea999ee9a8e9c331d5a9c31f3) C:\Windows\system32\drivers\tdtcp.sys
2011/06/16 22:35:42.0556 4124 tdx (cb39e896a2a83702d1737bfd402b3542) C:\Windows\system32\DRIVERS\tdx.sys
2011/06/16 22:35:42.0586 4124 TermDD (c36f41ee20e6999dbf4b0425963268a5) C:\Windows\system32\DRIVERS\termdd.sys
2011/06/16 22:35:42.0708 4124 TfFsMon (18d09508877e3f697866b39e9d0e6dcf) C:\Windows\system32\drivers\TfFsMon.sys
2011/06/16 22:35:42.0766 4124 TfNetMon (c657f352613d8e592efb54cc35f21f5e) C:\Windows\system32\drivers\TfNetMon.sys
2011/06/16 22:35:42.0800 4124 TFSysMon (71e3073419cfda8d60813c1502acc420) C:\Windows\system32\drivers\TfSysMon.sys
2011/06/16 22:35:42.0959 4124 tssecsrv (98ae6fa07d12cb4ec5cf4a9bfa5f4242) C:\Windows\system32\DRIVERS\tssecsrv.sys
2011/06/16 22:35:42.0992 4124 tunnel (3e461d890a97f9d4c168f5fda36e1d00) C:\Windows\system32\DRIVERS\tunnel.sys
2011/06/16 22:35:43.0027 4124 uagp35 (750fbcb269f4d7dd2e420c56b795db6d) C:\Windows\system32\DRIVERS\uagp35.sys
2011/06/16 22:35:43.0125 4124 udfs (09cc3e16f8e5ee7168e01cf8fcbe061a) C:\Windows\system32\DRIVERS\udfs.sys
2011/06/16 22:35:43.0183 4124 uliagpkx (44e8048ace47befbfdc2e9be4cbc8880) C:\Windows\system32\DRIVERS\uliagpkx.sys
2011/06/16 22:35:43.0211 4124 umbus (049b3a50b3d646baeeee9eec9b0668dc) C:\Windows\system32\DRIVERS\umbus.sys
2011/06/16 22:35:43.0242 4124 UmPass (7550ad0c6998ba1cb4843e920ee0feac) C:\Windows\system32\DRIVERS\umpass.sys
2011/06/16 22:35:43.0383 4124 USBAAPL (d4fb6ecc60a428564ba8768b0e23c0fc) C:\Windows\system32\Drivers\usbaapl.sys
2011/06/16 22:35:43.0494 4124 usbaudio (2436a42aab4ad48a9b714e5b0f344627) C:\Windows\system32\drivers\usbaudio.sys
2011/06/16 22:35:43.0593 4124 usbccgp (8455c4ed038efd09e99327f9d2d48ffa) C:\Windows\system32\DRIVERS\usbccgp.sys
2011/06/16 22:35:43.0641 4124 usbcir (04ec7cec62ec3b6d9354eee93327fc82) C:\Windows\system32\DRIVERS\usbcir.sys
2011/06/16 22:35:43.0675 4124 usbehci (1c333bfd60f2fed2c7ad5daf533cb742) C:\Windows\system32\DRIVERS\usbehci.sys
2011/06/16 22:35:43.0704 4124 usbhub (ee6ef93ccfa94fae8c6ab298273d8ae2) C:\Windows\system32\DRIVERS\usbhub.sys
2011/06/16 22:35:43.0807 4124 usbohci (a6fb7957ea7afb1165991e54ce934b74) C:\Windows\system32\DRIVERS\usbohci.sys
2011/06/16 22:35:43.0842 4124 usbprint (797d862fe0875e75c7cc4c1ad7b30252) C:\Windows\system32\DRIVERS\usbprint.sys
2011/06/16 22:35:43.0872 4124 USBSTOR (d8889d56e0d27e57ed4591837fe71d27) C:\Windows\system32\DRIVERS\USBSTOR.SYS
2011/06/16 22:35:43.0894 4124 usbuhci (78780c3ebce17405b1ccd07a3a8a7d72) C:\Windows\system32\DRIVERS\usbuhci.sys
2011/06/16 22:35:43.0934 4124 usbvideo (f642a7e4bf78cfa359cca0a3557c28d7) C:\Windows\system32\Drivers\usbvideo.sys
2011/06/16 22:35:44.0051 4124 vdrvroot (a059c4c3edb09e07d21a8e5c0aabd3cb) C:\Windows\system32\DRIVERS\vdrvroot.sys
2011/06/16 22:35:44.0124 4124 VF0350Vfx (86326062a90494bdd79ce383511d7d69) C:\Windows\system32\DRIVERS\V0350VFx.sys
2011/06/16 22:35:44.0242 4124 VF0350Vid (f9a3663065a897cec4a48c9854b35cd3) C:\Windows\system32\DRIVERS\V0350Vid.sys
2011/06/16 22:35:44.0284 4124 vga (17c408214ea61696cec9c66e388b14f3) C:\Windows\system32\DRIVERS\vgapnp.sys
2011/06/16 22:35:44.0315 4124 VgaSave (8e38096ad5c8570a6f1570a61e251561) C:\Windows\System32\drivers\vga.sys
2011/06/16 22:35:44.0354 4124 vhdmp (3be6e1f3a4f1afec8cee0d7883f93583) C:\Windows\system32\DRIVERS\vhdmp.sys
2011/06/16 22:35:44.0486 4124 viaagp (c829317a37b4bea8f39735d4b076e923) C:\Windows\system32\DRIVERS\viaagp.sys
2011/06/16 22:35:44.0507 4124 ViaC7 (e02f079a6aa107f06b16549c6e5c7b74) C:\Windows\system32\DRIVERS\viac7.sys
2011/06/16 22:35:44.0671 4124 VIAHdAudAddService (eb8cba4ec8a30566d3086730d78df259) C:\Windows\system32\drivers\viahduaa.sys
2011/06/16 22:35:44.0790 4124 viaide (e43574f6a56a0ee11809b48c09e4fd3c) C:\Windows\system32\DRIVERS\viaide.sys
2011/06/16 22:35:44.0869 4124 vmbus (379b349f65f453d2a6e75ea6b7448e49) C:\Windows\system32\DRIVERS\vmbus.sys
2011/06/16 22:35:44.0965 4124 VMBusHID (ec2bbab4b84d0738c6c83d2234dc36fe) C:\Windows\system32\DRIVERS\VMBusHID.sys
2011/06/16 22:35:45.0011 4124 volmgr (384e5a2aa49934295171e499f86ba6f3) C:\Windows\system32\DRIVERS\volmgr.sys
2011/06/16 22:35:45.0037 4124 volmgrx (b5bb72067ddddbbfb04b2f89ff8c3c87) C:\Windows\system32\drivers\volmgrx.sys
2011/06/16 22:35:45.0155 4124 volsnap (58df9d2481a56edde167e51b334d44fd) C:\Windows\system32\DRIVERS\volsnap.sys
2011/06/16 22:35:45.0198 4124 vpcbus (33e74df34753fcaab06f6f2bdc8cabf5) C:\Windows\system32\DRIVERS\vpchbus.sys
2011/06/16 22:35:45.0288 4124 vpcnfltr (5f04362ceb5fb5901037e9d9eadd3760) C:\Windows\system32\DRIVERS\vpcnfltr.sys
2011/06/16 22:35:45.0357 4124 vpcusb (625088d6ee9ede977fd03cf18d1cd5c5) C:\Windows\system32\DRIVERS\vpcusb.sys
2011/06/16 22:35:45.0490 4124 vpcvmm (5ed378d91e32134f3c0b3810860ffd71) C:\Windows\system32\drivers\vpcvmm.sys
2011/06/16 22:35:45.0554 4124 vsmraid (9dfa0cc2f8855a04816729651175b631) C:\Windows\system32\DRIVERS\vsmraid.sys
2011/06/16 22:35:45.0650 4124 vwifibus (90567b1e658001e79d7c8bbd3dde5aa6) C:\Windows\system32\DRIVERS\vwifibus.sys
2011/06/16 22:35:45.0710 4124 vwififlt (7090d3436eeb4e7da3373090a23448f7) C:\Windows\system32\DRIVERS\vwififlt.sys
2011/06/16 22:35:45.0814 4124 vwifimp (a3f04cbea6c2a10e6cb01f8b47611882) C:\Windows\system32\DRIVERS\vwifimp.sys
2011/06/16 22:35:45.0881 4124 WacomPen (de3721e89c653aa281428c8a69745d90) C:\Windows\system32\DRIVERS\wacompen.sys
2011/06/16 22:35:45.0911 4124 WANARP (692a712062146e96d28ba0b7d75de31b) C:\Windows\system32\DRIVERS\wanarp.sys
2011/06/16 22:35:45.0926 4124 Wanarpv6 (692a712062146e96d28ba0b7d75de31b) C:\Windows\system32\DRIVERS\wanarp.sys
2011/06/16 22:35:46.0041 4124 Wd (1112a9badacb47b7c0bb0392e3158dff) C:\Windows\system32\DRIVERS\wd.sys
2011/06/16 22:35:46.0104 4124 Wdf01000 (9950e3d0f08141c7e89e64456ae7dc73) C:\Windows\system32\drivers\Wdf01000.sys
2011/06/16 22:35:46.0284 4124 WfpLwf (8b9a943f3b53861f2bfaf6c186168f79) C:\Windows\system32\DRIVERS\wfplwf.sys
2011/06/16 22:35:46.0383 4124 WIMMount (5cf95b35e59e2a38023836fff31be64c) C:\Windows\system32\drivers\wimmount.sys
2011/06/16 22:35:46.0472 4124 winachsf (8b976d4ca270110111df4f313da0e6e8) C:\Windows\system32\DRIVERS\HSX_CNXT.sys
2011/06/16 22:35:46.0616 4124 WinUsb (30fc6e5448d0cbaaa95280eeef7fedae) C:\Windows\system32\DRIVERS\WinUsb.sys
2011/06/16 22:35:46.0672 4124 WmiAcpi (0217679b8fca58714c3bf2726d2ca84e) C:\Windows\system32\DRIVERS\wmiacpi.sys
2011/06/16 22:35:46.0729 4124 ws2ifsl (6db3276587b853bf886b69528fdb048c) C:\Windows\system32\drivers\ws2ifsl.sys
2011/06/16 22:35:46.0784 4124 WudfPf (6f9b6c0c93232cff47d0f72d6db1d21e) C:\Windows\system32\drivers\WudfPf.sys
2011/06/16 22:35:46.0901 4124 WUDFRd (f91ff1e51fca30b3c3981db7d5924252) C:\Windows\system32\DRIVERS\WUDFRd.sys
2011/06/16 22:35:46.0972 4124 XAudio (894f963be999ba9db5aac3aed55b115d) C:\Windows\system32\DRIVERS\XAudio32.sys
2011/06/16 22:35:47.0179 4124 {1BA31E5A-C098-42d8-8F88-3C9F78A2FDDC} (74ec37b9eaf9fca015b933a526825c7a) C:\Program Files\CyberLink\PowerDVD10\NavFilter\000.fcl
2011/06/16 22:35:47.0235 4124 MBR (0x1B8) (a36c5e4f47e84449ff07ed3517b43a31) \Device\Harddisk0\DR0
2011/06/16 22:35:47.0271 4124 ================================================================================
2011/06/16 22:35:47.0271 4124 Scan finished
2011/06/16 22:35:47.0271 4124 ================================================================================
2011/06/16 22:35:47.0287 4700 Detected object count: 0
2011/06/16 22:35:47.0287 4700 Actual detected object count: 0
2011/06/16 22:35:51.0055 4240 Deinitialize success



Google Fix Log:


GooredFix by jpshortstuff (03.07.10.1)
Log created at 22:46 on 16/06/2011 (Andy Gar)
Firefox version 4.0.1 (en-US)

========== GooredScan ==========


========== GooredLog ==========

C:\Program Files\Mozilla Firefox\extensions\
{972ce4c6-7e08-4474-a285-3208198ce6fd} [06:40 09/06/2011]

C:\Users\Bryan Chu\Application Data\Mozilla\Firefox\Profiles\8m8cwzr2.default\extensions\
toolbar@ask.com [11:05 13/06/2011]

[HKEY_LOCAL_MACHINE\Software\Mozilla\Firefox\Extensions]
"avg@igeared"="C:\Program Files\AVG\AVG10\Toolbar\Firefox\avg@igeared" [12:43 11/06/2011]
"{1E73965B-8B48-48be-9C8D-68B920ABC1C4}"="C:\Program Files\AVG\AVG10\Firefox4\" [02:55 30/03/2011]
"{cb84136f-9c44-433a-9048-c5cd9df1dc16}"="C:\Program Files\PC Tools Security\BDT\FireFox\" [08:08 21/04/2011]

---------- Old Logs ----------
GooredFix[05.38.19_17-06-2011].txt
GooredFix[20.34.30_08-06-2011].txt
GooredFix[21.06.22_08-06-2011].txt

-=E.O.F=-

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:29 AM

Posted 17 June 2011 - 10:57 AM

If this machine is on a router and the only one on it..

Your router is hijacked by trojan DNS-hijacker.

  • Please read this: Malware Silently Alters Wireless Router Settings

  • Then reset your router to it's factory default settings:

    "If your machine has been infected by one of these Zlob/DNSchanger Trojans, and your router settings have been altered, I would strongly recommend that you reset the router to its default configuration. Usually, this can be done by inserting something tiny like a paper clip end or pencil tip into a small hole labeled "reset" located on the back of the router. Press and hold down the small button inside until the lights on the front of the router blink off and then on again (usually about 10 seconds)"


  • This is the difficult part.
    First get to the routers server. To do that open Internet Explorer and type http:\\192.168.1.1 in the address bar and click Enter. You get the log in window.
    Fill in the password you have already found and you will get the configuration page.
    Configure the router to allow you to connect to your ISP server. In some routers it is done by a setup wizard. But you have to fill in the log in password your ISP has initially given to you.
    You can also call your ISP if you don't have your initial password.
    Don't forget to change the routers default password and set a strong password. Note down the password and keep it somewhere for future reference.

How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#5 AndyGarr

AndyGarr
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 17 June 2011 - 04:44 PM

Ok, I guess I wasn't sure whether I was supposed to enter my router username and password (the password to use the wireless internet at my house), or look through the list at "http://www.phenoelit-us.org/dpl/dpl.html". I tried entering my router username and password a couple times (just to be sure I wasn't entering it in wrong), and the log in attempts failed. I wasn't able to log in with the user and pass provided at "http://www.phenoelit-us.org/dpl/dpl.html", because I got this message from verizon (http:\\192.168.1.1) :

Step 1.
We now require you to change your default login User Name and Password. Please select a new login User Name and Password and type it into the appropriate fields below.
NOTE: The password must be at least 6 characters long and include at least one alpha numeric character. The password cannot begin with characters such as "?!@#$%^&*".

New User Name:
New Password:
Retype New Password:
Step 2.
Please select your appropriate Time Zone and click OK.


Should I go ahead and make a new user and pass? What should I do after that? There are other computers running on this router (wireless and wired), but they don't seem to be infected with the redirect virus. This laptop that I'm using seems to be the only one with the google redirect problem.

Edit: by the way, should I be doing this on my desktop computer (wired to the router) or should I do this on my wireless internet Laptop (Infected with the redirect virus)?

Edited by AndyGarr, 17 June 2011 - 05:07 PM.


#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:29 AM

Posted 17 June 2011 - 08:21 PM

Yes you were to use yours or the default if you did not change it.
Make the new user and pass.

I would use the wired as that is probably where it was set from at the beginning.

Edited by boopme, 17 June 2011 - 08:22 PM.

How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#7 AndyGarr

AndyGarr
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 18 June 2011 - 12:09 AM

I was able to create a new user and password; I am now at the configuration, but I have no idea how to:

"Configure the router to allow you to connect to your ISP server. In some routers it is done by a setup wizard. But you have to fill in the log in password your ISP has initially given to you."

I'm not very computer savvy, and I have no idea what to do. Hopefully you can guide me though this, sorry about this boopme.

Edit: If it is any help, I have noticed that most of the redirects on google lead me to search-high.com and search-cool.net, which leads me to other sites. There is probably more websites that I could be redirected to, but those two sites seem to be the most consistent.

Thanks again for your hard work, I appreciate it.

Edited by AndyGarr, 18 June 2011 - 06:41 AM.


#8 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:11:29 AM

Posted 18 June 2011 - 08:35 PM

Hello I am a BC Advisor who is familiar with hardware issues.

Boopme has asked me to assist you in this thread and I am more than willing to help you through this. :thumbup2:

Can you please look closely at the device to which your computer is connecting to for your Internet connection.

There should be a label stuck to the device with the brand name and model number on it, can you please post that information in your next reply?

I would also like a clearer understanding of how your network is put together.

Do you have a cable-TV modem?
Do you have a DSL modem?

What devices are connected to your network?
In other words, do you have a separate modem and router setup?

If you have a separate modem and router setup, I would need to know the brand name and model number of both devices. There should be stickers stuck on each device that list a model number.

Please post that information in your next reply.

As a piece of technical information, some devices such as AT&T U-verse list the default router log-in right on the device label.

As for accessing wireless Internet, there is usually an account name and password supplied by the service provider, this is not the same name and password required to access the router's configuration utility, the two names and passwords are entirely totally different credentials.

Your account name and password is needed for your device to connect to your service provider, often this is already setup when your device is installed and the ID is automatically recognized by your service providers servers.

When a separate router is used, such as a linksys or netgear router, the main menu of your router's internal configuration may require a user name and password to gain access to your modem, this user name and password is the one provided by your ISP and should be printed on a piece of paper that was sent to you by your ISP.

It could be something like MrBruce@comcast.net password: T6CSrtGvf, once that information is added the router will establish a connection to the modem, thus you now have access to the Internet.

I can provide more accurate information once I have a reply from you on what devices you have in your network setup.

Thanks in advance.

Bruce.

Edited by MrBruce1959, 18 June 2011 - 08:41 PM.

Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#9 AndyGarr

AndyGarr
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 19 June 2011 - 08:18 PM

Great, glad that you are here to help me Bruce.

I am using a Verizon Fios Router.

-Brand Name: Actiontec
-Model Number: MI424-WR Rev. F

- I have Verizon Fios, so I believe that is a cable internet connection; I do not have dsl.

"What devices are connected to your network?
In other words, do you have a separate modem and router setup?"
-Sorry, I'm a bit unclear with what you are trying to ask, but I will try to answer. No I do not have another modem, this Actiontec MI424WR is my only modem. There are two desktop computers that are wired to the modem, and two laptops that are connected to the modem via wireless.


I hope I have answered everything that you've asked for. If I'm missing anything be sure to tell me!
Also, I would like to note that I have been getting this message (without quotes) a lot after searching on google today:


"To continue, please type the characters below:

Please enable images




About this page

Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot. Why did this happen?"



Under this message displays my IP address, Time, and URL, but I just did not want to include that on here. Is this message safe? Should I be worried about this?


Much thanks.

Edited by AndyGarr, 19 June 2011 - 09:20 PM.


#10 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:11:29 AM

Posted 19 June 2011 - 11:15 PM

I am providing the support page for your modem/router below.

http://www.actiontec.com/support/product_details.php?pid=213

Please follow the following instructions carefully, pay close attention the any spaces in the bold text as those are important for the following commands I am posting for you to type to work correctly. :thumbup2:

Upon completing the instructions below, you should end up with a text file on your desktop, if you find anything of concern please let me know.

Although I do not always do things outside the forum, if you feel uncomfortable about that information being made public in this forum board, you are more than welcome to copy and paste that text into a personal message to me and I will look through it for any possible signs of intrusion in your network.


You can investigate unwanted connections:
  • Click start-->Run
  • Type cmd in your Windows Run box.
  • Type netstat -b 5 > activity.txt at the command prompt and press enter.
  • Wait 2 minutes or so and press Ctrl+C, then close the command window (the longer you wait, the bigger the log).
  • Open a command window again and Type activity.txt at the command prompt then press Enter to open the log file in notepad.
This .txt file will have a record of everything that has made an Internet connection during those few minutes...you can also check your task manager to find out where and what it is that's connecting and take care of it if you wish to.

But as I stated above, you can either copy and paste that text into your next reply or if you wish you can copy and paste that text into a personal message to me and I will only reveal in this thread what I feel is applicable and slightly edited to protect your personal information.

Remember, the longer you wait before you close the command prompt, the longer your log will be and may reveal unauthorized activity.

By the way, some of the Google search activity may be linked to something suspicious, and may involve an entry in your HOSTS file, but we'll cross that path shortly.

Bruce.

Edited by MrBruce1959, 20 June 2011 - 05:46 PM.

Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#11 AndyGarr

AndyGarr
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 20 June 2011 - 03:25 AM

Heya, Bruce. I would paste activity.txt on this board, but just to be on the safe side, I sent it to you via pm labeled "AndyGarr's activity.txt". I hope I did everything correctly, let me know if I'm missing something.

thanks.

#12 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:11:29 AM

Posted 20 June 2011 - 03:19 PM

Just to keep you updated and informed, you did everything correctly :thumbup2: and I have received your personal messages containing your logs.

I will review those logs and reply back to you with my findings in this forum instead of a personal message.

Thank you for your patience and thank you for choosing Bleepingcomputer.com as your source of information and help assistance. :thumbsup:

Kind regards............

Bruce.
Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#13 AndyGarr

AndyGarr
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 20 June 2011 - 05:07 PM

Sounds great, looking forward to your reply Bruce.

#14 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:11:29 AM

Posted 20 June 2011 - 08:19 PM

I am assuming you are using Fire Fox as your default browser on the troublesome computer.

I am not giving you a 100% Guarantee at this point that this will correct this problem, but it has its possibilities.

Performing the procedure described at the link below, will reset Fire Fox to its default settings.

http://support.mozilla.com/en-US/kb/Resetting%20preferences?s=reset+to+defaults&as=s

There is a picture on this page that shows the box where a check-mark has to be placed to perform this procedure, use that as your reference.

Once you have done that, restart the computer and try using Google again.

By the way, your Netstat log only showed connections to AOL Instant messenger, so I am assuming someone has been using AIM to chat on-line.

I am a bit concerned with the following entries though:

TCP 192.168.1.7:49892 hades:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49893 216:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49894 216:http ESTABLISHED
[firefox.exe]


These entries are to Google's server in California

TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]


You can simply check any IP address at this web address: http://whatismyipaddress.com/ip-lookup

It will show your IP address in the box provided, but if you copy and paste a new IP into that box, it will tell you who the domain is owned by.
Such as the case with the IP above 74.125.224.185, the results are linked to below.

http://whatismyipaddress.com/ip/74.125.224.185

Hostname:74.125.224.185
ISP:Google
Organization:Google
Proxy:None detected


I understand you have reset your router and changed your log-in password.
Changes to modem/routers should only be made through a wired device, which is what I believe you did. The reason for this being the best way to make changes is because a wireless connection can become lost once changes are made to the wireless configuration.
Because wired connections do not need to be as secure, changes to not affect their connectivity.

Since I have read through your logs and do not see anything in them that I feel is private information, I am going to post them here for public viewing. They only show the IP address that your DHCP router has assigned you, those are common IP addresses used by routers and do not pose any personal threat to your ISP assigned IP address.

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49889 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49890 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49891 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49892 hades:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49893 216:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49894 216:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49889 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49890 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49891 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49892 hades:http CLOSE_WAIT
[firefox.exe]
TCP 192.168.1.7:49893 216:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49894 216:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49881 pz-in-f102:http TIME_WAIT
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49884 74.125.224.185:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49889 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49890 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49891 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49892 hades:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49893 216:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49894 216:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49889 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49890 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49891 74.125.224.220:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49892 hades:http CLOSE_WAIT
[firefox.exe]
TCP 192.168.1.7:49893 216:http ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49894 216:http ESTABLISHED
[firefox.exe]

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:27015 Gateway-ID5822U:49156 ESTABLISHED
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49156 Gateway-ID5822U:27015 ESTABLISHED
[iTunesHelper.exe]
TCP 127.0.0.1:49823 Gateway-ID5822U:49824 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49824 Gateway-ID5822U:49823 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49825 Gateway-ID5822U:49826 ESTABLISHED
[firefox.exe]
TCP 127.0.0.1:49826 Gateway-ID5822U:49825 ESTABLISHED
[firefox.exe]
TCP 192.168.1.7:49793 bos-m016c-sdr4:https ESTABLISHED
[aim.exe]
TCP 192.168.1.7:49794 oam-m09a:https ESTABLISHED
[aim.exe]

Bruce.

Edited by MrBruce1959, 20 June 2011 - 08:26 PM.

Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#15 AndyGarr

AndyGarr
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:07:29 AM

Posted 20 June 2011 - 09:01 PM

Hey Bruce, I tried resetting Firefox (my default browser) with the instructions provided, but that did not work. Yes, I have AIM installed on my computer, so I don't think there was anything wrong there.

Edited by AndyGarr, 20 June 2011 - 09:02 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users