I still get gpu 0 found nonce plus the readout of the card I'm benchmarking. I don't know why.
That's because sp is using the thread id for the "nonce found" message, not the card number. 
Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 695. (Read 2347641 times)
i have a little problem when running 3 or more card, their memory is sitting at 3000mega instead of 3600, those are 970
Thanks Sp_ for the git updates!
Cool you are still opensourcing some juice ;-)
Cool you are still opensourcing some juice ;-)
Opensourcing is the correct way to do it, but private kernals give more profit. I will opensource some of my work as long as donations keep coming.
It's because I forked ccminer 1.5 back in 2014, and have done 1000+ checkins to improve the speed for the maxwell cards. (Alot of free work)
https://github.com/sp-hash/ccminer/commits/windows
Tvpruvot hasn't merged all my changes in his latest ccminer 1.7.5
The sp-mod private includes some extra speed for the donators.
I am working to merge all my kernals into the 1.7.5 release, but it takes time.
https://github.com/sp-hash/ccminer/commits/windows
Tvpruvot hasn't merged all my changes in his latest ccminer 1.7.5
The sp-mod private includes some extra speed for the donators.
I am working to merge all my kernals into the 1.7.5 release, but it takes time.
that hashrate is impressive are you using sp mod or what? i can barely scratch 13.5 mega with 1500 core
SPmod 5 is getting around 19.1 at around 1500 Mhz core (GV-N970WF3OC).
ah yes i'm now getting 16.6 with sp mod, and 12 with decred fork, didn't know it was so inefficient with quark, qubit etc...
that hashrate is impressive are you using sp mod or what? i can barely scratch 13.5 mega with 1500 core
SPmod 5 is getting around 19.1 at around 1500 Mhz core (GV-N970WF3OC).
If you wonder why quark is +62% and x11 is only up 18%, it's because x11 need some more work and donations...
I just did a comparison between my buyable private miner (0.1BTC) and the latest 1.7.5 release.
I have written 0-10% faster, but I should have written 17-74% faster
Sp-Mod #5 default intensities hashrates in MHASH/s. (980ti 1290 coreclock/1650 memclock)
nist5: 43.80 (+17%)
quark: 27.85 (+61,91%)
lyra2v2 16.10 (+16.6%)
x11: 12.85 (+18%)
x13: 10.27 (+19.97)
x15: 8.83 (+18.52 )
neoscrypt: 0.99 (+73.68%)
1.7.5: (32bit windows build cuda 7.5) default intensities in MHASH/s (980ti 1290 coreclock/1650 memclock)
nist5: 37.45
quark: 17.20
lyra2v2: 13.81
x11: 10.88
x13: 8.56
x15: 7.45
neoscrypt: 0.57
1.7.5: (32bit windows build cuda 6.5) (980ti 1290 coreclock/1650 memclock)
nist5: 38.93
quark: 17.5
lyra2v2: 13.18
x11: 10.95
x13: 8.88
x15: 7.7
neoscrypt: 0.71
I have written 0-10% faster, but I should have written 17-74% faster
Sp-Mod #5 default intensities hashrates in MHASH/s. (980ti 1290 coreclock/1650 memclock)
nist5: 43.80 (+17%)
quark: 27.85 (+61,91%)
lyra2v2 16.10 (+16.6%)
x11: 12.85 (+18%)
x13: 10.27 (+19.97)
x15: 8.83 (+18.52 )
neoscrypt: 0.99 (+73.68%)
1.7.5: (32bit windows build cuda 7.5) default intensities in MHASH/s (980ti 1290 coreclock/1650 memclock)
nist5: 37.45
quark: 17.20
lyra2v2: 13.81
x11: 10.88
x13: 8.56
x15: 7.45
neoscrypt: 0.57
1.7.5: (32bit windows build cuda 6.5) (980ti 1290 coreclock/1650 memclock)
nist5: 38.93
quark: 17.5
lyra2v2: 13.18
x11: 10.95
x13: 8.88
x15: 7.7
neoscrypt: 0.71
He is running sp-mod private #5 (0.1BTC)
check that the sata for the riser is separate, maybe try installing just the one card and see then if it will change anything. maybe check the asic quality with gpu-z to see what comes up.
I just ran it then activated nvidia inspector ...crash! So I updated it a week ago but I also had trouble getting the drivers to install ... as soon as I added that card..... everything started crashing.Gpu-z how do I check the asic quality with that?
I also had all memory clocks show 4505 on my 2x 980ti and the one 970..then I added the second one and the memory clocks showed 4505 on the 980ti and 5109 on both 970's. Like they linked up.
Looks good....before crash.
that hashrate is impressive are you using sp mod or what? i can barely scratch 13.5 mega with 1500 core
Try swapping the suspect card with card 0 (in the x16 slot I presume) to see if the probkem moves.
Swapping cards... but gpu0 is not the 16x slot.
I think you're going in the wrong direction. You installed a new card and your system destabilized.
You know the system was stable before but you don't know if the card is defective. That is
your first objective. You need to isolate the problem.
Swap the suspect card with whatever card just to see if the problem follows it. Try removing the suspect card to
get back to a stable system. Try removing all but the suspect card. Look for a pattern.
If the card proves ok then you can look at system problems, starting with power. Do you have enough power?
Do you have too many risers on the same rail?
There appears to be nothing in the software that has changed that could have caused it.
@tbearhere - I was thinking the same thing. If you don't have enough power feeding the cards the system will act wonky! What size power supply and how many video cards in total on the board? Only (2) 970's?
check that the sata for the riser is separate, maybe try installing just the one card and see then if it will change anything. maybe check the asic quality with gpu-z to see what comes up.
I just ran it then activated nvidia inspector ...crash! So I updated it a week ago but I also had trouble getting the drivers to install ... as soon as I added that card..... everything started crashing.Gpu-z how do I check the asic quality with that?
I also had all memory clocks show 4505 on my 2x 980ti and the one 970..then I added the second one and the memory clocks showed 4505 on the 980ti and 5109 on both 970's. Like they linked up.
Looks good....before crash.
Do you have SLI enabled by any chance?
Now it only last a minute then crashes.
How do I check to disabled it? thx
EDIT: I'm checking now but I didn't enable it unless it does it automatically.
I can't even access nvidia control panel.
tbearhere ...
the sli connection is a physical connector for the cards ... if the cards are separate ( ie - you dont have a phisical connecter ont he top of both cards connecting them to one another ) - then you dont have sli connected ...
unless there is a bios settign as well that you changed - then sli will be disabled there as well - though i dont now of any bios settigns that exist for sli anyway ... but i thought id mention that just in case ...
i also noticed that you are running ccminer with NO -i settings ... have you considered that the default intensity is way too high for the cards? ...
sp doesnt publish the default intensities ( actually none of the devs do - and ive requested this many times before in this thread - but no one has ) - so there may be an intensity issue here ...
try using -i 16 as a lower intensity - which wont mine much - but may just show you that the miner itself is stable ... if it still crashes while intensity is as low as 16 - then im out of ideas ... unless i had the machine infront of me for a full rebuild ...
#crysx
check that the sata for the riser is separate, maybe try installing just the one card and see then if it will change anything. maybe check the asic quality with gpu-z to see what comes up.
I just ran it then activated nvidia inspector ...crash! So I updated it a week ago but I also had trouble getting the drivers to install ... as soon as I added that card..... everything started crashing.Gpu-z how do I check the asic quality with that?
I also had all memory clocks show 4505 on my 2x 980ti and the one 970..then I added the second one and the memory clocks showed 4505 on the 980ti and 5109 on both 970's. Like they linked up.
Looks good....before crash.
Do you have SLI enabled by any chance?
Now it only last a minute then crashes.
How do I check to disabled it? thx
EDIT: I'm checking now but I didn't enable it unless it does it automatically.
I can't even access nvidia control panel.
check that the sata for the riser is separate, maybe try installing just the one card and see then if it will change anything. maybe check the asic quality with gpu-z to see what comes up.
I just ran it then activated nvidia inspector ...crash! So I updated it a week ago but I also had trouble getting the drivers to install ... as soon as I added that card..... everything started crashing.Gpu-z how do I check the asic quality with that?
I also had all memory clocks show 4505 on my 2x 980ti and the one 970..then I added the second one and the memory clocks showed 4505 on the 980ti and 5109 on both 970's. Like they linked up.
Looks good....before crash.
Do you have SLI enabled by any chance?
Try swapping the suspect card with card 0 (in the x16 slot I presume) to see if the probkem moves.
Swapping cards... but gpu0 is not the 16x slot.
I think you're going in the wrong direction. You installed a new card and your system destabilized.
You know the system was stable before but you don't know if the card is defective. That is
your first objective. You need to isolate the problem.
Swap the suspect card with whatever card just to see if the problem follows it. Try removing the suspect card to
get back to a stable system. Try removing all but the suspect card. Look for a pattern.
If the card proves ok then you can look at system problems, starting with power. Do you have enough power?
Do you have too many risers on the same rail?
There appears to be nothing in the software that has changed that could have caused it.
The "--broken-neo-wallet" switch doesn't fix the issue for solo-mining neoscrypt coins?
"--BROKEN-NEO-WALLET" --
That fixed it! I am communicating with my PhoenixCoin (PXC) wallet. When I get the fine details down, I will report them. FeatherCoin is next up.
I remembered the command, but not the exact syntax. Thank you for the reminder! --scryptr
Was just about to write that. ccminer --help is always useful.
I solomined some FTC 3 days ago on the old wallet. I refuse to use the 9x wallets until the issue with the orphans is fixed.
FEATHERCOIN IS STUBBORN--
Using the v0.9.3.1 wallet I was not able to solo-mine, even using a nearly identical set of configuration files as I used for PhoenixCoin. I spent about an hour, then went back to the pool for FeatherCoin. I'll try again later. --scryptr
Sorry sp I have no place to go but here to get help on my card 970 gtx gigabyte G1 not working.
Ok I was mining ok on my rig then I got a 2nd 970 G1 and ever since my rig won't work constantly.
Drivers crash.. ccminer crashes... ect. I tried replacing the power riser .. but still happening. It maybe a bad card I don't know. So I did a benchmark test
and this is the result. And it doesn't matter which card I benchmark .. I still get gpu 0 found nonce plus the readout of the card I'm benchmarking. I
don't know why.
My rig just crashes or ccminer and or drivers crash.
And help please... Anyone.
Ok I was mining ok on my rig then I got a 2nd 970 G1 and ever since my rig won't work constantly.
Drivers crash.. ccminer crashes... ect. I tried replacing the power riser .. but still happening. It maybe a bad card I don't know. So I did a benchmark test
and this is the result. And it doesn't matter which card I benchmark .. I still get gpu 0 found nonce plus the readout of the card I'm benchmarking. I
don't know why.
My rig just crashes or ccminer and or drivers crash.
And help please... Anyone.
The benchmark thing may be unrelated to your problem.
Try swapping the suspect card with card 0 (in the x16 slot I presume) to see if the probkem moves.
EDIT: Just got net framework crash report covering nividia inspector JIT .. ect.
And I read the error report ... it maybe just maybe I need an app updated.
No that wasn't it.
Swapping cards... but gpu0 is not the 16x slot.
And I thought the 970 g1 fans were supposed to stop when idle. They consistently run.
The "--broken-neo-wallet" switch doesn't fix the issue for solo-mining neoscrypt coins?
"--BROKEN-NEO-WALLET" --
That fixed it! I am communicating with my PhoenixCoin (PXC) wallet. When I get the fine details down, I will report them. FeatherCoin is next up.
I remembered the command, but not the exact syntax. Thank you for the reminder! --scryptr
Was just about to write that. ccminer --help is always useful.
I solomined some FTC 3 days ago on the old wallet. I refuse to use the 9x wallets until the issue with the orphans is fixed.
SOLO-MINING FEATHERCOIN--
I was reading in Ghostlander's thread about the difficulty they have had with the FeatherCoin wallet. Apparently, wallet v0.9.3.1 is the recommended stable version, as versions prior to and after (v11.x has been recalled) may cause blockchain problems. If a miner is to solo-mine, he must use wallet v0.9.3.1 to avoid this problem, and to receive proper payouts.
What I came across is this:
" ghostlander REGULAR MEMBER 10 days ago
Solo mining works through Getwork. It’s broken in SGminer still. NSGminer works fine. "
Ghostlander is referring to his special version of SGminer, NSGminer (neoscrypt SGminer). It is an OpenCL miner that is AMD oriented, but reputed to work with nVidia cards as well. Ghostlander knows the workings of the FeatherCoin wallet, and also the PhoenixCoin wallet.
Whatever the code must be in NSGminer, it may fix the problems with solo-mining neoscrypt coins that CCminer has. I am hoping a good coder could look into the code for a good patch. --scryptr
I was reading in Ghostlander's thread about the difficulty they have had with the FeatherCoin wallet. Apparently, wallet v0.9.3.1 is the recommended stable version, as versions prior to and after (v11.x has been recalled) may cause blockchain problems. If a miner is to solo-mine, he must use wallet v0.9.3.1 to avoid this problem, and to receive proper payouts.
What I came across is this:
" ghostlander REGULAR MEMBER 10 days ago
Solo mining works through Getwork. It’s broken in SGminer still. NSGminer works fine. "
Ghostlander is referring to his special version of SGminer, NSGminer (neoscrypt SGminer). It is an OpenCL miner that is AMD oriented, but reputed to work with nVidia cards as well. Ghostlander knows the workings of the FeatherCoin wallet, and also the PhoenixCoin wallet.
Whatever the code must be in NSGminer, it may fix the problems with solo-mining neoscrypt coins that CCminer has. I am hoping a good coder could look into the code for a good patch. --scryptr
The "--broken-neo-wallet" switch doesn't fix the issue for solo-mining neoscrypt coins?
"--BROKEN-NEO-WALLET" --
That fixed it! I am communicating with my PhoenixCoin (PXC) wallet. When I get the fine details down, I will report them. FeatherCoin is next up.
PhoenixCoin solo-mined with CCminer
I remembered the command, but not the exact syntax. Thank you for the reminder! --scryptr
SOLO-MINING FEATHERCOIN--
I was reading in Ghostlander's thread about the difficulty they have had with the FeatherCoin wallet. Apparently, wallet v0.9.3.1 is the recommended stable version, as versions prior to and after (v11.x has been recalled) may cause blockchain problems. If a miner is to solo-mine, he must use wallet v0.9.3.1 to avoid this problem, and to receive proper payouts.
What I came across is this:
" ghostlander REGULAR MEMBER 10 days ago
Solo mining works through Getwork. It’s broken in SGminer still. NSGminer works fine. "
Ghostlander is referring to his special version of SGminer, NSGminer (neoscrypt SGminer). It is an OpenCL miner that is AMD oriented, but reputed to work with nVidia cards as well. Ghostlander knows the workings of the FeatherCoin wallet, and also the PhoenixCoin wallet.
Whatever the code must be in NSGminer, it may fix the problems with solo-mining neoscrypt coins that CCminer has. I am hoping a good coder could look into the code for a good patch. --scryptr
I was reading in Ghostlander's thread about the difficulty they have had with the FeatherCoin wallet. Apparently, wallet v0.9.3.1 is the recommended stable version, as versions prior to and after (v11.x has been recalled) may cause blockchain problems. If a miner is to solo-mine, he must use wallet v0.9.3.1 to avoid this problem, and to receive proper payouts.
What I came across is this:
" ghostlander REGULAR MEMBER 10 days ago
Solo mining works through Getwork. It’s broken in SGminer still. NSGminer works fine. "
Ghostlander is referring to his special version of SGminer, NSGminer (neoscrypt SGminer). It is an OpenCL miner that is AMD oriented, but reputed to work with nVidia cards as well. Ghostlander knows the workings of the FeatherCoin wallet, and also the PhoenixCoin wallet.
Whatever the code must be in NSGminer, it may fix the problems with solo-mining neoscrypt coins that CCminer has. I am hoping a good coder could look into the code for a good patch. --scryptr
The "--broken-neo-wallet" switch doesn't fix the issue for solo-mining neoscrypt coins?
Sorry sp I have no place to go but here to get help on my card 970 gtx gigabyte G1 not working.
Ok I was mining ok on my rig then I got a 2nd 970 G1 and ever since my rig won't work constantly.
Drivers crash.. ccminer crashes... ect. I tried replacing the power riser .. but still happening. It maybe a bad card I don't know. So I did a benchmark test
and this is the result. And it doesn't matter which card I benchmark .. I still get gpu 0 found nonce plus the readout of the card I'm benchmarking. I
don't know why.
My rig just crashes or ccminer and or drivers crash.
And help please... Anyone.
Ok I was mining ok on my rig then I got a 2nd 970 G1 and ever since my rig won't work constantly.
Drivers crash.. ccminer crashes... ect. I tried replacing the power riser .. but still happening. It maybe a bad card I don't know. So I did a benchmark test
and this is the result. And it doesn't matter which card I benchmark .. I still get gpu 0 found nonce plus the readout of the card I'm benchmarking. I
don't know why.
My rig just crashes or ccminer and or drivers crash.
And help please... Anyone.
The benchmark thing may be unrelated to your problem.
Try swapping the suspect card with card 0 (in the x16 slot I presume) to see if the probkem moves.
EDIT: Just got net framework crash report covering nividia inspector JIT .. ect.
And I read the error report ... it maybe just maybe I need an app updated.
No that wasn't it.
Swapping cards... but gpu0 is not the 16x slot.
Jump to: