1) Message boards : Number crunching : lost 4 WUs seconds after enabling gtx-770 (Message 49079)
Posted 2 days ago by Profile Retvari Zoltan
So why did this happen?
This is a known problem of the present GPUGrid CUDA8.0 app (v9.18). CC3.0 cards (like the GTX 770) will produce this error if the host has multiple GPUs with different Compute Capabilities. (Your GTX 1070 Ti is CC6.1). You should disable the GTX 770, or move it to a different PC to avoid this.

See the App update 17 April 2017 thread
and the middle of the all WUs downloaded recently produce "computation error" right away thread.
2) Message boards : Number crunching : 113 mil credit loss on inactive system at boincstats (Message 49003)
Posted 5 days ago by Profile Retvari Zoltan
From your graph, it looks like it took a week before the change (-108mil) or so showed up on boincstats
ie 1-30 on your table to 2-9 on boincstats.
The data I've used comes from BOINCStats, I've simply swapped the columns and the rows.

This is what concerns me and I posted at gridcoin about this:

If it takes a week or months for boincstats to remove credits from a merge (I know you say there was none) then

The "extra credits" show up causing a large mining payoff (I am guessing of course), then I remove gridcoin as the "team", wait for the credit differential to be fixed, then register my old system as a new one, join the gridcoin team, and there is no record of the credit differential.

Seems like a security problem.
GridCoin does not based on BOINCStats, it takes the data directly from the project's servers.

I am currently mining using the grcpool and there is no way to do a merge while using the pool since the pool is the owner of the gpugrid account. However, once I switch to BAM! and start solo mining, possibly one could game the system using merge or whatever is causing the large credit changes.
Aw, then it's not the host I've checked on GPUGrid. Could you give me a link to the host's details on GPUGrid? Or could you check how many credits this host has according to GPUGrid?
3) Message boards : Number crunching : 113 mil credit loss on inactive system at boincstats (Message 49001)
Posted 5 days ago by Profile Retvari Zoltan
There is *more* strangeness in it than what meets the eye for the first sight:
1st: Your host has lost credit, which is strange
2nd: Your host lost credit 6 times, so its source could not be the "merge"
3rd: The rank of your host decreases while its total credit doesn't increase. This could be only if other hosts have lost credits on that day.
4th: Your host (#171317) has 151,883,400 credits today according to GPUGrid.
Date Total Credits Credit/Day Rank CHG 2018-02-19 182,645,879 0 1,686 +1 2018-02-18 182,645,879 0 1,685 -2 This is strange 2018-02-17 182,645,879 0 1,687 +2 2018-02-16 182,645,879 0 1,685 +3 2018-02-15 182,645,879 0 1,682 -2 This is strange 2018-02-14 182,645,879 0 1,684 -1 This is strange 2018-02-13 182,645,879 0 1,685 +4 2018-02-12 182,645,879 0 1,681 +7 2018-02-11 182,645,879 0 1,674 -1 This is strange 2018-02-10 182,645,879 0 1,675 +1 2018-02-09 182,645,879 0 1,674 -4 This is strange 2018-02-08 182,645,879 0 1,678 +1 2018-02-07 182,645,879 -48,350 1,677 +1 2018-02-06 182,694,229 -378,820 1,676 +8 2018-02-05 183,073,049 0 1,668 0 2018-02-04 183,073,049 0 1,668 +5 2018-02-03 183,073,049 0 1,663 -4 This is strange 2018-02-02 183,073,049 0 1,667 0 2018-02-01 183,073,049 0 1,667 +3 2018-01-31 183,073,049 -816,960 1,664 +3 2018-01-30 183,890,009 -108,314,676 1,661 +645 2018-01-29 292,204,685 -2,210,019 1,016 +10 2018-01-28 294,414,704 0 1,006 +3 2018-01-27 294,414,704 -56,834 1,003 +3 2018-01-26 294,471,538 0 1,000 +1 2018-01-25 294,471,538 0 999 +2 2018-01-24 294,471,538 0 997 -1 This is strange 2018-01-23 294,471,538 0 998 -1 This is strange 2018-01-22 294,471,538 0 999 0 2018-01-21 294,471,538 0 999 +5 2018-01-20 294,471,538 53 994 +1 2018-01-19 294,471,485 993 Host's creation
I can not explain this.
According to BOINCStats, your host is "First seen on 2017-08-07" which does not match with 2018-01-19, when it received the initial 294,471,485 credits.
This could be because the "merge", but it's still strange.
4) Message boards : News : Linux app failing (Message 48935)
Posted 11 days ago by Profile Retvari Zoltan
Is there something that needs to done on client side to get these updated linux apps?
No, it will be automatically downloaded when you receive a new task.
5) Message boards : News : Linux app failing (Message 48929)
Posted 11 days ago by Profile Retvari Zoltan
I have uploaded a new linux version of the old app. But we are also expecting to deploy a new app soon with faster performance.

the current new linux version is 919. Let me know if it works.


Could you please update the Linux app in the Short queue as well?
6) Message boards : Graphics cards (GPUs) : "Thermal cycle" (Message 48911)
Posted 13 days ago by Profile Retvari Zoltan
... causing the GPU temps going down by about 5°C, from 62° or 63°C to 57°C or 58°C.
This is negligible.
The "normal" thermal cycle is going from room temperature (~25°C) to ~80°C. That is 55°C difference.
The "extreme" thermal cycle is going from room temperature to -196°C (Liquid nitrogen cooling), that is 221°C difference.
7) Message boards : Number crunching : ...complex...GIANNI_CPXB tasks failing right after start (Message 48908)
Posted 13 days ago by Profile Retvari Zoltan
Another "... complex ... GIANNI..." task that failed, this time though after about 32.000 seconds:


stderr says:
# Simulation unstable. Flag 3 value 1
# The simulation has become unstable. Terminating to avoid lock-up
# The simulation has become unstable. Terminating to avoid lock-up (2)
# Attempting restart (step 6965000)

One possibility is you may need to clock back your GPU a bit.

This workunit has failed on every host (including one of mine) with the same error message. It is very unlikely that 8 different GPUs (including known reliable ones) have the same condition which makes the workunit fail the same way. In this case the source of the error is the algorithm which checks the stability of the simulation probably set to an overly sensitive level.
8) Message boards : Number crunching : Gridcoin (Message 48901)
Posted 13 days ago by Profile Retvari Zoltan
Weeks... So I'm not far off and that not receiving any GRC atm is normal?
No, I receive ~90GRC daily.
Do you have any GRC in your wallet?
Have you sent your initial beacon?
Do you have the latest ( client?

I've been seeing the "estimate time to earn reward" message go around 1 to 5 hours for some time now, it's been teasing me.
That's a very rough estimate, based on your magnitude and the GRCs you are staking.

Also the connection for me seems to be quiet intermittent. The Gridcoin Wallet program tends to report that it's offline, then online, then offline again, despite being able to sync.
That's true. I usually restart my client every other day.
9) Message boards : News : Linux app failing (Message 48880)
Posted 17 days ago by Profile Retvari Zoltan
I should have deprecated the current one, so at least it does not get out.
It should have been deprecated from the short runs as well. It took me by surprise that short tasks are present on my hosts, which have failed before on Linux hosts (but after this issue have been recognized).
10) Message boards : Number crunching : Lost 8 hours of work on a long WU why? (Message 48802)
Posted 21 days ago by Profile Retvari Zoltan
1. Who actually does the checkpoint?
The GPUGrid app does the checkpoint. When you have a very fast GPU, it does its checkpoints so frequently that the (Windows) disk cache never writes the actual data to the drive (this could be resolved by disabling the write caching of the BOINC drive). This behavior results in an error only if the procession of a GPUGrid task is broken unexpectedly (by a power failure, or a system hang)

here are 3 lines of the service request xml from gpugrid. Note that grcpool is identified as a project. It is actually a manager.


here is the reply from grcpool back to gpugrid with the corresponding pieces from the xml



Note that grcpool thinks it is replying back to WCG!!!!!

No, it says that your most recent computing preferences are on WCG.

Next 10