Client Error...computing

Jimbo2002
Jimbo2002
Joined: 4 Sep 05
Posts: 11
Credit: 168284363
RAC: 172727
Topic 189903

Does this mean that I had a faulty data unit or what?

One day man may become.

Stick
Stick
Joined: 24 Feb 05
Posts: 790
Credit: 33137945
RAC: 1033

Client Error...computing

It doesn't look like you have a major problem here (i.e. only one unit that I could see). But, if you start getting more Client error Computing messages, it could be a symptom of a BOINC 4.45/Einstein 4.79 incompatibility problem. If and when you get to that point, you should check out the Einstein Windows Beta Application (under More Information on the E@H home page).

Quote:
Does this mean that I had a faulty data unit or what?


Tern
Tern
Joined: 27 Jul 05
Posts: 309
Credit: 99440614
RAC: 0

RE: ...could be a symptom

Message 17108 in response to message 17107

Quote:
...could be a symptom of a BOINC 4.45/Einstein 4.79 incompatibility problem...

Or also, if it continues, could be a symptom of a computer problem - bad RAM, or CPU overheating due to dust buildup or such. I'd first check the temperature of your CPU to make sure it hasn't risen a lot lately, then try the latest beta app, then run a bunch of system diagnostics. A bad transmission of the WU or a bad WU is what I would guess if it only happens once. If it happens again, software is probably more likely than hardware, but checking CPU temp is always a good idea anyway when a heavy load is kept on the CPU.

Ananas
Ananas
Joined: 22 Jan 05
Posts: 272
Credit: 2500681
RAC: 0

#define DBG_TERMINATE_PROCESS

#define DBG_TERMINATE_PROCESS 0x40010004

so it is probably something related to DrWatson or something where DrWatson tried to get control.

Is there an entry in drwtsn32.log that would match the time when the error occured?

The same error number has been reported in most other projects too and with various BOINC versions now and then so it is most likely not specific for Einstein.

One guy seemed to have it only when he started and then immediately stopped the BOINC graphics. If it happens again, you could try to remember if you did something with that too when the crash occured.

If you get it more often, you might want to watch your temperatures with Motherboard Monitor or so.

Jimbo2002
Jimbo2002
Joined: 4 Sep 05
Posts: 11
Credit: 168284363
RAC: 172727

Thanks for all your responses

Thanks for all your responses guys. As far as I can tell the error occured when the computer was completely working on its own. I don't believe anyone did anything to stop the work in progress. But, I have done that on countless occassions and have not had this problem since. I will monitor the CPU temp more closely. I hope it was a work unit glitch.

One day man may become.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.