I'm loading a first batch of 1000 workunits for a new project (GSN*) on the acemd3 app. This batch is both for a basic science investigation, and for load-testing the app. Thanks!

If you disabled "acemd3" from the preferences for some reason, please re-enable it.

Hi,
my first new WU stop at 1% after 20 minutes of running.
I suspended and restart it, the elapsed time restart from 0.
After another 20 minutes of running, without increase of working progress i kill it.
For investigation see http://www.gpugrid.net/result.php?resultid=21501927
Thanks in advance.
K.

---

Dreams do not always come true. But not because they are too big or impossible. Why did we stop believing.
(Martin Luther King)

Thank you Toni!

I already have my GTX 1070/1080 GPU's pegged to nearly 100% even with one WU running on each.

The GPU load does drop lower intermittently and also will drop PerfCap to Idle.

The new thing I am noticing is I am now hitting the Power PerfCap throttling the GPU's.

Hi,
my first new WU stop at 1% after 20 minutes of running.
I suspended and restart it, the elapsed time restart from 0.
After another 20 minutes of running, without increase of working progress i kill it.
For investigation see http://www.gpugrid.net/result.php?resultid=21501927
Thanks in advance.
K.

[PUGLIA] kidkidkid3

It would help a lot to know what your setup looks like. Your computers are hidden so we can't see them. Also, the configuration may make a difference

Please provide some details.

Sorry for mistake of configuration

Intel Quadcore Q9450 with 4GB (2*2 DDR3 at 1333) and GTX 750 TI

... here the log.

Output su Stderr
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
aborted by user</message>
<stderr_txt>
19:10:11 (2408): wrapper (7.9.26016): starting
19:10:11 (2408): wrapper: running acemd3.exe (--boinc input --device 0)
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {1583} normal block at 0x0000020099013380, 8 bytes long.
Data: < > 00 00 F9 98 00 02 00 00
..\lib\diagnostics_win.cpp(417) : {198} normal block at 0x0000020099011BA0, 1080 bytes long.
Data: <( ` > 28 11 00 00 CD CD CD CD 60 01 00 00 00 00 00 00
Object dump complete.

</stderr_txt>

---

Dreams do not always come true. But not because they are too big or impossible. Why did we stop believing.
(Martin Luther King)

Sorry for mistake of configuration ... here the log.

Output su Stderr
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
aborted by user</message>
<stderr_txt>
19:10:11 (2408): wrapper (7.9.26016): starting
19:10:11 (2408): wrapper: running acemd3.exe (--boinc input --device 0)
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {1583} normal block at 0x0000020099013380, 8 bytes long.
Data: < > 00 00 F9 98 00 02 00 00
..\lib\diagnostics_win.cpp(417) : {198} normal block at 0x0000020099011BA0, 1080 bytes long.
Data: <( ` > 28 11 00 00 CD CD CD CD 60 01 00 00 00 00 00 00
Object dump complete.

</stderr_txt>
]]>

OK so I can check on the link to the computer and I see you have 2x GTX 750 Ti's
http://www.gpugrid.net/show_host_detail.php?hostid=208691

I'm not sure a GTX 750 series can run the new app. Let's see if one of the resident experts will know the answer.

I'm not sure a GTX 750 series can run the new app. Let's see if one of the resident experts will know the answer.

the strange thing with my hosts here is that the host with the GTX980ti and the host with the GTX970 received the new ACEMD v2.10 tasks this evening, but the two hosts with a GTX750ti did NOT. Was this coincidence, or is the new version not being sent to GTX750ti cards?

I'm not sure a GTX 750 series can run the new app

I can confirm that I've finished successfully ACEMD3 test tasks on GTX750 and GTX750Ti graphics cards running under Linux OS.
I can also remark that I had some troubles under Windows 10 regarding some Antivirus interference.
This was commented at following thread:
http://www.gpugrid.net/forum_thread.php?id=4999

Was this coincidence, or is the new version not being sent to GTX750ti cards?

Please, try updating drivers

Just starting a task on my GTX 1050TI (fully updated drivers, no overdrive, default settings)
Been running 30 mins and it did 2% finally.
You should change something in the code so it spits out decimal update % done information. I use that to check if the task is moving in Boinc Tasks.
Your config only updates the 1-x% and no decimal.
Memory usage is minimal compared to LHC ATLAS. You use only 331 MB real memory and 648 Virtual, which is more in the range of what Rosetta uses.
So it looks like I should have this task done in about 26 hrs from now.
For a GPU task it is taking a lot of CPU, it needs 100%+ all the time in CPU usage.

Hi, I'm running test 309 on an i7-860 with one GTX 750Ti and ACEMD 3 test is reporting 4.680%/Hr.
Better than my GTX 1060 and i7-7700K running test 725 @ 4.320%/Hr.
Why does the GTX 1060 run slower, Toni, anybody?
(running latest drivers)

---

"Together we crunch
To check out a hunch
And wish all our credit
Could just buy us lunch"

Piasa Tribe - Illini Nation

I got this one today http://www.gpugrid.net/workunit.php?wuid=16850979 and it ran fine. As I've said before, Linux machines are quite ready.

Three finished so far, working on a fourth. Keep 'em coming.

Got one task. GTX1060 with Max-Q. Windows 10. Task errored out. Following is the complete story.
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code 195 (0xc3)</message>
<stderr_txt>
23:16:17 (1648): wrapper (7.9.26016): starting
23:16:17 (1648): wrapper: running acemd3.exe (--boinc input --device 0)
# Engine failed: Error invoking kernel: CUDA_ERROR_ILLEGAL_ADDRESS (700)
02:43:35 (1648): acemd3.exe exited; CPU time 12377.906250
02:43:35 (1648): app exit status: 0x1
02:43:35 (1648): called boinc_finish(195)
0 bytes in 0 Free Blocks.
506 bytes in 8 Normal Blocks.
1144 bytes in 1 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 0 bytes.
Total allocations: 184328910 bytes.
Dumping objects ->
{1806} normal block at 0x000001C10FAA6190, 48 bytes long.
Data: <ACEMD_PLUGIN_DIR> 41 43 45 4D 44 5F 50 4C 55 47 49 4E 5F 44 49 52
{1795} normal block at 0x000001C10FAA6350, 48 bytes long.
Data: <HOME=D:\ProgramD> 48 4F 4D 45 3D 44 3A 5C 50 72 6F 67 72 61 6D 44
{1784} normal block at 0x000001C10FAA6580, 48 bytes long.
Data: <TMP=D:\ProgramDa> 54 4D 50 3D 44 3A 5C 50 72 6F 67 72 61 6D 44 61
{1773} normal block at 0x000001C10FAA6120, 48 bytes long.
Data: <TEMP=D:\ProgramD> 54 45 4D 50 3D 44 3A 5C 50 72 6F 67 72 61 6D 44
{1762} normal block at 0x000001C10FAA5CC0, 48 bytes long.
Data: <TMPDIR=D:\Progra> 54 4D 50 44 49 52 3D 44 3A 5C 50 72 6F 67 72 61
{1751} normal block at 0x000001C10FA8A0B0, 141 bytes long.
Data: <<project_prefere> 3C 70 72 6F 6A 65 63 74 5F 70 72 65 66 65 72 65
..\api\boinc_api.cpp(309) : {1748} normal block at 0x000001C10FAA86C0, 8 bytes long.
Data: < > 00 00 A4 0F C1 01 00 00
{977} normal block at 0x000001C10FA8D840, 141 bytes long.
Data: <<project_prefere> 3C 70 72 6F 6A 65 63 74 5F 70 72 65 66 65 72 65
{203} normal block at 0x000001C10FAA8CB0, 8 bytes long.
Data: < > 10 BB AA 0F C1 01 00 00
{197} normal block at 0x000001C10FAA5B70, 48 bytes long.
Data: <--boinc input --> 2D 2D 62 6F 69 6E 63 20 69 6E 70 75 74 20 2D 2D
{196} normal block at 0x000001C10FAA8030, 16 bytes long.
Data: < > 18 BA AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{195} normal block at 0x000001C10FAA83F0, 16 bytes long.
Data: < > F0 B9 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{194} normal block at 0x000001C10FAA89E0, 16 bytes long.
Data: < > C8 B9 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{193} normal block at 0x000001C10FAA7FE0, 16 bytes long.
Data: < > A0 B9 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{192} normal block at 0x000001C10FAA8DA0, 16 bytes long.
Data: <x > 78 B9 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{191} normal block at 0x000001C10FAA8B20, 16 bytes long.
Data: <P > 50 B9 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{190} normal block at 0x000001C10FAA5A90, 48 bytes long.
Data: <ComSpec=C:\Windo> 43 6F 6D 53 70 65 63 3D 43 3A 5C 57 69 6E 64 6F
{189} normal block at 0x000001C10FAA7F90, 16 bytes long.
Data: < > D0 FE A8 0F C1 01 00 00 00 00 00 00 00 00 00 00
{188} normal block at 0x000001C10FA9D540, 32 bytes long.
Data: <SystemRoot=C:\Wi> 53 79 73 74 65 6D 52 6F 6F 74 3D 43 3A 5C 57 69
{187} normal block at 0x000001C10FAA88F0, 16 bytes long.
Data: < > A8 FE A8 0F C1 01 00 00 00 00 00 00 00 00 00 00
{185} normal block at 0x000001C10FAA8C10, 16 bytes long.
Data: < > 80 FE A8 0F C1 01 00 00 00 00 00 00 00 00 00 00
{184} normal block at 0x000001C10FAA81C0, 16 bytes long.
Data: <X > 58 FE A8 0F C1 01 00 00 00 00 00 00 00 00 00 00
{183} normal block at 0x000001C10FAA8210, 16 bytes long.
Data: <0 > 30 FE A8 0F C1 01 00 00 00 00 00 00 00 00 00 00
{182} normal block at 0x000001C10FAA85D0, 16 bytes long.
Data: < > 08 FE A8 0F C1 01 00 00 00 00 00 00 00 00 00 00
{181} normal block at 0x000001C10FAA88A0, 16 bytes long.
Data: < > E0 FD A8 0F C1 01 00 00 00 00 00 00 00 00 00 00
{180} normal block at 0x000001C10FA8FDE0, 280 bytes long.
Data: < \ > A0 88 AA 0F C1 01 00 00 C0 5C AA 0F C1 01 00 00
{179} normal block at 0x000001C10FAA8800, 16 bytes long.
Data: <0 > 30 B9 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{178} normal block at 0x000001C10FAA8A80, 16 bytes long.
Data: < > 08 B9 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{177} normal block at 0x000001C10FAA8850, 16 bytes long.
Data: < > E0 B8 AA 0F C1 01 00 00 00 00 00 00 00 00 00 00
{176} normal block at 0x000001C10FAAB8E0, 496 bytes long.
Data: <P acemd3.e> 50 88 AA 0F C1 01 00 00 61 63 65 6D 64 33 2E 65
{65} normal block at 0x000001C10FAA8C60, 16 bytes long.
Data: < > 80 EA D6 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{64} normal block at 0x000001C10FA9BA00, 16 bytes long.
Data: <@ > 40 E9 D6 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{63} normal block at 0x000001C10FA9B9B0, 16 bytes long.
Data: < W > F8 57 D3 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{62} normal block at 0x000001C10FA9B960, 16 bytes long.
Data: < W > D8 57 D3 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{61} normal block at 0x000001C10FA9B910, 16 bytes long.
Data: <P > 50 04 D3 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{60} normal block at 0x000001C10FA9B870, 16 bytes long.
Data: <0 > 30 04 D3 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{59} normal block at 0x000001C10FA9B780, 16 bytes long.
Data: < > E0 02 D3 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{58} normal block at 0x000001C10FA9B730, 16 bytes long.
Data: < > 10 04 D3 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{57} normal block at 0x000001C10FA9B690, 16 bytes long.
Data: <p > 70 04 D3 DA F7 7F 00 00 00 00 00 00 00 00 00 00
{56} normal block at 0x000001C10FA9B640, 16 bytes long.
Data: < > 18 C0 D1 DA F7 7F 00 00 00 00 00 00 00 00 00 00
Object dump complete.

</stderr_txt>

Enjoy reading it.

I'm not sure a GTX 750 series can run the new app.

I have a GTX 750 on a linux host that is processing an ACEMD3 task, it is about half way through and should complete the task in about 1 day.

A Win7 host with GTX 750 ti is also processing an ACEMD3 task. This should take 20 hours.

On a Win7 host with GTX 960, two ACEMD3 tasks have failed. Both with this error: # Engine failed: Particle coordinate is nan
Host can be found here: http://gpugrid.net/results.php?hostid=274119

What I have noticed on my Linux hosts is nvidia-smi reports the ACEMD3 tasks are using 10% more power than the ACEMD2 tasks. This would indicate that the ACEMD3 tasks are more efficient at pushing the GPU to it's full potential.

Because of this, I have reduced the overclocking on some hosts (particularly the GTX 960 above)

Was this coincidence, or is the new version not being sent to GTX750ti cards?

Please, try updating drivers

would be useful if we were told which is the minimum required version number of the driver.

would be useful if we were told which is the minimum required version number of the driver.

This info can be found here:
http://gpugrid.net/forum_thread.php?id=5002

would be useful if we were told which is the minimum required version number of the driver.

This info can be found here:
http://gpugrid.net/forum_thread.php?id=5002

oh, thanks very much; so all is clear now - I need to update my drivers on the two GTX750ti hosts.

Hi, I'm running test 309 on an i7-860 with one GTX 750Ti and ACEMD 3 test is reporting 4.680%/Hr.
Better than my GTX 1060 and i7-7700K running test 725 @ 4.320%/Hr.
Why does the GTX 1060 run slower, Toni, anybody?
(running latest drivers)

The gtx 1060 performance seems fine for the ACEMD2 task in your task list.
May find some clues to the slow ACEMD3 performance in the Stderr output when task completes.
The ACEMD3 task progress reporting is not as accurate as the ACEMD2 tasks, a side affect of using a Wrapper. So the performance should only be judged when it has completed.

would be useful if we were told which is the minimum required version number of the driver.

This info can be found here:
http://gpugrid.net/forum_thread.php?id=5002

oh, thanks very much; so all is clear now - I need to update my drivers on the two GTX750ti hosts.

Driver updates complete, and 1 of my 2 GTX750ti has already received a task, it's running well.

What I noticed, also on the other hosts (GTX980ti and GTX970), is that the GPU usage (as shown in the NVIDIA Inspector and GPU-Z) now is up to 99% most of the time; this was not the case before, most probably due to the WDDM "brake" in Win7 and Win10 (it was at 99% in WinXP which had no WDDM).
And this is noticable, as the new software seems to have overcome this problem.