Consistant problem with this machine.

Why do I get this conflict? It is on a lan with another machine by way of a router while the other machine does not get any conflicts.Here is the log of the ten last steps and when I restarted the computer I got this error...

[09:30:24] Completed 1252 out of 2086 steps (60)
[09:30:24] Writing local files
[09:45:53] Timered checkpoint triggered.
[09:50:45] Completed 1273 out of 2086 steps (61)
[09:50:45] Writing local files
[10:06:13] Timered checkpoint triggered.
[10:11:05] Completed 1294 out of 2086 steps (62)
[10:11:05] Writing local files
[10:26:33] Timered checkpoint triggered.
[10:31:24] Completed 1315 out of 2086 steps (63)
[10:31:24] Writing local files
[10:46:52] Timered checkpoint triggered.
[10:51:45] Completed 1336 out of 2086 steps (64)
[10:51:45] Writing local files
[11:07:13] Timered checkpoint triggered.
[11:11:06] Completed 1356 out of 2086 steps (65)
[11:11:06] Writing local files
[11:26:34] Timered checkpoint triggered.
[11:31:26] Completed 1377 out of 2086 steps (66)
[11:31:26] Writing local files
[11:36:08] - Autosending finished units...
[11:36:08] Trying to send all finished work units
[11:36:08] + No unsent completed units remaining.
[11:36:08] - Autosend completed
[11:46:54] Timered checkpoint triggered.
[11:51:46] Completed 1398 out of 2086 steps (67)
[11:51:46] Writing local files
[12:07:14] Timered checkpoint triggered.
[12:12:05] Completed 1419 out of 2086 steps (68)
[12:12:05] Writing local files
[12:27:33] Timered checkpoint triggered.
[12:32:24] Completed 1440 out of 2086 steps (69)
[12:32:24] Writing local files
[12:47:53] Timered checkpoint triggered.
[12:52:45] Completed 1461 out of 2086 steps (70)
[12:52:45] Writing local files
[13:08:31] Timered checkpoint triggered.


--- Opening Log file [January 23 13:20:41]


# Windows Console Edition #####################################################
###############################################################################

Folding@Home Client Version 5.02

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\FAH
Executable: C:\Program Files\FAH\FAH502-Console.exe
Arguments: -local -service -advmethods -verbosity 9 -forceasm

Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.

[13:20:41] - Ask before connecting: No
[13:20:41] - User name: F(OC)LD (Team 32)
[13:20:41] - User ID: 31E2D3BB2A64C25F
[13:20:41] - Machine ID: 1
[13:20:41]

A potential conflict was detected:

Process 2032 is currently running and may also be a client with Mach. ID 1.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
C:\Program Files\FAH before restarting.

This error is fairly common with XP (perhaps all Windows versions using NTFS). Perhaps one in ten improper shutdowns leads to the conflict message, the result of a lock file not being deleted. There should be a sigterm message in the log when shutdown properly.

my pc often hits check points after boot up because of SERVICES using 50% of the cpu resorces for ~25 minutes this also happens if i play a game or on very large protiens (600+pointers)
look to see if you are runing a cpu intensive task that should not be thier/ sweep for spyware viruses etc

when you get that

A potential conflict was detected:

Click to expand...

a task is luanched symultainiusly and has tryed to use the same id. its just a windows goofy-ness that can happen some times or when wiundows doesnt get a responce instantainiusly that its started F@H so retrys the task.
( i think ChasR might have a much beter explination as to why this occurs here)
solution to this is to go to start/run type "services.msc" (no quotes marks"") then select FAH for the instance that has stoped click "stop" this is important that you click stop not pause or restart then wait 1 minute at least and then click "start" for this service. check the log and it should be running again.

Well thanks guys I thought it might be something more serious or troublesome.It just started up nicely again after stopping the service and starting it again.

This is sort of a bug in version 5.0x of FAH. The process in conflict is FAH its self and will happen on machines that run nothing but FAH and the Win XP. I say it is sort of a bug rather than a real bug because if FAH is properly shutdown, you'll never get this message (At least I've never gotten it any other way). The question for strat is why is the machine not shutting down properly? As you've found, stopping and restarting the client gets you folding again.

ChasR said:

The question for strat is why is the machine not shutting down properly?

Click to expand...

I just restarted the computer like I would any other time but I guess once in a while it just gets screwed up.Oh well at least I know how to fix it now.Thanks again.

Is a simple reboot of one's computer by going ->start/turn off/restart harmful to a WU?
Is it advisable to always use Services to shut down a client, before rebooting?

ihrsetrdr said:

Is a simple reboot of one's computer by going ->start/turn off/restart harmful to a WU?
Is it advisable to always use Services to shut down a client, before rebooting?

Click to expand...

Normal shutdown should work fine ... windows sends a sigterm to each app telling it to shutdown which should be the same as you manually stopping the service ( or console if not running as a service).

I got that message last night. It happened after a series of early shut downs because of overclocking. It started up and finished nicely upon going back to stable OC settings.

ChasR: Perhaps one in ten improper shutdowns leads to the conflict message

Click to expand...

CJ-5 said:

I got that message last night. It happened after a series of early shut downs because of overclocking. It started up and finished nicely upon going back to stable OC settings.

Click to expand...

same here... darn overclocking ruins everything(but it's so darn fun!) lol.