Kilohash/s constantly being squashed to around 20\.
-
I was using CGMiner and adjusting settings in the batch file to try and get the maximum amount of khash/s, and even though I did manage to get it up to 600 or so, within a few seconds, that number plummeted to around 20 ~
Regardless of the settings this ALWAYS happens.
I used to have the same problem with LTC until I started using GUIMiner - Scrypt. I tried using GUIMiner - Scrypt for FTC, but it never connected and kept telling me I probably had entered something wrong, which I hadn’t.
I’m currently just using the FeatherCoin Wallet to min, and getting around 32 khash/s on average.
It sure would be nice if there was a decicated FTC GUI Miner.
-
When you first start cgminer your hash rate should swing a bit then stabilize shortly thereafter at your correct rate. What are you mining with?
-
try using the latest version of cuda but move all new files to cuda inside gui miner-scrypt
here is what my cuda scrypt looks like:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1“C:\xxxx\xxxxx\Desktop\guiminer-scrypt_win32_binaries_v0.04\cudaminer\cudaminer.exe” -o http://www.xxxx.com:####/ -O xxxx.xxxx:xxxxxxx -d 0 -i 1 -l 16x2 -C 0 -m 1 -D
here is my other feathercoin mining setup too using latest cgminer
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1C:\xxxx\xxxx\Desktop\guiminer-scrypt_win32_binaries_v0.04\cgminer\cgminer-3.1.1-windows\cgminer.exe --scrypt -u xxxx.xxxxx -p xxxxx -o stratum+tcp://pool.xxxxl.com:#### 2>logfile.txt --sharelog share.log --gpu-platform 0 -d 0 -w 128 -v 1 -I 9 -g 1 -l 1 --shaders 1500 --thread-concurrency 4096 --lookup-gap 2
-
Also a little thing I was not aware of before recently too, as I use both gpu and cpu.
I never noticed it before, but if I have the cpu going on all 4 cores, it kills the gpu. I thought they’d have been separate, but then I read about it and it seems I need at least 1 core to keep the gpu kicking.
Bugger. but it makes sense.
So I’d kick off cgminer and minerd and occasionally I’d see cgminer crawling at about 20-100 and could not work out why. Only recently when I stopped using a frontend to start them both on selected pools, did I realise it was the issue, and I noticed that without cpumining I was getting a lot closer to 400khash/s than the 380 I was used to seeing. I don’t know if it was due to not using a priority setting when starting minerd or not, but it’s not worth me mining both on the same rig.
Just something to think if the OP’s issue doesnt resolve and they do run something that grabs the gpu or interferes with it running at full.