Windows 10: nvlddmkm stopped responding and recovered. PC freeze

Hi,
2 weeks ago, pc suffered power loss and my psu went dead. i managed to install a new PSU and reinstall nvidia driver. but last few days, i m having screen blackouts for a few seconds and then screen will comes back a few sec later.

under event viewer, i keep getting this error message:
"Display driver nvlddmkm stopped responding and has successfully recovered. "
And below error message:
================================================================
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3
1973(168c) 00000000 00000000
the message resource is present but the message is not found in the string/message table
================================================================
yesterday, my PC freezes everytime i m running 3 to 5 software applications and i have to do a hard restart to reboot pc. now i can't use those applications because my pc will freeze, but i need to run those applications for my work which i have used for years with no issue.
even though there is no BSOD but i remembered i had similar problem last year and it was solved based on your expert advice. so i have attached a DM log file for your reference.
pls see DM log.
thanks in advance for your help!

:)

 

frequent windows event 4101(Display driver nvlddmkm stopped responding and has successfully recovered.)

Having the same exact issue in bf1, second monitor goes dark then game freezes.

In event log getting

the 4101 event

Display driver nvlddmkm stopped responding and has successfully recovered.

 

Windows 10 on Dell XPS 630I ?

Level Date and Time Source Event ID Task Category

Error 8/13/2015 11:59:58 PM Service Control Manager 7031 None The User Data Access_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

Error 8/13/2015 11:59:58 PM Service Control Manager 7031 None The User Data Storage_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

Error 8/13/2015 11:59:58 PM Service Control Manager 7031 None The Contact Data_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

Error 8/13/2015 11:59:58 PM Service Control Manager 7031 None The Sync Host_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

Information 8/13/2015 11:59:58 PM User32 1074 None "The process C:\Windows\System32\RuntimeBroker.exe (DANPC) has initiated the power off of computer DANPC on behalf of user DanPC\Dan for the following reason: Other (Unplanned)

Reason Code: 0x0

Shutdown Type: power off

Comment: "

Information 8/13/2015 11:59:42 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.

Information 8/13/2015 11:00:10 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.

Error 8/13/2015 9:04:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout.

Information 8/13/2015 9:02:55 PM SRTSP 2003 None Symantec Antivirus minifilter successfully loaded.

Information 8/13/2015 9:02:46 PM Microsoft-Windows-FilterManager 6 None File System Filter 'SRTSP' (6.1, ‎2015‎-‎06‎-‎14T03:19:20.000000000Z) has successfully loaded and registered with Filter Manager.

Error 8/13/2015 9:01:32 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:32 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:32 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:32 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:32 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:32 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:32 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:32 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:32 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:32 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:31 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:31 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:31 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:31 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:31 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:31 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:29 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{B52D54BB-4818-4EB9-AA80-F9EACD371DF8}"

Error 8/13/2015 9:01:29 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:27 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:27 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:27 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}"

Error 8/13/2015 9:01:27 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:23 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:

{9E175B6D-F52A-11D8-B9A5-505054503030}"

Error 8/13/2015 9:01:23 PM Service Control Manager 7000 None "The Windows Search service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

Error 8/13/2015 9:01:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.

Error 8/13/2015 9:01:13 PM Service Control Manager 7031 None The Windows Search service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.

Error 8/13/2015 9:01:13 PM Service Control Manager 7024 None "The Windows Search service terminated with the following service-specific error:

%%2147749126"

Information 8/13/2015 9:00:56 PM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program

Information 8/13/2015 8:59:54 PM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load:

dam"

Error 8/13/2015 8:59:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 14 service to connect.

Information 8/13/2015 8:59:30 PM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started

Information 8/13/2015 8:59:30 PM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started

Information 8/13/2015 8:59:28 PM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2015‎-‎07‎-‎09T23:17:31.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:28 PM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎2015‎-‎07‎-‎09T23:14:34.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:11 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (1 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States

Nominal Frequency (MHz): 2672

Maximum performance percentage: 100

Minimum performance percentage: 75

Minimum throttle percentage: 75"

Information 8/13/2015 8:59:11 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (1 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States

Nominal Frequency (MHz): 2672

Maximum performance percentage: 100

Minimum performance percentage: 75

Minimum throttle percentage: 75"

Information 8/13/2015 8:59:11 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (1 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States

Nominal Frequency (MHz): 2672

Maximum performance percentage: 100

Minimum performance percentage: 75

Minimum throttle percentage: 75"

Information 8/13/2015 8:59:11 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (1 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States

Nominal Frequency (MHz): 2672

Maximum performance percentage: 100

Minimum performance percentage: 75

Minimum throttle percentage: 75"

Information 8/13/2015 8:59:10 PM Microsoft-Windows-Kernel-Power 508 (159) "The system has been constrained to a periodic tick

Reason: No HW support."

Critical 8/13/2015 8:59:10 PM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Information 8/13/2015 8:59:10 PM Microsoft-Windows-FilterManager 6 None File System Filter 'BHDrvx64' (6.1, ‎2015‎-‎07‎-‎11T00:11:26.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:09 PM Microsoft-Windows-FilterManager 6 None File System Filter 'eeCtrl' (6.1, ‎2015‎-‎07‎-‎15T21:17:05.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:09 PM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2015‎-‎07‎-‎09T23:14:31.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:09 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2015‎-‎07‎-‎09T23:14:31.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:09 PM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume2) is healthy. No action is needed.

Information 8/13/2015 8:59:02 PM Microsoft-Windows-FilterManager 6 None File System Filter 'SymEFASI' (6.0, ‎2015‎-‎05‎-‎07T05:44:15.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:02 PM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2015‎-‎08‎-‎05T22:13:43.000000000Z) has successfully loaded and registered with Filter Manager.

Information 8/13/2015 8:59:02 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2015‎-‎07‎-‎09T23:14:57.000000000Z) has successfully loaded and registered with Filter Manager.

Error 8/13/2015 8:58:59 PM nvraid 11 None "The description for Event ID 11 from source nvraid cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install
or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the message resource is present but the message is not found in the string/message table

"

Error 8/13/2015 8:58:59 PM nvraid 11 None "The description for Event ID 11 from source nvraid cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install
or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the message resource is present but the message is not found in the string/message table

"

Error 8/13/2015 8:58:59 PM nvraid 11 None "The description for Event ID 11 from source nvraid cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install
or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the message resource is present but the message is not found in the string/message table

"

Error 8/13/2015 8:58:59 PM nvraid 11 None "The description for Event ID 11 from source nvraid cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install
or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the message resource is present but the message is not found in the string/message table

"

Error 8/13/2015 8:58:59 PM nvraid 11 None "The description for Event ID 11 from source nvraid cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install
or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the message resource is present but the message is not found in the string/message table

"

Information 8/13/2015 8:59:30 PM EventLog 6013 None The system uptime is 31 seconds.

Information 8/13/2015 8:59:30 PM EventLog 6005 None The Event log service was started.

Information 8/13/2015 8:59:30 PM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 10240 Multiprocessor Free.

Error 8/13/2015 8:59:30 PM EventLog 6008 None The previous system shutdown at 8:58:02 PM on ‎8/‎13/‎2015 was unexpected.

Information 8/13/2015 8:58:58 PM Microsoft-Windows-Kernel-Boot 32 None The bootmgr spent 0 ms waiting for user input.

Information 8/13/2015 8:58:58 PM Microsoft-Windows-Kernel-Boot 18 None There are 0x1 boot options on this system.

Information 8/13/2015 8:58:58 PM Microsoft-Windows-Kernel-Boot 25 None The boot menu policy was 0x1.

Information 8/13/2015 8:58:58 PM Microsoft-Windows-Kernel-Boot 27 None The boot type was 0x0.

Information 8/13/2015 8:58:58 PM Microsoft-Windows-Kernel-Boot 20 None The last shutdown's success status was false. The last boot's success status was true.

Information 8/13/2015 8:58:58 PM Microsoft-Windows-Kernel-General 12 None The operating system started at system time ‎2015‎-‎08‎-‎14T00:58:58.495669700Z.

Warning 8/13/2015 8:58:04 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:58:01 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:58 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:55 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:51 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:48 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:45 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:42 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:39 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:35 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:32 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:29 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:26 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:23 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:20 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:16 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:13 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:10 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:07 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:04 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:57:00 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:57 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:54 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:51 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:48 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:45 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:41 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:38 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:35 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:32 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:29 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:26 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:22 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:19 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:16 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:13 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:09 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:06 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:03 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:56:00 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:57 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:54 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:50 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:47 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:44 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:41 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:38 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:34 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:31 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:28 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:25 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:22 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:18 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:15 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:12 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:09 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:06 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:55:02 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:59 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:56 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:53 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:50 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:46 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:43 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:40 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:37 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:34 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:30 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:27 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:24 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:21 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:18 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:15 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:11 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:08 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:05 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:54:02 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:59 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:55 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:52 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:49 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:46 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:43 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:39 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:36 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:33 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:30 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:27 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:23 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:20 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:16 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:12 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:09 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:06 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:53:03 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:59 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:56 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:53 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:50 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:47 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:43 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:40 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:37 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:33 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:30 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:27 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:24 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:21 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:16 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:13 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:10 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:06 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:03 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:52:00 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:57 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:54 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:50 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:47 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:44 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:41 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:37 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:34 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:31 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:28 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:25 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:21 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:18 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:15 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Warning 8/13/2015 8:51:12 PM Display 4101 None Display driver nvlddmkm stopped responding and has successfully recovered.

Information 8/13/2015 8:38:18 PM Microsoft-Windows-Eventlog 104 Log clear The Windows PowerShell log file was cleared.

Information 8/13/2015 8:38:18 PM Microsoft-Windows-Eventlog 104 Log clear The System log file was cleared.