Topic: CryptoDredge 0.27.0 — CUDA Miner - page 38. (Read 86186 times)
I have used Windows version of your miner at the first versions. It was good and stable. But its temp was hotter than the hsr miner fork. But nothing to worried about it. Because its not too high. I only tested your miner because i had to switch all my NVIDIA rigs to HiveOS. I see you have linux version now. I have installed it on HiveOS. Yes, it is minnig but its temp is too high.GTX1050TI has 78 c
Whoaaaa. it is too high. So i had to switch back crytonight-v7 xmrstak.
if you can find a solution about temparature, i can use your miner for neoscrypt. I have 155 pcs GTX1050TI, 41 pcs GTX1060, 5 pcs GTX1070
Hi, I have CUDA9.2 and Ubuntu 18.05
while CryptoDredge 0.8.3 is running - nvidia-smi and nvidia-setting works extremely slow, anybody can help with this?
nvidia-smi and nvidia-settings works pretty fast with vertminer and ccminer
That's a driver bug on large rigs. Split the cards into two miner instances and it should be more responsive. while CryptoDredge 0.8.3 is running - nvidia-smi and nvidia-setting works extremely slow, anybody can help with this?
nvidia-smi and nvidia-settings works pretty fast with vertminer and ccminer
Hy everyone I just installed crypto dredge 0.804 beta ,it was ok with some coin , Im try nice hash lyra 2v etccc. always get error red ; no autorize ,i have change the BTC wallet ,try register one nice hash to ,same message ,any idea to mine in nice hash lyra2v2
Hi, I have CUDA9.2 and Ubuntu 18.05
while CryptoDredge 0.8.3 is running - nvidia-smi and nvidia-setting works extremely slow, anybody can help with this?
nvidia-smi and nvidia-settings works pretty fast with vertminer and ccminer
while CryptoDredge 0.8.3 is running - nvidia-smi and nvidia-setting works extremely slow, anybody can help with this?
nvidia-smi and nvidia-settings works pretty fast with vertminer and ccminer
Strange things are going on my rig with P104-100:
fixed in latest 0.8.4 beta. 
what -i factor you set? btw are u mining lyra2z?
It's -i 6 by default I didn't change it. I'm mining lyra2z on nicehash. I use -i 4 on my PC when I mine from time to time for test purposes cos with intensity >4 it's impossible even to move a mouse\browse
Yeah i see
>4 be carefull
From picture we can see (4186/24,81=168 watt) high level of power using.
Strange things are going on my rig with P104-100:
How are you getting 4200 with your 1070ti's though? I'm not getting anywhere near that :O
Would like to know too, I am getting only 3000 with my 1070ti, but im using only 60%pl and overclocked a little. But I dont think 100% pl can get anywhere near 4200mhz. Share please.
How are you getting 4200 with your 1070ti's though? I'm not getting anywhere near that :O
what -i factor you set? btw are u mining lyra2z?
It's -i 6 by default I didn't change it. I'm mining lyra2z on nicehash. I use -i 4 on my PC when I mine from time to time for test purposes cos with intensity >4 it's impossible even to move a mouse\browse
My GTX1080's get 4.45Mhs @ 150Wt, thought I got one very good sample which gets 4.65 @150Wt) As for 1080Ti's I get 5.8-5.85Mhs @ 195Wt
what -i factor you set? btw are u mining lyra2z?
Finally this is huge! 
So did you guys fix the auto-start problem ? Would be really nice to know how and why the program starts on boot when its not supposed to or in msconfig
Hi, it may be a stupid question, but... when I am using CryptoDredge with phi2, my GPU makes strange sound. It's hard to describe, but something like something was burning. I've made underclock, raised fans etc.
Whenever I turn it off, the sounds stop immediately. Is it normal?
Whenever I turn it off, the sounds stop immediately. Is it normal?
Coil Whine
I know how coils whines on my GPU (high tone). It's something different and a bit disturbing.
I checked ccminer and z-enemy and I haven't that issue on these while using phi-2 algo.
Thank you.
Pool settings on all my rigs are the same. But only this rig has that issue.
trying version 0.8.3 - same issue.
Pool settings on all my rigs are the same. But only this rig has that issue.
trying version 0.8.3 - same issue.
Try any other pool on this rig, if issue goes away - flush DNS cache of your problematic rig, you can do it with ipconfig /flushdns command from CMD with administrative privileges, then restart.
If not, try starting miner with limited number of devices running, -d 0,1,2 , etc. Until you find exact device causing problem.
If it'll still be there, try reinstalling videodriver.
Problem solved.
I copied text from my bat-file to new one and problem is gone.
I have no idea how, but its help me.
Thanks for all)
I hadn't specified it originally. Looks like lowering core did the trick. I'm at +60 now and no more crashes. Hashrate seems broadly unaffected anyway. Fingers crossed! 
The miner keeps crashing on me on Phi2...
"GPUx stopped working due to a critical error"
Trying to use my usual settings (core+110, PL 85%), mem at stock. Does intensity needs lowering for Phi2 on 1080's?
EDIT: it crashes with -i 5 too... Lowering clocks...
try to remove -i parameter."GPUx stopped working due to a critical error"
Trying to use my usual settings (core+110, PL 85%), mem at stock. Does intensity needs lowering for Phi2 on 1080's?
EDIT: it crashes with -i 5 too... Lowering clocks...
it helps for me
The miner keeps crashing on me on Phi2...
"GPUx stopped working due to a critical error"
Trying to use my usual settings (core+110, PL 85%), mem at stock. Does intensity needs lowering for Phi2 on 1080's?
EDIT: it crashes with -i 5 too... Lowering clocks...
"GPUx stopped working due to a critical error"
Trying to use my usual settings (core+110, PL 85%), mem at stock. Does intensity needs lowering for Phi2 on 1080's?
EDIT: it crashes with -i 5 too... Lowering clocks...
Thank you.
Pool settings on all my rigs are the same. But only this rig has that issue.
trying version 0.8.3 - same issue.
Pool settings on all my rigs are the same. But only this rig has that issue.
trying version 0.8.3 - same issue.
Try any other pool on this rig, if issue goes away - flush DNS cache of your problematic rig, you can do it with ipconfig /flushdns command from CMD with administrative privileges, then restart.
If not, try starting miner with limited number of devices running, -d 0,1,2 , etc. Until you find exact device causing problem.
If it'll still be there, try reinstalling videodriver.
Jump to: