Thanks, but it was a couple "simulation became unstable" errors, which I believe to be a problem with the GPUGrid application.

I think it's safe to promote the CUDA6.5 application to the long queue.

Not just yet...

Are we waiting for your GTX980 to arrive?

I think it's safe to promote the CUDA6.5 application to the long queue.

Not just yet...

Are we waiting for your GTX980 to arrive?

It's probably due to me overclocking my GTX980. I had several tasks fail while I was at work yesterday. Since I clocked back, I've had 4 short run tasks complete successfully.

My apologies for messing up the beta test.

I had another failure, where simulation became unstable on a 8.46 Cuda 6.5 beta task. http://www.gpugrid.net/result.php?resultid=13161365

I am not entirely convinced that the error is the fault of the task or the application. Perhaps the new 344.11 drivers push the GPUs even harder than previous drivers. I will do additional testing, with Heaven, to attempt to confirm.

Thanks,
Jacob

Name 30-MJHARVEY_TEST1999-5-10-RND7983_0
Workunit 10132352
Created 2 Oct 2014 | 16:49:51 UTC
Sent 2 Oct 2014 | 21:36:23 UTC
Received 2 Oct 2014 | 22:20:50 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status -97 (0xffffffffffffff9f) Unknown error number
Computer ID 153764
Report deadline 7 Oct 2014 | 21:36:23 UTC
Run time 386.44
CPU time 100.75
Validate state Invalid
Credit 0.00
Application version ACEMD beta version v8.46 (cuda65)
Stderr output

<core_client_version>7.4.22</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -97 (0xffffff9f)
</message>
<stderr_txt>
# GPU [GeForce GTX 660 Ti] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 2 :
# Name : GeForce GTX 660 Ti
# ECC : Disabled
# Global mem : 3072MB
# Capability : 3.0
# PCI ID : 0000:08:00.0
# Device clock : 1045MHz
# Memory clock : 3004MHz
# Memory width : 192bit
# Driver version : r343_98 : 34411
# GPU 0 : 69C
# GPU 1 : 64C
# GPU 2 : 70C
# GPU 1 : 65C
# GPU 1 : 66C
# GPU 1 : 67C
# BOINC suspending at user request (exit)
# GPU [GeForce GTX 660 Ti] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 2 :
# Name : GeForce GTX 660 Ti
# ECC : Disabled
# Global mem : 3072MB
# Capability : 3.0
# PCI ID : 0000:08:00.0
# Device clock : 1045MHz
# Memory clock : 3004MHz
# Memory width : 192bit
# Driver version : r343_98 : 34411
# GPU 0 : 62C
# GPU 1 : 58C
# GPU 2 : 54C
# GPU 0 : 63C
# GPU 1 : 59C
# GPU 2 : 55C
# GPU 0 : 64C
# GPU 1 : 60C
# GPU 2 : 56C
# GPU 0 : 65C
# GPU 2 : 57C
# GPU 0 : 66C
# GPU 1 : 61C
# GPU 2 : 58C
# GPU 2 : 59C
# GPU 0 : 67C
# GPU 1 : 62C
# GPU 2 : 60C
# GPU 2 : 61C
# GPU 0 : 68C
# GPU 1 : 63C
# GPU 2 : 62C
# GPU 2 : 63C
# GPU 0 : 69C
# GPU 1 : 64C
# GPU 2 : 64C
# GPU 2 : 65C
# GPU 0 : 70C
# GPU 0 : 71C
# GPU 1 : 65C
# GPU 2 : 66C
# GPU 1 : 66C
# GPU 2 : 67C
# GPU 0 : 72C
# GPU 1 : 67C
# GPU 2 : 68C
# The simulation has become unstable. Terminating to avoid lock-up (1)
# Attempting restart (step 12630000)
# GPU [GeForce GTX 660 Ti] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 2 :
# Name : GeForce GTX 660 Ti
# ECC : Disabled
# Global mem : 3072MB
# Capability : 3.0
# PCI ID : 0000:08:00.0
# Device clock : 1045MHz
# Memory clock : 3004MHz
# Memory width : 192bit
# Driver version : r343_98 : 34411
# The simulation has become unstable. Terminating to avoid lock-up (1)

</stderr_txt>
]]>

I don't think the 344.11 driver is pushing the cards harder as with this driver my 780Ti's are around 700 seconds slower than with the 331 driver I used until 309 September when I was forced to update as I got errors with the new app. See below in this thread.

---

Greetings from TJ

Hello - I have noticed that my dual gtx 780 machine has been getting mostly beta tasks lately - only 2 short runs and no long runs over the past few days ? I even set my prefs to no beta and no other apps but still pulling only beta tasks?

My other 3 systems on the account - gtx 770 & 660 do not show any beta tasks?

Just curious

I too seem to only be getting Beta, even though I've re-enabled all applications. Is the scheduler prioritizing the Beta application somehow?

I don't think the 344.11 driver is pushing the cards harder as with this driver my 780Ti's are around 700 seconds slower than with the 331 driver I used until 309 September when I was forced to update as I got errors with the new app. See below in this thread.

With new technologies being added to 343 branch driver for Second Generation Maxwell GM204: Dynamic Super Resolution, Third Generation Delta Color Compression, Multi-Pixel Programming Sampling, NVidia VXGI (Real-Time-Voxel-Global Illumination), VR Direct, Multi-Projection Acceleration, and Multi-Frame Sampled Anti-Aliasing(MFAA) with support for CSAA removed. HDMI 2.0 support was also added.

I'd say this driver branch is not fully complete yet. A couple more releases should find driver's full potential. Considering how support for pre-Fermi cards were dropped, and amount differences between SM/SMX/SMM, these first 343 branch drivers have room to be refined.

Matt:

I even think the canary behavior works better for me now. I tried the scenario where it was failing on the 8.41 app, and now it worked fine without failure on the 8.46 beta app.

Can you please explain, in detail, how the canary behavior was changed? How exactly does behave in 8.46?

Thanks,
Jacob

Any answer on this?

Can you please explain, in detail, how the canary behavior was changed? How exactly does behave in 8.46?

It doesn't. I've disabled it altogether. I'm counting on the newer drivers to do a better job at recovering from deadlocks.

Matt

Sound good to me. If you ever decide to re-add it, or modify its functionality, please be sure to let us know.

Thanks,
Jacob

Can you please explain, in detail, how the canary behavior was changed? How exactly does behave in 8.46?

It doesn't. I've disabled it altogether. I'm counting on the newer drivers to do a better job at recovering from deadlocks. Matt

Thanks much for disabling that feature, I've lost a lot of WUs to it :-)