Firefox may not be mentioned by name but I'm still curious to see your event log. Do the following
Re-create the FF error. Then download VEW. then right click VEW.exe click [FONT=Arial]Run as Administrator. [/FONT]When VEW opens,
Under Select log to query: select Application and System
Under Select type to list: select Error and Warning
Click the radio button for Number of events, Type 20 in the 1 to 20 box
Then click the Run button. It may take several seconds, Notepad will open with the output log.
In Notepad, click Edit> Select all
·Then press Edit > Copy
·Press Ctrl+V on your keyboard to paste the log to your next reply
(Courtesy rev-Olie)
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 11/09/2013 6:47:09 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 06/09/2013 1:33:11 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program fximager.exe version 6.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 1aec Start Time: 01ceaaa0f9aeead7 Termination Time: 5 Application Path: C:\Program Files (x86)\FuturixImager\fximager.exe Report Id: 43e34129-1694-11e3-b307-00269e6ca864
Log: 'Application' Date/Time: 05/09/2013 11:48:50 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "c:\program files (x86)\ESET\eset online scanner\ESETSmartInstaller.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
Log: 'Application' Date/Time: 01/09/2013 4:50:22 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program iexplore.exe version 10.0.9200.16660 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 123c Start Time: 01cea73350ce441c Termination Time: 7 Application Path: C:\Program Files\Internet Explorer\iexplore.exe Report Id: 932da2e3-1326-11e3-b307-00269e6ca864
Log: 'Application' Date/Time: 01/09/2013 4:09:05 PM
Type: Error Category: 0
Event: 11720 Source: MsiInstaller
Product: Microsoft Fix it 50043 -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action ProcessCheck script error -2147221163, : Line 30, Column 1,
Log: 'Application' Date/Time: 01/09/2013 1:15:46 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program iexplore.exe version 10.0.9200.16660 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 1708 Start Time: 01cea7155091af70 Termination Time: 19 Application Path: C:\Program Files\Internet Explorer\iexplore.exe Report Id: 9432baac-1308-11e3-a7de-00269e6ca864
Log: 'Application' Date/Time: 30/08/2013 5:57:09 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program IEXPLORE.EXE version 10.0.9200.16660 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: bbc Start Time: 01cea5aa4973cfd9 Termination Time: 7 Application Path: C:\Program Files\Internet Explorer\IEXPLORE.EXE Report Id: 930f3f4e-119d-11e3-a7de-00269e6ca864
Log: 'Application' Date/Time: 30/08/2013 1:23:08 PM
Type: Error Category: 0
Event: 11720 Source: MsiInstaller
Product: Skype Toolbars -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action TerminateSkypeNames2.9634CD8B_3E2F_4F6E_AAFB_AD3F948985A2 script error -2147221163, : Line 5, Column 6,
Log: 'Application' Date/Time: 30/08/2013 1:15:25 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MsiExec.exe, version: 5.0.7601.17514, time stamp: 0x4ce792c4 Faulting module name: QuickTime.qts_unloaded, version: 0.0.0.0, time stamp: 0x4cf4536a Exception code: 0xc0000005 Fault offset: 0x670dbb89 Faulting process id: 0x1e00 Faulting application start time: 0x01cea582f9a43998 Faulting application path: C:\Windows\syswow64\MsiExec.exe Faulting module path: QuickTime.qts Report Id: 3ae53642-1176-11e3-8513-00269e6ca864
Log: 'Application' Date/Time: 29/08/2013 9:57:34 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "c:\program files (x86)\ESET\eset online scanner\ESETSmartInstaller.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
Log: 'Application' Date/Time: 29/08/2013 2:28:39 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program iexplore.exe version 10.0.9200.16660 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 1a20 Start Time: 01cea4c3de18f6f3 Termination Time: 37 Application Path: C:\Program Files\Internet Explorer\iexplore.exe Report Id: 2c579a0a-10b7-11e3-b2aa-00269e6ca864
Log: 'Application' Date/Time: 24/08/2013 10:27:30 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program mbam.exe version 1.62.0.140 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 1ad4 Start Time: 01cea118e7db73c4 Termination Time: 6 Application Path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe Report Id: 4cd18be2-0d0c-11e3-b2aa-00269e6ca864
Log: 'Application' Date/Time: 22/08/2013 8:29:47 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.7601.17610, time stamp: 0x4dc0d019 Faulting module name: TQUERY.DLL, version: 7.0.7601.17610, time stamp: 0x4dc0e17a Exception code: 0xc0000005 Fault offset: 0x000000000008e3b3 Faulting process id: 0x5cc Faulting application start time: 0x01ce9b2fa5e332fd Faulting application path: C:\windows\system32\SearchIndexer.exe Faulting module path: C:\windows\system32\TQUERY.DLL Report Id: 96013714-0b69-11e3-b2aa-00269e6ca864
Log: 'Application' Date/Time: 22/08/2013 8:26:49 PM
Type: Error Category: 0
Event: 9020 Source: Desktop Window Manager
The Desktop Window Manager has encountered a fatal error (0x80070008)
Log: 'Application' Date/Time: 22/08/2013 12:30:51 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program BitTorrent.exe version 7.8.0.29626 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: f74 Start Time: 01ce9b2fd58119d8 Termination Time: 19 Application Path: C:\Program Files (x86)\BitTorrent\BitTorrent.exe Report Id: a3d67044-0b26-11e3-b2aa-00269e6ca864
Log: 'Application' Date/Time: 14/08/2013 8:25:51 AM
Type: Error Category: 3
Event: 3007 Source: Microsoft-Windows-Search
Performance monitoring cannot be initialized for the gatherer object, because the counters are not loaded or the shared memory object cannot be opened. This only affects availability of the perfmon counters. Restart the computer.
Context: Application, SystemIndex Catalog
Log: 'Application' Date/Time: 18/07/2013 5:04:13 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: DivXUpdate.exe, version: 1.0.6.15, time stamp: 0x4e31ebcf Faulting module name: RPCRT4.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00039093 Faulting process id: 0xf7c Faulting application start time: 0x01ce7d9e6bd352e3 Faulting application path: C:\Program Files (x86)\DivX\DivX Update\DivXUpdate.exe Faulting module path: C:\windows\syswow64\RPCRT4.dll Report Id: 7c711e08-ef67-11e2-88f4-00269e6ca864
Log: 'Application' Date/Time: 18/07/2013 4:14:01 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program fximager.exe version 6.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 1cd0 Start Time: 01ce836d2f332ade Termination Time: 8 Application Path: C:\Program Files (x86)\FuturixImager\fximager.exe Report Id: 72a5844b-ef60-11e2-88f4-00269e6ca864
Log: 'Application' Date/Time: 13/07/2013 5:33:00 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "c:\program files (x86)\ESET\eset online scanner\ESETSmartInstaller.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
Log: 'Application' Date/Time: 12/07/2013 1:58:47 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "c:\program files (x86)\ESET\eset online scanner\ESETSmartInstaller.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
Log: 'Application' Date/Time: 05/07/2013 9:03:38 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "c:\program files (x86)\ESET\eset online scanner\ESETSmartInstaller.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 30/08/2013 1:46:22 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 29/08/2013 3:15:20 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 17/08/2013 1:31:54 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 05/07/2013 12:49:03 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 30/05/2013 12:06:25 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 26/05/2013 12:26:27 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 03/12/2012 9:42:59 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 02/12/2012 8:30:15 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 02/12/2012 8:25:23 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/09/2013 1:14:18 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4EB61BAC-A3B6-4760-9581-655041EF4D69} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 08/09/2013 6:40:27 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (120000 milliseconds) was reached while waiting for a transaction response from the Wlansvc service.
Log: 'System' Date/Time: 07/09/2013 2:42:55 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 07/09/2013 2:42:14 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 07/09/2013 2:40:39 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified.
Log: 'System' Date/Time: 06/09/2013 1:21:36 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 06/09/2013 1:20:29 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified.
Log: 'System' Date/Time: 01/09/2013 3:33:36 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 01/09/2013 3:31:43 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified.
Log: 'System' Date/Time: 01/09/2013 2:48:07 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 01/09/2013 2:46:37 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified.
Log: 'System' Date/Time: 01/09/2013 2:28:51 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 01/09/2013 2:26:21 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified.
Log: 'System' Date/Time: 01/09/2013 2:11:47 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {0002DF01-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 01/09/2013 2:06:10 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Update service hung on starting.
Log: 'System' Date/Time: 01/09/2013 2:01:20 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 01/09/2013 1:59:06 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified.
Log: 'System' Date/Time: 01/09/2013 1:57:28 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The HP Network Devices Support service terminated with the following error: %%-2147467243
Log: 'System' Date/Time: 01/09/2013 1:56:47 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified.
Log: 'System' Date/Time: 01/09/2013 1:54:14 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Update service hung on starting.