chopperbob

Maurice, since I'm at my relative's house for several hours, I googled this issue and found some other examples that were successfully resolved, so am annotating those here for your knowledge, as well as other's who have this same issue, as one of these solutions might work for them! UNFORTUNATELY, none of them worked for me!!!First off, I googled "system restore blank page", and after dismissing the dozen or so articles I had previously read prior to even posting this issue here, I came across http://www.computing...age/129223.html, where she posted: Her issue was solved by HiJinx, who's solution was to fix a damaged Windows Script: Unfortunately, HiJinx's hyperlink no longer works, so I googled "windows script for xp sp3", and selected the very first posting http://answers.micro...b2-d2f0a3a57cd6 , which implied that a damaged Windows Script can cause several pages to be blank (to include System Restore): The suggested solution that worked for KevinD872 was the following: As you know, I've already done the first two, so I did the rest, but it did not work..... Now, I did find the "Windows Script Download and Repair Page at http://www.macropool.../scripting.html and followed its example of checking what version of vbscript.dll is on this computer, and it is newer than v. 5.7: Anyway, I then googled "windows xp sp3 system restore blank" and went to http://www.computing...-oo/192537.html, where the poster's issue was solved by Chuck 2 when he suggested the following link http://support.micro...om/?kbid=831430 for Microsoft's solution: Since I had previously done "Method 1", I skipped to "Method 2", and the following photos show that all three (3) registries were correct: Maurice, the result of my efforts today may assist others in solving a blank System Restore page, but I'm still unable to get it fixed, thus far.

Good afternoon Maurice! Here's the report from Vino's Event Viewer: Vino's Event Viewer v01c run on Windows XP in English Report run at 23/01/2013 12:45:34 PM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 10/01/2013 1:22:34 PM Type: error Category: 0 Event: 7 Source: WindowsLiveMessenger The event description cannot be found. Log: 'Application' Date/Time: 30/12/2012 8:16:40 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: 26/12/2012 11:14:43 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: 25/12/2012 10:57:12 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application YahooMessenger.exe, version 10.0.0.1270, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 25/12/2012 10:57:11 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application YahooMessenger.exe, version 10.0.0.1270, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 25/12/2012 10:54:14 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: 24/12/2012 7:57:48 AM Type: error Category: 12 Event: 447 Source: ESENT wlcomm (2156) A bad page link (error -338) has been detected in a B-Tree (ObjectId: 10, PgnoRoot: 42) of database C:\Documents and Settings\HP_Administrator\Local Settings\Application Data\Microsoft\Windows Live Contacts\{194429b2-6c9e-4cdf-9622-c3776354b2ea}\DBStore\contacts.edb (42 => 323, 324). Log: 'Application' Date/Time: 22/12/2012 10:28:58 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application YahooMessenger.exe, version 10.0.0.1270, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 22/12/2012 10:21:15 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application chrome.exe, version 23.0.1271.97, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 20/12/2012 5:04:39 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: 19/12/2012 12:07:30 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application avp.exe, version 13.0.1.4210, faulting module avzkrnl.dll, version 4.39.0.6, fault address 0x001ae112. Log: 'Application' Date/Time: 19/12/2012 7:13:04 AM Type: error Category: 0 Event: 1000 Source: Application Error Faulting application yahoomessenger.exe, version 10.0.0.1270, faulting module yahoomessenger.exe, version 10.0.0.1270, fault address 0x000482e8. Log: 'Application' Date/Time: 17/12/2012 8:03:55 PM Type: error Category: 0 Event: 1000 Source: Application Error Faulting application iexplore.exe, version 8.0.6001.18702, faulting module skypeieplugin.dll, version 6.5.0.11422, fault address 0x00012c87. Log: 'Application' Date/Time: 10/12/2012 9:15:01 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application wmplayer.exe, version 10.0.0.3646, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 09/12/2012 2:32:11 PM Type: error Category: 0 Event: 1001 Source: Application Error Fault bucket -1988463584. Log: 'Application' Date/Time: 09/12/2012 2:31:20 PM Type: error Category: 0 Event: 1000 Source: Application Error Faulting application yahoomessenger.exe, version 10.0.0.1270, faulting module ntdll.dll, version 5.1.2600.6055, fault address 0x00012440. Log: 'Application' Date/Time: 27/11/2012 9:53:09 PM Type: error Category: 0 Event: 1001 Source: Application Hang Fault bucket 1895706856. Log: 'Application' Date/Time: 27/11/2012 9:53:02 PM Type: error Category: 0 Event: 1001 Source: Application Hang Fault bucket 1895706856. Log: 'Application' Date/Time: 27/11/2012 9:52:48 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application YahooMessenger.exe, version 10.0.0.1270, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 27/11/2012 9:52:31 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application YahooMessenger.exe, version 10.0.0.1270, hang module hungapp, version 0.0.0.0, hang address 0x00000000. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - information Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 23/01/2013 10:23:26 AM Type: information Category: 1 Event: 101 Source: SkypeUpdate Service stopped. Log: 'Application' Date/Time: 23/01/2013 10:23:25 AM Type: information Category: 1 Event: 103 Source: SkypeUpdate SkypeUpdate service is shutting down due to idle timeout. Log: 'Application' Date/Time: 23/01/2013 10:22:25 AM Type: information Category: 1 Event: 100 Source: SkypeUpdate Service started. Log: 'Application' Date/Time: 23/01/2013 10:02:04 AM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 23/01/2013 10:02:01 AM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 23/01/2013 10:01:53 AM Type: information Category: 1 Event: 101 Source: SkypeUpdate Service stopped. Log: 'Application' Date/Time: 23/01/2013 10:01:52 AM Type: information Category: 1 Event: 103 Source: SkypeUpdate SkypeUpdate service is shutting down due to idle timeout. Log: 'Application' Date/Time: 23/01/2013 9:59:53 AM Type: information Category: 0 Event: 1800 Source: SecurityCenter The Windows Security Center Service has started. Log: 'Application' Date/Time: 23/01/2013 9:59:52 AM Type: information Category: 1 Event: 100 Source: SkypeUpdate Service started. Log: 'Application' Date/Time: 23/01/2013 9:59:48 AM Type: information Category: 0 Event: 4 Source: LightScribeService The LightScribe Service started successfully. Log: 'Application' Date/Time: 23/01/2013 9:59:48 AM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 22/01/2013 6:02:03 PM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 22/01/2013 6:02:00 PM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 22/01/2013 1:02:06 PM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 22/01/2013 1:02:01 PM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 22/01/2013 8:11:31 AM Type: information Category: 1 Event: 101 Source: SkypeUpdate Service stopped. Log: 'Application' Date/Time: 22/01/2013 8:11:30 AM Type: information Category: 1 Event: 103 Source: SkypeUpdate SkypeUpdate service is shutting down due to idle timeout. Log: 'Application' Date/Time: 22/01/2013 8:10:30 AM Type: information Category: 1 Event: 100 Source: SkypeUpdate Service started. Log: 'Application' Date/Time: 22/01/2013 8:02:04 AM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 22/01/2013 8:02:01 AM Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 22/01/2013 9:14:45 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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/01/2013 6:37:57 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 16/01/2013 6:37:57 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 16/01/2013 6:32:15 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 16/01/2013 6:32:14 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 13/01/2013 9:30:45 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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: 12/01/2013 8:31:49 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 12/01/2013 8:31:49 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 10/01/2013 1:54:11 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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: 09/01/2013 9:03:10 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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: 09/01/2013 12:35:56 AM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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: 09/01/2013 12:35:55 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: 08/01/2013 5:25:40 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 08/01/2013 5:25:40 PM Type: warning Category: 0 Event: 63 Source: WinMgmt A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Log: 'Application' Date/Time: 08/01/2013 2:28:59 PM 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: 08/01/2013 2:26:06 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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: 02/01/2013 10:17:24 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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: 22/12/2012 10:24:35 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user YOUR-55E5F9E3D2\HP_Administrator 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: 22/12/2012 10:24:34 PM 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: 22/12/2012 9:18:51 PM Type: warning Category: 52 Event: 4354 Source: EventSystem The COM+ Event System failed to fire the StopScreenSaver method on subscription {3C1BF16A-73ED-4F5A-88B7-C5B44EB45973}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 80010100. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 16/01/2013 1:19:39 PM Type: error Category: 0 Event: 7034 Source: Service Control Manager The Pml Driver HPZ12 service terminated unexpectedly. It has done this 1 time(s). Log: 'System' Date/Time: 12/01/2013 7:19:02 PM Type: error Category: 0 Event: 25 Source: VolSnap The shadow copy of volume C: was aborted because the diff area file could not grow in time. Consider reducing the IO load on this system to avoid this problem in the future. Log: 'System' Date/Time: 12/01/2013 7:18:55 PM Type: error Category: 0 Event: 10 Source: VolSnap The shadow copy of volume C: took too long to install. Log: 'System' Date/Time: 12/01/2013 7:14:14 PM Type: error Category: 0 Event: 12 Source: VolSnap The shadow copy of volume C: became low on diff area space before it was properly installed. Log: 'System' Date/Time: 08/01/2013 5:06:26 PM Type: error Category: 0 Event: 7034 Source: Service Control Manager The Skype C2C Service service terminated unexpectedly. It has done this 1 time(s). Log: 'System' Date/Time: 08/01/2013 2:38:52 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service MDM with arguments "" in order to run the server: {0C0A3666-30C9-11D0-8F20-00805F2CD064} Log: 'System' Date/Time: 08/01/2013 2:37:25 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service MDM with arguments "" in order to run the server: {943B6A75-BB5E-41A7-A6D3-A1A5E892B33B} Log: 'System' Date/Time: 08/01/2013 2:37:23 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service MDM with arguments "" in order to run the server: {0C0A3666-30C9-11D0-8F20-00805F2CD064} Log: 'System' Date/Time: 08/01/2013 2:36:13 PM Type: error Category: 0 Event: 7026 Source: Service Control Manager The following boot-start or system-start driver(s) failed to load: AFD Fips intelppm IPSec KLIF kltdi kneps MRxSmb NetBIOS NetBT RasAcd Rdbss Tcpip Log: 'System' Date/Time: 08/01/2013 2:36:13 PM Type: error Category: 0 Event: 7001 Source: Service Control Manager The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error: A device attached to the system is not functioning. Log: 'System' Date/Time: 08/01/2013 2:36:13 PM Type: error Category: 0 Event: 7001 Source: Service Control Manager The TCP/IP NetBIOS Helper service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. Log: 'System' Date/Time: 08/01/2013 2:36:13 PM Type: error Category: 0 Event: 7001 Source: Service Control Manager The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error: A device attached to the system is not functioning. Log: 'System' Date/Time: 08/01/2013 2:36:13 PM Type: error Category: 0 Event: 7001 Source: Service Control Manager The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error: A device attached to the system is not functioning. Log: 'System' Date/Time: 08/01/2013 2:35:35 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} Log: 'System' Date/Time: 08/01/2013 1:13:53 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} Log: 'System' Date/Time: 08/01/2013 1:13:30 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service netman with arguments "" in order to run the server: {BA126AD1-2166-11D1-B1D0-00805FC1270E} Log: 'System' Date/Time: 08/01/2013 1:12:37 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service MDM with arguments "" in order to run the server: {0C0A3666-30C9-11D0-8F20-00805F2CD064} Log: 'System' Date/Time: 08/01/2013 1:12:31 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service MDM with arguments "" in order to run the server: {943B6A75-BB5E-41A7-A6D3-A1A5E892B33B} Log: 'System' Date/Time: 08/01/2013 1:12:31 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service MDM with arguments "" in order to run the server: {0C0A3666-30C9-11D0-8F20-00805F2CD064} Log: 'System' Date/Time: 08/01/2013 1:11:46 PM Type: error Category: 0 Event: 10005 Source: DCOM DCOM got error "%1084" attempting to start the service MDM with arguments "" in order to run the server: {0C0A3666-30C9-11D0-8F20-00805F2CD064} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - information Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 23/01/2013 12:34:28 PM Type: information Category: 0 Event: 7035 Source: Service Control Manager The MBAMSwissArmy service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 12:06:01 PM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Adobe Flash Player Update Service service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 12:06:01 PM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Adobe Flash Player Update Service service entered the stopped state. Log: 'System' Date/Time: 23/01/2013 12:06:01 PM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Adobe Flash Player Update Service service entered the running state. Log: 'System' Date/Time: 23/01/2013 11:06:02 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Adobe Flash Player Update Service service entered the stopped state. Log: 'System' Date/Time: 23/01/2013 11:06:02 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Adobe Flash Player Update Service service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 11:06:01 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Adobe Flash Player Update Service service entered the running state. Log: 'System' Date/Time: 23/01/2013 10:23:26 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Skype Updater service entered the stopped state. Log: 'System' Date/Time: 23/01/2013 10:22:25 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Skype Updater service entered the running state. Log: 'System' Date/Time: 23/01/2013 10:22:25 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Skype Updater service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 10:20:59 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The HTTP SSL service entered the running state. Log: 'System' Date/Time: 23/01/2013 10:20:58 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The HTTP SSL service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 10:20:50 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The IMAPI CD-Burning COM Service service entered the stopped state. Log: 'System' Date/Time: 23/01/2013 10:20:43 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The IMAPI CD-Burning COM Service service entered the running state. Log: 'System' Date/Time: 23/01/2013 10:20:42 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The IMAPI CD-Burning COM Service service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 10:20:39 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The SSDP Discovery Service service entered the running state. Log: 'System' Date/Time: 23/01/2013 10:20:39 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The SSDP Discovery Service service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 10:18:48 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Fast User Switching Compatibility service was successfully sent a start control. Log: 'System' Date/Time: 23/01/2013 10:18:48 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Fast User Switching Compatibility service entered the running state. Log: 'System' Date/Time: 23/01/2013 10:14:55 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Remote Access Connection Manager service entered the running state. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 22/01/2013 7:48:46 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: 22/01/2013 7:18:30 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: 21/01/2013 8:42:30 PM Type: warning Category: 0 Event: 240 Source: Win32k A request to suspend power was denied by winlogon.exe. Log: 'System' Date/Time: 12/01/2013 6:25:07 PM Type: warning Category: 0 Event: 10 Source: W32Time The time provider 'NtpClient' returned an error when asked for time samples. The error will be ignored. The error was: The handle is invalid. (0x80070006) Log: 'System' Date/Time: 12/01/2013 6:13:37 PM Type: warning Category: 0 Event: 7 Source: W32Time The time provider 'NtpClient' returned an error while updating its configuration. The error will be ignored. The error was: Catastrophic failure (0x8000FFFF)

Yes, you and I have already checked that, too, and all is well with that.

As of 8:00 pm last night, system restore page still comes up blank. I'll see if they can start another scan, but at the very beginning of this issue, I had informed you that it had just finished a complete scan less than 23 hrs prior to my post and found nothing.

Maurice, I'm please to inform you that the MS Technet forum link you provided gave me the needed info to fix my issue! I typed "Winmgmt" in the forum's search box and the very first topic listed was Windows 7 WMI repair (systeminfo does not work)‎ which I clicked on and found this solution: I followed the instructions, and Voila!!! my System Information is back! I want to thank you for all your patience and helpful instructions to ensure my laptop was completely free of viruses and malwares, and providing me that helpful link. If there's a way for you to show this issue as "Resolved" or "Solved" so others with a similar problem can find it, it would be helpful. Have a great week!!

Here's the MBAM log.txt file: Malwarebytes Anti-Malware (PRO) 1.70.0.1100 www.malwarebytes.org Database version: v2013.01.16.07 Windows XP Service Pack 3 x86 NTFS Internet Explorer 8.0.6001.18702 HP_Administrator :: YOUR-55E5F9E3D2 [administrator] Protection: Enabled 1/16/2013 1:49:59 PM mbam-log-2013-01-16 (13-49-59).txt Scan type: Full scan (C:\|D:\|) Scan options enabled: Memory | Startup | Registry | File System | Heuristics/Extra | Heuristics/Shuriken | PUP | PUM Scan options disabled: P2P Objects scanned: 372242 Time elapsed: 1 hour(s), 49 minute(s), 29 second(s) Memory Processes Detected: 0 (No malicious items detected) Memory Modules Detected: 0 (No malicious items detected) Registry Keys Detected: 0 (No malicious items detected) Registry Values Detected: 0 (No malicious items detected) Registry Data Items Detected: 0 (No malicious items detected) Folders Detected: 0 (No malicious items detected) Files Detected: 0 (No malicious items detected) (end)

Maurice, I'm glad to hear there are no viruses or malware in my laptop, even though my issue is still unresolved! I've found the following suggestions (I haven't done any of them) when googling "failed connection to this computer. check to see that the winmgmt service is running" and wanted your opinion on them: Suggestion #1: Go to Start/Run/CMD and type in: net stop winmgmt. Then delete the %windir&\system32\wbem\repository directory. Once done go back to Start/Run/CMD and type in: net start winmgmt If that doesn't help, try this: Open a Command Prompt and type "winmgmt /clearadap" to clear prior WMI /resyncperf information from the registry. Then type "winmgmt /resyncperf" to register the system performance libraries with WMI again. Suggestion #2: Register WMI Components: 1. Click start ->All Programs ->Accessories. Right-click Command Prompt and click Run as an administrator. 2. Type the following command in the prompt window and press Enter after every line. winmgmt /clearadap winmgmt /kill winmgmt /unregserver winmgmt /regserver winmgmt /resyncperf This may or may not repair the repository but will re-install wmi into the registry. Courtesy of Kelly T. @ http://www.kellys-korner.com/ [Windows Management Instrumentation - WinMgmt could not initialize the core parts] Suggestion 3: Import WMI Registry Keys: Step 1: Back up Registry -------------------------------------- 1. Click Start, type "regedit" (without quotation marks) in the Open line, and click OK. 2. In the Registry Editor, click File menu, and click Export. 3. In the Save In list, select the folder where you want to save the backup. 4. In the File Name box, type a name for your backup file, such as "Options" or "Backup". 5. Click Save. Step 2: Create and Run the Registry File --------------------------------------- 1. Click Start, type "notepad C:\register.reg" (without quotation marks) in the Open box, and then click OK. Choose Yes when you are prompted to create a new file. 2. Copy the following texts between the star marks (BEGIN & END) and then paste them into the opened Notepad window: ***************BEGIN*************** Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winmgmt] "DisplayName"="Windows Management Instrumentation" "ImagePath"=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\ 74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\ 00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\ 6b,00,20,00,6e,00,65,00,74,00,73,00,76,00,63,00,73,00,00,00 "Description"="Provides a common interface and object model to access management information about operating system, devices, applications and services. If this service is stopped, most Windows-based software will not function properly. If this service is disabled, any services that explicitly depend on it will fail to start." "ObjectName"="localSystem" "ErrorControl"=dword:00000000 "Start"=dword:00000002 "Type"=dword:00000020 "DependOnService"=hex(7):52,00,50,00,43,00,53,00,53,00,00,00,00,00 "ServiceSidType"=dword:00000001 "FailureActions"=hex:80,51,01,00,00,00,00,00,00,00,00,00,02,00,00,00,14,00,00,\ 00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winmgmt\Parameters] "ServiceDllUnloadOnStop"=dword:00000001 "ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\ 00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\ 77,00,62,00,65,00,6d,00,5c,00,57,00,4d,00,49,00,73,00,76,00,63,00,2e,00,64,\ 00,6c,00,6c,00,00,00 "ServiceMain"="ServiceMain" ****************END**************** After you paste the above commands, please close the Notepad window. Choose Yes when you are prompted to save the file. 3. Click Start, type "C:\register.reg" (without quotation marks) and press Enter to run the commands we have pasted. 4. When you receive a message box asking "Are you sure you want to add the information in the REG file to the registry", choose "Yes" 5. You will receive another message box indicating "Information in the REG file has been successfully entered into the registry"; please click "OK" to confirm. 6. Restart the computer.

Maurice, Here's the Rkill.txt: Rkill 2.4.5 by Lawrence Abrams (Grinler) http://www.bleepingcomputer.com/ Copyright 2008-2013 BleepingComputer.com More Information about Rkill can be found at this link: http://www.bleepingcomputer.com/forums/topic308364.html Program started at: 01/16/2013 01:19:35 PM in x86 mode. Windows Version: Microsoft Windows XP Service Pack 3 Checking for Windows services to stop: * No malware services found to stop. Checking for processes to terminate: * C:\WINDOWS\system32\HPZipm12.exe (PID: 1680) [WD-HEUR] 1 proccess terminated! Checking Registry for malware related settings: * No issues found in the Registry. Resetting .EXE, .COM, & .BAT associations in the Windows Registry. Performing miscellaneous checks: * Windows Firewall Disabled [HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile] "EnableFirewall" = dword:00000000 Checking Windows Service Integrity: * No issues found. Searching for Missing Digital Signatures: * C:\WINDOWS\System32\drivers\mqac.sys [NoSig] +-> C:\WINDOWS\$hf_mig$\KB971032\SP2QFE\mqac.sys : 91,776 : 06/22/2009 00:30 AM : 9229e191fe206628be17d1e67a5faed9 [Pos Repl] +-> C:\WINDOWS\$NtUninstallKB971032$\mqac.sys : 72,960 : 08/10/2004 00:00 AM : db07b0088cdfd20c2a22e675120ede34 [Pos Repl] +-> C:\WINDOWS\ServicePackFiles\i386\mqac.sys : 92,544 : 04/13/2008 02:39 PM : 70c14f5cca5cf73f8a645c73a01d8726 [Pos Repl] +-> C:\WINDOWS\system32\dllcache\mqac.sys : 91,776 : 06/22/2009 02:48 AM : eee50bf24caeedb515a8f3b22756d3bb [Pos Repl] Checking HOSTS File: * HOSTS file entries found: 127.0.0.1 localhost Program finished at: 01/16/2013 01:20:51 PM Execution time: 0 hours(s), 1 minute(s), and 16 seconds(s)

Maurice, I don't want to seem ungrateful, but in my very first post I stated I had already checked this and it was running, but here's the proof, anyway: Okay, I'm at my relative's house, so I'll be doing those steps and will check back to see what you suggest next for my issue. Thanks!

Maurice, I remember setting the "Selective startup" over a year ago when customizing some programs, like Microsoft Outlook, to delay their startup to improve boot-up. Anyway, I selected "Normal startup" radio button, as instructed. All of the services you listed were shown and all were checked. I was prompted to reboot after selecting the "Normal startup", and after I rebooted, I still could not access System Information.

Maurice, Just checking what you wanted me to do next on my relative's computer (I plan on visiting tomorrow), and I noticed your instructions above. She does NOT have MBAM installed, just Kaspersky Internet Security 2013.

The KasperskyTDSSKiller scan found no viruses and report is posted below: 16:59:10.0328 5664 TDSS rootkit removing tool 2.8.15.0 Oct 31 2012 21:47:35 16:59:10.0759 5664 ============================================================ 16:59:10.0759 5664 Current date / time: 2013/01/15 16:59:10.0759 16:59:10.0759 5664 SystemInfo: 16:59:10.0759 5664 16:59:10.0759 5664 OS Version: 6.1.7601 ServicePack: 1.0 16:59:10.0759 5664 Product type: Workstation 16:59:10.0759 5664 ComputerName: BOBINGHAM-PC 16:59:10.0760 5664 UserName: Bob Ingham 16:59:10.0760 5664 Windows directory: C:\windows 16:59:10.0760 5664 System windows directory: C:\windows 16:59:10.0760 5664 Running under WOW64 16:59:10.0760 5664 Processor architecture: Intel x64 16:59:10.0760 5664 Number of processors: 8 16:59:10.0760 5664 Page size: 0x1000 16:59:10.0760 5664 Boot type: Normal boot 16:59:10.0760 5664 ============================================================ 16:59:11.0393 5664 Drive \Device\Harddisk0\DR0 - Size: 0xAEA8CDE000 (698.64 Gb), SectorSize: 0x200, Cylinders: 0x16441, SectorsPerTrack: 0x3F, TracksPerCylinder: 0xFF, Type 'K0', Flags 0x00000040 16:59:11.0399 5664 ============================================================ 16:59:11.0399 5664 \Device\Harddisk0\DR0: 16:59:11.0400 5664 MBR partitions: 16:59:11.0400 5664 \Device\Harddisk0\DR0\Partition1: MBR, Type 0x7, StartLBA 0x2EE800, BlocksNum 0x55432800 16:59:11.0400 5664 ============================================================ 16:59:11.0453 5664 C: <-> \Device\Harddisk0\DR0\Partition1 16:59:11.0453 5664 ============================================================ 16:59:11.0454 5664 Initialize success 16:59:11.0454 5664 ============================================================ 16:59:37.0002 8236 ============================================================ 16:59:37.0002 8236 Scan started 16:59:37.0002 8236 Mode: Manual; 16:59:37.0002 8236 ============================================================ 16:59:47.0256 8236 ================ Scan system memory ======================== 16:59:47.0257 8236 System memory - ok 16:59:47.0257 8236 ================ Scan services ============================= 16:59:47.0746 8236 [ A87D604AEA360176311474C87A63BB88 ] 1394ohci C:\windows\system32\drivers\1394ohci.sys 16:59:47.0750 8236 1394ohci - ok 16:59:47.0788 8236 [ D81D9E70B8A6DD14D42D7B4EFA65D5F2 ] ACPI C:\windows\system32\drivers\ACPI.sys 16:59:47.0793 8236 ACPI - ok 16:59:47.0833 8236 [ 99F8E788246D495CE3794D7E7821D2CA ] AcpiPmi C:\windows\system32\drivers\acpipmi.sys 16:59:47.0834 8236 AcpiPmi - ok 16:59:48.0038 8236 [ D19C4EE2AC7C47B8F5F84FFF1A789D8A ] AdobeARMservice C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\armsvc.exe 16:59:48.0040 8236 AdobeARMservice - ok 16:59:48.0456 8236 [ 424877CB9D5517F980FF7BACA2EB379D ] AdobeFlashPlayerUpdateSvc C:\windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe 16:59:48.0458 8236 AdobeFlashPlayerUpdateSvc - ok 16:59:48.0559 8236 [ 2F6B34B83843F0C5118B63AC634F5BF4 ] adp94xx C:\windows\system32\drivers\adp94xx.sys 16:59:48.0566 8236 adp94xx - ok 16:59:48.0641 8236 [ 597F78224EE9224EA1A13D6350CED962 ] adpahci C:\windows\system32\drivers\adpahci.sys 16:59:48.0645 8236 adpahci - ok 16:59:48.0665 8236 [ E109549C90F62FB570B9540C4B148E54 ] adpu320 C:\windows\system32\drivers\adpu320.sys 16:59:48.0669 8236 adpu320 - ok 16:59:48.0692 8236 [ 4B78B431F225FD8624C5655CB1DE7B61 ] AeLookupSvc C:\windows\System32\aelupsvc.dll 16:59:48.0693 8236 AeLookupSvc - ok 16:59:48.0746 8236 [ 1C7857B62DE5994A75B054A9FD4C3825 ] AFD C:\windows\system32\drivers\afd.sys 16:59:48.0752 8236 AFD - ok 16:59:48.0778 8236 [ 608C14DBA7299D8CB6ED035A68A15799 ] agp440 C:\windows\system32\drivers\agp440.sys 16:59:48.0780 8236 agp440 - ok 16:59:48.0812 8236 [ 3290D6946B5E30E70414990574883DDB ] ALG C:\windows\System32\alg.exe 16:59:48.0814 8236 ALG - ok 16:59:48.0838 8236 [ 5812713A477A3AD7363C7438CA2EE038 ] aliide C:\windows\system32\drivers\aliide.sys 16:59:48.0840 8236 aliide - ok 16:59:48.0862 8236 [ 1FF8B4431C353CE385C875F194924C0C ] amdide C:\windows\system32\drivers\amdide.sys 16:59:48.0864 8236 amdide - ok 16:59:48.0875 8236 [ 7024F087CFF1833A806193EF9D22CDA9 ] AmdK8 C:\windows\system32\drivers\amdk8.sys 16:59:48.0876 8236 AmdK8 - ok 16:59:48.0889 8236 [ 1E56388B3FE0D031C44144EB8C4D6217 ] AmdPPM C:\windows\system32\drivers\amdppm.sys 16:59:48.0892 8236 AmdPPM - ok 16:59:48.0919 8236 [ D4121AE6D0C0E7E13AA221AA57EF2D49 ] amdsata C:\windows\system32\drivers\amdsata.sys 16:59:48.0922 8236 amdsata - ok 16:59:48.0957 8236 [ F67F933E79241ED32FF46A4F29B5120B ] amdsbs C:\windows\system32\drivers\amdsbs.sys 16:59:48.0960 8236 amdsbs - ok 16:59:48.0970 8236 [ 540DAF1CEA6094886D72126FD7C33048 ] amdxata C:\windows\system32\drivers\amdxata.sys 16:59:48.0972 8236 amdxata - ok 16:59:49.0006 8236 [ 89A69C3F2F319B43379399547526D952 ] AppID C:\windows\system32\drivers\appid.sys 16:59:49.0008 8236 AppID - ok 16:59:49.0039 8236 [ 0BC381A15355A3982216F7172F545DE1 ] AppIDSvc C:\windows\System32\appidsvc.dll 16:59:49.0041 8236 AppIDSvc - ok 16:59:49.0054 8236 [ 3977D4A871CA0D4F2ED1E7DB46829731 ] Appinfo C:\windows\System32\appinfo.dll 16:59:49.0056 8236 Appinfo - ok 16:59:49.0172 8236 [ 7EF47644B74EBE721CC32211D3C35E76 ] Apple Mobile Device C:\Program Files (x86)\Common Files\Apple\Mobile Device Support\AppleMobileDeviceService.exe 16:59:49.0174 8236 Apple Mobile Device - ok 16:59:49.0196 8236 [ C484F8CEB1717C540242531DB7845C4E ] arc C:\windows\system32\drivers\arc.sys 16:59:49.0198 8236 arc - ok 16:59:49.0226 8236 [ 019AF6924AEFE7839F61C830227FE79C ] arcsas C:\windows\system32\drivers\arcsas.sys 16:59:49.0228 8236 arcsas - ok 16:59:49.0274 8236 [ 4FCAEF0C5BE7629AEB878998E0FE959B ] aswFsBlk C:\windows\system32\drivers\aswFsBlk.sys 16:59:49.0276 8236 aswFsBlk - ok 16:59:49.0314 8236 [ B50CDD87772D6A11CB90924AAD399DF8 ] aswMonFlt C:\windows\system32\drivers\aswMonFlt.sys 16:59:49.0316 8236 aswMonFlt - ok 16:59:49.0382 8236 [ 57768C7DB4681F2510F247F82EF31D4F ] aswRdr C:\windows\System32\Drivers\aswrdr2.sys 16:59:49.0384 8236 aswRdr - ok 16:59:49.0408 8236 [ E71D826A1F3CE9C9DE3E77F2D02AFFBF ] aswSnx C:\windows\system32\drivers\aswSnx.sys 16:59:49.0419 8236 aswSnx - ok 16:59:49.0460 8236 [ 538A32E2C99BF073D4CA76C30BEDAA60 ] aswSP C:\windows\system32\drivers\aswSP.sys 16:59:49.0465 8236 aswSP - ok 16:59:49.0478 8236 [ 6EDC79D73745FD44C41B55B2D13D0B70 ] aswTdi C:\windows\system32\drivers\aswTdi.sys 16:59:49.0479 8236 aswTdi - ok 16:59:49.0505 8236 [ 769765CE2CC62867468CEA93969B2242 ] AsyncMac C:\windows\system32\DRIVERS\asyncmac.sys 16:59:49.0506 8236 AsyncMac - ok 16:59:49.0534 8236 [ 02062C0B390B7729EDC9E69C680A6F3C ] atapi C:\windows\system32\drivers\atapi.sys 16:59:49.0536 8236 atapi - ok 16:59:49.0581 8236 [ F23FEF6D569FCE88671949894A8BECF1 ] AudioEndpointBuilder C:\windows\System32\Audiosrv.dll 16:59:49.0589 8236 AudioEndpointBuilder - ok 16:59:49.0599 8236 [ F23FEF6D569FCE88671949894A8BECF1 ] AudioSrv C:\windows\System32\Audiosrv.dll 16:59:49.0604 8236 AudioSrv - ok 16:59:49.0711 8236 [ 8FA553E9AE69808D99C164733A0F9590 ] avast! Antivirus C:\Program Files\AVAST Software\Avast\AvastSvc.exe 16:59:49.0712 8236 avast! Antivirus - ok 16:59:49.0745 8236 [ A6BF31A71B409DFA8CAC83159E1E2AFF ] AxInstSV C:\windows\System32\AxInstSV.dll 16:59:49.0749 8236 AxInstSV - ok 16:59:49.0791 8236 [ 3E5B191307609F7514148C6832BB0842 ] b06bdrv C:\windows\system32\drivers\bxvbda.sys 16:59:49.0798 8236 b06bdrv - ok 16:59:49.0830 8236 [ B5ACE6968304A3900EEB1EBFD9622DF2 ] b57nd60a C:\windows\system32\DRIVERS\b57nd60a.sys 16:59:49.0834 8236 b57nd60a - ok 16:59:49.0866 8236 [ FDE360167101B4E45A96F939F388AEB0 ] BDESVC C:\windows\System32\bdesvc.dll 16:59:49.0868 8236 BDESVC - ok 16:59:49.0893 8236 [ 16A47CE2DECC9B099349A5F840654746 ] Beep C:\windows\system32\drivers\Beep.sys 16:59:49.0894 8236 Beep - ok 16:59:49.0930 8236 [ 82974D6A2FD19445CC5171FC378668A4 ] BFE C:\windows\System32\bfe.dll 16:59:49.0938 8236 BFE - ok 16:59:49.0974 8236 [ 1EA7969E3271CBC59E1730697DC74682 ] BITS C:\windows\System32\qmgr.dll 16:59:50.0030 8236 BITS - ok 16:59:50.0053 8236 [ 61583EE3C3A17003C4ACD0475646B4D3 ] blbdrive C:\windows\system32\drivers\blbdrive.sys 16:59:50.0054 8236 blbdrive - ok 16:59:50.0075 8236 [ 6C02A83164F5CC0A262F4199F0871CF5 ] bowser C:\windows\system32\DRIVERS\bowser.sys 16:59:50.0077 8236 bowser - ok 16:59:50.0115 8236 [ 56E4345F392F17D66683225E214840CB ] bpenum C:\windows\system32\DRIVERS\bpenum.sys 16:59:50.0118 8236 bpenum - ok 16:59:50.0135 8236 [ D50B07C4D7AFEC4CA6AC8FCB72583C5B ] bpmp C:\windows\system32\DRIVERS\bpmp.sys 16:59:50.0138 8236 bpmp - ok 16:59:50.0146 8236 [ A85BA55E4FE9CB2F342F281AAF7DE810 ] bpusb C:\windows\system32\Drivers\bpusb.sys 16:59:50.0149 8236 bpusb - ok 16:59:50.0174 8236 [ F09EEE9EDC320B5E1501F749FDE686C8 ] BrFiltLo C:\windows\system32\drivers\BrFiltLo.sys 16:59:50.0203 8236 BrFiltLo - ok 16:59:50.0241 8236 [ B114D3098E9BDB8BEA8B053685831BE6 ] BrFiltUp C:\windows\system32\drivers\BrFiltUp.sys 16:59:50.0242 8236 BrFiltUp - ok 16:59:50.0312 8236 [ 05F5A0D14A2EE1D8255C2AA0E9E8E694 ] Browser C:\windows\System32\browser.dll 16:59:50.0316 8236 Browser - ok 16:59:50.0376 8236 [ 43BEA8D483BF1870F018E2D02E06A5BD ] Brserid C:\windows\System32\Drivers\Brserid.sys 16:59:50.0420 8236 Brserid - ok 16:59:50.0439 8236 [ A6ECA2151B08A09CACECA35C07F05B42 ] BrSerWdm C:\windows\System32\Drivers\BrSerWdm.sys 16:59:50.0441 8236 BrSerWdm - ok 16:59:50.0455 8236 [ B79968002C277E869CF38BD22CD61524 ] BrUsbMdm C:\windows\System32\Drivers\BrUsbMdm.sys 16:59:50.0456 8236 BrUsbMdm - ok 16:59:50.0478 8236 [ A87528880231C54E75EA7A44943B38BF ] BrUsbSer C:\windows\System32\Drivers\BrUsbSer.sys 16:59:50.0481 8236 BrUsbSer - ok 16:59:50.0492 8236 [ 9DA669F11D1F894AB4EB69BF546A42E8 ] BTHMODEM C:\windows\system32\drivers\bthmodem.sys 16:59:50.0494 8236 BTHMODEM - ok 16:59:50.0532 8236 [ 95F9C2976059462CBBF227F7AAB10DE9 ] bthserv C:\windows\system32\bthserv.dll 16:59:50.0535 8236 bthserv - ok 16:59:50.0550 8236 [ B8BD2BB284668C84865658C77574381A ] cdfs C:\windows\system32\DRIVERS\cdfs.sys 16:59:50.0552 8236 cdfs - ok 16:59:50.0584 8236 [ F036CE71586E93D94DAB220D7BDF4416 ] cdrom C:\windows\system32\DRIVERS\cdrom.sys 16:59:50.0586 8236 cdrom - ok 16:59:50.0632 8236 [ A965B206921C55F2D1481789D609B711 ] CeKbFilter C:\windows\system32\DRIVERS\CeKbFilter.sys 16:59:50.0634 8236 CeKbFilter - ok 16:59:50.0666 8236 [ F17D1D393BBC69C5322FBFAFACA28C7F ] CertPropSvc C:\windows\System32\certprop.dll 16:59:50.0668 8236 CertPropSvc - ok 16:59:50.0694 8236 [ D7CD5C4E1B71FA62050515314CFB52CF ] circlass C:\windows\system32\drivers\circlass.sys 16:59:50.0696 8236 circlass - ok 16:59:50.0713 8236 [ FE1EC06F2253F691FE36217C592A0206 ] CLFS C:\windows\system32\CLFS.sys 16:59:50.0718 8236 CLFS - ok 16:59:50.0792 8236 [ D88040F816FDA31C3B466F0FA0918F29 ] clr_optimization_v2.0.50727_32 C:\windows\Microsoft.NET\Framework\v2.0.50727\mscorsvw.exe 16:59:50.0794 8236 clr_optimization_v2.0.50727_32 - ok 16:59:50.0853 8236 [ D1CEEA2B47CB998321C579651CE3E4F8 ] clr_optimization_v2.0.50727_64 C:\windows\Microsoft.NET\Framework64\v2.0.50727\mscorsvw.exe 16:59:50.0854 8236 clr_optimization_v2.0.50727_64 - ok 16:59:50.0945 8236 [ C5A75EB48E2344ABDC162BDA79E16841 ] clr_optimization_v4.0.30319_32 C:\windows\Microsoft.NET\Framework\v4.0.30319\mscorsvw.exe 16:59:50.0948 8236 clr_optimization_v4.0.30319_32 - ok 16:59:51.0013 8236 [ C6F9AF94DCD58122A4D7E89DB6BED29D ] clr_optimization_v4.0.30319_64 C:\windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe 16:59:51.0017 8236 clr_optimization_v4.0.30319_64 - ok 16:59:51.0037 8236 [ 0840155D0BDDF1190F84A663C284BD33 ] CmBatt C:\windows\system32\drivers\CmBatt.sys 16:59:51.0038 8236 CmBatt - ok 16:59:51.0056 8236 [ E19D3F095812725D88F9001985B94EDD ] cmdide C:\windows\system32\drivers\cmdide.sys 16:59:51.0058 8236 cmdide - ok 16:59:51.0112 8236 [ 9AC4F97C2D3E93367E2148EA940CD2CD ] CNG C:\windows\system32\Drivers\cng.sys 16:59:51.0118 8236 CNG - ok 16:59:51.0152 8236 [ 102DE219C3F61415F964C88E9085AD14 ] Compbatt C:\windows\system32\drivers\compbatt.sys 16:59:51.0154 8236 Compbatt - ok 16:59:51.0193 8236 [ 03EDB043586CCEBA243D689BDDA370A8 ] CompositeBus C:\windows\system32\drivers\CompositeBus.sys 16:59:51.0194 8236 CompositeBus - ok 16:59:51.0204 8236 COMSysApp - ok 16:59:51.0223 8236 [ 1C827878A998C18847245FE1F34EE597 ] crcdisk C:\windows\system32\drivers\crcdisk.sys 16:59:51.0239 8236 crcdisk - ok 16:59:51.0293 8236 [ 9C01375BE382E834CC26D1B7EAF2C4FE ] CryptSvc C:\windows\system32\cryptsvc.dll 16:59:51.0297 8236 CryptSvc - ok 16:59:51.0340 8236 [ 5C627D1B1138676C0A7AB2C2C190D123 ] DcomLaunch C:\windows\system32\rpcss.dll 16:59:51.0349 8236 DcomLaunch - ok 16:59:51.0381 8236 [ 3CEC7631A84943677AA8FA8EE5B6B43D ] defragsvc C:\windows\System32\defragsvc.dll 16:59:51.0386 8236 defragsvc - ok 16:59:51.0421 8236 [ 9BB2EF44EAA163B29C4A4587887A0FE4 ] DfsC C:\windows\system32\Drivers\dfsc.sys 16:59:51.0423 8236 DfsC - ok 16:59:51.0471 8236 [ 43D808F5D9E1A18E5EEB5EBC83969E4E ] Dhcp C:\windows\system32\dhcpcore.dll 16:59:51.0475 8236 Dhcp - ok 16:59:51.0498 8236 [ 13096B05847EC78F0977F2C0F79E9AB3 ] discache C:\windows\system32\drivers\discache.sys 16:59:51.0500 8236 discache - ok 16:59:51.0531 8236 [ 9819EEE8B5EA3784EC4AF3B137A5244C ] Disk C:\windows\system32\drivers\disk.sys 16:59:51.0533 8236 Disk - ok 16:59:51.0564 8236 [ E7B489FA5B15D2FEC3E52066E015B788 ] DMAgent C:\Program Files\Intel\WiMAX\Bin\DMAgent.exe 16:59:51.0570 8236 DMAgent - ok 16:59:51.0599 8236 [ 16835866AAA693C7D7FCEBA8FFF706E4 ] Dnscache C:\windows\System32\dnsrslvr.dll 16:59:51.0602 8236 Dnscache - ok 16:59:51.0622 8236 [ B1FB3DDCA0FDF408750D5843591AFBC6 ] dot3svc C:\windows\System32\dot3svc.dll 16:59:51.0626 8236 dot3svc - ok 16:59:51.0645 8236 [ B26F4F737E8F9DF4F31AF6CF31D05820 ] DPS C:\windows\system32\dps.dll 16:59:51.0649 8236 DPS - ok 16:59:51.0686 8236 [ 9B19F34400D24DF84C858A421C205754 ] drmkaud C:\windows\system32\drivers\drmkaud.sys 16:59:51.0687 8236 drmkaud - ok 16:59:51.0751 8236 [ 46571ED73AE84469DCA53081D33CF3C8 ] dtsoftbus01 C:\windows\system32\DRIVERS\dtsoftbus01.sys 16:59:51.0755 8236 dtsoftbus01 - ok 16:59:51.0794 8236 [ 85DBF6EC7BDFA6187F4A1EC8F3145CD0 ] DXGKrnl C:\windows\System32\drivers\dxgkrnl.sys 16:59:51.0805 8236 DXGKrnl - ok 16:59:51.0835 8236 [ E2DDA8726DA9CB5B2C4000C9018A9633 ] EapHost C:\windows\System32\eapsvc.dll 16:59:51.0838 8236 EapHost - ok 16:59:51.0921 8236 [ DC5D737F51BE844D8C82C695EB17372F ] ebdrv C:\windows\system32\drivers\evbda.sys 16:59:51.0999 8236 ebdrv - ok 16:59:52.0052 8236 [ C118A82CD78818C29AB228366EBF81C3 ] EFS C:\windows\System32\lsass.exe 16:59:52.0055 8236 EFS - ok 16:59:52.0102 8236 [ C4002B6B41975F057D98C439030CEA07 ] ehRecvr C:\windows\ehome\ehRecvr.exe 16:59:52.0110 8236 ehRecvr - ok 16:59:52.0139 8236 [ 4705E8EF9934482C5BB488CE28AFC681 ] ehSched C:\windows\ehome\ehsched.exe 16:59:52.0141 8236 ehSched - ok 16:59:52.0182 8236 [ 0E5DA5369A0FCAEA12456DD852545184 ] elxstor C:\windows\system32\drivers\elxstor.sys 16:59:52.0193 8236 elxstor - ok 16:59:52.0227 8236 [ 34A3C54752046E79A126E15C51DB409B ] ErrDev C:\windows\system32\drivers\errdev.sys 16:59:52.0229 8236 ErrDev - ok 16:59:52.0283 8236 [ 4166F82BE4D24938977DD1746BE9B8A0 ] EventSystem C:\windows\system32\es.dll 16:59:52.0289 8236 EventSystem - ok 16:59:52.0389 8236 [ 57E61DC4F7980D57C0B162FC5B9F0B38 ] EvtEng C:\Program Files\Intel\WiFi\bin\EvtEng.exe 16:59:52.0406 8236 EvtEng - ok 16:59:52.0431 8236 [ A510C654EC00C1E9BDD91EEB3A59823B ] exfat C:\windows\system32\drivers\exfat.sys 16:59:52.0435 8236 exfat - ok 16:59:52.0464 8236 [ 0ADC83218B66A6DB380C330836F3E36D ] fastfat C:\windows\system32\drivers\fastfat.sys 16:59:52.0468 8236 fastfat - ok 16:59:52.0583 8236 [ DBEFD454F8318A0EF691FDD2EAAB44EB ] Fax C:\windows\system32\fxssvc.exe 16:59:52.0592 8236 Fax - ok 16:59:52.0647 8236 [ D765D19CD8EF61F650C384F62FAC00AB ] fdc C:\windows\system32\drivers\fdc.sys 16:59:52.0649 8236 fdc - ok 16:59:52.0725 8236 [ 0438CAB2E03F4FB61455A7956026FE86 ] fdPHost C:\windows\system32\fdPHost.dll 16:59:52.0728 8236 fdPHost - ok 16:59:52.0802 8236 [ 802496CB59A30349F9A6DD22D6947644 ] FDResPub C:\windows\system32\fdrespub.dll 16:59:52.0804 8236 FDResPub - ok 16:59:52.0852 8236 [ 655661BE46B5F5F3FD454E2C3095B930 ] FileInfo C:\windows\system32\drivers\fileinfo.sys 16:59:52.0854 8236 FileInfo - ok 16:59:52.0876 8236 [ 5F671AB5BC87EEA04EC38A6CD5962A47 ] Filetrace C:\windows\system32\drivers\filetrace.sys 16:59:52.0878 8236 Filetrace - ok 16:59:53.0025 8236 [ A3A5DCF65B4AC8D98C7E2DD9B58B37A3 ] Flexlm Service 1 C:\Program Files (x86)\UGS\NX 7.5\UGFLEXLM\lmgrd.exe 16:59:53.0042 8236 Flexlm Service 1 - ok 16:59:53.0055 8236 [ C172A0F53008EAEB8EA33FE10E177AF5 ] flpydisk C:\windows\system32\drivers\flpydisk.sys 16:59:53.0057 8236 flpydisk - ok 16:59:53.0100 8236 [ DA6B67270FD9DB3697B20FCE94950741 ] FltMgr C:\windows\system32\drivers\fltmgr.sys 16:59:53.0104 8236 FltMgr - ok 16:59:53.0149 8236 [ 5C4CB4086FB83115B153E47ADD961A0C ] FontCache C:\windows\system32\FntCache.dll 16:59:53.0164 8236 FontCache - ok 16:59:53.0205 8236 [ A8B7F3818AB65695E3A0BB3279F6DCE6 ] FontCache3.0.0.0 C:\windows\Microsoft.Net\Framework64\v3.0\WPF\PresentationFontCache.exe 16:59:53.0207 8236 FontCache3.0.0.0 - ok 16:59:53.0221 8236 [ D43703496149971890703B4B1B723EAC ] FsDepends C:\windows\system32\drivers\FsDepends.sys 16:59:53.0223 8236 FsDepends - ok 16:59:53.0268 8236 [ 6BD9295CC032DD3077C671FCCF579A7B ] Fs_Rec C:\windows\system32\drivers\Fs_Rec.sys 16:59:53.0269 8236 Fs_Rec - ok 16:59:53.0303 8236 [ 1F7B25B858FA27015169FE95E54108ED ] fvevol C:\windows\system32\DRIVERS\fvevol.sys 16:59:53.0307 8236 fvevol - ok 16:59:53.0327 8236 [ 8C778D335C9D272CFD3298AB02ABE3B6 ] gagp30kx C:\windows\system32\drivers\gagp30kx.sys 16:59:53.0329 8236 gagp30kx - ok 16:59:53.0367 8236 [ 277BBC7E1AA1EE957F573A10ECA7EF3A ] gpsvc C:\windows\System32\gpsvc.dll 16:59:53.0378 8236 gpsvc - ok 16:59:53.0436 8236 [ F02A533F517EB38333CB12A9E8963773 ] gupdate C:\Program Files (x86)\Google\Update\GoogleUpdate.exe 16:59:53.0438 8236 gupdate - ok 16:59:53.0457 8236 [ F02A533F517EB38333CB12A9E8963773 ] gupdatem C:\Program Files (x86)\Google\Update\GoogleUpdate.exe 16:59:53.0459 8236 gupdatem - ok 16:59:53.0486 8236 [ 5D4BC124FAAE6730AC002CDB67BF1A1C ] gusvc C:\Program Files (x86)\Google\Common\Google Updater\GoogleUpdaterService.exe 16:59:53.0490 8236 gusvc - ok 16:59:53.0513 8236 [ F2523EF6460FC42405B12248338AB2F0 ] hcw85cir C:\windows\system32\drivers\hcw85cir.sys 16:59:53.0514 8236 hcw85cir - ok 16:59:53.0555 8236 [ 975761C778E33CD22498059B91E7373A ] HdAudAddService C:\windows\system32\drivers\HdAudio.sys 16:59:53.0560 8236 HdAudAddService - ok 16:59:53.0588 8236 [ 97BFED39B6B79EB12CDDBFEED51F56BB ] HDAudBus C:\windows\system32\drivers\HDAudBus.sys 16:59:53.0591 8236 HDAudBus - ok 16:59:53.0617 8236 [ 78E86380454A7B10A5EB255DC44A355F ] HidBatt C:\windows\system32\drivers\HidBatt.sys 16:59:53.0619 8236 HidBatt - ok 16:59:53.0631 8236 [ 7FD2A313F7AFE5C4DAB14798C48DD104 ] HidBth C:\windows\system32\drivers\hidbth.sys 16:59:53.0633 8236 HidBth - ok 16:59:53.0659 8236 [ 0A77D29F311B88CFAE3B13F9C1A73825 ] HidIr C:\windows\system32\drivers\hidir.sys 16:59:53.0661 8236 HidIr - ok 16:59:53.0683 8236 [ BD9EB3958F213F96B97B1D897DEE006D ] hidserv C:\windows\system32\hidserv.dll 16:59:53.0685 8236 hidserv - ok 16:59:53.0720 8236 [ 9592090A7E2B61CD582B612B6DF70536 ] HidUsb C:\windows\system32\DRIVERS\hidusb.sys 16:59:53.0722 8236 HidUsb - ok 16:59:53.0748 8236 [ 387E72E739E15E3D37907A86D9FF98E2 ] hkmsvc C:\windows\system32\kmsvc.dll 16:59:53.0751 8236 hkmsvc - ok 16:59:53.0768 8236 [ EFDFB3DD38A4376F93E7985173813ABD ] HomeGroupListener C:\windows\system32\ListSvc.dll 16:59:53.0773 8236 HomeGroupListener - ok 16:59:53.0804 8236 [ 908ACB1F594274965A53926B10C81E89 ] HomeGroupProvider C:\windows\system32\provsvc.dll 16:59:53.0810 8236 HomeGroupProvider - ok 16:59:53.0839 8236 [ 39D2ABCD392F3D8A6DCE7B60AE7B8EFC ] HpSAMD C:\windows\system32\drivers\HpSAMD.sys 16:59:53.0842 8236 HpSAMD - ok 16:59:53.0869 8236 [ 0EA7DE1ACB728DD5A369FD742D6EEE28 ] HTTP C:\windows\system32\drivers\HTTP.sys 16:59:53.0878 8236 HTTP - ok 16:59:53.0885 8236 [ A5462BD6884960C9DC85ED49D34FF392 ] hwpolicy C:\windows\system32\drivers\hwpolicy.sys 16:59:53.0886 8236 hwpolicy - ok 16:59:53.0918 8236 [ FA55C73D4AFFA7EE23AC4BE53B4592D3 ] i8042prt C:\windows\system32\drivers\i8042prt.sys 16:59:53.0920 8236 i8042prt - ok 16:59:53.0951 8236 [ D469B77687E12FE43E344806740B624D ] iaStor C:\windows\system32\DRIVERS\iaStor.sys 16:59:53.0954 8236 iaStor - ok 16:59:53.0992 8236 [ AAAF44DB3BD0B9D1FB6969B23ECC8366 ] iaStorV C:\windows\system32\drivers\iaStorV.sys 16:59:53.0998 8236 iaStorV - ok 16:59:54.0043 8236 [ 5988FC40F8DB5B0739CD1E3A5D0D78BD ] idsvc C:\windows\Microsoft.NET\Framework64\v3.0\Windows Communication Foundation\infocard.exe 16:59:54.0049 8236 idsvc - ok 16:59:54.0510 8236 [ 93C8115D4BAEB1BD047AB0A9B265EE7A ] igfx C:\windows\system32\DRIVERS\igdkmd64.sys 16:59:54.0749 8236 igfx - ok 16:59:54.0783 8236 [ 5C18831C61933628F5BB0EA2675B9D21 ] iirsp C:\windows\system32\drivers\iirsp.sys 16:59:54.0785 8236 iirsp - ok 16:59:54.0826 8236 [ FCD84C381E0140AF901E58D48882D26B ] IKEEXT C:\windows\System32\ikeext.dll 16:59:54.0836 8236 IKEEXT - ok 16:59:54.0895 8236 [ CADDF0927DAC63EDAE48F5C35A61D87D ] intaud_WaveExtensible C:\windows\system32\drivers\intelaud.sys 16:59:54.0896 8236 intaud_WaveExtensible - ok 16:59:54.0969 8236 [ 4B2151F04BB466EC1924AA27315E1118 ] IntcAzAudAddService C:\windows\system32\drivers\RTKVHD64.sys 16:59:55.0059 8236 IntcAzAudAddService - ok 16:59:55.0087 8236 [ FC727061C0F47C8059E88E05D5C8E381 ] IntcDAud C:\windows\system32\DRIVERS\IntcDAud.sys 16:59:55.0092 8236 IntcDAud - ok 16:59:55.0113 8236 [ F00F20E70C6EC3AA366910083A0518AA ] intelide C:\windows\system32\drivers\intelide.sys 16:59:55.0114 8236 intelide - ok 16:59:55.0139 8236 [ ADA036632C664CAA754079041CF1F8C1 ] intelppm C:\windows\system32\DRIVERS\intelppm.sys 16:59:55.0141 8236 intelppm - ok 16:59:55.0165 8236 [ 098A91C54546A3B878DAD6A7E90A455B ] IPBusEnum C:\windows\system32\ipbusenum.dll 16:59:55.0168 8236 IPBusEnum - ok 16:59:55.0199 8236 [ C9F0E1BD74365A8771590E9008D22AB6 ] IpFilterDriver C:\windows\system32\DRIVERS\ipfltdrv.sys 16:59:55.0201 8236 IpFilterDriver - ok 16:59:55.0266 8236 [ 08C2957BB30058E663720C5606885653 ] iphlpsvc C:\windows\System32\iphlpsvc.dll 16:59:55.0275 8236 iphlpsvc - ok 16:59:55.0349 8236 [ 0FC1AEA580957AA8817B8F305D18CA3A ] IPMIDRV C:\windows\system32\drivers\IPMIDrv.sys 16:59:55.0370 8236 IPMIDRV - ok 16:59:55.0398 8236 [ AF9B39A7E7B6CAA203B3862582E9F2D0 ] IPNAT C:\windows\system32\drivers\ipnat.sys 16:59:55.0400 8236 IPNAT - ok 16:59:55.0426 8236 [ 3ABF5E7213EB28966D55D58B515D5CE9 ] IRENUM C:\windows\system32\drivers\irenum.sys 16:59:55.0428 8236 IRENUM - ok 16:59:55.0440 8236 [ 2F7B28DC3E1183E5EB418DF55C204F38 ] isapnp C:\windows\system32\drivers\isapnp.sys 16:59:55.0442 8236 isapnp - ok 16:59:55.0455 8236 [ D931D7309DEB2317035B07C9F9E6B0BD ] iScsiPrt C:\windows\system32\drivers\msiscsi.sys 16:59:55.0460 8236 iScsiPrt - ok 16:59:55.0497 8236 [ F415A88162D23977B5EDAE4F0410E903 ] IviRegMgr C:\Program Files (x86)\Common Files\InterVideo\RegMgr\iviRegMgr.exe 16:59:55.0499 8236 IviRegMgr - ok 16:59:55.0543 8236 [ 716F66336F10885D935B08174DC54242 ] iwdbus C:\windows\system32\DRIVERS\iwdbus.sys 16:59:55.0545 8236 iwdbus - ok 16:59:55.0587 8236 [ 25D602AE635A0443458FBED1A8B6E4E9 ] JMCR C:\windows\system32\DRIVERS\jmcr.sys 16:59:55.0592 8236 JMCR - ok 16:59:55.0611 8236 [ BC02336F1CBA7DCC7D1213BB588A68A5 ] kbdclass C:\windows\system32\DRIVERS\kbdclass.sys 16:59:55.0613 8236 kbdclass - ok 16:59:55.0636 8236 [ 0705EFF5B42A9DB58548EEC3B26BB484 ] kbdhid C:\windows\system32\DRIVERS\kbdhid.sys 16:59:55.0638 8236 kbdhid - ok 16:59:55.0653 8236 [ C118A82CD78818C29AB228366EBF81C3 ] KeyIso C:\windows\system32\lsass.exe 16:59:55.0655 8236 KeyIso - ok 16:59:55.0705 8236 [ 97A7070AEA4C058B6418519E869A63B4 ] KSecDD C:\windows\system32\Drivers\ksecdd.sys 16:59:55.0708 8236 KSecDD - ok 16:59:55.0723 8236 [ 26C43A7C2862447EC59DEDA188D1DA07 ] KSecPkg C:\windows\system32\Drivers\ksecpkg.sys 16:59:55.0726 8236 KSecPkg - ok 16:59:55.0765 8236 [ 6869281E78CB31A43E969F06B57347C4 ] ksthunk C:\windows\system32\drivers\ksthunk.sys 16:59:55.0767 8236 ksthunk - ok 16:59:55.0790 8236 [ 6AB66E16AA859232F64DEB66887A8C9C ] KtmRm C:\windows\system32\msdtckrm.dll 16:59:55.0797 8236 KtmRm - ok 16:59:55.0826 8236 [ D9F42719019740BAA6D1C6D536CBDAA6 ] LanmanServer C:\windows\system32\srvsvc.dll 16:59:55.0832 8236 LanmanServer - ok 16:59:55.0879 8236 [ 851A1382EED3E3A7476DB004F4EE3E1A ] LanmanWorkstation C:\windows\System32\wkssvc.dll 16:59:55.0896 8236 LanmanWorkstation - ok 16:59:55.0994 8236 [ 88E52495B47C67126B510AF53FDB0BC7 ] LBTServ C:\Program Files\Common Files\Logishrd\Bluetooth\LBTServ.exe 16:59:55.0997 8236 LBTServ - ok 16:59:56.0061 8236 [ B6552D382FF070B4ED34CBD6737277C0 ] LHidFilt C:\windows\system32\DRIVERS\LHidFilt.Sys 16:59:56.0064 8236 LHidFilt - ok 16:59:56.0094 8236 [ 1538831CF8AD2979A04C423779465827 ] lltdio C:\windows\system32\DRIVERS\lltdio.sys 16:59:56.0096 8236 lltdio - ok 16:59:56.0126 8236 [ C1185803384AB3FEED115F79F109427F ] lltdsvc C:\windows\System32\lltdsvc.dll 16:59:56.0132 8236 lltdsvc - ok 16:59:56.0150 8236 [ F993A32249B66C9D622EA5592A8B76B8 ] lmhosts C:\windows\System32\lmhsvc.dll 16:59:56.0153 8236 lmhosts - ok 16:59:56.0220 8236 [ 73C1F563AB73D459DFFE682D66476558 ] LMouFilt C:\windows\system32\DRIVERS\LMouFilt.Sys 16:59:56.0272 8236 LMouFilt - ok 16:59:56.0385 8236 [ 50C7CE53EF461870410355F1F2E7D515 ] LMS C:\Program Files (x86)\Intel\Intel® Management Engine Components\LMS\LMS.exe 16:59:56.0390 8236 LMS - ok 16:59:56.0409 8236 [ 2825A71E7501CB33B3B9F856610C729D ] LPCFilter C:\windows\system32\DRIVERS\LPCFilter.sys 16:59:56.0411 8236 LPCFilter - ok 16:59:56.0442 8236 [ 1A93E54EB0ECE102495A51266DCDB6A6 ] LSI_FC C:\windows\system32\drivers\lsi_fc.sys 16:59:56.0444 8236 LSI_FC - ok 16:59:56.0457 8236 [ 1047184A9FDC8BDBFF857175875EE810 ] LSI_SAS C:\windows\system32\drivers\lsi_sas.sys 16:59:56.0459 8236 LSI_SAS - ok 16:59:56.0478 8236 [ 30F5C0DE1EE8B5BC9306C1F0E4A75F93 ] LSI_SAS2 C:\windows\system32\drivers\lsi_sas2.sys 16:59:56.0480 8236 LSI_SAS2 - ok 16:59:56.0514 8236 [ 0504EACAFF0D3C8AED161C4B0D369D4A ] LSI_SCSI C:\windows\system32\drivers\lsi_scsi.sys 16:59:56.0517 8236 LSI_SCSI - ok 16:59:56.0545 8236 [ 43D0F98E1D56CCDDB0D5254CFF7B356E ] luafv C:\windows\system32\drivers\luafv.sys 16:59:56.0547 8236 luafv - ok 16:59:56.0603 8236 [ 92EB844D90615CB266F84C3202B8786E ] MBAMProtector C:\windows\system32\drivers\mbam.sys 16:59:56.0605 8236 MBAMProtector - ok 16:59:56.0657 8236 [ 1ACAA67676E9E7BDA5E0C41B6E0DECAF ] MBAMScheduler C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamscheduler.exe 16:59:56.0662 8236 MBAMScheduler - ok 16:59:56.0696 8236 [ 916B8954AC3E06DC9E898AFFB41F3FB6 ] MBAMService C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamservice.exe 16:59:56.0704 8236 MBAMService - ok 16:59:56.0731 8236 [ 0BE09CD858ABF9DF6ED259D57A1A1663 ] Mcx2Svc C:\windows\system32\Mcx2Svc.dll 16:59:56.0734 8236 Mcx2Svc - ok 16:59:56.0768 8236 [ A55805F747C6EDB6A9080D7C633BD0F4 ] megasas C:\windows\system32\drivers\megasas.sys 16:59:56.0769 8236 megasas - ok 16:59:56.0787 8236 [ BAF74CE0072480C3B6B7C13B2A94D6B3 ] MegaSR C:\windows\system32\drivers\MegaSR.sys 16:59:56.0793 8236 MegaSR - ok 16:59:56.0819 8236 [ A6518DCC42F7A6E999BB3BEA8FD87567 ] MEIx64 C:\windows\system32\DRIVERS\HECIx64.sys 16:59:56.0821 8236 MEIx64 - ok 16:59:56.0851 8236 [ E40E80D0304A73E8D269F7141D77250B ] MMCSS C:\windows\system32\mmcss.dll 16:59:56.0855 8236 MMCSS - ok 16:59:56.0871 8236 [ 800BA92F7010378B09F9ED9270F07137 ] Modem C:\windows\system32\drivers\modem.sys 16:59:56.0873 8236 Modem - ok 16:59:56.0902 8236 [ B03D591DC7DA45ECE20B3B467E6AADAA ] monitor C:\windows\system32\DRIVERS\monitor.sys 16:59:56.0904 8236 monitor - ok 16:59:56.0941 8236 [ 7D27EA49F3C1F687D357E77A470AEA99 ] mouclass C:\windows\system32\DRIVERS\mouclass.sys 16:59:56.0943 8236 mouclass - ok 16:59:56.0962 8236 [ D3BF052C40B0C4166D9FD86A4288C1E6 ] mouhid C:\windows\system32\DRIVERS\mouhid.sys 16:59:56.0964 8236 mouhid - ok 16:59:56.0983 8236 [ 32E7A3D591D671A6DF2DB515A5CBE0FA ] mountmgr C:\windows\system32\drivers\mountmgr.sys 16:59:56.0985 8236 mountmgr - ok 16:59:57.0074 8236 [ 8C7336950F1E69CDFD811CBBD9CF00A2 ] MozillaMaintenance C:\Program Files (x86)\Mozilla Maintenance Service\maintenanceservice.exe 16:59:57.0077 8236 MozillaMaintenance - ok 16:59:57.0095 8236 [ A44B420D30BD56E145D6A2BC8768EC58 ] mpio C:\windows\system32\drivers\mpio.sys 16:59:57.0097 8236 mpio - ok 16:59:57.0114 8236 [ 6C38C9E45AE0EA2FA5E551F2ED5E978F ] mpsdrv C:\windows\system32\drivers\mpsdrv.sys 16:59:57.0116 8236 mpsdrv - ok 16:59:57.0151 8236 [ 54FFC9C8898113ACE189D4AA7199D2C1 ] MpsSvc C:\windows\system32\mpssvc.dll 16:59:57.0163 8236 MpsSvc - ok 16:59:57.0182 8236 [ DC722758B8261E1ABAFD31A3C0A66380 ] MRxDAV C:\windows\system32\drivers\mrxdav.sys 16:59:57.0184 8236 MRxDAV - ok 16:59:57.0199 8236 [ A5D9106A73DC88564C825D317CAC68AC ] mrxsmb C:\windows\system32\DRIVERS\mrxsmb.sys 16:59:57.0202 8236 mrxsmb - ok 16:59:57.0218 8236 [ D711B3C1D5F42C0C2415687BE09FC163 ] mrxsmb10 C:\windows\system32\DRIVERS\mrxsmb10.sys 16:59:57.0223 8236 mrxsmb10 - ok 16:59:57.0251 8236 [ 9423E9D355C8D303E76B8CFBD8A5C30C ] mrxsmb20 C:\windows\system32\DRIVERS\mrxsmb20.sys 16:59:57.0253 8236 mrxsmb20 - ok 16:59:57.0265 8236 [ C25F0BAFA182CBCA2DD3C851C2E75796 ] msahci C:\windows\system32\DRIVERS\msahci.sys 16:59:57.0266 8236 msahci - ok 16:59:57.0283 8236 [ DB801A638D011B9633829EB6F663C900 ] msdsm C:\windows\system32\drivers\msdsm.sys 16:59:57.0285 8236 msdsm - ok 16:59:57.0313 8236 [ DE0ECE52236CFA3ED2DBFC03F28253A8 ] MSDTC C:\windows\System32\msdtc.exe 16:59:57.0317 8236 MSDTC - ok 16:59:57.0349 8236 [ AA3FB40E17CE1388FA1BEDAB50EA8F96 ] Msfs C:\windows\system32\drivers\Msfs.sys 16:59:57.0350 8236 Msfs - ok 16:59:57.0379 8236 [ F9D215A46A8B9753F61767FA72A20326 ] mshidkmdf C:\windows\System32\drivers\mshidkmdf.sys 16:59:57.0380 8236 mshidkmdf - ok 16:59:57.0388 8236 [ D916874BBD4F8B07BFB7FA9B3CCAE29D ] msisadrv C:\windows\system32\drivers\msisadrv.sys 16:59:57.0389 8236 msisadrv - ok 16:59:57.0415 8236 [ 808E98FF49B155C522E6400953177B08 ] MSiSCSI C:\windows\system32\iscsiexe.dll 16:59:57.0419 8236 MSiSCSI - ok 16:59:57.0424 8236 msiserver - ok 16:59:57.0446 8236 [ 49CCF2C4FEA34FFAD8B1B59D49439366 ] MSKSSRV C:\windows\system32\drivers\MSKSSRV.sys 16:59:57.0448 8236 MSKSSRV - ok 16:59:57.0479 8236 [ BDD71ACE35A232104DDD349EE70E1AB3 ] MSPCLOCK C:\windows\system32\drivers\MSPCLOCK.sys 16:59:57.0481 8236 MSPCLOCK - ok 16:59:57.0502 8236 [ 4ED981241DB27C3383D72092B618A1D0 ] MSPQM C:\windows\system32\drivers\MSPQM.sys 16:59:57.0504 8236 MSPQM - ok 16:59:57.0518 8236 [ 759A9EEB0FA9ED79DA1FB7D4EF78866D ] MsRPC C:\windows\system32\drivers\MsRPC.sys 16:59:57.0524 8236 MsRPC - ok 16:59:57.0532 8236 [ 0EED230E37515A0EAEE3C2E1BC97B288 ] mssmbios C:\windows\system32\drivers\mssmbios.sys 16:59:57.0534 8236 mssmbios - ok 16:59:57.0561 8236 [ 2E66F9ECB30B4221A318C92AC2250779 ] MSTEE C:\windows\system32\drivers\MSTEE.sys 16:59:57.0563 8236 MSTEE - ok 16:59:57.0577 8236 [ 7EA404308934E675BFFDE8EDF0757BCD ] MTConfig C:\windows\system32\drivers\MTConfig.sys 16:59:57.0579 8236 MTConfig - ok 16:59:57.0591 8236 [ F9A18612FD3526FE473C1BDA678D61C8 ] Mup C:\windows\system32\Drivers\mup.sys 16:59:57.0593 8236 Mup - ok 16:59:57.0627 8236 [ 50B99D53BC013458381C6476D790C9F3 ] MyWiFiDHCPDNS C:\Program Files\Intel\WiFi\bin\PanDhcpDns.exe 16:59:57.0632 8236 MyWiFiDHCPDNS - ok 16:59:57.0659 8236 [ 582AC6D9873E31DFA28A4547270862DD ] napagent C:\windows\system32\qagentRT.dll 16:59:57.0666 8236 napagent - ok 16:59:57.0711 8236 [ 1EA3749C4114DB3E3161156FFFFA6B33 ] NativeWifiP C:\windows\system32\DRIVERS\nwifi.sys 16:59:57.0715 8236 NativeWifiP - ok 16:59:57.0776 8236 [ 760E38053BF56E501D562B70AD796B88 ] NDIS C:\windows\system32\drivers\ndis.sys 16:59:57.0787 8236 NDIS - ok 16:59:57.0820 8236 [ 9F9A1F53AAD7DA4D6FEF5BB73AB811AC ] NdisCap C:\windows\system32\DRIVERS\ndiscap.sys 16:59:57.0822 8236 NdisCap - ok 16:59:57.0840 8236 [ 30639C932D9FEF22B31268FE25A1B6E5 ] NdisTapi C:\windows\system32\DRIVERS\ndistapi.sys 16:59:57.0842 8236 NdisTapi - ok 16:59:57.0862 8236 [ 136185F9FB2CC61E573E676AA5402356 ] Ndisuio C:\windows\system32\DRIVERS\ndisuio.sys 16:59:57.0864 8236 Ndisuio - ok 16:59:57.0889 8236 [ 53F7305169863F0A2BDDC49E116C2E11 ] NdisWan C:\windows\system32\DRIVERS\ndiswan.sys 16:59:57.0892 8236 NdisWan - ok 16:59:57.0914 8236 [ 015C0D8E0E0421B4CFD48CFFE2825879 ] NDProxy C:\windows\system32\drivers\NDProxy.sys 16:59:57.0916 8236 NDProxy - ok 16:59:57.0943 8236 [ 86743D9F5D2B1048062B14B1D84501C4 ] NetBIOS C:\windows\system32\DRIVERS\netbios.sys 16:59:57.0945 8236 NetBIOS - ok 16:59:57.0963 8236 [ 09594D1089C523423B32A4229263F068 ] NetBT C:\windows\system32\DRIVERS\netbt.sys 16:59:57.0967 8236 NetBT - ok 16:59:57.0975 8236 [ C118A82CD78818C29AB228366EBF81C3 ] Netlogon C:\windows\system32\lsass.exe 16:59:57.0977 8236 Netlogon - ok 16:59:58.0015 8236 [ 847D3AE376C0817161A14A82C8922A9E ] Netman C:\windows\System32\netman.dll 16:59:58.0023 8236 Netman - ok 16:59:58.0042 8236 [ 5F28111C648F1E24F7DBC87CDEB091B8 ] netprofm C:\windows\System32\netprofm.dll 16:59:58.0049 8236 netprofm - ok 16:59:58.0080 8236 [ 3E5A36127E201DDF663176B66828FAFE ] NetTcpPortSharing C:\windows\Microsoft.NET\Framework64\v3.0\Windows Communication Foundation\SMSvcHost.exe 16:59:58.0081 8236 NetTcpPortSharing - ok 16:59:58.0435 8236 [ AC69618DE5BCCE8747C9AB0AAE1003C1 ] NETwNs64 C:\windows\system32\DRIVERS\NETwNs64.sys 16:59:58.0695 8236 NETwNs64 - ok 16:59:58.0721 8236 [ 77889813BE4D166CDAB78DDBA990DA92 ] nfrd960 C:\windows\system32\drivers\nfrd960.sys 16:59:58.0723 8236 nfrd960 - ok 16:59:58.0773 8236 [ 8AD77806D336673F270DB31645267293 ] NlaSvc C:\windows\System32\nlasvc.dll 16:59:58.0779 8236 NlaSvc - ok 16:59:58.0792 8236 [ 1E4C4AB5C9B8DD13179BBDC75A2A01F7 ] Npfs C:\windows\system32\drivers\Npfs.sys 16:59:58.0794 8236 Npfs - ok 16:59:58.0821 8236 [ D54BFDF3E0C953F823B3D0BFE4732528 ] nsi C:\windows\system32\nsisvc.dll 16:59:58.0824 8236 nsi - ok 16:59:58.0839 8236 [ E7F5AE18AF4168178A642A9247C63001 ] nsiproxy C:\windows\system32\drivers\nsiproxy.sys 16:59:58.0841 8236 nsiproxy - ok 16:59:58.0908 8236 [ E453ACF4E7D44E5530B5D5F2B9CA8563 ] Ntfs C:\windows\system32\drivers\Ntfs.sys 16:59:58.0927 8236 Ntfs - ok 16:59:58.0953 8236 [ 9899284589F75FA8724FF3D16AED75C1 ] Null C:\windows\system32\drivers\Null.sys 16:59:58.0955 8236 Null - ok 16:59:58.0992 8236 [ 0EBC9D13CD96C15B1B18D8678A609E4B ] nusb3hub C:\windows\system32\DRIVERS\nusb3hub.sys 16:59:58.0994 8236 nusb3hub - ok 16:59:59.0012 8236 [ 7BDEC000D56D485021D9C1E63C2F81CA ] nusb3xhc C:\windows\system32\DRIVERS\nusb3xhc.sys 16:59:59.0016 8236 nusb3xhc - ok 16:59:59.0056 8236 [ 0A92CB65770442ED0DC44834632F66AD ] nvraid C:\windows\system32\drivers\nvraid.sys 16:59:59.0059 8236 nvraid - ok 16:59:59.0077 8236 [ DAB0E87525C10052BF65F06152F37E4A ] nvstor C:\windows\system32\drivers\nvstor.sys 16:59:59.0080 8236 nvstor - ok 16:59:59.0109 8236 [ 270D7CD42D6E3979F6DD0146650F0E05 ] nv_agp C:\windows\system32\drivers\nv_agp.sys 16:59:59.0111 8236 nv_agp - ok 16:59:59.0209 8236 [ 785F487A64950F3CB8E9F16253BA3B7B ] odserv C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\ODSERV.EXE 16:59:59.0215 8236 odserv - ok 16:59:59.0242 8236 [ 3589478E4B22CE21B41FA1BFC0B8B8A0 ] ohci1394 C:\windows\system32\drivers\ohci1394.sys 16:59:59.0244 8236 ohci1394 - ok 16:59:59.0272 8236 [ 9D10F99A6712E28F8ACD5641E3A7EA6B ] ose C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE 16:59:59.0275 8236 ose - ok 16:59:59.0423 8236 [ 61BFFB5F57AD12F83AB64B7181829B34 ] osppsvc C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPSVC.EXE 16:59:59.0525 8236 osppsvc - ok 16:59:59.0557 8236 [ 3EAC4455472CC2C97107B5291E0DCAFE ] p2pimsvc C:\windows\system32\pnrpsvc.dll 16:59:59.0563 8236 p2pimsvc - ok 16:59:59.0584 8236 [ 927463ECB02179F88E4B9A17568C63C3 ] p2psvc C:\windows\system32\p2psvc.dll 16:59:59.0591 8236 p2psvc - ok 16:59:59.0626 8236 papycpu2 - ok 16:59:59.0630 8236 papyjoy - ok 16:59:59.0650 8236 [ 0086431C29C35BE1DBC43F52CC273887 ] Parport C:\windows\system32\drivers\parport.sys 16:59:59.0652 8236 Parport - ok 16:59:59.0689 8236 [ E9766131EEADE40A27DC27D2D68FBA9C ] partmgr C:\windows\system32\drivers\partmgr.sys 16:59:59.0691 8236 partmgr - ok 16:59:59.0733 8236 [ 3AEAA8B561E63452C655DC0584922257 ] PcaSvc C:\windows\System32\pcasvc.dll 16:59:59.0738 8236 PcaSvc - ok 16:59:59.0750 8236 [ 94575C0571D1462A0F70BDE6BD6EE6B3 ] pci C:\windows\system32\drivers\pci.sys 16:59:59.0753 8236 pci - ok 16:59:59.0761 8236 [ B5B8B5EF2E5CB34DF8DCF8831E3534FA ] pciide C:\windows\system32\DRIVERS\pciide.sys 16:59:59.0763 8236 pciide - ok 16:59:59.0787 8236 [ B2E81D4E87CE48589F98CB8C05B01F2F ] pcmcia C:\windows\system32\drivers\pcmcia.sys 16:59:59.0791 8236 pcmcia - ok 16:59:59.0806 8236 [ D6B9C2E1A11A3A4B26A182FFEF18F603 ] pcw C:\windows\system32\drivers\pcw.sys 16:59:59.0807 8236 pcw - ok 16:59:59.0826 8236 [ 68769C3356B3BE5D1C732C97B9A80D6E ] PEAUTH C:\windows\system32\drivers\peauth.sys 16:59:59.0834 8236 PEAUTH - ok 16:59:59.0897 8236 [ E495E408C93141E8FC72DC0C6046DDFA ] PerfHost C:\windows\SysWow64\perfhost.exe 16:59:59.0900 8236 PerfHost - ok 16:59:59.0970 8236 [ 91111CEBBDE8015E822C46120ED9537C ] PGEffect C:\windows\system32\DRIVERS\pgeffect.sys 16:59:59.0972 8236 PGEffect - ok 17:00:00.0100 8236 [ 0015113A604B94769AB5159E8DCFC6E6 ] PinnacleUpdateSvc C:\Program Files (x86)\PowerUp Software\Pinnacle Game Profiler\pinnacle_updater.exe 17:00:00.0117 8236 PinnacleUpdateSvc - ok 17:00:00.0160 8236 [ C7CF6A6E137463219E1259E3F0F0DD6C ] pla C:\windows\system32\pla.dll 17:00:00.0227 8236 pla - ok 17:00:00.0382 8236 [ 25FBDEF06C4D92815B353F6E792C8129 ] PlugPlay C:\windows\system32\umpnpmgr.dll 17:00:00.0391 8236 PlugPlay - ok 17:00:00.0419 8236 [ 7195581CEC9BB7D12ABE54036ACC2E38 ] PNRPAutoReg C:\windows\system32\pnrpauto.dll 17:00:00.0422 8236 PNRPAutoReg - ok 17:00:00.0445 8236 [ 3EAC4455472CC2C97107B5291E0DCAFE ] PNRPsvc C:\windows\system32\pnrpsvc.dll 17:00:00.0450 8236 PNRPsvc - ok 17:00:00.0478 8236 [ 4F15D75ADF6156BF56ECED6D4A55C389 ] PolicyAgent C:\windows\System32\ipsecsvc.dll 17:00:00.0486 8236 PolicyAgent - ok 17:00:00.0504 8236 [ 6BA9D927DDED70BD1A9CADED45F8B184 ] Power C:\windows\system32\umpo.dll 17:00:00.0509 8236 Power - ok 17:00:00.0537 8236 [ F92A2C41117A11A00BE01CA01A7FCDE9 ] PptpMiniport C:\windows\system32\DRIVERS\raspptp.sys 17:00:00.0539 8236 PptpMiniport - ok 17:00:00.0551 8236 [ 0D922E23C041EFB1C3FAC2A6F943C9BF ] Processor C:\windows\system32\drivers\processr.sys 17:00:00.0553 8236 Processor - ok 17:00:00.0610 8236 [ 53E83F1F6CF9D62F32801CF66D8352A8 ] ProfSvc C:\windows\system32\profsvc.dll 17:00:00.0616 8236 ProfSvc - ok 17:00:00.0630 8236 [ C118A82CD78818C29AB228366EBF81C3 ] ProtectedStorage C:\windows\system32\lsass.exe 17:00:00.0634 8236 ProtectedStorage - ok 17:00:00.0660 8236 [ 0557CF5A2556BD58E26384169D72438D ] Psched C:\windows\system32\DRIVERS\pacer.sys 17:00:00.0663 8236 Psched - ok 17:00:00.0694 8236 [ F036CFB275D0C55F4E45FBBF5F98B3C8 ] PSI_SVC_2 C:\Program Files (x86)\Common Files\Protexis\License Service\PsiService_2.exe 17:00:00.0698 8236 PSI_SVC_2 - ok 17:00:00.0742 8236 [ A53A15A11EBFD21077463EE2C7AFEEF0 ] ql2300 C:\windows\system32\drivers\ql2300.sys 17:00:00.0759 8236 ql2300 - ok 17:00:00.0786 8236 [ 4F6D12B51DE1AAEFF7DC58C4D75423C8 ] ql40xx C:\windows\system32\drivers\ql40xx.sys 17:00:00.0789 8236 ql40xx - ok 17:00:00.0815 8236 [ 906191634E99AEA92C4816150BDA3732 ] QWAVE C:\windows\system32\qwave.dll 17:00:00.0821 8236 QWAVE - ok 17:00:00.0834 8236 [ 76707BB36430888D9CE9D705398ADB6C ] QWAVEdrv C:\windows\system32\drivers\qwavedrv.sys 17:00:00.0835 8236 QWAVEdrv - ok 17:00:00.0863 8236 [ 5A0DA8AD5762FA2D91678A8A01311704 ] RasAcd C:\windows\system32\DRIVERS\rasacd.sys 17:00:00.0865 8236 RasAcd - ok 17:00:00.0884 8236 [ 7ECFF9B22276B73F43A99A15A6094E90 ] RasAgileVpn C:\windows\system32\DRIVERS\AgileVpn.sys 17:00:00.0886 8236 RasAgileVpn - ok 17:00:00.0915 8236 [ 8F26510C5383B8DBE976DE1CD00FC8C7 ] RasAuto C:\windows\System32\rasauto.dll 17:00:00.0920 8236 RasAuto - ok 17:00:00.0938 8236 [ 471815800AE33E6F1C32FB1B97C490CA ] Rasl2tp C:\windows\system32\DRIVERS\rasl2tp.sys 17:00:00.0940 8236 Rasl2tp - ok 17:00:00.0961 8236 [ EE867A0870FC9E4972BA9EAAD35651E2 ] RasMan C:\windows\System32\rasmans.dll 17:00:00.0969 8236 RasMan - ok 17:00:00.0994 8236 [ 855C9B1CD4756C5E9A2AA58A15F58C25 ] RasPppoe C:\windows\system32\DRIVERS\raspppoe.sys 17:00:00.0996 8236 RasPppoe - ok 17:00:01.0004 8236 [ E8B1E447B008D07FF47D016C2B0EEECB ] RasSstp C:\windows\system32\DRIVERS\rassstp.sys 17:00:01.0006 8236 RasSstp - ok 17:00:01.0027 8236 [ 77F665941019A1594D887A74F301FA2F ] rdbss C:\windows\system32\DRIVERS\rdbss.sys 17:00:01.0033 8236 rdbss - ok 17:00:01.0043 8236 [ 302DA2A0539F2CF54D7C6CC30C1F2D8D ] rdpbus C:\windows\system32\drivers\rdpbus.sys 17:00:01.0045 8236 rdpbus - ok 17:00:01.0077 8236 [ CEA6CC257FC9B7715F1C2B4849286D24 ] RDPCDD C:\windows\system32\DRIVERS\RDPCDD.sys 17:00:01.0078 8236 RDPCDD - ok 17:00:01.0093 8236 [ BB5971A4F00659529A5C44831AF22365 ] RDPENCDD C:\windows\system32\drivers\rdpencdd.sys 17:00:01.0095 8236 RDPENCDD - ok 17:00:01.0124 8236 [ 216F3FA57533D98E1F74DED70113177A ] RDPREFMP C:\windows\system32\drivers\rdprefmp.sys 17:00:01.0126 8236 RDPREFMP - ok 17:00:01.0178 8236 [ E61608AA35E98999AF9AAEEEA6114B0A ] RDPWD C:\windows\system32\drivers\RDPWD.sys 17:00:01.0182 8236 RDPWD - ok 17:00:01.0219 8236 [ 34ED295FA0121C241BFEF24764FC4520 ] rdyboost C:\windows\system32\drivers\rdyboost.sys 17:00:01.0222 8236 rdyboost - ok 17:00:01.0248 8236 [ 4D9AFDDDA0EFE97CDBFD3B5FA48B05F6 ] regi C:\windows\system32\drivers\regi.sys 17:00:01.0250 8236 regi - ok 17:00:01.0308 8236 [ 18505D90FEE940EE9EAE4C5B421F22B4 ] RegSrvc C:\Program Files\Common Files\Intel\WirelessCommon\RegSrvc.exe 17:00:01.0320 8236 RegSrvc - ok 17:00:01.0351 8236 [ 254FB7A22D74E5511C73A3F6D802F192 ] RemoteAccess C:\windows\System32\mprdim.dll 17:00:01.0355 8236 RemoteAccess - ok 17:00:01.0378 8236 [ E4D94F24081440B5FC5AA556C7C62702 ] RemoteRegistry C:\windows\system32\regsvc.dll 17:00:01.0384 8236 RemoteRegistry - ok 17:00:01.0408 8236 [ E4DC58CF7B3EA515AE917FF0D402A7BB ] RpcEptMapper C:\windows\System32\RpcEpMap.dll 17:00:01.0413 8236 RpcEptMapper - ok 17:00:01.0437 8236 [ D5BA242D4CF8E384DB90E6A8ED850B8C ] RpcLocator C:\windows\system32\locator.exe 17:00:01.0440 8236 RpcLocator - ok 17:00:01.0464 8236 [ 5C627D1B1138676C0A7AB2C2C190D123 ] RpcSs C:\windows\system32\rpcss.dll 17:00:01.0469 8236 RpcSs - ok 17:00:01.0497 8236 [ DDC86E4F8E7456261E637E3552E804FF ] rspndr C:\windows\system32\DRIVERS\rspndr.sys 17:00:01.0499 8236 rspndr - ok 17:00:01.0527 8236 [ EE082E06A82FF630351D1E0EBBD3D8D0 ] RTL8167 C:\windows\system32\DRIVERS\Rt64win7.sys 17:00:01.0534 8236 RTL8167 - ok 17:00:01.0542 8236 [ C118A82CD78818C29AB228366EBF81C3 ] SamSs C:\windows\system32\lsass.exe 17:00:01.0544 8236 SamSs - ok 17:00:01.0579 8236 [ AC03AF3329579FFFB455AA2DAABBE22B ] sbp2port C:\windows\system32\drivers\sbp2port.sys 17:00:01.0582 8236 sbp2port - ok 17:00:01.0607 8236 [ 9B7395789E3791A3B6D000FE6F8B131E ] SCardSvr C:\windows\System32\SCardSvr.dll 17:00:01.0613 8236 SCardSvr - ok 17:00:01.0623 8236 [ 253F38D0D7074C02FF8DEB9836C97D2B ] scfilter C:\windows\system32\DRIVERS\scfilter.sys 17:00:01.0624 8236 scfilter - ok 17:00:01.0653 8236 [ 262F6592C3299C005FD6BEC90FC4463A ] Schedule C:\windows\system32\schedsvc.dll 17:00:01.0668 8236 Schedule - ok 17:00:01.0689 8236 [ F17D1D393BBC69C5322FBFAFACA28C7F ] SCPolicySvc C:\windows\System32\certprop.dll 17:00:01.0690 8236 SCPolicySvc - ok 17:00:01.0732 8236 [ 111E0EBC0AD79CB0FA014B907B231CF0 ] sdbus C:\windows\system32\DRIVERS\sdbus.sys 17:00:01.0734 8236 sdbus - ok 17:00:01.0757 8236 [ 6EA4234DC55346E0709560FE7C2C1972 ] SDRSVC C:\windows\System32\SDRSVC.dll 17:00:01.0763 8236 SDRSVC - ok 17:00:01.0778 8236 [ 3EA8A16169C26AFBEB544E0E48421186 ] secdrv C:\windows\system32\drivers\secdrv.sys 17:00:01.0780 8236 secdrv - ok 17:00:01.0801 8236 [ BC617A4E1B4FA8DF523A061739A0BD87 ] seclogon C:\windows\system32\seclogon.dll 17:00:01.0813 8236 seclogon - ok 17:00:01.0956 8236 [ C32AB8FA018EF34C0F113BD501436D21 ] SENS C:\windows\System32\sens.dll 17:00:01.0960 8236 SENS - ok 17:00:02.0013 8236 [ 0336CFFAFAAB87A11541F1CF1594B2B2 ] SensrSvc C:\windows\system32\sensrsvc.dll 17:00:02.0018 8236 SensrSvc - ok 17:00:02.0040 8236 [ CB624C0035412AF0DEBEC78C41F5CA1B ] Serenum C:\windows\system32\drivers\serenum.sys 17:00:02.0042 8236 Serenum - ok 17:00:02.0083 8236 [ C1D8E28B2C2ADFAEC4BA89E9FDA69BD6 ] Serial C:\windows\system32\drivers\serial.sys 17:00:02.0086 8236 Serial - ok 17:00:02.0121 8236 [ 1C545A7D0691CC4A027396535691C3E3 ] sermouse C:\windows\system32\drivers\sermouse.sys 17:00:02.0123 8236 sermouse - ok 17:00:02.0186 8236 [ 0B6231BF38174A1628C4AC812CC75804 ] SessionEnv C:\windows\system32\sessenv.dll 17:00:02.0190 8236 SessionEnv - ok 17:00:02.0211 8236 [ A554811BCD09279536440C964AE35BBF ] sffdisk C:\windows\system32\drivers\sffdisk.sys 17:00:02.0213 8236 sffdisk - ok 17:00:02.0232 8236 [ FF414F0BAEFEBA59BC6C04B3DB0B87BF ] sffp_mmc C:\windows\system32\drivers\sffp_mmc.sys 17:00:02.0234 8236 sffp_mmc - ok 17:00:02.0251 8236 [ DD85B78243A19B59F0637DCF284DA63C ] sffp_sd C:\windows\system32\drivers\sffp_sd.sys 17:00:02.0253 8236 sffp_sd - ok 17:00:02.0275 8236 [ A9D601643A1647211A1EE2EC4E433FF4 ] sfloppy C:\windows\system32\drivers\sfloppy.sys 17:00:02.0277 8236 sfloppy - ok 17:00:02.0401 8236 [ B95F6501A2F8B2E78C697FEC401970CE ] SharedAccess C:\windows\System32\ipnathlp.dll 17:00:02.0407 8236 SharedAccess - ok 17:00:02.0444 8236 [ AAF932B4011D14052955D4B212A4DA8D ] ShellHWDetection C:\windows\System32\shsvcs.dll 17:00:02.0453 8236 ShellHWDetection - ok 17:00:02.0480 8236 [ 843CAF1E5FDE1FFD5FF768F23A51E2E1 ] SiSRaid2 C:\windows\system32\drivers\SiSRaid2.sys 17:00:02.0482 8236 SiSRaid2 - ok 17:00:02.0496 8236 [ 6A6C106D42E9FFFF8B9FCB4F754F6DA4 ] SiSRaid4 C:\windows\system32\drivers\sisraid4.sys 17:00:02.0498 8236 SiSRaid4 - ok 17:00:02.0586 8236 [ A4FAB5F7818A69DA6E740943CB8F7CA9 ] SkypeUpdate C:\Program Files (x86)\Skype\Updater\Updater.exe 17:00:02.0589 8236 SkypeUpdate - ok 17:00:02.0622 8236 [ 548260A7B8654E024DC30BF8A7C5BAA4 ] Smb C:\windows\system32\DRIVERS\smb.sys 17:00:02.0624 8236 Smb - ok 17:00:02.0671 8236 [ 6313F223E817CC09AA41811DAA7F541D ] SNMPTRAP C:\windows\System32\snmptrap.exe 17:00:02.0675 8236 SNMPTRAP - ok 17:00:02.0692 8236 [ B9E31E5CACDFE584F34F730A677803F9 ] spldr C:\windows\system32\drivers\spldr.sys 17:00:02.0694 8236 spldr - ok 17:00:02.0739 8236 [ 85DAA09A98C9286D4EA2BA8D0E644377 ] Spooler C:\windows\System32\spoolsv.exe 17:00:02.0749 8236 Spooler - ok 17:00:02.0825 8236 [ E17E0188BB90FAE42D83E98707EFA59C ] sppsvc C:\windows\system32\sppsvc.exe 17:00:02.0882 8236 sppsvc - ok 17:00:02.0899 8236 [ 93D7D61317F3D4BC4F4E9F8A96A7DE45 ] sppuinotify C:\windows\system32\sppuinotify.dll 17:00:02.0903 8236 sppuinotify - ok 17:00:02.0931 8236 [ 441FBA48BFF01FDB9D5969EBC1838F0B ] srv C:\windows\system32\DRIVERS\srv.sys 17:00:02.0937 8236 srv - ok 17:00:02.0955 8236 [ B4ADEBBF5E3677CCE9651E0F01F7CC28 ] srv2 C:\windows\system32\DRIVERS\srv2.sys 17:00:02.0962 8236 srv2 - ok 17:00:02.0979 8236 [ 27E461F0BE5BFF5FC737328F749538C3 ] srvnet C:\windows\system32\DRIVERS\srvnet.sys 17:00:02.0982 8236 srvnet - ok 17:00:03.0019 8236 [ 51B52FBD583CDE8AA9BA62B8B4298F33 ] SSDPSRV C:\windows\System32\ssdpsrv.dll 17:00:03.0024 8236 SSDPSRV - ok 17:00:03.0039 8236 [ AB7AEBF58DAD8DAAB7A6C45E6A8885CB ] SstpSvc C:\windows\system32\sstpsvc.dll 17:00:03.0044 8236 SstpSvc - ok 17:00:03.0062 8236 [ F3817967ED533D08327DC73BC4D5542A ] stexstor C:\windows\system32\drivers\stexstor.sys 17:00:03.0064 8236 stexstor - ok 17:00:03.0098 8236 [ 8DD52E8E6128F4B2DA92CE27402871C1 ] stisvc C:\windows\System32\wiaservc.dll 17:00:03.0107 8236 stisvc - ok 17:00:03.0124 8236 [ D01EC09B6711A5F8E7E6564A4D0FBC90 ] swenum C:\windows\system32\drivers\swenum.sys 17:00:03.0126 8236 swenum - ok 17:00:03.0157 8236 [ E08E46FDD841B7184194011CA1955A0B ] swprv C:\windows\System32\swprv.dll 17:00:03.0167 8236 swprv - ok 17:00:03.0214 8236 [ F5B46DF59FEAA48A442AED7EEB754D4B ] SynTP C:\windows\system32\DRIVERS\SynTP.sys 17:00:03.0230 8236 SynTP - ok 17:00:03.0298 8236 [ BF9CCC0BF39B418C8D0AE8B05CF95B7D ] SysMain C:\windows\system32\sysmain.dll 17:00:03.0332 8236 SysMain - ok 17:00:03.0361 8236 [ E3C61FD7B7C2557E1F1B0B4CEC713585 ] TabletInputService C:\windows\System32\TabSvc.dll 17:00:03.0366 8236 TabletInputService - ok 17:00:03.0414 8236 [ 40F0849F65D13EE87B9A9AE3C1DD6823 ] TapiSrv C:\windows\System32\tapisrv.dll 17:00:03.0448 8236 TapiSrv - ok 17:00:03.0466 8236 [ 1BE03AC720F4D302EA01D40F588162F6 ] TBS C:\windows\System32\tbssvc.dll 17:00:03.0470 8236 TBS - ok 17:00:03.0552 8236 [ 37608401DFDB388CAF66917F6B2D6FB0 ] Tcpip C:\windows\system32\drivers\tcpip.sys 17:00:03.0574 8236 Tcpip - ok 17:00:03.0629 8236 [ 37608401DFDB388CAF66917F6B2D6FB0 ] TCPIP6 C:\windows\system32\DRIVERS\tcpip.sys 17:00:03.0640 8236 TCPIP6 - ok 17:00:03.0681 8236 [ 1B16D0BD9841794A6E0CDE0CEF744ABC ] tcpipreg C:\windows\system32\drivers\tcpipreg.sys 17:00:03.0683 8236 tcpipreg - ok 17:00:03.0712 8236 [ FD542B661BD22FA69CA789AD0AC58C29 ] tdcmdpst C:\windows\system32\DRIVERS\tdcmdpst.sys 17:00:03.0714 8236 tdcmdpst - ok 17:00:03.0746 8236 [ 3371D21011695B16333A3934340C4E7C ] TDPIPE C:\windows\system32\drivers\tdpipe.sys 17:00:03.0748 8236 TDPIPE - ok 17:00:03.0776 8236 [ 51C5ECEB1CDEE2468A1748BE550CFBC8 ] TDTCP C:\windows\system32\drivers\tdtcp.sys 17:00:03.0779 8236 TDTCP - ok 17:00:03.0807 8236 [ DDAD5A7AB24D8B65F8D724F5C20FD806 ] tdx C:\windows\system32\DRIVERS\tdx.sys 17:00:03.0810 8236 tdx - ok 17:00:03.0822 8236 [ 561E7E1F06895D78DE991E01DD0FB6E5 ] TermDD C:\windows\system32\drivers\termdd.sys 17:00:03.0824 8236 TermDD - ok 17:00:03.0862 8236 [ 2E648163254233755035B46DD7B89123 ] TermService C:\windows\System32\termsrv.dll 17:00:03.0873 8236 TermService - ok 17:00:03.0892 8236 [ F0344071948D1A1FA732231785A0664C ] Themes C:\windows\system32\themeservice.dll 17:00:03.0897 8236 Themes - ok 17:00:03.0928 8236 [ 7F35CA8296A52C7161088EB1D952E8ED ] Thpdrv C:\windows\system32\DRIVERS\thpdrv.sys 17:00:03.0932 8236 Thpdrv - ok 17:00:03.0961 8236 [ B4E609047434ED948AF7BDEF2FA66E38 ] Thpevm C:\windows\system32\DRIVERS\Thpevm.SYS 17:00:03.0963 8236 Thpevm - ok 17:00:04.0002 8236 [ 0B4734AE9EC70B843DF02E7B1C056377 ] Thpsrv C:\windows\system32\ThpSrv.exe 17:00:04.0011 8236 Thpsrv - ok 17:00:04.0018 8236 [ E40E80D0304A73E8D269F7141D77250B ] THREADORDER C:\windows\system32\mmcss.dll 17:00:04.0021 8236 THREADORDER - ok 17:00:04.0075 8236 [ 71C321649B28638EE80A2EEB164C1DC8 ] TMachInfo C:\Program Files (x86)\TOSHIBA\TOSHIBA Service Station\TMachInfo.exe 17:00:04.0077 8236 TMachInfo - ok 17:00:04.0105 8236 [ 8E2C799D3476EAC32C3BA0DF7CE6AF19 ] TODDSrv C:\windows\system32\TODDSrv.exe 17:00:04.0110 8236 TODDSrv - ok 17:00:04.0158 8236 [ 1C73689B900428C7D054A41C4687F55C ] TosCoSrv C:\Program Files\TOSHIBA\Power Saver\TosCoSrv.exe 17:00:04.0208 8236 TosCoSrv - ok 17:00:04.0403 8236 [ 63AAFCF3EA5DBB17123E0BAE9AFE4D58 ] TOSHIBA eco Utility Service C:\Program Files\TOSHIBA\TECO\TecoService.exe 17:00:04.0407 8236 TOSHIBA eco Utility Service - ok 17:00:04.0451 8236 [ 29D0886CF250FCEF1BF9E65AB8D2C0C8 ] TOSHIBA HDD SSD Alert Service C:\Program Files\TOSHIBA\TOSHIBA HDD SSD Alert\TosSmartSrv.exe 17:00:04.0454 8236 TOSHIBA HDD SSD Alert Service - ok 17:00:04.0489 8236 [ 09FF7B0B1B5C3D225495CB6F5A9B39F8 ] tos_sps64 C:\windows\system32\DRIVERS\tos_sps64.sys 17:00:04.0496 8236 tos_sps64 - ok 17:00:04.0542 8236 [ 098B8A408C17E125A3D9A8E1166780C8 ] TPCHSrv C:\Program Files\TOSHIBA\TPHM\TPCHSrv.exe 17:00:04.0552 8236 TPCHSrv - ok 17:00:04.0580 8236 [ 7E7AFD841694F6AC397E99D75CEAD49D ] TrkWks C:\windows\System32\trkwks.dll 17:00:04.0585 8236 TrkWks - ok 17:00:04.0636 8236 [ 773212B2AAA24C1E31F10246B15B276C ] TrustedInstaller C:\windows\servicing\TrustedInstaller.exe 17:00:04.0639 8236 TrustedInstaller - ok 17:00:04.0664 8236 [ CE18B2CDFC837C99E5FAE9CA6CBA5D30 ] tssecsrv C:\windows\system32\DRIVERS\tssecsrv.sys 17:00:04.0666 8236 tssecsrv - ok 17:00:04.0692 8236 [ D11C783E3EF9A3C52C0EBE83CC5000E9 ] TsUsbFlt C:\windows\system32\drivers\tsusbflt.sys 17:00:04.0694 8236 TsUsbFlt - ok 17:00:04.0710 8236 [ 9CC2CCAE8A84820EAECB886D477CBCB8 ] TsUsbGD C:\windows\system32\drivers\TsUsbGD.sys 17:00:04.0712 8236 TsUsbGD - ok 17:00:04.0761 8236 [ 3566A8DAAFA27AF944F5D705EAA64894 ] tunnel C:\windows\system32\DRIVERS\tunnel.sys 17:00:04.0764 8236 tunnel - ok 17:00:04.0812 8236 [ 550B567F9364D8F7684C3FB3EA665A72 ] TVALZ C:\windows\system32\DRIVERS\TVALZ_O.SYS 17:00:04.0814 8236 TVALZ - ok 17:00:04.0856 8236 [ 9C7191F4B2E49BFF47A6C1144B5923FA ] TVALZFL C:\windows\system32\DRIVERS\TVALZFL.sys 17:00:04.0858 8236 TVALZFL - ok 17:00:04.0874 8236 [ B4DD609BD7E282BFC683CEC7EAAAAD67 ] uagp35 C:\windows\system32\drivers\uagp35.sys 17:00:04.0876 8236 uagp35 - ok 17:00:04.0903 8236 [ FF4232A1A64012BAA1FD97C7B67DF593 ] udfs C:\windows\system32\DRIVERS\udfs.sys 17:00:04.0908 8236 udfs - ok 17:00:04.0936 8236 [ 3CBDEC8D06B9968ABA702EBA076364A1 ] UI0Detect C:\windows\system32\UI0Detect.exe 17:00:04.0940 8236 UI0Detect - ok 17:00:04.0967 8236 [ 4BFE1BC28391222894CBF1E7D0E42320 ] uliagpkx C:\windows\system32\drivers\uliagpkx.sys 17:00:04.0969 8236 uliagpkx - ok 17:00:05.0009 8236 [ DC54A574663A895C8763AF0FA1FF7561 ] umbus C:\windows\system32\DRIVERS\umbus.sys 17:00:05.0011 8236 umbus - ok 17:00:05.0041 8236 [ B2E8E8CB557B156DA5493BBDDCC1474D ] UmPass C:\windows\system32\drivers\umpass.sys 17:00:05.0043 8236 UmPass - ok 17:00:05.0138 8236 [ 374EBDA379A8F38E0CFC2211611E7167 ] UNS C:\Program Files (x86)\Intel\Intel® Management Engine Components\UNS\UNS.exe 17:00:05.0167 8236 UNS - ok 17:00:05.0200 8236 [ D47EC6A8E81633DD18D2436B19BAF6DE ] upnphost C:\windows\System32\upnphost.dll 17:00:05.0207 8236 upnphost - ok 17:00:05.0247 8236 [ FB251567F41BC61988B26731DEC19E4B ] USBAAPL64 C:\windows\system32\Drivers\usbaapl64.sys 17:00:05.0249 8236 USBAAPL64 - ok 17:00:05.0279 8236 [ 6F1A3157A1C89435352CEB543CDB359C ] usbccgp C:\windows\system32\DRIVERS\usbccgp.sys 17:00:05.0281 8236 usbccgp - ok 17:00:05.0296 8236 [ AF0892A803FDDA7492F595368E3B68E7 ] usbcir C:\windows\system32\drivers\usbcir.sys 17:00:05.0299 8236 usbcir - ok 17:00:05.0307 8236 [ C025055FE7B87701EB042095DF1A2D7B ] usbehci C:\windows\system32\DRIVERS\usbehci.sys 17:00:05.0309 8236 usbehci - ok 17:00:05.0344 8236 [ 287C6C9410B111B68B52CA298F7B8C24 ] usbhub C:\windows\system32\drivers\usbhub.sys 17:00:05.0349 8236 usbhub - ok 17:00:05.0365 8236 [ 9840FC418B4CBD632D3D0A667A725C31 ] usbohci C:\windows\system32\drivers\usbohci.sys 17:00:05.0366 8236 usbohci - ok 17:00:05.0401 8236 [ 73188F58FB384E75C4063D29413CEE3D ] usbprint C:\windows\system32\DRIVERS\usbprint.sys 17:00:05.0403 8236 usbprint - ok 17:00:05.0444 8236 [ AAA2513C8AED8B54B189FD0C6B1634C0 ] usbscan C:\windows\system32\DRIVERS\usbscan.sys 17:00:05.0446 8236 usbscan - ok 17:00:05.0464 8236 [ FED648B01349A3C8395A5169DB5FB7D6 ] USBSTOR C:\windows\system32\DRIVERS\USBSTOR.SYS 17:00:05.0477 8236 USBSTOR - ok 17:00:05.0489 8236 [ 62069A34518BCF9C1FD9E74B3F6DB7CD ] usbuhci C:\windows\system32\drivers\usbuhci.sys 17:00:05.0491 8236 usbuhci - ok 17:00:05.0518 8236 [ 454800C2BC7F3927CE030141EE4F4C50 ] usbvideo C:\windows\system32\Drivers\usbvideo.sys 17:00:05.0521 8236 usbvideo - ok 17:00:05.0552 8236 [ EDBB23CBCF2CDF727D64FF9B51A6070E ] UxSms C:\windows\System32\uxsms.dll 17:00:05.0556 8236 UxSms - ok 17:00:05.0575 8236 [ C118A82CD78818C29AB228366EBF81C3 ] VaultSvc C:\windows\system32\lsass.exe 17:00:05.0578 8236 VaultSvc - ok 17:00:05.0644 8236 [ C30F3D43CEB6F79ADE9B805387E5F63C ] VBoxDrv C:\windows\system32\DRIVERS\VBoxDrv.sys 17:00:05.0648 8236 VBoxDrv - ok 17:00:05.0676 8236 [ 8ACF22B86CE4E85C23E3E9513BF45C37 ] VBoxNetAdp C:\windows\system32\DRIVERS\VBoxNetAdp.sys 17:00:05.0679 8236 VBoxNetAdp - ok 17:00:05.0709 8236 [ 7B657669C53A0E6583F07EBAA303D9EA ] VBoxNetFlt C:\windows\system32\DRIVERS\VBoxNetFlt.sys 17:00:05.0712 8236 VBoxNetFlt - ok 17:00:05.0801 8236 [ CF3EE68CD9723E9F21E3198A0F690400 ] VBoxUSBMon C:\windows\system32\DRIVERS\VBoxUSBMon.sys 17:00:05.0804 8236 VBoxUSBMon - ok 17:00:05.0833 8236 [ C5C876CCFC083FF3B128F933823E87BD ] vdrvroot C:\windows\system32\drivers\vdrvroot.sys 17:00:05.0835 8236 vdrvroot - ok 17:00:05.0867 8236 [ 8D6B481601D01A456E75C3210F1830BE ] vds C:\windows\System32\vds.exe 17:00:05.0877 8236 vds - ok 17:00:05.0913 8236 [ DA4DA3F5E02943C2DC8C6ED875DE68DD ] vga C:\windows\system32\DRIVERS\vgapnp.sys 17:00:05.0915 8236 vga - ok 17:00:05.0931 8236 [ 53E92A310193CB3C03BEA963DE7D9CFC ] VgaSave C:\windows\System32\drivers\vga.sys 17:00:05.0933 8236 VgaSave - ok 17:00:05.0948 8236 [ 2CE2DF28C83AEAF30084E1B1EB253CBB ] vhdmp C:\windows\system32\drivers\vhdmp.sys 17:00:05.0951 8236 vhdmp - ok 17:00:05.0962 8236 [ E5689D93FFE4E5D66C0178761240DD54 ] viaide C:\windows\system32\drivers\viaide.sys 17:00:05.0964 8236 viaide - ok 17:00:05.0989 8236 [ D2AAFD421940F640B407AEFAAEBD91B0 ] volmgr C:\windows\system32\drivers\volmgr.sys 17:00:05.0991 8236 volmgr - ok 17:00:06.0006 8236 [ A255814907C89BE58B79EF2F189B843B ] volmgrx C:\windows\system32\drivers\volmgrx.sys 17:00:06.0013 8236 volmgrx - ok 17:00:06.0023 8236 [ DF8126BD41180351A093A3AD2FC8903B ] volsnap C:\windows\system32\drivers\volsnap.sys 17:00:06.0028 8236 volsnap - ok 17:00:06.0062 8236 [ B4A73CA4EF9A02B9738CEA9AD5FE5917 ] vpcbus C:\windows\system32\DRIVERS\vpchbus.sys 17:00:06.0065 8236 vpcbus - ok 17:00:06.0113 8236 [ E675FB2B48C54F09895482E2253B289C ] vpcnfltr C:\windows\system32\DRIVERS\vpcnfltr.sys 17:00:06.0116 8236 vpcnfltr - ok 17:00:06.0151 8236 [ 5FB42082B0D19A0268705F1DD343DF20 ] vpcusb C:\windows\system32\DRIVERS\vpcusb.sys 17:00:06.0153 8236 vpcusb - ok 17:00:06.0301 8236 [ 207B6539799CC1C112661A9B620DD233 ] vpcvmm C:\windows\system32\drivers\vpcvmm.sys 17:00:06.0331 8236 vpcvmm - ok 17:00:06.0379 8236 [ 5E2016EA6EBACA03C04FEAC5F330D997 ] vsmraid C:\windows\system32\drivers\vsmraid.sys 17:00:06.0382 8236 vsmraid - ok 17:00:06.0436 8236 [ B60BA0BC31B0CB414593E169F6F21CC2 ] VSS C:\windows\system32\vssvc.exe 17:00:06.0457 8236 VSS - ok 17:00:06.0493 8236 [ 36D4720B72B5C5D9CB2B9C29E9DF67A1 ] vwifibus C:\windows\system32\DRIVERS\vwifibus.sys 17:00:06.0495 8236 vwifibus - ok 17:00:06.0627 8236 [ 6A3D66263414FF0D6FA754C646612F3F ] vwififlt C:\windows\system32\DRIVERS\vwififlt.sys 17:00:06.0629 8236 vwififlt - ok 17:00:06.0664 8236 [ 6A638FC4BFDDC4D9B186C28C91BD1A01 ] vwifimp C:\windows\system32\DRIVERS\vwifimp.sys 17:00:06.0665 8236 vwifimp - ok 17:00:06.0688 8236 [ 1C9D80CC3849B3788048078C26486E1A ] W32Time C:\windows\system32\w32time.dll 17:00:06.0696 8236 W32Time - ok 17:00:06.0712 8236 [ 4E9440F4F152A7B944CB1663D3935A3E ] WacomPen C:\windows\system32\drivers\wacompen.sys 17:00:06.0713 8236 WacomPen - ok 17:00:06.0839 8236 [ 5CF6E9A685199445FEE02FE8C191C9BA ] wampapache c:\wamp\bin\apache\apache2.2.21\bin\httpd.exe 17:00:06.0841 8236 wampapache - ok 17:00:06.0899 8236 wampmysqld - ok 17:00:06.0926 8236 [ 356AFD78A6ED4457169241AC3965230C ] WANARP C:\windows\system32\DRIVERS\wanarp.sys 17:00:06.0928 8236 WANARP - ok 17:00:06.0932 8236 [ 356AFD78A6ED4457169241AC3965230C ] Wanarpv6 C:\windows\system32\DRIVERS\wanarp.sys 17:00:06.0933 8236 Wanarpv6 - ok 17:00:07.0026 8236 [ 3CEC96DE223E49EAAE3651FCF8FAEA6C ] WatAdminSvc C:\windows\system32\Wat\WatAdminSvc.exe 17:00:07.0042 8236 WatAdminSvc - ok 17:00:07.0130 8236 [ 78F4E7F5C56CB9716238EB57DA4B6A75 ] wbengine C:\windows\system32\wbengine.exe 17:00:07.0150 8236 wbengine - ok 17:00:07.0183 8236 [ 3AA101E8EDAB2DB4131333F4325C76A3 ] WbioSrvc C:\windows\System32\wbiosrvc.dll 17:00:07.0190 8236 WbioSrvc - ok 17:00:07.0275 8236 [ 7368A2AFD46E5A4481D1DE9D14848EDD ] wcncsvc C:\windows\System32\wcncsvc.dll 17:00:07.0283 8236 wcncsvc - ok 17:00:07.0301 8236 [ 20F7441334B18CEE52027661DF4A6129 ] WcsPlugInService C:\windows\System32\WcsPlugInService.dll 17:00:07.0305 8236 WcsPlugInService - ok 17:00:07.0327 8236 [ 72889E16FF12BA0F235467D6091B17DC ] Wd C:\windows\system32\drivers\wd.sys 17:00:07.0329 8236 Wd - ok 17:00:07.0380 8236 [ 442783E2CB0DA19873B7A63833FF4CB4 ] Wdf01000 C:\windows\system32\drivers\Wdf01000.sys 17:00:07.0390 8236 Wdf01000 - ok 17:00:07.0401 8236 [ BF1FC3F79B863C914687A737C2F3D681 ] WdiServiceHost C:\windows\system32\wdi.dll 17:00:07.0406 8236 WdiServiceHost - ok 17:00:07.0411 8236 [ BF1FC3F79B863C914687A737C2F3D681 ] WdiSystemHost C:\windows\system32\wdi.dll 17:00:07.0415 8236 WdiSystemHost - ok 17:00:07.0445 8236 [ 3DB6D04E1C64272F8B14EB8BC4616280 ] WebClient C:\windows\System32\webclnt.dll 17:00:07.0451 8236 WebClient - ok 17:00:07.0472 8236 [ C749025A679C5103E575E3B48E092C43 ] Wecsvc C:\windows\system32\wecsvc.dll 17:00:07.0479 8236 Wecsvc - ok 17:00:07.0499 8236 [ 7E591867422DC788B9E5BD337A669A08 ] wercplsupport C:\windows\System32\wercplsupport.dll 17:00:07.0503 8236 wercplsupport - ok 17:00:07.0532 8236 [ 6D137963730144698CBD10F202E9F251 ] WerSvc C:\windows\System32\WerSvc.dll 17:00:07.0537 8236 WerSvc - ok 17:00:07.0568 8236 [ 611B23304BF067451A9FDEE01FBDD725 ] WfpLwf C:\windows\system32\DRIVERS\wfplwf.sys 17:00:07.0570 8236 WfpLwf - ok 17:00:07.0633 8236 [ 245EA6A2CFAE7B183EE9A14A4673B1F1 ] WiMAXAppSrv C:\Program Files\Intel\WiMAX\Bin\AppSrv.exe 17:00:07.0644 8236 WiMAXAppSrv - ok 17:00:07.0662 8236 [ 05ECAEC3E4529A7153B3136CEB49F0EC ] WIMMount C:\windows\system32\drivers\wimmount.sys 17:00:07.0664 8236 WIMMount - ok 17:00:07.0680 8236 WinDefend - ok 17:00:07.0684 8236 WinHttpAutoProxySvc - ok 17:00:07.0726 8236 [ 19B07E7E8915D701225DA41CB3877306 ] Winmgmt C:\windows\system32\wbem\WMIsvc.dll 17:00:07.0730 8236 Winmgmt - ok 17:00:07.0797 8236 [ BCB1310604AA415C4508708975B3931E ] WinRM C:\windows\system32\WsmSvc.dll 17:00:07.0823 8236 WinRM - ok 17:00:07.0879 8236 [ FE88B288356E7B47B74B13372ADD906D ] WinUsb C:\windows\system32\DRIVERS\WinUsb.sys 17:00:07.0880 8236 WinUsb - ok 17:00:07.0924 8236 [ 4FADA86E62F18A1B2F42BA18AE24E6AA ] Wlansvc C:\windows\System32\wlansvc.dll 17:00:07.0937 8236 Wlansvc - ok 17:00:07.0991 8236 [ 06C8FA1CF39DE6A735B54D906BA791C6 ] wlcrasvc C:\Program Files\Windows Live\Mesh\wlcrasvc.exe 17:00:07.0993 8236 wlcrasvc - ok 17:00:08.0090 8236 [ 2BACD71123F42CEA603F4E205E1AE337 ] wlidsvc C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE 17:00:08.0116 8236 wlidsvc - ok 17:00:08.0141 8236 [ F6FF8944478594D0E414D3F048F0D778 ] WmiAcpi C:\windows\system32\drivers\wmiacpi.sys 17:00:08.0143 8236 WmiAcpi - ok 17:00:08.0206 8236 [ 38B84C94C5A8AF291ADFEA478AE54F93 ] wmiApSrv C:\windows\system32\wbem\WmiApSrv.exe 17:00:08.0211 8236 wmiApSrv - ok 17:00:08.0264 8236 WMPNetworkSvc - ok 17:00:08.0383 8236 [ 96C6E7100D724C69FCF9E7BF590D1DCA ] WPCSvc C:\windows\System32\wpcsvc.dll 17:00:08.0388 8236 WPCSvc - ok 17:00:08.0402 8236 [ 93221146D4EBBF314C29B23CD6CC391D ] WPDBusEnum C:\windows\system32\wpdbusenum.dll 17:00:08.0408 8236 WPDBusEnum - ok 17:00:08.0427 8236 [ 6BCC1D7D2FD2453957C5479A32364E52 ] ws2ifsl C:\windows\system32\drivers\ws2ifsl.sys 17:00:08.0428 8236 ws2ifsl - ok 17:00:08.0457 8236 [ E8B1FE6669397D1772D8196DF0E57A9E ] wscsvc C:\windows\System32\wscsvc.dll 17:00:08.0461 8236 wscsvc - ok 17:00:08.0464 8236 WSearch - ok 17:00:08.0549 8236 [ D9EF901DCA379CFE914E9FA13B73B4C4 ] wuauserv C:\windows\system32\wuaueng.dll 17:00:08.0605 8236 wuauserv - ok 17:00:08.0647 8236 [ AB886378EEB55C6C75B4F2D14B6C869F ] WudfPf C:\windows\system32\drivers\WudfPf.sys 17:00:08.0649 8236 WudfPf - ok 17:00:08.0711 8236 [ DDA4CAF29D8C0A297F886BFE561E6659 ] WUDFRd C:\windows\system32\DRIVERS\WUDFRd.sys 17:00:08.0715 8236 WUDFRd - ok 17:00:08.0751 8236 [ B20F051B03A966392364C83F009F7D17 ] wudfsvc C:\windows\System32\WUDFSvc.dll 17:00:08.0757 8236 wudfsvc - ok 17:00:08.0780 8236 [ 9A3452B3C2A46C073166C5CF49FAD1AE ] WwanSvc C:\windows\System32\wwansvc.dll 17:00:08.0786 8236 WwanSvc - ok 17:00:08.0917 8236 [ D42B153CD9AC1237B7FAC8BA24E1A7E4 ] wwEngineSvc C:\Program Files (x86)\Webroot\Washer\WasherSvc.exe 17:00:08.0922 8236 wwEngineSvc - ok 17:00:09.0024 8236 [ 1619A3283D9125D44116A1EE9143E035 ] XMail C:\Program Files (x86)\acquia-drupal\xmail\XMail.exe 17:00:09.0030 8236 XMail - ok 17:00:09.0077 8236 [ 38F55D07B1D3391065C40EC065F984E2 ] xusb21 C:\windows\system32\DRIVERS\xusb21.sys 17:00:09.0080 8236 xusb21 - ok 17:00:09.0159 8236 [ DD0042F0C3B606A6A8B92D49AFB18AD6 ] YahooAUService C:\Program Files (x86)\Yahoo!\SoftwareUpdate\YahooAUService.exe 17:00:09.0165 8236 YahooAUService - ok 17:00:09.0204 8236 ================ Scan global =============================== 17:00:09.0227 8236 [ BA0CD8C393E8C9F83354106093832C7B ] C:\windows\system32\basesrv.dll 17:00:09.0277 8236 [ 9E479C2B605C25DA4971ABA36250FAEF ] C:\windows\system32\winsrv.dll 17:00:09.0287 8236 [ 9E479C2B605C25DA4971ABA36250FAEF ] C:\windows\system32\winsrv.dll 17:00:09.0319 8236 [ D6160F9D869BA3AF0B787F971DB56368 ] C:\windows\system32\sxssrv.dll 17:00:09.0343 8236 [ 24ACB7E5BE595468E3B9AA488B9B4FCB ] C:\windows\system32\services.exe 17:00:09.0350 8236 [Global] - ok 17:00:09.0350 8236 ================ Scan MBR ================================== 17:00:09.0363 8236 [ 5B5E648D12FCADC244C1EC30318E1EB9 ] \Device\Harddisk0\DR0 17:00:09.0567 8236 \Device\Harddisk0\DR0 - ok 17:00:09.0568 8236 ================ Scan VBR ================================== 17:00:09.0583 8236 [ 01DC71CFDF6F5BA7AFCA83B0124D6033 ] \Device\Harddisk0\DR0\Partition1 17:00:09.0585 8236 \Device\Harddisk0\DR0\Partition1 - ok 17:00:09.0585 8236 ============================================================ 17:00:09.0585 8236 Scan finished 17:00:09.0585 8236 ============================================================ 17:00:09.0592 7564 Detected object count: 0 17:00:09.0592 7564 Actual detected object count: 0

Maurice, I'm quoting those above so I can apologize for the wrong statement of "all of my previous restore points dated since January 8th have been deleted", as I meant to say before January 8th. So, again, don't know why those created before the windows update were deleted.

And yes I was able to run msinfo32.exe, but still can't access System Information. Okay, on to your next task.

Maurice, Yes, this is my personal laptop and I am the Administrator, and yes I am logged in as Administrator. What caught my attention about losing my system restore points, was the fact that I lost ALL of my restore points, not that a newer restore point had been saved and caused all of them to be deleted, as there were absolutely none there (as I wrote in my first post). So, I don't know if some software or malware had turned off my System Restore, causing all to be deleted, but I know I haven't. Additionally, the last restore point was created by Windows Update on January 10th, but it didn't use all of the disk space set aside, so I'm wondering why none of the previously created restore points were kept after it was created. Mmmmmmmmmmm.........