Thanks Matt great work with the application.

Time to do some work with Pascal.

Ok, Pascal app is live on acemdlong now.

Great news!
I've got one PABLO_SH2TRIPEP_T_TRI running.
GPU: GTX 1080@2000MHz, GDDR5X@4763MHz
GPU usage: 75~78%, GPU bus usage: 23~27%
GPU power: 56%
Estimated completion time: 13.684sec
A similar workunit on a GTX980Ti under Windows XP took 12.052sec. (that is 13.5% faster)

Suspend long workunits no problem ether.

Next target will be to test for linux

I just caught outta the corner of my eye something Trend-Micro picked up when starting a Pascal WU.

I tried to see what pinged Trend and where it copied it to but I can't seem to find in all the settings what it was and where it went. Hopefully Trend isn't coming up with false positives and it doesn't affect results.

Anyone else getting this on Antivirus programs? I may need to dig deeper and see if I can tell Trend to ignore anything coming / going outta my BOINC directories.

I just caught outta the corner of my eye something Trend-Micro picked up when starting a Pascal WU.

I tried to see what pinged Trend and where it copied it to but I can't seem to find in all the settings what it was and where it went. Hopefully Trend isn't coming up with false positives and it doesn't affect results.

Anyone else getting this on Antivirus programs? I may need to dig deeper and see if I can tell Trend to ignore anything coming / going outta my BOINC directories.

No issue with windows defender.

Looking at my GPU with GPU Tweak from Asus and it looks like my GPU is only working at 60% of his capacity. I have a GTX1070 Strix. Feel Free to contact me if needed.

Jonathan Bacon

Linux app is live now.

I just caught outta the corner of my eye something Trend-Micro picked up when starting a Pascal WU.

I tried to see what pinged Trend and where it copied it to but I can't seem to find in all the settings what it was and where it went. Hopefully Trend isn't coming up with false positives and it doesn't affect results.

Anyone else getting this on Antivirus programs? I may need to dig deeper and see if I can tell Trend to ignore anything coming / going outta my BOINC directories.

No issue with windows defender.

No issue with Kaspersky...

---

I would love to see HCF1 protein folding and interaction simulations to help my little boy... someday.

Linux app is live now.

866999 GPUGRID 11/1/2016 2:58:03 PM Sending scheduler request: To fetch work.
867000 GPUGRID 11/1/2016 2:58:03 PM Requesting new tasks for CPU and Miner ASIC and NVIDIA GPU
867001 GPUGRID 11/1/2016 2:58:06 PM Scheduler request completed: got 0 new tasks
867002 GPUGRID 11/1/2016 2:58:06 PM No tasks sent
867003 GPUGRID 11/1/2016 2:58:06 PM No tasks are available for Short runs (2-3 hours on fastest card)
867004 GPUGRID 11/1/2016 2:58:06 PM No tasks are available for Long runs (8-12 hours on fastest card)

GTX 1060. Am I missing something?

GTX 1060. Am I missing something?

Working now.

GTX 1060. Am I missing something?

Working now.

Thanks

Seems to be working for me (GTX 1060) but GPU usage is only at 70%? I don't know if this is related but in BOINC it says Running 0.975 CPUs and 1 Nvidia GPU. I have a 4 core CPU so it should be using 1 full core no? I tried changing in GPUGRID "Maximum CPU for graphics" to 100 but no difference.

Have you tried suspending the stalled task and then resuming it? POEM used to do the same thing and suspending/resuming usually got the task moving again.

I did, it didn't help. Only restart does the trick.

It sounds like the card downclocked itself. It happens when you (or the factory) overclock your card too much.

It is not overclocked. And the behaviour is really strange. Yesterday in the morning my computer started long WU. After 4h it was 60% done, remaining time 3h with some minutes. Everything great to this point, right? But two hours later it was still 60% and remaining time was just "-- --", GPU at 250Mhz and IDLE. So I restarted BM, WCG started, GPUGRID "waiting to start" for about an hour. So I restarted computer, it was crunching again from 60% but this time no problem. Until today when I saw that the same WU has 90% processed, remaining time "-- --", GPU idle... Restarted computer again and it was ended and uploaded.

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

Reported with run time of 14h, in reality it was almost 25. I will update the driver to the newest version cause I don't have any other ideas.

I've received a task for my 1080 on a Win7 x64 host. Currently at ~57%GPU usage and ~35% power level. About 70% complete after a little over two hours. The card has not boosted and is running at base clock of 1708MHz.

Manually managed the hanging download issues and ran a few tasks. 4 short tasks completed in 464-537 seconds but another listed as a short task took 13,764 seconds. What's up with that?
GTX 1060 at stock settings, Ubuntu 16.04 LTS, driver 367.35.

Upon further inspection it seems that the longer running task had 5 million steps where the other 4 had only 250k.

It is not overclocked. And the behaviour is really strange. Yesterday in the morning my computer started long WU. After 4h it was 60% done, remaining time 3h with some minutes. Everything great to this point, right? But two hours later it was still 60% and remaining time was just "-- --", GPU at 250Mhz and IDLE. So I restarted BM, WCG started, GPUGRID "waiting to start" for about an hour. So I restarted computer, it was crunching again from 60% but this time no problem. Until today when I saw that the same WU has 90% processed, remaining time "-- --", GPU idle... Restarted computer again and it was ended and uploaded.

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

Reported with run time of 14h, in reality it was almost 25. I will update the driver to the newest version cause I don't have any other ideas.

Looking at your task's stderr.txt there's no "exit" messages, so it seems that either the ACEMD app stops (crashes), or it gets disconnected from the GPU. Do you have multiple user accounts on that PC? Switching users could cause such behavior (as the GPU is switched over to the another user, while the BOINC manager still runs as the original user).
Is there anything suspicious in the BOINC manager's event log?

Linux app is live now.

What driver version is needed to use the CUDA8.5 (Linux) app?

It is not overclocked. And the behaviour is really strange. Yesterday in the morning my computer started long WU. After 4h it was 60% done, remaining time 3h with some minutes. Everything great to this point, right? But two hours later it was still 60% and remaining time was just "-- --", GPU at 250Mhz and IDLE. So I restarted BM, WCG started, GPUGRID "waiting to start" for about an hour. So I restarted computer, it was crunching again from 60% but this time no problem. Until today when I saw that the same WU has 90% processed, remaining time "-- --", GPU idle... Restarted computer again and it was ended and uploaded.

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

Reported with run time of 14h, in reality it was almost 25. I will update the driver to the newest version cause I don't have any other ideas.

Looking at your task's stderr.txt there's no "exit" messages, so it seems that either the ACEMD app stops (crashes), or it gets disconnected from the GPU. Do you have multiple user accounts on that PC? Switching users could cause such behavior (as the GPU is switched over to the another user, while the BOINC manager still runs as the original user).
Is there anything suspicious in the BOINC manager's event log?

I am the only user of this PC. And it happens even when I am working on it. Driver updated - no change, GPU clock lowered by 200Mhz - no change. Folding@home works flawless. I have no idea what else I could do.

Linux app is live now.

What driver version is needed to use the CUDA8.5 (Linux) app?

The newest I could find for Linux is 367.44. I'm currently using 367.35 and the completed tasks I have show v9.14 (CUDA 80) as the app. Don't know if the newest driver would make use of 8.5 but since I've had too many gnarly experiences with video driver updates I'm not going to play guinea pig on this one. Maybe someone who has already updated to 367.44 can chime in.

I am the only user of this PC. And it happens even when I am working on it. Driver updated - no change, GPU clock lowered by 200Mhz - no change. Folding@home works flawless. I have no idea what else I could do.

Windows at times has video driver timeout issues with XP, Vista, 7, 8 and 8.1 but that was with ATI cards. If you're using Win10 I have no experience with that OS. Never heard of it happening with Nvidia but that doesn't mean it couldn't. Try this and see if it helps. If it doesn't work it should not affect your computer in any way but to be super safe and eliminate "murphy's law" you could image your drive before you start if it would make you more comfortable. I've shown this fix many times to others without a single problem reported.

Copy and paste ALL of the text below as is into notepad. Rename the file timeoutfix.reg(or another name if you like). Now double click on it. You'll be prompted about adding files to the registry. Just click yes on any that appear. Now restart your computer. If your strange behavior stops then it was a timeout issue. If not then it's something else. If it doesn't work you can always go back and delete the reg entries if you're not comfortable leaving them there.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog]
"DisableBugCheck"="1"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog\Display]
"EaRecovery"="0"