Hello, I am still trying to figure out the problem

I just copied these from the event viewer,

I am running windows xp updated wth service pack 3
explorer 7.0


Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 63
Date: 3/1/2009
Time: 8:02:02 PM
User: GREGORY\HOME
Computer: GREGORY
Description:
A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, 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.


Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 3/1/2009
Time: 8:06:48 PM
User: NT AUTHORITY\SYSTEM
Computer: GREGORY
Description:
Windows saved user GREGORY\HOME 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.

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 3/1/2009
Time: 8:13:51 PM
User: NT AUTHORITY\SYSTEM
Computer: GREGORY
Description:
Windows saved user GREGORY\HOME 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.

.Event Type: Failure Audit
Event Source: Security
Event Category: Policy Change
Event ID: 615
Date: 3/3/2009
Time: 8:01:57 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: GREGORY
Description:
IPSec Services: IPSec Services failed to get the complete list of network interfaces on the machine. This can be a potential security hazard to the machine since some of the network interfaces may not get the protection as desired by the applied IPSec filters. Please run IPSec monitor snap-in to further diagnose the problem.