For me the only setting that will work is “4x120”. Anything else I’ve tried crashes, even the default of 8x40. I’ve tried so many different combinations. I removed the OC I had on my card and it didn’t make a difference.

Linux:

I tried to get this working on linux. After working through various compile issues mostly with gcc g++ version issues I was able to compile it fine. The issue was that it would say couldn't find cuda device. I tried driver re-installs different cuda versions 5.5 & 6.0 with no luck. Made sure I had all the variable paths correct. Linux saw it and was using it, running nvidia-settings it was listed correctly showing all info. I tried it on ubuntu 14.04 x64. I might have to try again later, maybe on ubuntu 13.10?

I found tutorials to compile cudaminer on linux. I might try a tuturial for getting cudaminer compiled on linux and working first then try ccminer.

It's making windows to think the driver crashed because it's taking long enough without returning a result (windows default is 2 seconds for the GPU) and that's why windows restarts the driver and ccminer won't work and show you impossible hash rate. I made the timeout 40 seconds on my machine (tried with 10 first - it worked for some time, but then it crashed again). This made my laptop second nvidea card to start happily mining with about 22 H/s. Don't do this if you don't have a second video card, because your PC will become completely unusable while mining (if you are cpu mining on the same machine run the cpu miner before running the gpu miner, because otherwise it'll become difficult for you to even start the cpu miner). Here is a link to a .reg file, which will set the timeout to 40 seconds - just double click it and it'll add the setting to the registry (it'll ask you if you are sure). Then you should restart your windows and ccminer should work after the restart. If you find it useful don't forget to tip me https://www.dropbox.com/s/ci8b3h7oxtvd6dq/TdrDelaySetTo40.reg

It's making windows to think the driver crashed because it's taking long enough without returning a result (windows default is 2 seconds for the GPU) and that's why windows restarts the driver and ccminer won't work and show you impossible hash rate. I made the timeout 40 seconds on my machine (tried with 10 first - it worked for some time, but then it crashed again). This made my laptop second nvidea card to start happily mining with about 22 H/s. Don't do this if you don't have a second video card, because your PC will become completely unusable while mining (if you are cpu mining on the same machine run the cpu miner before running the gpu miner, because otherwise it'll become difficult for you to even start the cpu miner). Here is a link to a .reg file, which will set the timeout to 40 seconds - just double click it and it'll add the setting to the registry (it'll ask you if you are sure). Then you should restart your windows and ccminer should work after the restart. If you find it useful don't forget to tip me https://www.dropbox.com/s/ci8b3h7oxtvd6dq/TdrDelaySetTo40.reg

Thank you for this. Going with the same OC on my 780 Ti I applied this and now I'm getting 350-360 using 6x120. I can play with the numbers a bit without crashing now. The best I've been able to do is 6x120 with higher hashrates. There is definitely a sweet spot you have to find. Hey it's better than what my i5 was doing for sure now.

I would like to comment briefly on awarding the bounty since I am responsible for the largest pledge (I think).

From what I have seen, tsiv should receive a bounty payment. I'm not sure he should receive the full amount quite yet. (Though I am also not saying he should not.)

I would like to hear public comments on the following points before reaching a conclusion.

My criteria for awarding the bounty are:

1. Quality. Is the miner 100% reliable, or does it crash or hang?

2. Compatibility. Does the miner support a full range of operating systems, hardware devices (limited to the specified family -- AMD or NV), and drivers? Hardware, operating systems, or drivers which lack some essential features for acceptable performance can be excluded, as can obviously obsolete ones.

3. Open source, maintainability. Is the code provided in a full open source manner, such that others can contribute improvements? Is it well documented, well organized, and easy to understand?

4. Performance. Does the mine provided competitive performance (i.e. does it make sense to actually use it).

100% perfection on every one of these points is not necessary or practical -- certainly not to receive a partial bounty. These are guidelines for evaluation, not specific requirements.

If there are significant deficiencies in any or all of these areas, then the original developer should have the opportunity to address them in order to qualify for the full bounty. Failing that, others may contribute improvements to claim part of the bounty.

I would like to hear substantive comments from any stakeholders or community members addressing these points.

I would like to comment briefly on awarding the bounty since I am responsible for the largest pledge (I think).

From what I have seen, tsiv should receive a bounty payment. I'm not sure he should receive the full amount quite yet. (Though I am also not saying he should not.)

I would like to hear public comments on the following points before reaching a conclusion.

My criteria for awarding the bounty are:

1. Quality. Is the miner 100% reliable, or does it crash or hang?

2. Compatibility. Does the miner support a full range of operating systems, hardware devices (limited to the specified family -- AMD or NV), and drivers? Hardware, operating systems, or drivers which lack some essential features for acceptable performance can be excluded, as can obviously obsolete ones.

3. Open source, maintainability. Is the code provided in a full open source manner, such that others can contribute improvements? Is it well documented, well organized, and easy to understand?

4. Performance. Does the mine provided competitive performance (i.e. does it make sense to actually use it).

100% perfection on every one of these points is not necessary or practical -- certainly not to receive a partial bounty. These are guidelines for evaluation, not specific requirements.

If there are significant deficiencies in any or all of these areas, then the original developer should have the opportunity to address them in order to qualify for the full bounty. Failing that, others may contribute improvements to claim part of the bounty.

I would like to hear substantive comments from any stakeholders or community members addressing these points.

1. Definitely no crashing or hanging in my experience. Since crashing can be a result of overclocking and improper settings, I share mine in hopes to avoid 'crashing' as an obstacle to Tsiv's bounty: I have clocks set via msi afterburner on all 3 rigs / 17 gpus, and use +140 / +317 / 95% power. My os are all w7 x64, 8gb ram or higher.

2. I can only personally attest to w7 x64 os. I have read (in the cudaminer thread on this forum site) that S_tring has made it possible to mine in w8 by specifying switches (-l 6x40) follow this link: https://bitcointalk.org/index.php?topic=167229.msg7529384#msg7529384This leaves Linux based OS, OSX (if anybody mines using that os, I just dont know), and older versions of windows.As for hardware devices, I have strong opinions on this one: the Tsiv miner is intended for Nvidia, and in my opinion the only real nvidia gpu worthy of being used for mining is the GTX 750ti (until more maxwell GPUs come out that are comparable or superior in terms of hash/cost and hash/watt. This said, the newer nvidia gpus do seem to be supported. And I can see a scenario such as this: ask forum members to chime in re compatibility with their specific nvidia GPUs; ask Tsiv to modify his miner to support the missing ones (just the major ones, of course).

3. I am not a coder, so I can't answer this one. I just know some basics that giv me impression in the affirmative: [.a.] the code is essentially a fork of CBuchner & ChrisH's ccminer; [.b.] it is (has been) on github for a long time with many revisions, contributions

4. I get 210-220h/s per gpu x 17gpus = 3.5 kh/s average (conservative), and total wattage of 920w (an over estimate). As the miner app gets revised, expect that it will get more power hungry in order to deliver more hashes. In my experience, the current miner from other algos require 10-15% more power from my rigs, whereas previously, they consume around the same wattage as Tsiv's miner, and delivered around 20-25% less hashes.

To be fair, I believe Tsiv already deserves a substantial portion of the bounty. However it is also practical to withhold a small portion of the bounty for some things people may have overlooked. In the interest of fairness, may I suggest think of it as a warranty period -- if no problems arise in the next 14 days (a lifetime in cryptoland), then Tsiv gets awarded the balance of the bounty.

I have since been able to test it on my little gt 640 thanks to the contribution of the registry file from equipoise, for windows. Before that it blew my drivers immediately. I ran the program successfully for just over 5 hours after that modification, at a rate of 8 whopping hashes/s (it tops out at 32 h/s but I wanted to be able to have better use of the computer. Program did not crash or hang for that time. Address I mined to @ mro.poolto.be =

2. Compatibility. Does the miner support a full range of operating systems, hardware devices (limited to the specified family -- AMD or NV), and drivers? Hardware, operating systems, or drivers which lack some essential features for acceptable performance can be excluded, as can obviously obsolete ones.

Still testing on multiple OS's, but can confirm does work w/ windows 7 64 bit, and vista 64 bit. I won't be able to test it further than that until after next week, as I will be away from my equipment until then .. but I see that other people have used many OS's and would like to hear from them. I've now seen support down to compute 2.1 levels, using whatever driver was newest/not beta

Quote

4. Performance. Does the miner provide competitive performance (i.e. does it make sense to actually use it).

I can buy a 640 for about the same cost as a haswell pentium (~the same cost if buying on ebay). Both top out around 30 h/s. It seems to be competitive from my situation, and would make sense to mine with the card if I wanted to mine. Have not measured power consumption .. but I don't think anyone in my situation would be overly concerned with that

Quote

100% perfection on every one of these points is not necessary or practical -- certainly not to receive a partial bounty. These are guidelines for evaluation, not specific requirements.

If there are significant deficiencies in any or all of these areas, then the original developer should have the opportunity to address them in order to qualify for the full bounty. Failing that, others may contribute improvements to claim part of the bounty.

I would like to hear substantive comments from any stakeholders or community members addressing these points.

Overall I'm very satisfied with the program, and would gladly release partial/full bounty .. pending a quick answer for why I had to edit the registry to get the program to operate. Equipoise I will send you a few xmr outside of the bounty, thanks a lot for providing it! I would like to hear some more from tsiv.

I can buy a 640 for about the same cost as a haswell pentium (~the same cost if buying on ebay). Both top out around 30 h/s. It seems to be competitive from my situation, and would make sense to mine with the card if I wanted to mine. Have not measured power consumption .. but I don't think anyone in my situation would be overly concerned with that

I would like to comment briefly on awarding the bounty since I am responsible for the largest pledge (I think).

From what I have seen, tsiv should receive a bounty payment. I'm not sure he should receive the full amount quite yet. (Though I am also not saying he should not.)

I would like to hear public comments on the following points before reaching a conclusion.

My criteria for awarding the bounty are:

1. Quality. Is the miner 100% reliable, or does it crash or hang?

2. Compatibility. Does the miner support a full range of operating systems, hardware devices (limited to the specified family -- AMD or NV), and drivers? Hardware, operating systems, or drivers which lack some essential features for acceptable performance can be excluded, as can obviously obsolete ones.

3. Open source, maintainability. Is the code provided in a full open source manner, such that others can contribute improvements? Is it well documented, well organized, and easy to understand?

4. Performance. Does the mine provided competitive performance (i.e. does it make sense to actually use it).

100% perfection on every one of these points is not necessary or practical -- certainly not to receive a partial bounty. These are guidelines for evaluation, not specific requirements.

If there are significant deficiencies in any or all of these areas, then the original developer should have the opportunity to address them in order to qualify for the full bounty. Failing that, others may contribute improvements to claim part of the bounty.

I would like to hear substantive comments from any stakeholders or community members addressing these points.

Running this miner for 24h without troubles on my linux dedicated rig, 12x750ti running @198H/s each.No troubles, no crash. He deserve this bounty as the first really good Nvidia CryptoNight miner Current estimation is 12.5$/day for me, It's in the top 3 of rentability right now if I check what I use to mine.

It's making windows to think the driver crashed because it's taking long enough without returning a result (windows default is 2 seconds for the GPU) and that's why windows restarts the driver and ccminer won't work and show you impossible hash rate. I made the timeout 40 seconds on my machine (tried with 10 first - it worked for some time, but then it crashed again). This made my laptop second nvidea card to start happily mining with about 22 H/s. Don't do this if you don't have a second video card, because your PC will become completely unusable while mining (if you are cpu mining on the same machine run the cpu miner before running the gpu miner, because otherwise it'll become difficult for you to even start the cpu miner). Here is a link to a .reg file, which will set the timeout to 40 seconds - just double click it and it'll add the setting to the registry (it'll ask you if you are sure). Then you should restart your windows and ccminer should work after the restart. If you find it useful don't forget to tip me https://www.dropbox.com/s/ci8b3h7oxtvd6dq/TdrDelaySetTo40.reg

Thank you for this. Going with the same OC on my 780 Ti I applied this and now I'm getting 350-360 using 6x120. I can play with the numbers a bit without crashing now. The best I've been able to do is 6x120 with higher hashrates. There is definitely a sweet spot you have to find. Hey it's better than what my i5 was doing for sure now.

There is something more to be done about the -l MxN.About the first number M:"First of all, your thread block size should always be a multiple of 32, because kernels issue instructions in warps (32 threads). For example, if you have a block size of 50 threads, the GPU will still issue commands to 64 threads and you'd just be wasting them."About the second number N:You could find it by gradually increasing it until your card stop working (showing impossible hash rate 3474958.52 H/s) and then restart is needed for maximum performance (but not for testing), because without restart my hash rate is felling 2x compared to the same options before the crash.