369x-SANTI_MAR422cap310-8-32-RND5608_0
80 (0x50) Unknown error number

http://www.gpugrid.net/result.php?resultid=7785880

369x-SANTI_MAR422cap310-8-32-RND5608_1
-97 (0xffffffffffffff9f) Unknown error number

http://www.gpugrid.net/result.php?resultid=7788789

thx for your Information.
Installed now the Afterburner.
Hope it will help :-)

I had no problems in the past, neither
with long term, Seti or Einstein
The fans are dust free.
Driver version 334.89

I had no problems in the past, neither
with long term, Seti or Einstein
The fans are dust free.
Driver version 334.89

The Specifications
for the GTX 760:
Thermal and Power Specs(in C):
97 C Maximum GPU Temperature
http://www.geforce.com/hardware/desktop-gpus/geforce-gtx-760/specifications

The normal Temperature under heavy load 80 / 81 C

So what's yer point? You think the tech specs prove that the years of experience skgiven has is wrong? Is that it? Do the tech specs tell you how to crunch GPUgrid?

Your GPU is running too hot and don't bother saying you don't have the problem at other projects because those projects don't work the GPU as hard as this project does.


____________
BOINC <<--- credit whores, pedants, alien hunters

As English is not my native language, feel free to interpret whatever you want in my words.
Anyway, have a nice day.

Killersocke --

I have had 3 tasks with this result - "The simulation has become unstable".

http://www.gpugrid.net/result.php?resultid=7790657
http://www.gpugrid.net/result.php?resultid=7788022
http://www.gpugrid.net/result.php?resultid=7776520

I have no problems with my GPU running other BOINC projects, normal usage, or stress tests.

The error message implies, to me at least, that the program has found a problem with the simulation and has decided to terminate it. I have no problems with that as it is just as valid a result as completing the simulation.

What I do object to is not getting credit for the several hours of work done for each task when there is no apparent fault with my PC.

So I've stopped GPUGRID for the moment at least.

Bob

BobMALCS,

I have come to the conclusion the GPUGrid is that absolute toughest thing I can through at my GPU cards. I would guess that a decision has been made to make the software a little less tolerant that we are normally use to. In a game, a bad colored pixel, a dropped frame, seeing through the wrong layer for example are annoying, but do not crash. As we have seen from Win7, it has another layer added to the video drivers which makes it crash a whole lot less. The bad part is that Win7 just crunches slower than XP and Linux. Of course XP and Linux are stable too. At least with XP, when I pushed the edge too hard on the GPU cards, I would crash the whole thing.

With that, I increase my voltages to run as fast as I can, but still keep the card at <=72C with the noise I can tolerate from the fans. Those squirrel cage fans are a little unbearable for me when they are at 85%, so I slow the overclock a bit to what I can bear (especially in summer). When I finally find the sweet balance, for not getting failed work units from GPU Grid...I also get no other GPU failures for any other software/games I use/play.

Maybe not the best way for things, but it is a bit of a fun challenge. :)

What I do object to is not getting credit for the several hours of work done for each task when there is no apparent fault with my PC.

Thanks for the comments. However my GT760 is overclocked and runs very nicely within its limits. So rather than spending hours trying to tweak it to run GPUGrid and potentially upset a very stable setup I'll just leave GPUGrid well alone.

How to read here I'm not alone with this problem:

http://www.gpugrid.net/forum_thread.php?id=3621#35242

So I've stopped GPUGRID for the moment at least.

angemessen
____________
BOINC <<--- credit whores, pedants, alien hunters

skgiven.

First my setup.
Intel Core i5 Quad 2500K (Sandy Bridge) OC to 4.33GHz.
GTX760 OC to 1097Mhz and 1.2V

I use a small program TThtottle to prevent BOINC tasks driving the CPU temp above 75C and the GPU temp above 70C. Quite often the CPU reaches 75C but it is rare for the GPU to reach 70C.

Of all the programs and BOINC projects I run only GPUGRID fails in any way so as far as I am concerned my system runs nicely.

From what I have read it seems that the only option I have to get GPUGRID to run is to downclock the GPU. If I did that then it will impact the other BOINC projects adversely. So I will not downclock the GPU.

It is, as you say, simple to change the various GPU parameters. However, it takes experience to do it properly. I suspect most people running GPUGRID are not experts nor wish to become one. Also, what you left unspoken, is that it takes many hours of checking, over several GPUGRID tasks, to ensure that the changes have the desired effect and also that other projects and programs still run as well as before.

One final point. It is quite possible to write programs, either deliberately or by accident, that drive a component beyond its safe limits or seriously affect other programs. It looks to me that GPUGRID, in a perfectly reasonable desire for efficiency, is reaching or has reached that point. It is now up to the programmer to seriously consider what and how they are coding.

In summary, getting GPUGRID tasks to run without error is not quite as simple as you make out.

I have no doubt others will, perhaps vehemently, disagree with me. But this is my opinion just as you have yours.

TThrottle is a great problem, however when using it with GPU-crunching it will results in errors. The program does not "slow down" the CPU and GPU usage at a certain rate, but let it run 100% and then only a few % and so on and then CPU and GPU stay cool(er). For at least with GPUGRID tasks this stopping and starting of the WU will let if fail after a while. That is the reason I don't use TThrottle anymore.
With MSI Afterburner you can set the speed of the fan for the GPU nicely and works on any card, any brand, nVidia as well AMD.

If your cards run nice and smooth at GPUGRID then they do on other projects as well you don't have to worry about that.

At last I will not defend anyone, but you can trust skgiven's advice. He it not always lengthy in his explanation and you have to search and try a bit for yourself. But he knows where he is talking about and I have used a lot from his knowledge myself.
____________
Greetings from TJ

skgiven.

First my setup.
Intel Core i5 Quad 2500K (Sandy Bridge) OC to 4.33GHz.
GTX760 OC to 1097Mhz and 1.2V

I use a small program TThtottle to prevent BOINC tasks driving the CPU temp above 75C and the GPU temp above 70C. Quite often the CPU reaches 75C but it is rare for the GPU to reach 70C.

Of all the programs and BOINC projects I run only GPUGRID fails in any way so as far as I am concerned my system runs nicely.

From what I have read it seems that the only option I have to get GPUGRID to run is to downclock the GPU. If I did that then it will impact the other BOINC projects adversely. So I will not downclock the GPU.

It is, as you say, simple to change the various GPU parameters. However, it takes experience to do it properly.

I suspect most people running GPUGRID are not experts nor wish to become one.

Also, what you left unspoken, is that it takes many hours of checking, over several GPUGRID tasks, to ensure that the changes have the desired effect and also that other projects and programs still run as well as before.

One final point. It is quite possible to write programs, either deliberately or by accident, that drive a component beyond its safe limits or seriously affect other programs. It looks to me that GPUGRID, in a perfectly reasonable desire for efficiency, is reaching or has reached that point. It is now up to the programmer to seriously consider what and how they are coding.

In summary, getting GPUGRID tasks to run without error is not quite as simple as you make out.

I have no doubt others will, perhaps vehemently, disagree with me. But this is my opinion just as you have yours.

<sigh>

1 - You know nothing about my skills, ability, or achievements any more than I know about yours.

2 - I will NOT turn this thread into a flame-fest. You can, of course, do whatever makes you feel good.

3 - I will let the readers make up their own minds.

I'm out of here.

Bye.

<sigh>

1 - You know nothing about my skills, ability, or achievements any more than I know about yours.

2 - I will NOT turn this thread into a flame-fest. You can, of course, do whatever makes you feel good.

3 - I will let the readers make up their own minds.

I'm out of here.

Bye.

In summary, getting GPUGRID tasks to run without error is not quite as simple as you make out.

I have no doubt others will, perhaps vehemently, disagree with me. But this is my opinion just as you have yours.

Impressive Jim, those two so 660 stable.
I can get them stable for only a few days and then an error. I tweak the cards, one by one almost every week. Clocks are way down, that the cards run slower then they should. Mine are EVGA's and the fan can run to a maximum of 75%, that is the reason the master GPU is always almost at 75°C.
____________
Greetings from TJ

TJ,

Have you tried to reduce the RAM clock of your card as well?

Also, I have had to increase the power limit (to 110%) of the cards using Nvidia Inspector. In fact, my most recent problem required that I increase the limit more than that. That required downloading the original BIOS using GPU-Z, modifying it using Kepler Bios Tweaker (I set the power limit to 137.5 watts), and then flashing the BIOS of my Zotac GTX 660 using nvflash. It is not for the faint of heart, and I don't think everyone should attempt it. But that is an extreme case because that card didn't have the greatest heatsink to begin with, and most cards don't require going into the BIOS. You can just use Nvidia Inspector (or MSI Afterburner or whatever else you want) for most cases.

Other cards require down-clocking the GPU, and maybe the memory too as RZ points out. So that is why it can get complicated; each card is an individual investigation if you want to get down to zero errors, and I don't think that is really necessary but mention it only to show that it is possible. A lot of the errors blamed on the work units are really due to instabilities of the card because it is being pushed too hard.

TJ,

Have you tried to reduce the RAM clock of your card as well?

Thanks Jim, I know the procedure of updating the GPU BIOS have all the tools but still not done it yet. If I get a second 780Ti I will put the 660 in an older system and then experiment with the BIOS too.
____________
Greetings from TJ