Allocating ip address

SharedAccess_NAT:
The DHCP allocator has disabled itself on ip address 192.168.1.2,since the IP address is outside the 192.168.137.0/255.255.255.0 scope from which addresses are being allocated to DHCP clients.To enable the DHCP allocator on this IP address,change the scope to include the ip address,or change the ip address to fall within the scope.
Log name : system
source : SharedAccess_NAT
Event id : 30013

Low virtual memory :
The DNS proxy agent was unable to allocate 0 bytes of memory.This may indicate that the system is low on virtual memory,or that the memory manager has encountered an internal error.


Configuring ipv6 stack :
The ICS_IPV6 failed to configure IPv6 stack.

Diagnostics Performance critical events 100 351

Error message :
This driver responded  slower than expected to the resume request while servicing this device:
Driver file name : \Driver\igfx
Driver Friendly Name : Intel Graphics Kernel Mode Driver
Driver version : 8.14.10.1930
Driver Total Time : 4377ms
Driver Degradation Time : 4056ms
Incident Time UTC : 2011-03-03T08:06:26.304300900Z
Device Name : PCI\VEN_8086&DEV_2A02&SUBSYS_30D9103C&REV_03\3&21436425&0&10
Device friendly name : MMobile Intel(R) 965 Express Chipset Family
Device total time : 4387 ms
Device degradation time : 4056ms


Additional details :
Log name : microsoft-windows diagnostics performance/operational
event id : 351
opcode : standby Degradation
Task category : standby performance monitoring
level : critical
source : diagnostics-performance
keywords : event log


Solution :
Windows standby/resume performance diagnostics's setting configure scenario execution level determines the execution level for windows standby/resume performance diagnostics.

If user enable this policy setting,then the user must select an execution level from the dropdown menu.If user select problem detection and troubleshooting only,the diagnostics policy service (DPS) will detect windows standby/ resume performance diagnostics problems and attempt to determine their root causes.These root causes will be logged to the event log when detected,but no corrective action will be taken.If user select detection,troubleshooting and resolution the DPS will detect windows standby/resume performance diagnostics problems and indicate to the user that assisted resolution is available.


Note : To enable or to know more about this service open local group policy editor and navigate to computer configuration->administrative template->system->troubleshooting and diagnostics.


Critical Event 100 Diagnostics-Performance :
Error message /Description :
Windows has started up :
Boot duration : 136574ms
IsDegradation : false
Incident Time (UTC): 2011-09-02T04:19:07.749600500Z
Opcode : Boot Information


Additional log details :
event id : 100
source : diagnostics-performance
user : local service
keywords: event log
task category : boot performance monitoring


Event 106, Diagnostics-Performance:
Background optimizations (prefetching) took longer to complete, resulting in a performance degradation in the system process:
Name: BackgroundPrefetchTime
Total time: 37810ms
Degradation time: 7957ms
level: critical
OpCode: boot degradation
task category: boot performance monitoring
keywords: event log
proof:

diagnostics performance event 351

Event 201 Scripted Diagnostic Engine

Error message and code:

'Scripted Diagnostic Engine has encountered an error 0x803c0101'.

Error code may also sometimes be 0x803c0100
Event id : 201

keywords : lifecycle keyword

source : Diagnosis-Scripted

Solution :

Scripted Diagnostic includes following important functions,

• Troubleshooting : Allow users to access online troubleshooting content on Microsoft servers from the Troubleshooting control panel (via the windows online troubleshooting service-WOTS).
• Troubleshooting : Allow users to access and run troubleshooting wizards. 
• Configure security policy for scripted diagnostics.

To enable or disable the above services do the following steps,

• Run -> gpedit.msc
• In Local group policy editor under computer configuration select Administrative Templates->system->Troubleshooting And Diagnostics->Scripted Diagnostics.

Note : The error may because of problems in troubleshooting wizards.So try re-enabling the service.

Fix error code 0x8002801c windows 7

Setup :
C:\system32\stdole2.tlb
Unable to register the DLL /OCX :Register Type Lib failed; code 0x8002801c.
Error accessing the OLE registry.


Solution :
'RegSvr32' is responsible for registering .dll files.RegSvr32 may encountered an error while trying to register the DLL file or ActiveX Control having extension .ocx.It is also important to ensure that,for registering a module,is user failed to provide a binary name?.

Note : if any dll or ActiveX Control gets failed to registered,then while running the disk cleanup utility,surely there will be a error as unregistering the file.

System restore event 8193 windows7

Windows logs /Event 8193,System restore:
Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description= Windows Update ; Error code = 0x81000101).

Failed to create restore point (process=C:\Windows\system32\msiexec.exe /V; Description= Removed microsoft games for windows-live redistributable; Error=0x8004231f

Process = C:\windows\system32\msiexec.exe/V; Description = Removed Apple Mobile Device Support; Error = 0x80070070
Additional log details :
log name : application.
source : system restore.
event id : 8193
keywords : classic