Reject REason: "share above target"
or "result does not validate on CPU" errors.
http://imgur.com/NJAJzE0
Topic: Star Trek Crypto Coin thread - Big changes are coming!! - page 37. (Read 40235 times)
is it normal to get errors mining GPL? I got a lot of
Reject REason: "share above target"
or "result does not validate on CPU" errors.
http://imgur.com/NJAJzE0
Reject REason: "share above target"
or "result does not validate on CPU" errors.
http://imgur.com/NJAJzE0
GPL - PoW/PoS or PoW only?
@trid, GPL is PoW/PoS, but the maturity time is 1 year. It's really a rare coin.
can you please address my question here https://bitcointalksearch.org/topic/m.4078561
I have over 1000 darsek that I mined at kedcoin.com before the relaunch. Can you please confirm this? I can't submit my wallet.dat because the pool owner has it.
Also what is going on with UFC?
@tokyoghetto, I am very sure that Dream will be able to get that to you.
Wrt UFC, stay tuned. A public information about that is coming 'Very Soon'TM
Please mail your old Darsek wallets to:
[email protected]
Attach the wallet.dat as a file and let me know what address on the new chain you want the replacement coins sent to.
Please allow for a couple of days, especially while I am still cleaning up the relaunch.
[email protected]
Attach the wallet.dat as a file and let me know what address on the new chain you want the replacement coins sent to.
Please allow for a couple of days, especially while I am still cleaning up the relaunch.
Just got my 999 KED back! Thanks Dreamwatcher!
Please mail your old Darsek wallets to:
[email protected]
Attach the wallet.dat as a file and let me know what address on the new chain you want the replacement coins sent to.
Please allow for a couple of days, especially while I am still cleaning up the relaunch.
[email protected]
Attach the wallet.dat as a file and let me know what address on the new chain you want the replacement coins sent to.
Please allow for a couple of days, especially while I am still cleaning up the relaunch.
can you please address my question here https://bitcointalksearch.org/topic/m.4078561
I have over 1000 darsek that I mined at kedcoin.com before the relaunch. Can you please confirm this? I can't submit my wallet.dat because the pool owner has it.
Also what is going on with UFC?
GPL has been stable, the original client and the network is working very well. I am mining it as we speak.
GPL - PoW/PoS or PoW only?
Is Gold Pressed Latinum being relaunched also? Or is it the same as it was before, has the difficulty been reset?
GPL has been stable, the original client and the network is working very well. I am mining it as we speak.
bump
Each block is only 3.5 coins correct?
Chain Type: Scrypt/POS
Block Target Time: 1 Minute
POW Block Reward: 3.5
PPC type re-targeting
Trade confirm: 6 Blocks
Coin maturity: 120 Blocks
RPC Port: 8444
P2P Port:8443
Yes
Each block is only 3.5 coins correct?
Please mail your old Darsek wallets to:
[email protected]
Attach the wallet.dat as a file and let me know what address on the new chain you want the replacement coins sent to.
Please allow for a couple of days, especially while I am still cleaning up the relaunch.
[email protected]
Attach the wallet.dat as a file and let me know what address on the new chain you want the replacement coins sent to.
Please allow for a couple of days, especially while I am still cleaning up the relaunch.
nº total coins?
I set it the same as the original chain: 500 million
nº total coins?
For solo mining: reboot the windows machine, start the client. If the client crashes, don´t close the c++ warning message. Still try connecting with your favorite miner like cgminer or bfgminer (last works fine for me)
With some luck your miner is working, only the gui crashes. I hit some blocks with 3 coins in minutes while gui not working.
@dreamwatcher: working on the RPC problem?
With some luck your miner is working, only the gui crashes. I hit some blocks with 3 coins in minutes while gui not working.
@dreamwatcher: working on the RPC problem?
I was just coming here to give the same advice. The errors Windows is showing are really non-fatal. Windows is complaining about how the client is closing threads.
This happens much more with RPC as RPC threads are always being opened and closed.
This is no longer a code issue, it is a compile issue between QT and Windows.
You can solo mine with Windows, just ignore the error as it really does not mean anything. In fact the only reason you have to shut down after this "non-crash" to restart the client, is because the client never really crashed. It still running even though Windows is hiding the GUI(QT) from you.
I will continue to work to fix this compile issue and get back ASAP.
Restarting windows allowed the darsek client to start.
For solo mining: reboot the windows machine, start the client. If the client crashes, don´t close the c++ warning message. Still try connecting with your favorite miner like cgminer or bfgminer (last works fine for me)
With some luck your miner is working, only the gui crashes. I hit some blocks with 3 coins in minutes while gui not working.
@dreamwatcher: working on the RPC problem?
With some luck your miner is working, only the gui crashes. I hit some blocks with 3 coins in minutes while gui not working.
@dreamwatcher: working on the RPC problem?
sorry about that, but "this application has requested the runtime to terminate in an unusual way."
I tried different win7 32bit and 64bit machines, the client crashes. Sometimes it runs for some minutes
but crashes when trying to solo mine or just type "peerinfo" on the debug window. Im sure you will fix it
I tried different win7 32bit and 64bit machines, the client crashes. Sometimes it runs for some minutes
but crashes when trying to solo mine or just type "peerinfo" on the debug window. Im sure you will fix it
I put the linux darsekd on a VPS and tried to add it as a node on my windows client.
from the console i used addnode thith the IP address. I immediately got the this application has requested the runtime to terminate in an unusual way message.
Now I get it every time I launch.
I tried removing all but wallet.dat from my %appdata%/Darsek folder no luck. So since my wallet was empty removed the entire Darsek folder and let it build a new wallet.dat.
Still have same message on launch.
I'm getting this error
Some detail to point you in the right direction
Some detail to point you in the right direction
That is due to you having the old Darsek directory on your machine. Move your wallet.dat file somewhere so you can send it in for redemption and delete everything out of your Darsek data Directory.
The issue is while Linux sees .darsek and .Darsek as different directories, Windows does not. The client cannot do the assertion because it is reading from the old chain and it does not match what is in its source.
The only old darsek I had was the test ting so I just got rid of it.
Now it works and I have a addreess for the pool now
Waiting for the Darsek swap!
Still have 34916 Darsek in my old wallet
Main addresses in my wallet:
Bt4uMqVQrjdNzxrcH8kpa72QUVQQYpWLNS
Btft3LJXCSBRgVGoPmufb8KBgeP7vAP3F5
Still have 34916 Darsek in my old wallet
Main addresses in my wallet:
Bt4uMqVQrjdNzxrcH8kpa72QUVQQYpWLNS
Btft3LJXCSBRgVGoPmufb8KBgeP7vAP3F5
OK so far:
This is what the debugger looks like with the crash. I remember having some issues with the way Windows handles RPC calls (RPCRTRemote.DLL)
The KillTimers error for the Qobject is what causes you to have to reset Windows to restart after the Mining error because not all the Clients threads are being shut down. That bug will be fixed automatically when what appears to be a RPC bug is squashed.
Code:
ModLoad: 00000000`75170000 00000000`7517e000 C:\Windows\SysWOW64\RpcRtRemote.dll
ModLoad: 00000000`745f0000 00000000`745f8000 C:\Windows\SysWOW64\winrnr.dll
ModLoad: 00000000`72fc0000 00000000`72fdc000 C:\Windows\SysWOW64\IPHLPAPI.DLL
ModLoad: 00000000`72fb0000 00000000`72fb7000 C:\Windows\SysWOW64\WINNSI.DLL
ModLoad: 00000000`70c70000 00000000`70c76000 C:\Windows\SysWOW64\rasadhlp.dll
ModLoad: 00000000`74e00000 00000000`74e38000 C:\Windows\SysWOW64\fwpuclnt.dll
ModLoad: 00000000`0cd60000 00000000`0d9aa000 C:\Windows\SysWOW64\shell32.dll
ModLoad: 00000000`0cd60000 00000000`0ce60000 C:\Windows\SysWOW64\user32.dll
ModLoad: 00000000`0cf60000 00000000`0dbaa000 C:\Windows\SysWOW64\shell32.dll
Invalid parameter passed to C runtime function.
Invalid parameter passed to C runtime function.
QObject::killTimers: timers cannot be stopped from another thread
ntdll!ZwTerminateProcess+0xa:
00000000`77b9157a c3 ret
This is what the debugger looks like with the crash. I remember having some issues with the way Windows handles RPC calls (RPCRTRemote.DLL)
The KillTimers error for the Qobject is what causes you to have to reset Windows to restart after the Mining error because not all the Clients threads are being shut down. That bug will be fixed automatically when what appears to be a RPC bug is squashed.
Jump to: