I'm starting to get a high number or short tasks that error out. Can someone explain why this is happening and how I can fix it? Have changed no settings.
Here is the log from one of the tasks.
WinXP SP3 dual 750Ti



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

I am getting errors too, but mine are with GERARD_EQUI WU's. Three had errors, two finished ok. It seems to be bad batch.

https://www.gpugrid.net/result.php?resultid=14210451



895456x4-GERARD_EQUI_26Apr_CXCL-0-1-RND0321_4
Workunit 10949024
Created 26 May 2015 | 23:34:38 UTC
Sent 26 May 2015 | 23:34:54 UTC
Received 26 May 2015 | 23:50:42 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status -97 (0xffffffffffffff9f) Unknown error number
Computer ID 30790
Report deadline 31 May 2015 | 23:34:54 UTC
Run time 87.09
CPU time 77.31
Validate state Invalid
Credit 0.00
Application version Short runs (2-3 hours on fastest card) v8.47 (cuda65)
Stderr output
<core_client_version>7.4.42</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -97 (0xffffff9f)
</message>
<stderr_txt>
# GPU [GeForce GTX 690] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 1 :
# Name : GeForce GTX 690
# ECC : Disabled
# Global mem : 2047MB
# Capability : 3.0
# PCI ID : 0000:05:00.0
# Device clock : 1019MHz
# Memory clock : 3004MHz
# Memory width : 256bit
# Driver version : r343_98 : 34411
# GPU [GeForce GTX 690] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 1 :
# Name : GeForce GTX 690
# ECC : Disabled
# Global mem : 2047MB
# Capability : 3.0
# PCI ID : 0000:05:00.0
# Device clock : 1019MHz
# Memory clock : 3004MHz
# Memory width : 256bit
# Driver version : r343_98 : 34411
# GPU [GeForce GTX 690] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 1 :
# Name : GeForce GTX 690
# ECC : Disabled
# Global mem : 2047MB
# Capability : 3.0
# PCI ID : 0000:05:00.0
# Device clock : 1019MHz
# Memory clock : 3004MHz
# Memory width : 256bit
# Driver version : r343_98 : 34411
# GPU [GeForce GTX 690] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 0 :
# Name : GeForce GTX 690
# ECC : Disabled
# Global mem : 2047MB
# Capability : 3.0
# PCI ID : 0000:04:00.0
# Device clock : 1019MHz
# Memory clock : 3004MHz
# Memory width : 256bit
# Driver version : r343_98 : 34411
# GPU 0 : 63C
# GPU 1 : 73C
# The simulation has become unstable. Terminating to avoid lock-up (1)

I'm getting some nasty errors too, with the GERARD_EQUI_26Apr_CXCL tasks. They're causing major TDRs, which in turn then make the computer have hardware acceleration problems in other tasks (like web browsing, or gaming), and also cause driver problems where the clocks never go back to 3d-mode clocks.

Admins: Please look into which batches need to be revoked, to prevent these problems. It's a major headache, for me at least.

1154144x3-GERARD_EQUI_26Apr_CXCL-0-1-RND9216_7
http://www.gpugrid.net/result.php?resultid=14210052
895456x5-GERARD_EQUI_26Apr_CXCL-0-1-RND9089_5
http://www.gpugrid.net/result.php?resultid=14210507

All my tasks are now erroring out. Suspending this project for now until this issue is resolved.

I've actually been having issues with the Graphics drivers themselves crashing and windows having to recover.

Same here. Now have five GERARD_EQUI_26Apr_CXCL tasks crashed.

Could you please post your errors in this thread? I will cancel the batch if they persist. Thanks for your patience...

https://www.gpugrid.net/result.php?resultid=14210324
Short WU errored after 80sek at 750Ti.

Could you please post your errors in this thread? I will cancel the batch if they persist. Thanks for your patience...

We detected an unexpected parameterization error in some of the simulations and we just cancelled them. Sorry for any inconvience caused and thank your for reporting it to us! If you find any other errors please do not hesitate to tell us (hopefully this particular issue is already resolved).

Excellent. Thank you!!

All short run tasks still failing here. Links to last 4

https://www.gpugrid.net/result.php?resultid=14213349

https://www.gpugrid.net/result.php?resultid=14211957

https://www.gpugrid.net/result.php?resultid=14211914

https://www.gpugrid.net/result.php?resultid=14211712

nanoprobe:

What is the exact make/model of your GPU? Do the tasks still fail when the Boost clock is set to the reference clock? My hunch is that your GPU is overclocked too much, either by the factory or by you.

"The simulation has become unstable. Terminating to avoid lock-up"
... generally means that you are overclocking too much, or have a hardware problem... from my experience.

Excellent. Thank you!!

nanoprobe:

What is the exact make/model of your GPU? Do the tasks still fail when the Boost clock is set to the reference clock? My hunch is that your GPU is overclocked too much, either by the factory or by you.

"The simulation has become unstable. Terminating to avoid lock-up"
... generally means that you are overclocking too much, or have a hardware problem... from my experience.

1232906x8-GERARD_EQUI_26Apr_CXCL-0-1-RND1418_4 causes a lot of crash of gpu drivers. Stopped!

nanoprobe:

Can you supply the exact model of the GPU, to confirm that it's not factory-overclocked?

Alternatively, could you use GPU-Z to confirm that the GPU Clock and Default Clock say 1020 MHz (which is the stock speed of a GTX 750 Ti, per http://en.wikipedia.org/wiki/GeForce_700_series)

If it's anything above 1020, then it is in fact overclocked, and I recommend using EVGA Precision X to downclock it back to reference 1020 MHz, to see if it helps.

I'm getting frustrated trying to help by offering advice that gets ignored.

nanoprobe:

[quote]I'm getting frustrated trying to help by offering advice that gets ignored.

I have had over 20 WUs fail...on my GTX 660 Ti devices. I will stop gettings tasks and now go to bed....

nanoprobe:

[quote]I'm getting frustrated trying to help by offering advice that gets ignored.

WOW! Let me offer you some advise. If it doesn't concern life, death or health then is surely isn't worth getting frustrated over.

FWIW the issue seems to have cleared up. The faulty WUs have been taken care of. Thanks for your help.

There were some faulty WUs, but they have nothing to do with tasks erroring out with "Simulation has become unstable." messages and no other error messages.

Errors like yours are usuall a result of overclocking too much.

The problem is still ongoing, for you.
See: https://www.gpugrid.net/result.php?resultid=14213909
# The simulation has become unstable. Terminating to avoid lock-up (1)

I know you said there is no factory overclock, but I still would love to know what GPU-Z says for your "GPU Clock" and "Default Clock". If you refuse to share, so be it. And if it's anything above 1020, then it is in fact overclocked.

Jacob:
We are all very well aware of the idea of overclocking.
But , honestly : Are you really thinking I will and need to shut down my system to get the GPU- stuff running ? Really ?
Let´s put it that way: If GPU -stuff is not running properly on a majority of systems and several users have the same experience and we ( the users ) do that for free - we shut down a over all properly running system for that ?
I really don´t think so.
I my opinion, if GPU do not work - make them work instead of begging on the overclocking stuff.
If GPU will not work properly, I simply switch to something else - you know, MY PC, MY time, MY decission.
Or to use a proverb: Not my circus , not my monkeys.

Kind regards,

I have definitely had certain GPU things, such as games and GPUGrid tasks, crash or error ("Simulation has become unstable"), as a direct result of a factory-overclock that was too aggressive. If the GPU is overclocked at all, and you are trying to resolve any GPU problem, you should see if lowering the clocks resolves the problem.

Yes, honestly.

I have 3 factory-overclocked GPUs. GPU 1 was factory-overclocked way too aggressively, and I've had to dial it back quite a bit to be completely stable in my games and with GPUGrid. GPU 2 was factory-overclocked too little, and I could push it even farther before noticing problems. And GPU 3 was factory-overclocked just right.

Forgive me for trying to help.

Jacob:
We are all very well aware of the idea of overclocking.
But , honestly : Are you really thinking I will and need to shut down my system to get the GPU- stuff running ? Really ?

Let´s put it that way: If GPU -stuff is not running properly on a majority of systems and several users have the same experience and we ( the users ) do that for free - we shut down a over all properly running system for that ?

I really don´t think so.
I my opinion, if GPU do not work - make them work instead of begging on the overclocking stuff.

If GPU will not work properly, I simply switch to something else - you know, MY PC, MY time, MY decission.
Or to use a proverb: Not my circus , not my monkeys.

The problem is still ongoing, for you.
See: https://www.gpugrid.net/result.php?resultid=14213909
# The simulation has become unstable. Terminating to avoid lock-up (1)

I know you said there is no factory overclock, but I still would love to know what GPU-Z says for your "GPU Clock" and "Default Clock". If you refuse to share, so be it. And if it's anything above 1020, then it is in fact overclocked.

Please keep my advice (use lower clocks) in mind, the next time you try to troubleshoot any GPU errors.

Please keep my advice (use lower clocks) in mind, the next time you try to troubleshoot any GPU errors.