Topic: Open Source XPM (Primecoin) GPU Miner & Pool xpmforall.org - page 12. (Read 110023 times)

Do u have 2080ti?

I am getting 0.32 to 0.33 cpd for R9 280x.

can someone share optimal settings for 2080 ti?

Can someone share speeds for 280X and 290 ?

Relax. the focus did not work. waiting for a freebie turned out to be a fake.  
inveterate mathematicians merge the remnants of coins. 

what drivers you need for the gtx 1060?  on 398.36 miner works max 3 min

I tried all sorts of options, the miner does not work more than 3 minutes

  https://bitcoinprime.org/  if this is not a fake then maybe that will determine the price of XPM in the near future ...

I both lowered and increased windowSize. I tried all sorts of different parameters but I have a miner more than 3 minutes does not work... tell me what I'm doing? vindows 10, card 3*1060 6g stock, 398.31 driver

Several of my miners are reporting the following error message when I try to start them. They had been previously running with no issues for several months. They are pointing to coinsforall.io


I'm guessing something is wrong with the blockchain data on the server backend?

try hooking a monitor too it or use a dummy plug
also disable ulps
also it can be risers that caused your crash as those super cheap cable version non usb types are garbage and can cause instability you want shielded or better
also those above cant take much flexing as they are shitty soldered pos risers
some of the powered types are even worse and sometimes they solder the positive/negative leads and cap backwards=POP so if using those types always check them 1st before using
this is for both the 80wire and 40wire types

Strange things happen, is there a problem?

My home computer have Vtx3d HD 7950. Normally it does ~0.25 cpd.

Today i strarted miner and it's been mining stable 0.46 cpd and xmpforall.org show same. How come? I haven't change any setting's and temps are same. Basically everythin is same.

https://i.imgur.com/XnDxq7K.jpg?1

Hey guys. Need your experience on this.

I recently changed to Win7 in order to try to get a stable build for my 5 GPU rig.

I'm using 5 AMD RX480 GPUs on this rig with Driver 16.9.2 and it looks very stable so far. The only problem is, the driver doesn't seem to recognize a 5th GPU, it only sees 4 of them.

I know that the issue is not a bad riser or the Motherboard. I had been able to run 5 GPUs on Win10 before but it eventually crashed after just 30 minutes or so. The difference was that I was able to hook up al 5 GPUs before.

Now, Windows7 can see all 5 cards on Device Manager, also I can see all 5 with GPU-Z. It seems that my problem is that I can't get the driver to manage all 5 cards. Wattman and can only see 4 of them.

Any ideas on how I can fix this?

Hi, everybody. Good people help. I like to fight it? windows 10 latest build (1 day as supplied) map of NVIDIA 1060 6g 398.36
GPU 0: has 10 CUs
GPU 0: primorial = 13082761331670030 (54 bits)
GPU 0: sieve size = 82575360 (27 bits)
N=12 SIZE=12288 STRIPES=210 WIDTH=22 PCOUNT=65536 TARGET=11
GPU 1: has 10 CUs
GPU 1: primorial = 13082761331670030 (54 bits)
GPU 1: sieve size = 82575360 (27 bits)
N=12 SIZE=12288 STRIPES=210 WIDTH=22 PCOUNT=65536 TARGET=11
GPU 2: has 10 CUs
GPU 2: primorial = 13082761331670030 (54 bits)
GPU 2: sieve size = 82575360 (27 bits)
Connecting to frontend: coinsforall.io:6666 ...
Connecting to bitcoin: 151.80.96.105:60000 ...
Connecting to signals: 151.80.96.105:60001 ...
Work received: height=2762574 diff=11.65595 latency=562ms
 * warning: ran out of hashes, increasing sha256 work size coefficient to 65536
 * warning: ran out of hashes, increasing sha256 work size coefficient to 65536
 * warning: ran out of hashes, increasing sha256 work size coefficient to 65536
 * warning: ran out of hashes, increasing sha256 work size coefficient to 98304
 * warning: ran out of hashes, increasing sha256 work size coefficient to 98304
 * warning: ran out of hashes, increasing sha256 work size coefficient to 131072
 * warning: ran out of hashes, increasing sha256 work size coefficient to 163840
Work received: height=2762576 diff=11.655666 latency=656ms
 * warning: ran out of hashes, increasing sha256 work size coefficient to 65536
 * warning: ran out of hashes, increasing sha256 work size coefficient to 65536
 * warning: ran out of hashes, increasing sha256 work size coefficient to 98304
 * warning: not enough candidates (1266 available, must be more than 2560
   * increase sieves per round to 6
 * warning: ran out of hashes, increasing sha256 work size coefficient to 65536
 * warning: ran out of hashes, increasing sha256 work size coefficient to 98304
 * warning: ran out of hashes, increasing sha256 work size coefficient to 98304
 * warning: ran out of hashes, increasing sha256 work size coefficient to 131072
error: 700
failed with error CUDA_ERROR_ILLEGAL_ADDRESS at C:/build/xpmclient/src/xpm/cuda/xpmclient.cpp:657

config
# Pool websites:
#   http://xpmforall.org
#   http://coinsforall.io

server = "coinsforall.io";
port = "6666";

# Your XPM payout address
address = "myadr";

# You can give this machine a custom name
# Computer name is used as default
#name = "min1";

# GPU crash handling (properly untested feature):
# 0 - do nothing
# 1 - close miner application
# 2 - reboot system (need superuser rights)
onCrash = "0";

# - Valid cpuload range: 0 to 4
# - More than 2 does not make sense
# - You can use 0 for really slow CPUs
cpuload = "1";

# Target Cunningham chain length, default = auto (adjust to difficulty)
target = "auto";

# Sieve size in stripes (1 stripe = 16384 bits), recommended 420 for AMD, 210 for NVidia
# Big sieve size gives more candidates with less prime probability
sieveSize = "210";

# Weave depth (primes number count using by sieve), recommended 40960 for AMD, 65536 for NVidia
# Big weave depth increases prime probability, but sieve generate less candidates
weaveDepth = "65536";

# Sieve layers number, optimal value is target*2; default = auto (target*2)
width = "auto";

# Sieve window size
windowSize = "12288";

# Maximal bit size of multipliers using with primorials 13, 14 and 15;
# Default values are 26, 33, 36
# Less values increases prime probability, but sieve generate less candidates
multiplierLimits = ["24", "31", "35"];

# - The following settings have one entry per GPU
# - If you have more than 4 just add more entries or leave it as is to use defaults
# - All entries must be separated by commas and set between double quotes

# 0 = don't use device
# 1 = use device
devices =        ["1", "1", "1"];

# sieves per round value, default = 5
sievePerRound = ["5", "5", "5"];

# -1 means don't change; not supported for NVidia
corefreq =       ["-1", "-1", "-1"];
memfreq =        ["-1", "-1", "-1"];
powertune =      ["-1", "-1", "-1"];
fanspeed =       ["-1", "-1", "-1"];

Hello! already asked the question: the miner can not connect to the server. firewall is disabled, there is no result.
http://f2.s.qip.ru/4xGIq0Gd.png

I havent had good luck with 1080tis on 398.36 -- moved back to 391.35 it was more stable at +40/+500 OC. Even no OC I was crashing on some algos running forager. Havent tried XPM miner yet.

Getting very low results on 1080tis, 0.52~0.56 per card, tried stock settings and overclocking, no much change, using 398.46 drivers, last windows 10 version, is there a way to fix it?

win10ltsb / blockchain drivers.

Thx!, on windows 10 /blockchain drivers?

R9 Fury (1000/500MHz, 1100mV) 0.6cpd
R9 FuryX (1000/500MHz, 1100mV) 0.65cpd

cpuload = "1";
target = "11";
sieveSize = "630";
weaveDepth = "40960";
width = "22";
windowSize = "8192";
multiplierLimits = ["24", "31", "35"];