Topic: arCUDAminer 64 bit v1.0c - PTS GPU miner for Windows (Read 10588 times)
Just had GT-440 fall in my lap, what should I expect out of it? .... in comparison to a middling CPU say.
ok, whats the best price/CPM ratio card on the market atm?
Trying the miner.
Keeps crashing is i use anything but sse4.
And using sse4 gives me this:
Keeps crashing is i use anything but sse4.
And using sse4 gives me this:
Code:
Could not malloc dev_data (2)
What about sph?
Trying the miner.
Keeps crashing is i use anything but sse4.
And using sse4 gives me this:
Keeps crashing is i use anything but sse4.
And using sse4 gives me this:
Code:
Could not malloc dev_data (2)
btw u decreased pts's price 50% just for 3500$ bounty 
Don't blame it on os
btw u decreased pts's price 50% just for 3500$ bounty
Any kind of debugging Information I might sent to you?
Nope, as I have no idea what's causing these spikes for you
Any kind of debugging Information I might sent to you?
First of all, thx for the update on this forum, and for your work in general.
Results with 1.0c are ~10%up from 1.0b GPU is constantly at 90%.
BUT:
At startup i still get the same -"99847394853" of 0 bytes-message and the FB is still spiking with does not really look optimized or is there an intrinsic reason for this to happen?
Results with 1.0c are ~10%up from 1.0b GPU is constantly at 90%.
BUT:
At startup i still get the same -"99847394853" of 0 bytes-message and the FB is still spiking with does not really look optimized or is there an intrinsic reason for this to happen?
That should be because of a printing mistake I did. A new version would coem soon pushing GPU usage to 100% but I still haven't been able to figure out your spikes
First of all, thx for the update on this forum, and for your work in general.
Results with 1.0c are ~10%up from 1.0b GPU is constantly at 90%.
BUT:
At startup i still get the same -"99847394853" of 0 bytes-message and the FB is still spiking with does not really look optimized or is there an intrinsic reason for this to happen?
http://thumbnails101.imagebam.com/30199/f11ba7301980006.jpg
Results with 1.0c are ~10%up from 1.0b GPU is constantly at 90%.
BUT:
At startup i still get the same -"99847394853" of 0 bytes-message and the FB is still spiking with does not really look optimized or is there an intrinsic reason for this to happen?
http://thumbnails101.imagebam.com/30199/f11ba7301980006.jpg
Thx for careing archit =)
Tried non-highperf and avx too for the same results. (regarding the spikes) Had it once starting with a little less spikes too for maybe 1 min achieved ~20-30% more collisions.
Running on a 750M (Kepler) with 4GB.
Tried non-highperf and avx too for the same results. (regarding the spikes) Had it once starting with a little less spikes too for maybe 1 min achieved ~20-30% more collisions.
Running on a 750M (Kepler) with 4GB.
That would be fixed soon.
EDIT: Should be fixed with 1.0c
Thx for careing archit =)
http://thumbnails112.imagebam.com/30142/e18196301418115.jpg
Tried non-highperf and avx too for the same results. (regarding the spikes) Had it once starting with a little less spikes too for maybe 1 min achieved ~20-30% more collisions.
Running on a 750M (Kepler) with 4GB.
http://thumbnails112.imagebam.com/30142/e18196301418115.jpg
Tried non-highperf and avx too for the same results. (regarding the spikes) Had it once starting with a little less spikes too for maybe 1 min achieved ~20-30% more collisions.
Running on a 750M (Kepler) with 4GB.
Around 800CPM with 680 gtx 
Want more!
Want more! If this was an answer to the spikes question: arCUDA 1.0 still gives me exactly the same gpu spikes.
EDIT: After initializing I also get a message like -965346328 free of 0 total bytes of memory.
EDIT: After initializing I also get a message like -965346328 free of 0 total bytes of memory.
What parameters? And can you copy the all the text that is written out
If this was an answer to the spikes question: arCUDA 1.0 still gives me exactly the same gpu spikes.
EDIT: After initializing I also get a message like -965346328 free of 0 total bytes of memory.
EDIT: After initializing I also get a message like -965346328 free of 0 total bytes of memory.
Use the newer version from bitsharestalk forum. I forgot to update the thread over here
Are those spikes for the GPU utilization expected or is sth bugged?
http://thumbnails111.imagebam.com/30114/d45ebc301135806.jpg
http://thumbnails111.imagebam.com/30114/d45ebc301135806.jpg
Reporting issues.
I'm mining @ ypool on a GTX 680; running Windows 8.
Sharerate is being calculated precisely (~100sh/h)
After the first donation round, when it 'switches' back to user mining, ypool's counter for my account stops taking into account shares submitted past that point. If I restart the miner, all is fine again.
Someone able to check this? I have the feeling it doesn't switch back to the user defined credentials after donation round.
I'm mining @ ypool on a GTX 680; running Windows 8.
Sharerate is being calculated precisely (~100sh/h)
After the first donation round, when it 'switches' back to user mining, ypool's counter for my account stops taking into account shares submitted past that point. If I restart the miner, all is fine again.
Someone able to check this? I have the feeling it doesn't switch back to the user defined credentials after donation round.
Before you donate, be aware of this earlier post of a CUDA PTS miner:
https://bitcointalksearch.org/topic/ann-cudapts-gpu-mining-for-protoshares-pts-404915
Windows version has more features than the open source Linux version. Also, I think that the OP is offering the Visual Studio project ready to compile. https://bitcointalksearch.org/topic/ann-cudapts-gpu-mining-for-protoshares-pts-404915
Before you donate, be aware of this earlier post of a CUDA PTS miner:
https://bitcointalksearch.org/topic/ann-cudapts-gpu-mining-for-protoshares-pts-404915
https://bitcointalksearch.org/topic/ann-cudapts-gpu-mining-for-protoshares-pts-404915
Jump to: