Topic: Claymore's CryptoNote Windows CPU Miner v4.0 - page 32. (Read 565401 times)
What about Ubuntu 14.04 x64 support?
******************** ERROR ********************
CANNOT ALLOCATE MEMORY!
Error #103-1-1
Start miner with ADMIN rights to configure system for best performance and then
REBOOT computer.
It is necessary to do it only once.
***********************************************
CANNOT ALLOCATE MEMORY!
Error #103-1-1
Start miner with ADMIN rights to configure system for best performance and then
REBOOT computer.
It is necessary to do it only once.
***********************************************
this is a common issue for the cpu miner on windows 8/8.1... all my win 7 rigs work excellent but my 2 win 8.1 rigs do not like the cpu miner and wont allocate memory giveing the same error.
Any chance of looking into this issue Claymore??
******************** ERROR ********************
CANNOT ALLOCATE MEMORY!
Error #103-1-1
Start miner with ADMIN rights to configure system for best performance and then
REBOOT computer.
It is necessary to do it only once.
***********************************************
CANNOT ALLOCATE MEMORY!
Error #103-1-1
Start miner with ADMIN rights to configure system for best performance and then
REBOOT computer.
It is necessary to do it only once.
***********************************************
Disable UAC (check OP for details), reboot and try again.
I fear for the safety of your computer. Perhaps start mining this service without shutting down completely?When you try to run with administrator privileges via the right mouse button does not start mining.
reboot.
186 h/s
I7-3770
Win 7 64bit
12Gb
2*7870 - no mining
-t 4
Disable UAC (check OP for details), reboot and try again.
reboot.
186 h/s
I7-3770
Win 7 64bit
12Gb
2*7870 - no mining
-t 4
You can build one version with fflush(stdout) after printf?
Not right now.
You can build one version with fflush(stdout) after printf?
I cannot redirect stdout using pipes, what function you use to print output?
printf
I cannot redirect stdout using pipes, what function you use to print output?
v3.2 is available:
- Added minergate pool support.
- Added "main pool" - miner will try to use main pool every 30 minutes.
- "pools.txt" file - now you can specify login and password for every pool.
- Current pool address is displayed for every new job.
- Improved stability.
- Added minergate pool support.
- Added "main pool" - miner will try to use main pool every 30 minutes.
- "pools.txt" file - now you can specify login and password for every pool.
- Current pool address is displayed for every new job.
- Improved stability.
Why do I get this message ??
I'm running in a sandbox, win 7 x64
I'm running in a sandbox, win 7 x64
Please consider this.
Since your software is in beta phase, and many bugs are ( will be detected) until final stuff is out lower you feed. If we are all here beta testers of YOUR product, and if we all loose because YOUR bugs in program, then lower feed, or made time limited app.
If we not tested your product, no one will use it because will be unstable, and with bugs. What you will get in that case?- Nothing since no one will use your app.
And what worth that your app is faster then Wolf if we dont have any problem with Wolf and have lots of problem with your app?.
Since your software is in beta phase, and many bugs are ( will be detected) until final stuff is out lower you feed. If we are all here beta testers of YOUR product, and if we all loose because YOUR bugs in program, then lower feed, or made time limited app.
If we not tested your product, no one will use it because will be unstable, and with bugs. What you will get in that case?- Nothing since no one will use your app.
And what worth that your app is faster then Wolf if we dont have any problem with Wolf and have lots of problem with your app?.
v 2.2 is available:
- Fixed bugs.
- Fixed bugs.
Not work:
And nothing happens... Sniffer don't see any connection from miner, only few packets, then it start. But after what - nothing. I wait 15 min and restart miner:
All works fine. May be problem with pool (but i tried 4 different and miner sometimes start work and sometimes not), but i don't understand why miner did not try connect to other pool after 10 or 15 seconds if there are problem with this pool.
Miner connects to pool, send login, pool sends answer. Are you sure that sniffer did not catch login request? It;s in text form so you can see it as text. This way you can check whether this problem related to miner or pool.
You are correct about timeout for getting job from pool after connection - I'll add it, due to ddos attacks pools are unstable and additional checks are necessary.
Now it is ok (was pool ddos may be), but if i see that problem again i save sniffer log.
v 2.2 is available:
- Fixed bugs.
- Fixed bugs.
Not work:
And nothing happens... Sniffer don't see any connection from miner, only few packets, then it start. But after what - nothing. I wait 15 min and restart miner:
All works fine. May be problem with pool (but i tried 4 different and miner sometimes start work and sometimes not), but i don't understand why miner did not try connect to other pool after 10 or 15 seconds if there are problem with this pool.
Miner connects to pool, send login, pool sends answer. Are you sure that sniffer did not catch login request? It;s in text form so you can see it as text. This way you can check whether this problem related to miner or pool.
You are correct about timeout for getting job from pool after connection - I'll add it, due to ddos attacks pools are unstable and additional checks are necessary.
v 2.2 is available:
- Fixed bugs.
- Fixed bugs.
Not work:
http://dl.deadzone.ru/1.png
And nothing happens... Sniffer don't see any connection from miner, only few packets, then it start. But after what - nothing. I wait 15 min and restart miner:
http://dl.deadzone.ru/2.png
All works fine. May be problem with pool (but i tried 4 different and miner sometimes start work and sometimes not), but i don't understand why miner did not try connect to other pool after 10 or 15 seconds if there are problem with this pool.
v 2.2 is available:
- Fixed bugs.
- Fixed bugs.
New CPUminer¨2.1 stopped and got a lot of line
outdated share line- skiped ( or something like that).... and that is all
6.5 hours without mining on cpu beacuse stupid error
Fix that!
Back to 2.0
On GPU, for now on 2.1 everything is looking ok!
CPUminer 2.1 stopped and GPUminer 2.1 stoppedoutdated share line- skiped ( or something like that).... and that is all
6.5 hours without mining on cpu beacuse stupid error
Fix that!
Back to 2.0
On GPU, for now on 2.1 everything is looking ok!
New CPUminer¨2.1 stopped and got a lot of line
outdated share line- skiped ( or something like that).... and that is all
6.5 hours without mining on cpu beacuse stupid error
Fix that!
Back to 2.0
On GPU, for now on 2.1 everything is looking ok!
CPUminer 2.1 stopped and GPUminer 2.1 stopped outdated share line- skiped ( or something like that).... and that is all
6.5 hours without mining on cpu beacuse stupid error
Fix that!
Back to 2.0
On GPU, for now on 2.1 everything is looking ok!
New CPUminer¨2.1 stopped and got a lot of line
outdated share line- skiped ( or something like that).... and that is all
6.5 hours without mining on cpu beacuse stupid error
Fix that!
Back to 2.0
On GPU, for now on 2.1 everything is looking ok!
outdated share line- skiped ( or something like that).... and that is all
6.5 hours without mining on cpu beacuse stupid error
Fix that!
Back to 2.0
On GPU, for now on 2.1 everything is looking ok!
Jump to: