There are dozens of these two:
Code:
An SSL 3.0 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.
Code:
The following fatal alert was generated: 40. The internal error state is 107.
A few of these:
Code:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa80088e5920, 0xfffffa80088e5c00, 0xfffff80002fdf460). A dump was saved in: C:\Windows\Minidump\120412-22183-01.dmp. Report Id: 120412-22183-01.
Code:
The Internet Connection Sharing (ICS) service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Some of these, usually 3-4 in a row. It only has 2 disks installed.
Code:
Event[1971]:
Log Name: System
Source: Disk
Date: 2012-12-18T11:01:30.046
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Klattu51
Description:
The driver detected a controller error on \Device\Harddisk6\DR6.
This is a Warning:
Code:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Quote
All of them does not need attention :)