شكرا اخي
هذا هو السجل هو طويل @@ (اتمني ان طوله لا يعني كثيرا من المشاكل)
====== سجل أخطاء النظام ======
Computer Name: Golden
Event Code: 36888
Message: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
Record Number: 1321
Source Name: Schannel
Time Written: 20130817212605.353937-000
Event Type: Error
User: NT AUTHORITY\SYSTEM
Computer Name: Golden
Event Code: 36888
Message: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
Record Number: 1320
Source Name: Schannel
Time Written: 20130817212250.916890-000
Event Type: Error
User: NT AUTHORITY\SYSTEM
Computer Name: Golden
Event Code: 36888
Message: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
Record Number: 1319
Source Name: Schannel
Time Written: 20130817212204.001481-000
Event Type: Error
User: NT AUTHORITY\SYSTEM
Computer Name: Golden
Event Code: 36888
Message: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
Record Number: 1316
Source Name: Schannel
Time Written: 20130817211554.485944-000
Event Type: Error
User: NT AUTHORITY\SYSTEM
Computer Name: Golden
Event Code: 36888
Message: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
Record Number: 1315
Source Name: Schannel
Time Written: 20130817211448.896845-000
Event Type: Error
User: NT AUTHORITY\SYSTEM
===== سجل أخطاء البرامج =====
Computer Name: Golden
Event Code: 78
Message: Activation context generation failed for "C:\Users\TOSHIBA\Desktop\Downloads\Programs\SoftonicDownloader_for_kmplayer.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16579_none_418ab7ef718b27ef.manifest. Component 2: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16579_none_8937eec6860750f5.manifest.
Record Number: 46846
Source Name: SideBySide
Time Written: 20140504174015.000000-000
Event Type: Error
User:
Computer Name: Golden
Event Code: 78
Message: Activation context generation failed for "c:\Users\TOSHIBA\AppData\Local\TNT2\2.0.0.1599\TNT2User.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16579_none_8937eec6860750f5.manifest. Component 2: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16579_none_418ab7ef718b27ef.manifest.
Record Number: 46845
Source Name: SideBySide
Time Written: 20140504173959.000000-000
Event Type: Error
User:
Computer Name: Golden
Event Code: 78
Message: Activation context generation failed for "c:\Users\TOSHIBA\AppData\Local\TNT2\2.0.0.1599\TNT2User.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16579_none_8937eec6860750f5.manifest. Component 2: C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16579_none_418ab7ef718b27ef.manifest.
Record Number: 46842
Source Name: SideBySide
Time Written: 20140504173538.000000-000
Event Type: Error
User:
Computer Name: Golden
Event Code: 8233
Message: The rules engine reported a failed VL activation attempt.
Reason:0xC004F074
AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b322da9c-a2e2-4058-9e4e-f59a6970bd69
Trigger=NetworkAvailable
Record Number: 46831
Source Name: Microsoft-Windows-Security-SPP
Time Written: 20140504172010.000000-000
Event Type: Warning
User:
Computer Name: Golden
Event Code: 8233
Message: The rules engine reported a failed VL activation attempt.
Reason:0xC004F074
AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b322da9c-a2e2-4058-9e4e-f59a6970bd69
Trigger=NetworkAvailable
Record Number: 46814
Source Name: Microsoft-Windows-Security-SPP
Time Written: 20140504153013.000000-000
Event Type: Warning
User:
===== السجل الأمني =====
Computer Name: Golden
Event Code: 4648
Message: A logon was attempted using explicit credentials.
Subject:
Security ID: S-1-5-18
Account Name: GOLDEN$
Account Domain: WORKGROUP
Logon ID: 0x3E7
Logon GUID: {00000000-0000-0000-0000-000000000000}
Account Whose Credentials Were Used:
Account Name: DWM-74
Account Domain: Window Manager
Logon GUID: {00000000-0000-0000-0000-000000000000}
Target Server:
Target Server Name: localhost
Additional Information: localhost
Process Information:
Process ID: 0x1880
Process Name: C:\Windows\System32\winlogon.exe
Network Information:
Network Address: -
Port: -
This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
Record Number: 68682
Source Name: Microsoft-Windows-Security-Auditing
Time Written: 20140815190942.819551-000
Event Type: Audit Success
User:
Computer Name: Golden
Event Code: 4672
Message: Special privileges assigned to new logon.
Subject:
Security ID: S-1-5-90-74
Account Name: DWM-74
Account Domain: Window Manager
Logon ID: 0x6454C7
Privileges: SeAssignPrimaryTokenPrivilege
SeAuditPrivilege
Record Number: 68681
Source Name: Microsoft-Windows-Security-Auditing
Time Written: 20140815190942.731494-000
Event Type: Audit Success
User:
Computer Name: Golden
Event Code: 4672
Message: Special privileges assigned to new logon.
Subject:
Security ID: S-1-5-90-74
Account Name: DWM-74
Account Domain: Window Manager
Logon ID: 0x6454B9
Privileges: SeAssignPrimaryTokenPrivilege
SeAuditPrivilege
SeImpersonatePrivilege
Record Number: 68680
Source Name: Microsoft-Windows-Security-Auditing
Time Written: 20140815190942.731494-000
Event Type: Audit Success
User:
Computer Name: Golden
Event Code: 4624
Message: An account was successfully logged on.
Subject:
Security ID: S-1-5-18
Account Name: GOLDEN$
Account Domain: WORKGROUP
Logon ID: 0x3E7
Logon Type: 2
Impersonation Level: Impersonation
New Logon:
Security ID: S-1-5-90-74
Account Name: DWM-74
Account Domain: Window Manager
Logon ID: 0x6454C7
Logon GUID: {00000000-0000-0000-0000-000000000000}
Process Information:
Process ID: 0x1880
Process Name: C:\Windows\System32\winlogon.exe
Network Information:
Workstation Name:
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon session is created. It is generated on the computer that was accessed.
The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The impersonation level field indicates the extent to which a process in the logon session can impersonate.
The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Record Number: 68679
Source Name: Microsoft-Windows-Security-Auditing
Time Written: 20140815190942.731494-000
Event Type: Audit Success
User:
Computer Name: Golden
Event Code: 4624
Message: An account was successfully logged on.
Subject:
Security ID: S-1-5-18
Account Name: GOLDEN$
Account Domain: WORKGROUP
Logon ID: 0x3E7
Logon Type: 2
Impersonation Level: Impersonation
New Logon:
Security ID: S-1-5-90-74
Account Name: DWM-74
Account Domain: Window Manager
Logon ID: 0x6454B9
Logon GUID: {00000000-0000-0000-0000-000000000000}
Process Information:
Process ID: 0x1880
Process Name: C:\Windows\System32\winlogon.exe
Network Information:
Workstation Name:
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon session is created. It is generated on the computer that was accessed.
The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The impersonation level field indicates the extent to which a process in the logon session can impersonate.
The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Record Number: 68678
Source Name: Microsoft-Windows-Security-Auditing
Time Written: 20140815190942.731494-000
Event Type: Audit Success
User:
===== تقرير انهيار البرامج =====
==================================================
Process File : svchost.exe
Event Name : Windows Update installation problem
Event Time : 8/30/2014 2:51:34 PM
User Name : All Users
Exception Code :
Exception Offset :
Fault Module Name :
Fault Module Version:
Process Path : C:\Windows\System32\svchost.exe
Report File Size : 2,290
Report File Path : C:\Users\All Users\Microsoft\Windows\WER\ReportArchive\NonCritical_7.8.9200.16924_5ab0e583e15e82876b74a15f1f86ba98391e6444_05c4ba9d\Report.wer
==================================================
==================================================
Process File : svchost.exe
Event Name : Windows Update installation problem
Event Time : 8/30/2014 2:51:34 PM
User Name :
Exception Code :
Exception Offset :
Fault Module Name :
Fault Module Version:
Process Path : C:\Windows\System32\svchost.exe
Report File Size : 2,290
Report File Path : C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.8.9200.16924_5ab0e583e15e82876b74a15f1f86ba98391e6444_05c4ba9d\Report.wer
==================================================
===== تقرير الشاشة الزرقاء =====
==================================================
Dump File : 083014-27875-01.dmp
Crash Time : 8/30/2014 1:13:49 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000000
Parameter 3 : fffffa80`0a96d2e0
Parameter 4 : 000007fc`614f2fd0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a540
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\083014-27875-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 301,136
==================================================
==================================================
Dump File : 083014-28718-01.dmp
Crash Time : 8/30/2014 2:47:48 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000000
Parameter 3 : fffffa80`098936c0
Parameter 4 : 00000052`91532fca
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a540
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\083014-28718-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 301,136
==================================================
==================================================
Dump File : 083014-69796-01.dmp
Crash Time : 8/30/2014 1:25:29 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000000
Parameter 3 : fffffa80`048d1b60
Parameter 4 : 0000000c`6523bb84
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a540
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\083014-69796-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 301,136
==================================================
