pc keeps dumping units

[RETARD]

I have a dual boot windows / Ubuntu 10.10
4Gb DDR3

The OS itself is stable but dumps these errors on me now and then.
On the smaller BA units as well as the larger ones 6900 & 6903 for eg.
I have another machine identical to this that floats along no problems
I have thought that it could be the clock speed of the CPU but having wound both the memory and cpu timings right back still produces the error.
I have with & without GPU aswell.

a summation of the error is below. (sometimes at the beginning, sometimes after a day or 2)

Code: Select all

[10:02:24] Project: 6903 (Run 3, Clone 6, Gen 16)

[10:02:46] Completed 765 out of 250000 steps  (0%)

step 4001399: Water molecule starting at atom 573289 can not be settled.
Check for bad contacts and/or reduce the timestep if appropriate.

step 4001400: Water molecule starting at atom 652852 can not be settled.
Check for bad contacts and/or reduce the timestep if appropriate.

step 4001400: Water molecule starting at atom 2431945 can not be settled.
Check for bad contacts and/or reduce the timestep if appropriate.

step 4001400: Water molecule starting at atom 573289 can not be settled.
Check for bad contacts and/or reduce the timestep if appropriate.
Segmentation fault
[10:15:20] CoreStatus = 8B (139)
[10:15:20] Client-core communications error: ERROR 0x8b
[10:15:20] Deleting current work unit & continuing...

Anyways to help resolve would be greatly appreciated

[orion]

Run Memtest86+ and see if you get any errors that way on the memory.

[P5-133XL]

You claim the system is stable but then give evidence that it isn't. May I suggest that you remove any OC'ing and see if that helps. Also, Memtest86+ is a good recommendation too. Monitoring temps is good.

[Grandpa_01]

I have found that the error you received is usually associated with memory problems, I would not necessary say bad memory but your settings may be too tight for the speed you are running at. Also I have seen the error one time from not enough V for the CPU for the OC but I was using a high BCLK when that happened. Any way I would back the OC off a little and go from there. If you are not OCed I would look at possibly bad memory or low v to the memory.