Hello RKinner and thank you so much for your help.
The CBS and Speccy logs are both attached.
Here is the data from the BSOD program:
==================================================
Dump File : 072615-14632-01.dmp
Crash Time : 7/26/2015 11:16:05 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`05e228f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072615-14632-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/26/2015 11:16:11 AM
==================================================
==================================================
Dump File : 072515-13260-01.dmp
Crash Time : 7/25/2015 2:53:59 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`05e108f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072515-13260-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/25/2015 2:54:02 PM
==================================================
==================================================
Dump File : 072515-13244-01.dmp
Crash Time : 7/25/2015 12:17:12 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0617f8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072515-13244-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/25/2015 12:17:14 PM
==================================================
==================================================
Dump File : 072515-14882-01.dmp
Crash Time : 7/25/2015 9:30:18 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`05e218f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072515-14882-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/25/2015 9:30:21 AM
==================================================
==================================================
Dump File : 072415-13416-01.dmp
Crash Time : 7/24/2015 7:38:31 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`06bc08f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072415-13416-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/24/2015 7:38:34 PM
==================================================
==================================================
Dump File : 072415-16816-01.dmp
Crash Time : 7/24/2015 6:43:28 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`05e1d8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072415-16816-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/24/2015 6:43:33 PM
==================================================
==================================================
Dump File : 071615-14773-01.dmp
Crash Time : 7/16/2015 5:06:02 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`06c34828
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071615-14773-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/16/2015 5:06:06 PM
==================================================
==================================================
Dump File : 071615-14258-01.dmp
Crash Time : 7/16/2015 1:05:15 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`06c978f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071615-14258-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/16/2015 1:05:19 PM
==================================================
==================================================
Dump File : 071415-14430-01.dmp
Crash Time : 7/14/2015 1:26:03 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`064c48f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071415-14430-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/14/2015 1:26:09 PM
==================================================
==================================================
Dump File : 071415-18220-01.dmp
Crash Time : 7/14/2015 1:16:53 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0649e038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2efc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+4b2efc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071415-18220-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 7/14/2015 1:17:02 PM
==================================================
And here is the info from the event viewer:
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 26/07/2015 12:08:33 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 26/07/2015 3:16:05 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: 25/07/2015 6:53: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: 25/07/2015 4:17:12 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: 25/07/2015 3:49:02 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device F:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:02 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device I:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:02 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device G:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:02 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device J:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:02 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device H:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:02 PM
Type: Critical Category: 64
Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
Log: 'System' Date/Time: 25/07/2015 3:49:01 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device J:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:01 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device F:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:01 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device I:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:01 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device H:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:01 PM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device G:\ (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Log: 'System' Date/Time: 25/07/2015 3:49:01 PM
Type: Critical Category: 64
Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
Log: 'System' Date/Time: 25/07/2015 1:30:18 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: 24/07/2015 11:38:31 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: 24/07/2015 10:43:28 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: 16/07/2015 9:06:02 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: 16/07/2015 5:26: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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 26/07/2015 4:05:35 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D3DCB472-7261-43CE-924B-0704BD730D5F} and APPID {D3DCB472-7261-43CE-924B-0704BD730D5F} to the user WestFamily-HP\WestFamily SID (S-1-5-21-2394937029-579550273-2574859083-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 26/07/2015 4:05:35 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {145B4335-FE2A-4927-A040-7C35AD3180EF} and APPID {145B4335-FE2A-4927-A040-7C35AD3180EF} to the user WestFamily-HP\WestFamily SID (S-1-5-21-2394937029-579550273-2574859083-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 26/07/2015 3:51:08 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D3DCB472-7261-43CE-924B-0704BD730D5F} and APPID {D3DCB472-7261-43CE-924B-0704BD730D5F} to the user WestFamily-HP\WestFamily SID (S-1-5-21-2394937029-579550273-2574859083-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 26/07/2015 3:51:07 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {145B4335-FE2A-4927-A040-7C35AD3180EF} and APPID {145B4335-FE2A-4927-A040-7C35AD3180EF} to the user WestFamily-HP\WestFamily SID (S-1-5-21-2394937029-579550273-2574859083-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 26/07/2015 3:26:32 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 26/07/2015 3:26:29 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 26/07/2015 3:26:28 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 26/07/2015 3:18:54 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 26/07/2015 3:16:54 PM
Type: Error Category: 0
Event: 20 Source: Microsoft-Windows-WHEA-Logger
A fatal hardware error has occurred. Component: AMD Northbridge Error Source: Machine Check Exception Error Type: HyperTransport Watchdog Timeout Error Processor ID: 0 The details view of this entry contains further information.
Log: 'System' Date/Time: 26/07/2015 3:16:14 PM
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8005e228f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\072615-14632-01.dmp. Report Id: 072615-14632-01.
Log: 'System' Date/Time: 26/07/2015 3:16:13 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 11:14:14 AM on ?7/?26/?2015 was unexpected.
Log: 'System' Date/Time: 25/07/2015 9:25:31 PM
Type: Error Category: 0
Event: 15006 Source: Microsoft-Windows-HttpEvent
Owner of the log file or directory \SystemRoot\System32\LogFiles\HTTPERR\httperr1.log is invalid. This could be because another user has already created the log file or the directory.
Log: 'System' Date/Time: 25/07/2015 7:03:44 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 25/07/2015 7:03:43 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 25/07/2015 7:03:42 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 25/07/2015 6:56:54 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
Log: 'System' Date/Time: 25/07/2015 6:54:53 PM
Type: Error Category: 0
Event: 20 Source: Microsoft-Windows-WHEA-Logger
A fatal hardware error has occurred. Component: AMD Northbridge Error Source: Machine Check Exception Error Type: HyperTransport Watchdog Timeout Error Processor ID: 0 The details view of this entry contains further information.
Log: 'System' Date/Time: 25/07/2015 6:54:07 PM
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8005e108f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\072515-13260-01.dmp. Report Id: 072515-13260-01.
Log: 'System' Date/Time: 25/07/2015 6:54:05 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 2:53:17 PM on ?7/?25/?2015 was unexpected.
Log: 'System' Date/Time: 25/07/2015 5:19:29 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The HP Support Assistant Service service failed to start due to the following error: The system cannot find the path specified.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 26/07/2015 3:16:54 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 6:54:53 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 5:54:18 PM
Type: Warning Category: 256
Event: 516 Source: mfehidk
Process **\MCUPDA~1.EXE pid (1656) contains signed but untrusted code, but was allowed to perform a privileged operation with a McAfee driver.
Log: 'System' Date/Time: 25/07/2015 5:54:16 PM
Type: Warning Category: 256
Event: 516 Source: mfehidk
Process **\MCUPDA~1.EXE pid (1656) contains signed but untrusted code, but was allowed to perform a privileged operation with a McAfee driver.
Log: 'System' Date/Time: 25/07/2015 5:11:15 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 5:09:34 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 25/07/2015 4:54:34 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 25/07/2015 4:37:34 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 25/07/2015 4:06:07 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 4:04:15 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 25/07/2015 3:51:02 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 3:49:24 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 25/07/2015 2:04:29 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 1:45:09 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 25/07/2015 1:44:44 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 1:43:35 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 25/07/2015 1:31:14 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 25/07/2015 12:28:09 AM
Type: Warning Category: 0
Event: 54 Source: TrueSight
The event description cannot be found.
Log: 'System' Date/Time: 24/07/2015 11:39:36 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Log: 'System' Date/Time: 24/07/2015 10:44:40 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_EPSON&PROD_STYLUS_STORAGE&REV_1.00#7&34A78F2F&0&423237303148FD1EA5&0#.
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 26/07/2015 12:11:51 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 25/07/2015 4:55:32 PM
Type: Error Category: 1
Event: 5010 Source: AVLogEvent
McShield failed to start because it is not trusted. Error Code:a7f40905
Log: 'Application' Date/Time: 25/07/2015 4:55:32 PM
Type: Error Category: 1
Event: 5007 Source: AVLogEvent
Failed to load a dependant module. Error Code:a7f42003
Log: 'Application' Date/Time: 25/07/2015 4:38:33 PM
Type: Error Category: 1
Event: 5010 Source: AVLogEvent
McShield failed to start because it is not trusted. Error Code:a7f40905
Log: 'Application' Date/Time: 25/07/2015 4:38:33 PM
Type: Error Category: 1
Event: 5007 Source: AVLogEvent
Failed to load a dependant module. Error Code:a7f42003
Log: 'Application' Date/Time: 25/07/2015 4:20:01 PM
Type: Error Category: 1
Event: 5010 Source: AVLogEvent
McShield failed to start because it is not trusted. Error Code:a7f40905
Log: 'Application' Date/Time: 25/07/2015 4:20:01 PM
Type: Error Category: 1
Event: 5007 Source: AVLogEvent
Failed to load a dependant module. Error Code:a7f42003
Log: 'Application' Date/Time: 22/07/2015 8:04:54 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program IEXPLORE.EXE version 11.0.9600.17909 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: 1414 Start Time: 01d0c4b9a22405a7 Termination Time: 47 Application Path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE Report Id:
Log: 'Application' Date/Time: 22/07/2015 3:45:57 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: GWXUX.exe, version: 6.3.9600.17923, time stamp: 0x55945dbd Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x556366f2 Exception code: 0xc0000005 Fault offset: 0x000000000004ada4 Faulting process id: 0x4190 Faulting application start time: 0x01d0c430ea196851 Faulting application path: C:\Windows\System32\GWX\GWXUX.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 28e136f2-3024-11e5-be23-d48564b1984b
Log: 'Application' Date/Time: 21/07/2015 4:47:24 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: GWXUX.exe, version: 6.3.9600.17923, time stamp: 0x55945dbd Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x556366f2 Exception code: 0xc0000005 Fault offset: 0x000000000004ada4 Faulting process id: 0xf34 Faulting application start time: 0x01d0c370554d807d Faulting application path: C:\Windows\System32\GWX\GWXUX.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 93ca3c50-2f63-11e5-be23-d48564b1984b
Log: 'Application' Date/Time: 20/07/2015 4:58:32 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: GWXUX.exe, version: 6.3.9600.17923, time stamp: 0x55945dbd Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x556366f2 Exception code: 0xc0000005 Fault offset: 0x000000000004ada4 Faulting process id: 0x3da0 Faulting application start time: 0x01d0c30d4da8ad78 Faulting application path: C:\Windows\System32\GWX\GWXUX.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 8d2316cc-2f00-11e5-be23-d48564b1984b
Log: 'Application' Date/Time: 20/07/2015 2:20:21 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: GWXUX.exe, version: 6.3.9600.17923, time stamp: 0x55945dbd Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x556366f2 Exception code: 0xc0000005 Fault offset: 0x000000000004ada4 Faulting process id: 0x2d3c Faulting application start time: 0x01d0c2929f60831d Faulting application path: C:\Windows\System32\GWX\GWXUX.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: dec58faf-2e85-11e5-be23-d48564b1984b
Log: 'Application' Date/Time: 18/07/2015 9:37:45 PM
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Internet Explorer because of this error. Program: Internet Explorer File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: 00000000 Disk type: 0
Log: 'Application' Date/Time: 18/07/2015 9:37:45 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: IEXPLORE.EXE, version: 11.0.9600.17909, time stamp: 0x55844c24 Faulting module name: nvwgf2um.dll, version: 10.18.13.5338, time stamp: 0x558aa184 Exception code: 0xc000001d Fault offset: 0x00236961 Faulting process id: 0x1548 Faulting application start time: 0x01d0c197c242d112 Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE Faulting module path: C:\Windows\system32\nvwgf2um.dll Report Id: 3993f0c9-2d95-11e5-be23-d48564b1984b
Log: 'Application' Date/Time: 18/07/2015 10:25:33 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: GWXUX.exe, version: 6.3.9600.17923, time stamp: 0x55945dbd Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x556366f2 Exception code: 0xc0000005 Fault offset: 0x000000000004ada4 Faulting process id: 0x11e8 Faulting application start time: 0x01d0c14413433ecc Faulting application path: C:\Windows\System32\GWX\GWXUX.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 5209fbf7-2d37-11e5-be23-d48564b1984b
Log: 'Application' Date/Time: 18/07/2015 10:23:22 AM
Type: Error Category: 0
Event: 2001 Source: NvStreamSvc
An error has occurred (Can't open process handle to nvstreamsvc.exe [87]).
Log: 'Application' Date/Time: 17/07/2015 11:15:59 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4 Faulting module name: wwanapi.dll, version: 6.1.7600.16385, time stamp: 0x4a5be0a8 Exception code: 0xc0000005 Fault offset: 0x00000000000333eb Faulting process id: 0x920 Faulting application start time: 0x01d0c0e660d59861 Faulting application path: C:\Windows\Explorer.EXE Faulting module path: C:\Windows\system32\wwanapi.dll Report Id: c85b90d8-2cd9-11e5-974b-d48564b1984b
Log: 'Application' Date/Time: 16/07/2015 11:12:19 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc000041d Fault offset: 0x0000000000000000 Faulting process id: 0xfe8 Faulting application start time: 0x01d0c01c7534c75d Faulting application path: C:\Windows\system32\mmc.exe Faulting module path: unknown Report Id: 1a9c5f8a-2c10-11e5-bd32-d48564b1984b
Log: 'Application' Date/Time: 16/07/2015 11:12:13 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process id: 0xfe8 Faulting application start time: 0x01d0c01c7534c75d Faulting application path: C:\Windows\system32\mmc.exe Faulting module path: unknown Report Id: 1739eaa7-2c10-11e5-bd32-d48564b1984b
Log: 'Application' Date/Time: 16/07/2015 10:51:39 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc000041d Fault offset: 0x0000000000000000 Faulting process id: 0x17ec Faulting application start time: 0x01d0c0194e6e63f5 Faulting application path: C:\Windows\system32\mmc.exe Faulting module path: unknown Report Id: 37b422a0-2c0d-11e5-959c-d48564b1984b
Log: 'Application' Date/Time: 16/07/2015 10:51:33 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process id: 0x17ec Faulting application start time: 0x01d0c0194e6e63f5 Faulting application path: C:\Windows\system32\mmc.exe Faulting module path: unknown Report Id: 34247398-2c0d-11e5-959c-d48564b1984b
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 26/07/2015 12:32:13 PM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
The content source <mapi://{S-1-5-21-2394937029-579550273-2574859083-1000}/> cannot be accessed.
Context: Application, SystemIndex Catalog
Details:
A server error occurred. Check that the server is available. (HRESULT : 0x80041206) (0x80041206)
Log: 'Application' Date/Time: 26/07/2015 9:39:59 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:36:44 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:32:14 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:28:29 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:24:44 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:20:59 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:16:59 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:12:59 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:09:44 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:05:29 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 9:02:59 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:59:29 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:53:59 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:50:14 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:46:14 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:42:14 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:38:29 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:34:44 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).
Log: 'Application' Date/Time: 26/07/2015 8:30:59 AM
Type: Warning Category: 0
Event: 2002 Source: NvStreamSvc
A warning has occured (Can continue stopping. [0]).