Virtually all my currently failing jobs have this "Found zero 10-12 H-bond term" warning. I have examined other people's results and more than once, the 'buddies' will error out as well. Is it known what side effects this "Found zero 10-12" warning has ? Is it being investigated ? One job (519558) had an out of memory error and was terminated by XP. I had disabled my 'faulty' GPU3, so this is NOT the 'faulty' one. My errors have occurred over several GPUs today. Do we have a GPU testing program ?
____________
Join team Bletchley Park, the innovators.

I.m running on CUDA device: GeForce 9800 GTX/9800 GTX+ (driver version 18608, compute capability 1.1, 1024MB, est. 85GFLOPS)
And have exact the same problem
OS is Vista 64

Only 5% of the wus completes normally

I have been experiencing this type of symptom for quite a while on one of my computers.... which as 2x GTX 260 Core 216 SC...backing off clocking doesn't seem to have helped, nor has reloading the driver, downgrading the driver or upgrading the driver.

I welcome a solution....
____________
Crunching for the benefit of humanity and in memory of my dad and other family members.

i tried every version of driver and still get the same errors, only a few wus finnishing correctly

I turned to run some wus for seti beta and have finnished 40 wus in last 20 hours, none of them had any errors at all

perhaps it would be possible to get some statistics of how many of the returned wus has errors for lets say 2 months time and if this shows a raising grapph of corrupted wus there might be some errors at server side
perhaps also adding info bout OS and CPUs
____________

A bit less than 2 weeks ago I almost constantly had this kind of errors. Backing down the GPU clock (including GPU Memory clock) did resolve the issues. With one exception, everything gpugrid has thrown to the system concerned ever since, ran without a glitch, although a bit slower ....

Please check your driver version. It is possible that very new drivers have problems. You should use the one suggested by Nvidia for CUDA 2.1 unless you have a reason to use another one (for instance a game requiring a new driver).
See the join section. Driver 181.xx are stable.

gdf

I returned all cards to stock speeds but have not crunched since. I did RMA my GPU3 (later GPU5 after swapping slots) card. It showed a hardware failure on one test with OCCT.

I still think there should be a testing / validation program for the shader processors. I found there is a bug in the memtestg80 program. It cannot run the same test on the same GPU twice in a row, the memory allocation always fails and after a little while the allocation fails with an 'unknown error'. This sounds familiar. Installing newer drivers should rule out driver errors on that one.
____________
Join team Bletchley Park, the innovators.

I tried to slow down my GPU processes but there still same problem with WUs from GPU grid
Seti @ hoem beta runs with 100% success.
Feels like waste of time to continue crunching for GPU-grid as long as this problem isn't solved.

core_client_version>6.6.33</core_client_version>
<![CDATA[
<message>
Felaktig funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 9800 GTX/9800 GTX+"
# Clock rate: 1850000 kilohertz
# Total amount of global memory: 1073741824 bytes
# Number of multiprocessors: 16
# Number of cores: 128
# Amber: readparm : Reading parm file parameters
# PARM file in AMBER 7 format
# Encounter 10-12 H-bond term
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
MDIO ERROR: cannot open file "restart.coor"
------------
<core_client_version>6.6.33</core_client_version>
<![CDATA[
<message>
Felaktig funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 9800 GTX/9800 GTX+"
# Clock rate: 1850000 kilohertz
# Total amount of global memory: 1073741824 bytes
# Number of multiprocessors: 16
# Number of cores: 128
MDIO ERROR: cannot open file "restart.coor"

Hi, not sure, the absence of GPU3 may have something to do with it too. I currently have the remaining 6 mildly overclocked to 633 (as that is an evga advertized speed for G200 based cards). So far so good. GPU3(5) has been RMA'd and its slot is currently empty. Fans are at 89% with temperatures not over 65c. It was not a power issue as there is plenty.

Also not a driver issue (at least not with 3 cards) because it still is the same driver.

I may try linux 64 today.

regards H.

@Hydro: seems like you're back up'n running. Was it "just" the downclocking?

@Ulf: you reverted to the older 182.50 driver, which is known to be good and you still have the error. So it does not look like software. I'd suppose hardware, although you also already tried downclocking. Further evidence: your WUs take a long time until they fail, which is typical for temperature / hardware failures just at the edge of stability.

Hydro wrote:

Is it known what side effects this "Found zero 10-12" warning has ? Is it being investigated ?

I think Ignasi said this warning is nothing to worry about (for us). Sounds like "no side effects are known".

MrS

Ubuntu 8 failed installation because of:
MP-BIOS bug, 8254 timer not connected to IO-APIC

Ubuntu 9 failed because it cannot detect my CD ROM, after booting from CD ROM...

____________
Join team Bletchley Park, the innovators.

Same error. Gpu isn't oc'ed and driver version is 182.08.

cheers
Mika

The error is caused by "Cuda error: Kernel [frc_sum_nb_forces] failed in file 'f
". Not much overclocked at 1700 MHZ compared to stock 1650 for a GTS 8800.

Again I think, even for overclocking tests, a good shader testing program would be useful.
____________
Join team Bletchley Park, the innovators.

Your error "Incorrect function. (0x1) - exit code 1 (0x1)" is a very general one which, roughly speaking, can happen due to anything going wrong during the calculation.

MrS

That's what I mean only 3 %.
____________
Join team Bletchley Park, the innovators.