CCminer(SP-MOD) Modded GPU kernels.

[qqqq]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

If someones can compile binaries i will testing quark with 45 Mhs.

[1714691390]

1714691390

[1714691390]

1714691390

[t-nelson]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

If someones can compile binaries i will testing quark with 45 Mhs.

What platform?

[qqqq]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

If someones can compile binaries i will testing quark with 45 Mhs.

What platform?

Windows

[t-nelson]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

If someones can compile binaries i will testing quark with 45 Mhs.

What platform?

Windows

Bleh... I'll try to fix my VM.

[djm34]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part).  
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

edit: and again, ccminer (at least my version) was tested on the wallet in order to correct some problem which was occurring in the previous version, and both wallet and miner were released once we (james for the wallet, myself for the miner) were sure  it was finding blocks properly.
(then it was tested on pool...)

edit2: may-be something to try instead of wasting 3 days: pick up an already found block (in the wallet) and try to submit it back with the correct nonce. it should be rejected, however it shouldn't generate a json error.

[t-nelson]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part). 
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

The sprintf() call was the only obvious path to a smashed stack that I saw in submit_upstream_work().  Being as the stack was utterly destroyed, I couldn't examine the parameters passed in to see if they were valid or not.  There could be a scribbler elsewhere, but it's going to take me a few more days to solve another block and hit my breakpoint.

[scryptr]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part).  
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

edit: and again, ccminer (at least my version) was tested on the wallet in order to correct some problem which was occurring in the previous version, and both wallet and miner were released once we (james for the wallet, myself for the miner) were sure  it was finding blocks properly.
(then it was tested on pool...)

GIT CLONE--

I attempted to clone the directory above with "git clone https://github.com/t-nelson/ccminer/tree/solo_stack_smash ." on the Linux command line, and received the message "fatal: repository 'https://github.com/t-nelson/ccminer/tree/solo_stack_smash/' not found".  This is the same command that I use to clone tpruvot's and sp_'s CCminer.

--scryptr

[djm34]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part). 
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

The sprintf() call was the only obvious path to a smashed stack that I saw in submit_upstream_work().  Being as the stack was utterly destroyed, I couldn't examine the parameters passed in to see if they were valid or not.  There could be a scribbler elsewhere, but it's going to take me a few more days to solve another block and hit my breakpoint.

if you are in luck you can try testnet (I tried, however, I haven't been able to sync... )

[qqqq]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part). 
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

The sprintf() call was the only obvious path to a smashed stack that I saw in submit_upstream_work().  Being as the stack was utterly destroyed, I couldn't examine the parameters passed in to see if they were valid or not.  There could be a scribbler elsewhere, but it's going to take me a few more days to solve another block and hit my breakpoint.

if you are in luck you can try testnet (I tried, however, I haven't been able to sync... )

Testnet is a not good thing for testing like finding real blocks. I know the guys who testing via testnet and thinking that eveything is ok, but in real mining is not.

[t-nelson]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part).  
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

edit: and again, ccminer (at least my version) was tested on the wallet in order to correct some problem which was occurring in the previous version, and both wallet and miner were released once we (james for the wallet, myself for the miner) were sure  it was finding blocks properly.
(then it was tested on pool...)

GIT CLONE--

I attempted to clone the directory above with "git clone https://github.com/t-nelson/ccminer/tree/solo_stack_smash ." on the Linux command line, and received the message "fatal: repository 'https://github.com/t-nelson/ccminer/tree/solo_stack_smash/' not found".  This is the same command that I use to clone tpruvot's and sp_'s CCminer.

--scryptr

Clone URL is https://github.com/t-nelson/ccminer.git
Once cloned you can checkout the branch with

Code:

git checkout -b test origin/solo_stack_smash

[t-nelson]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

If someones can compile binaries i will testing quark with 45 Mhs.

What platform?

Windows

Bleh... I'll try to fix my VM.

http://ge.tt/5IlhbIO2/v/0
SHA256: 00cf5e3f815107d4bbf185153393c37b8b16b4bdbc8fb8e36df4e3679e8e025a  ccminer.zip
SHA256: 2c179b8196006a29022be6a6db060b93b4d9ad40f499cb8a3d042371c0fea993  ccminer.exe

[scryptr]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part).  
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

edit: and again, ccminer (at least my version) was tested on the wallet in order to correct some problem which was occurring in the previous version, and both wallet and miner were released once we (james for the wallet, myself for the miner) were sure  it was finding blocks properly.
(then it was tested on pool...)

GIT CLONE--

I attempted to clone the directory above with "git clone https://github.com/t-nelson/ccminer/tree/solo_stack_smash ." on the Linux command line, and received the message "fatal: repository 'https://github.com/t-nelson/ccminer/tree/solo_stack_smash/' not found".  This is the same command that I use to clone tpruvot's and sp_'s CCminer.

--scryptr

Clone URL is https://github.com/t-nelson/ccminer.git
Once cloned you can checkout the branch with

Code:

git checkout -b test origin/solo_stack_smash

CHECKOUT--

I cloned ccminer.git as instructed, changed into the ccminer directory, and issued the above checkout command.  After compiling, I launched your test build of ccminer with my VTC wallet running.  There was the pause on launch after the thread initializaion, about 2 minutes, then the cards began posting hash results.  My 6x 750ti rig is now solo-mining across my LAN to my Win 7 x64 work computer.

According to the CoinWarz calculator, My 36Mh/s VTC rig should find a block every 0.72 days at the current difficulty (~520).  I do not have any error-catching or debugging software, but VertCoins are worth about a nickle each.  If I hit a block and get 50 coins, I could convert them to nickles, find a slot machine, and make myself a wealthy man.    It is all in the probability.       --scryptr

EDIT:  I also downloaded your Windows build and have launched it on my Win 7 x64 computer.  It is mining with the same VTC wallet, adding another 6Mh/s and reducing the average time to find a block to about 1 block every 2/3 day.        --scryptr

[qqqq]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

If someones can compile binaries i will testing quark with 45 Mhs.

What platform?

Windows

Bleh... I'll try to fix my VM.

http://ge.tt/5IlhbIO2/v/0
SHA256: 00cf5e3f815107d4bbf185153393c37b8b16b4bdbc8fb8e36df4e3679e8e025a  ccminer.zip
SHA256: 2c179b8196006a29022be6a6db060b93b4d9ad40f499cb8a3d042371c0fea993  ccminer.exe

Could you please upload somewhere else, mega for ex. Cause i can't download it. Very strange.

scryptr, maybe you can upload you compiled binaries ?

[djm34]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part).  
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

The sprintf() call was the only obvious path to a smashed stack that I saw in submit_upstream_work().  Being as the stack was utterly destroyed, I couldn't examine the parameters passed in to see if they were valid or not.  There could be a scribbler elsewhere, but it's going to take me a few more days to solve another block and hit my breakpoint.

if you are in luck you can try testnet (I tried, however, I haven't been able to sync... )

Testnet is a not good thing for testing like finding real blocks. I know the guys who testing via testnet and thinking that eveything is ok, but in real mining is not.

that's the proper way to test change without tempering with production wallet and it uses the exact same logic as far as mining is concerned (and for vertcoin since it was for testing the new fork and algo, there wasn't any other way to do it...)

[djm34]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

If someones can compile binaries i will testing quark with 45 Mhs.

What platform?

Windows

Bleh... I'll try to fix my VM.

http://ge.tt/5IlhbIO2/v/0
SHA256: 00cf5e3f815107d4bbf185153393c37b8b16b4bdbc8fb8e36df4e3679e8e025a  ccminer.zip
SHA256: 2c179b8196006a29022be6a6db060b93b4d9ad40f499cb8a3d042371c0fea993  ccminer.exe

Could you please upload somewhere else, mega for ex. Cause i can't download it. Very strange.

actually I can't even connect to ge.tt anymore (even though I have an account) malwarebyte forbid it 

[scryptr]

CCMINER STATS--

@T-Nelson--  Your Linux CCminer displays stats differently than sp_'s version.  I get Temperature, Fan Percent, and "c=0/0".  What is the third statistic?       --scryptr

@qqqq--  I don't have a file-sharing account anywhere.  I could send an e-mail attachment.       --scryptr

[scryptr]

VTC BLOCK??? --

While I was typing, I think that I hit a block with my Win 7 x64 GTX 960:


GTX 960 error result, solo-mining VTC on Win 7 x64

Unlike earlier crashes, it wasn't non-functional when found.  I am still getting the same error 18 minutes later, every 30 seconds.

I am going to go back to Quark on my rigs.  If your get another test build, I will try it.       --scryptr

[pallas]

CCMINER STATS--

@T-Nelson--  Your Linux CCminer displays stats differently than sp_'s version.  I get Temperature, Fan Percent, and "c=0/0".  What is the third statistic?       --scryptr

C=graphics clock/memory clock
If you're getting 0, it means it's not supported on your cards. Which chipset?

[pallas]

If anyone waiting on the solo work submission crash can compile, please test https://github.com/t-nelson/ccminer/tree/solo_stack_smash and let me know if it works.  Otherwise it will probably be another three days before I find out myself :/

don't think it is related...ccminer has been sending back much bigger messages (creditcoin for example) without any problem (and without changing that part). 
However I know that the message length has to be the one expected by the wallet otherwise it will get refused (like for neoscrypt btw and a few others. This assertion isn't present in all wallets... but it is present for sure for lyra2rev2 and neoscrypt, but usually the problem is more with getting the message than sending it back)

The sprintf() call was the only obvious path to a smashed stack that I saw in submit_upstream_work().  Being as the stack was utterly destroyed, I couldn't examine the parameters passed in to see if they were valid or not.  There could be a scribbler elsewhere, but it's going to take me a few more days to solve another block and hit my breakpoint.

if you are in luck you can try testnet (I tried, however, I haven't been able to sync... )

I had the same issue just before the vtc fork. Turned out there was nobody mining on testnet so no blocks were generated :-)

[scryptr]

CCMINER STATS--

@T-Nelson--  Your Linux CCminer displays stats differently than sp_'s version.  I get Temperature, Fan Percent, and "c=0/0".  What is the third statistic?       --scryptr

C=graphics clock/memory clock
If you're getting 0, it means it's not supported on your cards. Which chipset?

CHIPSET--

They are 750ti FTW cards, and I think my nVidia drivers are to blame.  I haven't updated them in a while.       --scryptr