91 replies to this topic

[Lewg]

Here is the Host file.

[Tomk]

No attachment was ... attached.

[Lewg]

Sorry! Maybe it will come throught this time.

Attached Files

•  Host.txt   552.83KB   1749 downloads

[Tomk]

Appears to be the standard MVPS host file which is very, very similiar to the one you would have if you were to click on Vaccinate in your Spybot program.

 

I don't see anything wrong with it.

 

What site are you unable to reach?

[Lewg]

I cannot get this site to come up when searching for it on Google and clicking the site once google finds it. .....A window pops up saying "Internet Explorer cannot display the Web Page.....I think it's my Host file causing the problem with a number of Pop up window Errors.....I renamed my host file and sites on Google will open.  When the Host file has it's original name HOST.* some sites on Google will will not open and the Error window pops up I mentioned earlier. .

    www.volkswagenoforangepark.com/

[Tomk]

Just  to be clear... when you rename your hosts file... everything works fine?

 

There is nothing in your hosts file that should stop you from accessing that site.  I can access that site from my computer... so I removed my hosts file and installed yours.  No change.  Still works - as it should seeing as how the error you provided is from the server that the site is hosted on.

[Lewg]

Open Google and type in Orange Park VW when the sites open click on the first site, It will not open if my host file is used. If I rename the file to "nohost.* ", it will open and other hits on the list will also open.  Not sure if you saw how many listings are in my host file.  Doubleclick must have a hundred different listings.

[Tomk]

I run MVPS hosts file also so my standard host file is the same as yours.

 

I did the google search with my hosts file in place.  The site worked.  I reset hosts file to factory (127.0.0.1  localhost) and did the search.  The site opened.  I used your hosts file.  The site still works.  I am unable to recreate your situation.

 

With that being said... if things work without the hosts file... then why use the hosts file?  You can try resetting the custom file by going to http://winhelp2002.mvps.org/hosts.htm and setting it again.

[Tomk]

How are things running now?  Do you have any updated information for me?

[Lewg]

Things seemed to be OK, however I still get a few Pop up windows that ask me to Send....I never do because it don't help.....

[Tomk]

Are sites still being blocked?

 

What kind of pop up window are you getting that asks you to send?

[Lewg]

The one pictured here!

 

http://hackingethics...ort-in-windows/
 

[Tomk]

Ok... the error report.  In theory, you should get that report when something fails in a program you are running - which should not be related to websites being blocked.  Can I assume that your websites are no longer being blocked?
 
Let's get a better look at the errors:
 
Download Vino's Event Viewer. No install needed, just double click on it to run.

Check the Application and System boxes.
Check the Error and Warning boxes. If Windows Vista or Windows 7 also click Critical (not XP).
Under Number or date of events select Number of events and type 20 in the box next to 1 to 20 and click Run
Once it finishes it will display a log file in notepad.
Copy and paste its entire contents into your next reply.

[Lewg]

I was not able to just double click on the program and have it run.....It would flash the screen I sent you earlier and disapear quickly...I tried several times but the only way I could get the program was to look at the properties and copy the url and paste it in a new tab.

 

 

Vino's Event Viewer v01c run on Windows XP in English
Report run at 20/03/2014 11:37:48 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 20/03/2014 11:35:45 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iexplore.exe, version 8.0.6001.18702, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 20/03/2014 11:34:59 PM
Type: error Category: 0
Event: 1001 Source: Application Error
Fault bucket -367089902.

Log: 'Application' Date/Time: 20/03/2014 11:34:43 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x028f78c8.

Log: 'Application' Date/Time: 20/03/2014 11:34:02 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iexplore.exe, version 8.0.6001.18702, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 20/03/2014 11:33:22 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 20/03/2014 11:32:56 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iexplore.exe, version 8.0.6001.18702, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 20/03/2014 11:32:23 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 20/03/2014 11:32:13 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application iexplore.exe, version 8.0.6001.18702, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 20/03/2014 11:31:31 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d.

Log: 'Application' Date/Time: 20/03/2014 11:31:25 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 20/03/2014 4:50:07 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 20/03/2014 2:39:06 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 19/03/2014 5:25:43 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 18/03/2014 9:00:18 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 18/03/2014 11:25:11 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

Log: 'Application' Date/Time: 18/03/2014 9:01:01 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x028f78c8.

Log: 'Application' Date/Time: 18/03/2014 8:49:10 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x028f78c8.

Log: 'Application' Date/Time: 18/03/2014 8:30:06 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x028f78c8.

Log: 'Application' Date/Time: 18/03/2014 8:11:01 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x028f78c8.

Log: 'Application' Date/Time: 16/03/2014 12:42:29 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x029f78c8.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 20/03/2014 11:34:44 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 19/03/2014 10:26:15 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 19/03/2014 10:26:10 AM
Type: warning Category: 0
Event: 1524 Source: Userenv
Windows cannot unload your classes registry file - it is still in use by other applications or services. The file will be unloaded when it is no longer in use.    

Log: 'Application' Date/Time: 18/03/2014 11:31:53 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 17/03/2014 12:43:38 PM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 16/03/2014 10:21:53 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 15/03/2014 10:10:56 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 14/03/2014 8:48:12 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 08/03/2014 10:08:11 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 05/03/2014 10:55:03 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 28/02/2014 10:26:40 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 27/02/2014 10:50:00 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 25/02/2014 9:31:18 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 24/02/2014 9:39:41 AM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 21/02/2014 1:39:39 PM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 19/02/2014 1:52:55 PM
Type: warning Category: 0
Event: 1517 Source: Userenv
Windows saved user LEW-0CCC0E88CE3\Lew registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Log: 'Application' Date/Time: 18/02/2014 9:10:55 AM
Type: warning Category: 0
Event: 1015 Source: MsiInstaller
Failed to connect to server. Error: 0x800401F0

Log: 'Application' Date/Time: 18/02/2014 9:10:54 AM
Type: warning Category: 0
Event: 1015 Source: MsiInstaller
Failed to connect to server. Error: 0x800401F0

Log: 'Application' Date/Time: 18/02/2014 9:10:54 AM
Type: warning Category: 0
Event: 1015 Source: MsiInstaller
Failed to connect to server. Error: 0x800401F0

Log: 'Application' Date/Time: 18/02/2014 9:10:53 AM
Type: warning Category: 0
Event: 1015 Source: MsiInstaller
Failed to connect to server. Error: 0x800401F0

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/03/2014 6:15:44 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load:  SASDIFSV SASKUTIL

Log: 'System' Date/Time: 19/03/2014 6:15:43 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Spybot-S&D 2 Security Center Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion. 

Log: 'System' Date/Time: 19/03/2014 6:15:43 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Spybot-S&D 2 Security Center Service service to connect.

Log: 'System' Date/Time: 16/03/2014 11:10:06 AM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load:  SASDIFSV SASKUTIL

Log: 'System' Date/Time: 16/03/2014 11:10:06 AM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Spybot-S&D 2 Security Center Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion. 

Log: 'System' Date/Time: 16/03/2014 11:10:06 AM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Spybot-S&D 2 Security Center Service service to connect.

Log: 'System' Date/Time: 14/03/2014 8:51:06 AM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load:  SASDIFSV SASKUTIL

Log: 'System' Date/Time: 14/03/2014 8:51:05 AM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Spybot-S&D 2 Security Center Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion. 

Log: 'System' Date/Time: 14/03/2014 8:51:05 AM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Spybot-S&D 2 Security Center Service service to connect.

Log: 'System' Date/Time: 13/03/2014 8:42:50 AM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load:  SASDIFSV SASKUTIL

Log: 'System' Date/Time: 13/03/2014 8:42:49 AM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Spybot-S&D 2 Security Center Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion. 

Log: 'System' Date/Time: 13/03/2014 8:42:49 AM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Spybot-S&D 2 Security Center Service service to connect.

Log: 'System' Date/Time: 12/03/2014 6:31:48 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load:  SASDIFSV SASKUTIL

Log: 'System' Date/Time: 12/03/2014 6:31:47 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Spybot-S&D 2 Security Center Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion. 

Log: 'System' Date/Time: 12/03/2014 6:31:47 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Spybot-S&D 2 Security Center Service service to connect.

Log: 'System' Date/Time: 07/03/2014 6:10:36 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load:  SASDIFSV SASKUTIL

Log: 'System' Date/Time: 07/03/2014 6:10:35 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Spybot-S&D 2 Security Center Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion. 

Log: 'System' Date/Time: 07/03/2014 6:10:35 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Spybot-S&D 2 Security Center Service service to connect.

Log: 'System' Date/Time: 07/03/2014 6:04:45 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load:  SASDIFSV SASKUTIL

Log: 'System' Date/Time: 07/03/2014 6:04:44 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Spybot-S&D 2 Security Center Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion. 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 20/03/2014 11:28:26 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 20/03/2014 7:54:54 AM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

Log: 'System' Date/Time: 19/03/2014 6:45:05 PM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 19/03/2014 9:09:07 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 18/03/2014 9:06:47 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 17/03/2014 12:43:39 PM
Type: warning Category: 2
Event: 57 Source: Ftdisk
The system failed to flush data to the transaction log. Corruption may occur.

Log: 'System' Date/Time: 17/03/2014 8:34:19 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 17/03/2014 12:49:16 AM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

Log: 'System' Date/Time: 16/03/2014 11:57:33 AM
Type: warning Category: 2
Event: 57 Source: Ftdisk
The system failed to flush data to the transaction log. Corruption may occur.

Log: 'System' Date/Time: 16/03/2014 11:34:28 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 16/03/2014 10:47:07 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 14/03/2014 10:30:16 PM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

Log: 'System' Date/Time: 14/03/2014 10:19:16 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 13/03/2014 10:22:00 PM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

Log: 'System' Date/Time: 12/03/2014 10:02:10 AM
Type: warning Category: 2
Event: 57 Source: Ftdisk
The system failed to flush data to the transaction log. Corruption may occur.

Log: 'System' Date/Time: 08/03/2014 7:49:46 AM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

Log: 'System' Date/Time: 05/03/2014 9:42:35 PM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

Log: 'System' Date/Time: 05/03/2014 9:37:46 AM
Type: warning Category: 0
Event: 4226 Source: Tcpip
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Log: 'System' Date/Time: 05/03/2014 5:59:32 AM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

Log: 'System' Date/Time: 04/03/2014 12:17:57 PM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

[Tomk]

Ok... a couple things there:

 

It appears that Spybot and Superantispyware are both trying to run and interfering with each other.  You need to get rid of one of them.  There are a bunch of errors for a domain caused by to many connections at one time... and it is Internet Explorer that is kicking the error warnings you've been seeing.

 

The predominate cause of the Internet Explorer error is third party add-ons.  It is possible that SAS and Spybot fighting could be the root of the cause but I don't think so.  The best thing to do is to shut off all third party add-ons and see if that resolves the issue.

 

1. Click "Tools" and select "Internet Options".
2. Click the "Advanced" tab on the right.
3. Under "Browsing", remove the "Enable third-party browser extensions" check box.
4. Click "OK" and close out of all instances of Internet Explorer.
5. Relaunch Internet Explorer.

 

Then try it a bit and let me know if you notice any difference.