Would it be possible to add something to the client, which checks, if there is a hardware failure, like a to far overclocked cpu? <br>I think of running one \"control timestep\" every model-month or so. Then the calculated result of this timestemp is compared with the correct result. If the calculated differs from the correct one, the client gives a error message and stops working. That would probably help to avoid some short runs.

Unfortunately, that only partially solves one of the problems. Many people are running significantly overclocked and stable. Poorly maintained PCs, PCs with poor RAM, PCs with inadequate HeatSink/Fans or case cooling, PCs running CPUs in spec but trying to eek the most out of their RAM by decreasing timings, all can also go unstable. No way to test for those.

&gt; Unfortunately, that only partially solves one of the problems. Many people
&gt; are running significantly overclocked and stable. Poorly maintained PCs, PCs
&gt; with poor RAM, PCs with inadequate HeatSink/Fans or case cooling, PCs running
&gt; CPUs in spec but trying to eek the most out of their RAM by decreasing
&gt; timings, all can also go unstable. No way to test for those.
&gt;
&gt;
This "control timestep" should be like a normal timestep. The only difference is that the variables (temp, pressure, ...) at the beginning of this step are always the same and the correct variables after this step are known. If the pc calculates something different, the pc is faulty. This may be due to cpu, ram or something else. <br>
But, it's probably no easy to implement it into the client.

&gt; This "control timestep" should be like a normal timestep. The only difference
&gt; is that the variables (temp, pressure, ...) at the beginning of this step are
&gt; always the same and the correct variables after this step are known. If the pc
&gt; calculates something different, the pc is faulty. This may be due to cpu, ram
&gt; or something else. <br>
&gt; But, it's probably no easy to implement it into the client.
&gt;
&gt;
Ahh. I misread your post. It's probably have to run for awhile to get the CPU/RAM heated up in order to catch those problems. I wish the CPDN team would recommend, maybe in the signup page, running Prime95 for 8 hrs and memtest86+ for 8 hrs in order to see if the system is stable enough to run CPDN.