What pool are you guys using for Monero?
Whatever that is not being DDoSd lol xDYea, aint that the truth!
Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 310. (Read 3426936 times)
June 24, 2014, 03:10:01 PM
Yea, aint that the truth!
June 24, 2014, 03:09:17 PM
CCMiner w/Cryptonight: I think the error with the windows drivers might be that one of the pointer addresses is either undeclared or unallocated. It definetly crashes because of a memory access error in the Nvidia driver dll's.
How did you find this out?
Which operating system were you running?
What nVidia driver version were you running?
June 24, 2014, 03:08:46 PM
What pool are you guys using for Monero?
Whatever that is not being DDoSd lol xD 
June 24, 2014, 03:06:38 PM
What pool are you guys using for Monero?
June 24, 2014, 02:46:00 PM
It seems every thread/card will need a core dedicated.
On my old Pentium [email protected], 1 card needs 50-60% CPU time in order to run at 200+
Running on -d 1, desktop is fine, but any desktop usage (chrome) kills hashrate in half. Have to upgarde
On my old Pentium [email protected], 1 card needs 50-60% CPU time in order to run at 200+
Running on -d 1, desktop is fine, but any desktop usage (chrome) kills hashrate in half. Have to upgarde
this has not been my experience... i am using an old cpu (2 threads) and mining 5x750ti at ~210kh / card
June 24, 2014, 02:28:37 PM
CCMiner w/Cryptonight: I think the error with the windows drivers might be that one of the pointer addresses is either undeclared or unallocated. It definetly crashes because of a memory access error in the Nvidia driver dll's.
June 24, 2014, 02:21:22 PM
Has anyone managed to mine Monero on Windows 8.1?
I'm using Windows 8.1
with -l 6x40, i'm getting this
Code:
[2014-06-25 03:35:13] GPU #1: GeForce GTX 750 Ti, 210.81 H/s
[2014-06-25 03:35:14] Stratum detected new block
[2014-06-25 03:35:15] GPU #1: GeForce GTX 750 Ti, 211.14 H/s
[2014-06-25 03:35:29] GPU #1: GeForce GTX 750 Ti, 205.14 H/s
[2014-06-25 03:35:29] accepted: 8/8 (100.00%), 205.14 H/s (yay!!!)
[2014-06-25 03:35:54] GPU #1: GeForce GTX 750 Ti, 201.03 H/s
[2014-06-25 03:35:55] Pool set diff to 5000
[2014-06-25 03:35:55] Stratum detected new block
[2014-06-25 03:35:55] accepted: 9/9 (100.00%), 201.03 H/s (yay!!!)
[2014-06-25 03:35:55] GPU #1: GeForce GTX 750 Ti, 211.58 H/s
[2014-06-25 03:36:40] Stratum detected new block
[2014-06-25 03:36:41] GPU #1: GeForce GTX 750 Ti, 210.70 H/s
[2014-06-25 03:36:49] Stratum detected new block
[2014-06-25 03:36:50] GPU #1: GeForce GTX 750 Ti, 210.81 H/s
[2014-06-25 03:37:08] GPU #1: GeForce GTX 750 Ti, 204.50 H/s
[2014-06-25 03:37:09] accepted: 10/10 (100.00%), 204.50 H/s (yay!!!)
[2014-06-25 03:37:46] GPU #1: GeForce GTX 750 Ti, 149.23 H/s
[2014-06-25 03:35:14] Stratum detected new block
[2014-06-25 03:35:15] GPU #1: GeForce GTX 750 Ti, 211.14 H/s
[2014-06-25 03:35:29] GPU #1: GeForce GTX 750 Ti, 205.14 H/s
[2014-06-25 03:35:29] accepted: 8/8 (100.00%), 205.14 H/s (yay!!!)
[2014-06-25 03:35:54] GPU #1: GeForce GTX 750 Ti, 201.03 H/s
[2014-06-25 03:35:55] Pool set diff to 5000
[2014-06-25 03:35:55] Stratum detected new block
[2014-06-25 03:35:55] accepted: 9/9 (100.00%), 201.03 H/s (yay!!!)
[2014-06-25 03:35:55] GPU #1: GeForce GTX 750 Ti, 211.58 H/s
[2014-06-25 03:36:40] Stratum detected new block
[2014-06-25 03:36:41] GPU #1: GeForce GTX 750 Ti, 210.70 H/s
[2014-06-25 03:36:49] Stratum detected new block
[2014-06-25 03:36:50] GPU #1: GeForce GTX 750 Ti, 210.81 H/s
[2014-06-25 03:37:08] GPU #1: GeForce GTX 750 Ti, 204.50 H/s
[2014-06-25 03:37:09] accepted: 10/10 (100.00%), 204.50 H/s (yay!!!)
[2014-06-25 03:37:46] GPU #1: GeForce GTX 750 Ti, 149.23 H/s
June 24, 2014, 01:55:52 PM
Has anyone managed to mine Monero on Windows 8.1?
June 24, 2014, 01:47:33 PM
Sounds like there will be some new Monero miners appearing, few basic pointers for you:
- Don't mine to an exchange address ever, you have to setup your own wallet!
- Monero doesnt make a point of being user friendly, but if you can get your mining rig working you can spend a few minutes reading the tutorial at monero.cc
- Your wallet wont work until your bitmonerod has synced the blockchain, save time by downloading most of it from the link here https://bitcointalksearch.org/topic/xmr-monero-a-secure-private-untraceable-cryptocurrency-583449
- The blockchain is currently around 1.3GB, so make sure you have at least 2GB free. Also be aware that the daemon can use a lot of Internet bandwidth if you let it, make sure your router's UPnP is disabled if you are on a capped connection
- Pool reliability has improved, orphans arent an issue but be careful of new pools, you can end up hashing an old block for a few hours. Hedge your bets by splitting miners across a couple of pools if you can.
- Most pools have a web IRC client if you dont have it already, #monero is good for support etc, I'm often there as CryptonotepoolUK
- Cryptonote coins like Monero work differently to Bitcoin and all its children, dont assume that things which worked for the last 20 coins you mined will be the same here
- Dont forget the payment ID when you send those hard earned coins to an exchange!
June 24, 2014, 01:40:46 PM
It seems every thread/card will need a core dedicated.
On my old Pentium [email protected], 1 card needs 50-60% CPU time in order to run at 200+
Running on -d 1, desktop is fine, but any desktop usage (chrome) kills hashrate in half. Have to upgarde
On my old Pentium [email protected], 1 card needs 50-60% CPU time in order to run at 200+
Running on -d 1, desktop is fine, but any desktop usage (chrome) kills hashrate in half. Have to upgarde
well i'll wait an optimized version then, seeing how every rig as at best a pentium g3220
June 24, 2014, 01:10:56 PM
It seems every thread/card will need a core dedicated.
On my old Pentium [email protected], 1 card needs 50-60% CPU time in order to run at 200+
Running on -d 1, desktop is fine, but any desktop usage (chrome) kills hashrate in half. Have to upgarde
On my old Pentium [email protected], 1 card needs 50-60% CPU time in order to run at 200+
Running on -d 1, desktop is fine, but any desktop usage (chrome) kills hashrate in half. Have to upgarde
June 24, 2014, 12:51:33 PM
On my 780 Ti, with -l 4x135 (get the highest performance from 4 threads, for whatever reason (the -l 8x60 that others on 750 Tis are using crashes the kernel)), I'm getting about 275 H/s on cryptonight.
Edit: Just tried the Wolf cpu miner and my i5-4670k @ 4.5 GHz gets 125-140 H/s >.>
Edit: Just tried the Wolf cpu miner and my i5-4670k @ 4.5 GHz gets 125-140 H/s >.>
June 24, 2014, 12:40:54 PM
Just to confirm my tests:
Cryptonight working fine under WinXP_32. With 6X750Ti (3 Palit Dual and 3 MSI TF) I'm getting ~1.000 H/s. Palits are ~220, and MSI ~150 H/s.
On Win8.1_64, it won't even start.
Cryptonight working fine under WinXP_32. With 6X750Ti (3 Palit Dual and 3 MSI TF) I'm getting ~1.000 H/s. Palits are ~220, and MSI ~150 H/s.
On Win8.1_64, it won't even start.
NVIDIA driver 335.28
June 24, 2014, 12:40:00 PM
Just to confirm my tests:
Cryptonight working fine under WinXP_32. With 6X750Ti (3 Palit Dual and 3 MSI TF) I'm getting ~1.000 H/s. Palits are ~220, and MSI ~150 H/s.
On Win8.1_64, it won't even start.
Cryptonight working fine under WinXP_32. With 6X750Ti (3 Palit Dual and 3 MSI TF) I'm getting ~1.000 H/s. Palits are ~220, and MSI ~150 H/s.
On Win8.1_64, it won't even start.
June 24, 2014, 12:30:20 PM
Is anyone tested COINKING multipool with x11 algo?
What can I espect(BTC) per day per 750Ti card?
Or is it better with cryptonight? (now that we have it)
What can I espect(BTC) per day per 750Ti card?
Or is it better with cryptonight? (now that we have it)
June 24, 2014, 11:18:22 AM
Death to all Windows rigs, mwahahahahhahaha.
This is the generic answer post.
I'm pretty sure I set both the Windows and Linux builds for a combined compute 3.0 and 3.5 build, that shouldn't be a problem in most cases. I'll see if I put together a compute 2.0 version as well, basically stripping out all the latest bells and whistles by Christian and building for 2.0. Anyway, back to the problems. I can't decide which of the other two likely suspects is more likely, trying to run too many threads to fit in the GPU memory (2 MB per thread, that's 8 x 40 x 2 = 640 MB on the default launch setting) or the kernel simply running too slow and triggering TRD. Should probably add a check if the large initial memory allocation succeeds or not but error checking is for little girls
Other thing I realized, I didn't think about rigs that have mixed types of GPUs in them, the launch parameters only takes a single value instead of a comma separated per-device list. Another thing on the todo list.
This is the generic answer post.
I'm pretty sure I set both the Windows and Linux builds for a combined compute 3.0 and 3.5 build, that shouldn't be a problem in most cases. I'll see if I put together a compute 2.0 version as well, basically stripping out all the latest bells and whistles by Christian and building for 2.0. Anyway, back to the problems. I can't decide which of the other two likely suspects is more likely, trying to run too many threads to fit in the GPU memory (2 MB per thread, that's 8 x 40 x 2 = 640 MB on the default launch setting) or the kernel simply running too slow and triggering TRD. Should probably add a check if the large initial memory allocation succeeds or not but error checking is for little girls
Other thing I realized, I didn't think about rigs that have mixed types of GPUs in them, the launch parameters only takes a single value instead of a comma separated per-device list. Another thing on the todo list.
Any ideas on the crazy hash rates on non 750ti cards? https://bitcointalksearch.org/topic/m.7489618
I tried 4x10 to see if maybe it was a memory problem but still get the same result.
OS?
GeForce GT 740M is Windows 8 64 - 8GB memory
qty 1 GeForce GTX 660 Windows 7 32bit - 4GB memory
qty 2 GeForce GTX 660 Windows Server 2012 R2 - 16GB memory
Carlo
PS the following works great
qty 2 GeForce GTX 750 TI Windows Server 2012 R2 - 16GB memory
June 24, 2014, 11:16:26 AM
@tsiv
any thoughts about FCN and merged mining?
btw. your -l 8x60 is also with my rigs the fastest option i tried so far
any thoughts about FCN and merged mining?
btw. your -l 8x60 is also with my rigs the fastest option i tried so far
Quote from: kopiemTu console output
[2014-06-24 17:57:02] GPU #4: GeForce GTX 750 Ti, 227.50 H/s
[2014-06-24 17:57:02] GPU #1: GeForce GTX 750 Ti, 230.30 H/s
[2014-06-24 17:57:03] GPU #0: GeForce GTX 750 Ti, 229.45 H/s
[2014-06-24 17:57:03] GPU #3: GeForce GTX 750 Ti, 229.19 H/s
[2014-06-24 17:57:03] GPU #5: GeForce GTX 750 Ti, 229.90 H/s
[2014-06-24 17:57:04] GPU #2: GeForce GTX 750 Ti, 230.12 H/s
[2014-06-24 17:57:13] GPU #3: GeForce GTX 750 Ti, 225.29 H/s
[2014-06-24 17:57:13] accepted: 46/46 (100.00%), 1372.57 H/s (yay!!!)
[2014-06-24 17:57:02] GPU #1: GeForce GTX 750 Ti, 230.30 H/s
[2014-06-24 17:57:03] GPU #0: GeForce GTX 750 Ti, 229.45 H/s
[2014-06-24 17:57:03] GPU #3: GeForce GTX 750 Ti, 229.19 H/s
[2014-06-24 17:57:03] GPU #5: GeForce GTX 750 Ti, 229.90 H/s
[2014-06-24 17:57:04] GPU #2: GeForce GTX 750 Ti, 230.12 H/s
[2014-06-24 17:57:13] GPU #3: GeForce GTX 750 Ti, 225.29 H/s
[2014-06-24 17:57:13] accepted: 46/46 (100.00%), 1372.57 H/s (yay!!!)
June 24, 2014, 11:14:32 AM
Death to all Windows rigs, mwahahahahhahaha.
This is the generic answer post.
I'm pretty sure I set both the Windows and Linux builds for a combined compute 3.0 and 3.5 build, that shouldn't be a problem in most cases. I'll see if I put together a compute 2.0 version as well, basically stripping out all the latest bells and whistles by Christian and building for 2.0. Anyway, back to the problems. I can't decide which of the other two likely suspects is more likely, trying to run too many threads to fit in the GPU memory (2 MB per thread, that's 8 x 40 x 2 = 640 MB on the default launch setting) or the kernel simply running too slow and triggering TRD. Should probably add a check if the large initial memory allocation succeeds or not but error checking is for little girls
Other thing I realized, I didn't think about rigs that have mixed types of GPUs in them, the launch parameters only takes a single value instead of a comma separated per-device list. Another thing on the todo list.
This is the generic answer post.
I'm pretty sure I set both the Windows and Linux builds for a combined compute 3.0 and 3.5 build, that shouldn't be a problem in most cases. I'll see if I put together a compute 2.0 version as well, basically stripping out all the latest bells and whistles by Christian and building for 2.0. Anyway, back to the problems. I can't decide which of the other two likely suspects is more likely, trying to run too many threads to fit in the GPU memory (2 MB per thread, that's 8 x 40 x 2 = 640 MB on the default launch setting) or the kernel simply running too slow and triggering TRD. Should probably add a check if the large initial memory allocation succeeds or not but error checking is for little girls
Other thing I realized, I didn't think about rigs that have mixed types of GPUs in them, the launch parameters only takes a single value instead of a comma separated per-device list. Another thing on the todo list.
Any ideas on the crazy hash rates on non 750ti cards? https://bitcointalksearch.org/topic/m.7489618
I tried 4x10 to see if maybe it was a memory problem but still get the same result.
OS?
June 24, 2014, 11:09:36 AM
Cryptonight ccMiner is complete fail on my Win 8.1 rig running 5*750Ti. Runs for about 5 secs then CPU shoots to 100% and complete lock up happens.
June 24, 2014, 10:56:35 AM
by the way, what are the "block" and "thread" in the case of this miner ?
Jump to: