[ANN] PTS.1GH.COM - GPU, CPU mining ★ New version 1.4! Please upgrade ASAP! ★

[Brekyrself]

Reorder

Are there any variables we can tune with?  One of my Vista64 machines is crashing the display drivers only after 6+ hours of mining.  Temps not an issue and I tried the registry fix.  Same cards/drivers however with Win7 64 have been running forever without a hitch with your miner.

If it matters I am using 2x HIS 7950's with AMD 13.12 drivers.

[slacking]

Getting around 990 cpm with a Powercolor 7950 (oc'd 1045 core/1500 memory) that I bought for $189.00 on Newegg before prices exploded recently...yippppeee!

[reorder]

Reorder

Are there any variables we can tune with?  One of my Vista64 machines is crashing the display drivers only after 6+ hours of mining.  Temps not an issue and I tried the registry fix.  Same cards/drivers however with Win7 64 have been running forever without a hitch with your miner.

If it matters I am using 2x HIS 7950's with AMD 13.12 drivers.

There is essentially nothing to tune about the algorithm save for amount of VRAM used, and that the miner tries to adjust automatically. I figure AMD does not give much love to Vista in their drivers anymore, probably you are hitting some driver bug.

[jly77]

Reorder

Are there any variables we can tune with?  One of my Vista64 machines is crashing the display drivers only after 6+ hours of mining.  Temps not an issue and I tried the registry fix.  Same cards/drivers however with Win7 64 have been running forever without a hitch with your miner.

If it matters I am using 2x HIS 7950's with AMD 13.12 drivers.

There is essentially nothing to tune about the algorithm save for amount of VRAM used, and that the miner tries to adjust automatically. I figure AMD does not give much love to Vista in their drivers anymore, probably you are hitting some driver bug.

I tried your pool today and it works great for me so far. Can you please optimize the miner for gtx660ti? It seems it's possible to get ~850cpm from gtx660ti. Thanks .

[Darkbane]

Wondering about the memory usage... I've got a 2GB video card but I see to only be using 1.1MB of the memory... wondering if this is normal from the program automatically configuring itself?

Windows 8.1
2x ASUS R9 270 (not the 270X) http://www.asus.com/Graphics_Cards/R9270DC2OC2GD5/
pts-1gh-win (is this version number or how do I tell)

side note for those wondering why it says dynamic memory instead of dedicated memory... For some reason GPU-Z has never reported dedicated memory usage, I think its just a snafu in the program or the driver itself reporting it correctly, when GPU mining scrypt I can change the threads and suck up every last bit of of the 2GB memory...

[CryptoN8]

Hey man, I'm getting this following error, even after following all the proper steps, my gpu is a 780 ti, any idea what may be happening:

http://content.screencast.com/users/AliMan89/folders/Jing/media/88de0fc6-c1d8-4381-bbe1-3bac758c3604/2014-01-19_1327.png

I'm getting this exact same error with the same card. Has anyone had luck with this card? Win 8.1 x64 w/332.21 GeForce drivers. Thanks.

[reorder]

Guys,

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

The pool now supports XPT protocol, for CPU mining you can now use yam! Connection string for yam is:

Code: [Select]

xpt2h://YOUR-PTS-ADDRESS:[email protected]:18120:18121:18122:18123/pts


[CryptoN8]

Guys,

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

The pool now supports XPT protocol, for CPU mining you can now use yam! Connection string for yam is:

Code: [Select]

xpt2h://YOUR-MMC-ADDRESS:[email protected]:18120:18121:18122:18123/pts


Sounds great, it will be nice to have all of my miners on the same pool. So we can use this miner? (the yvg1900 one?) from here:
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
Thanks.

[reorder]

Guys,

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

The pool now supports XPT protocol, for CPU mining you can now use yam! Connection string for yam is:

Code: [Select]

xpt2h://YOUR-MMC-ADDRESS:[email protected]:18120:18121:18122:18123/pts


Sounds great, it will be nice to have all of my miners on the same pool. So we can use this miner? (the yvg1900 one?) from here:
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
Thanks.

Yes, it is this one. Actually jhProtominer and xptMiner work too, but yam is the best.

[Darkbane]

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

using the 1.4 stratum version now, may I request you include a version number somewhere when it starts up, so we can easily identify in the future which version we are running? seems I am almost identical to previous work rates, so the inclusion of stratum to lower rejects should give a net increase with no wasted work time... huge bonus for all.

I started to try out the different workgroup sizes... seems I must settle on 256 as anything higher will error, is that expected for a 2GB video card? I'm guessing a 512 would work on a 4GB and so on? (just taking a stab at trying to understand since I see only 1.1GB of gpu memory being used, ASUS R9 270 2GB)

[earntodie]

Guys,

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

The pool now supports XPT protocol, for CPU mining you can now use yam! Connection string for yam is:

Code: [Select]

xpt2h://YOUR-PTS-ADDRESS:[email protected]:18120:18121:18122:18123/pts


Could you please add info about version in your gpu miner?!

[Darkbane]

Guys,

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

The pool now supports XPT protocol, for CPU mining you can now use yam! Connection string for yam is:

Code: [Select]

xpt2h://YOUR-MMC-ADDRESS:[email protected]:18120:18121:18122:18123/pts


Sounds great, it will be nice to have all of my miners on the same pool. So we can use this miner? (the yvg1900 one?) from here:
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
Thanks.

Do you find that your GPU mining lowers when you are CPU mining on the same machine? I attempted this and the loss in GPU was simply not worth the gains from the CPU, I was simply using more electricity for no gain... (I was using the yam) I'm sure results will vary person to person, just wondering if anyone has added them together to see yet?

[reorder]

I started to try out the different workgroup sizes... seems I must settle on 256 as anything higher will error, is that expected for a 2GB video card? I'm guessing a 512 would work on a 4GB and so on? (just taking a stab at trying to understand since I see only 1.1GB of gpu memory being used, ASUS R9 270 2GB)

The worksize is limited not by your VRAM, but rather by GPU architecture and driver. Setting it to lower than default may benefit older cards (low-end 6xxx in particular) and might solve a problem with some Nvidias that fail to start with what their driver provides as default.

[reorder]

Guys,

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

The pool now supports XPT protocol, for CPU mining you can now use yam! Connection string for yam is:

Code: [Select]

xpt2h://YOUR-PTS-ADDRESS:[email protected]:18120:18121:18122:18123/pts


Could you please add info about version in your gpu miner?!

Thank you for suggestion, will do that tomorrow.

[reorder]

Guys,

Pool miner is now updated to version 1.4, please download it from the pts.1gh.com page.

• It now uses stratum mining protocol, stale shares are almost zero
• It is now possible to override workgroup size detection, please try setting it to 64-128-256 if you had 'Invalid group size' error
• Hashrate is slightly improved

The pool now supports XPT protocol, for CPU mining you can now use yam! Connection string for yam is:

Code: [Select]

xpt2h://YOUR-MMC-ADDRESS:[email protected]:18120:18121:18122:18123/pts


Sounds great, it will be nice to have all of my miners on the same pool. So we can use this miner? (the yvg1900 one?) from here:
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
Thanks.

Do you find that your GPU mining lowers when you are CPU mining on the same machine? I attempted this and the loss in GPU was simply not worth the gains from the CPU, I was simply using more electricity for no gain... (I was using the yam) I'm sure results will vary person to person, just wondering if anyone has added them together to see yet?

Does the GPU miner use a lot of your CPU time? It was the case for me when using two cards without setting GPU_USE_SYNC_OBJECTS, now the miner sets this variable automatically. It is some old AMD driver issue.