BAMT stops mining after a few minutes v1.5

X

XViper

Gawd
Joined
Aug 24, 2012
Messages
838
I'm not sure what's causing it. It starts mining and then after several minutes, it registers zero:

{
"pools" : [
{
"url" : "xxx",
"user" : "xxx",
"pass" : "xxx"
},
{

},
{

},
{

}
],
"api-listen" : true,
"intensity" : "20",
"vectors" : "1",
"worksize" : "256",
"kernel" : "scrypt",
"auto-fan" : true,
"temp-cutoff" : "85",
"temp-overheat" : "75",
"temp-target" : "70",
"expiry" : "30",
"gpu-dyninterval" : "7",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "30",
"scrypt" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"shaders" : "2816",
"thread-concurrency" : "32765",
"gpu-thread" : "1",
"gpu-engine" : "920",
"sharethreads" : "32",
"lookup-gap" : "2",
"gpu-powertune" : "20",
"gpu-memclock" : "1500"
}

Is it just buggy with 1.5? I get a solid 890 hash for a while. Running Asus R9 290x reference.

Also how do I adjust fan speed? It's on 100% all the time and sounds like a 747 taking off. I just want to turn it down a bit. Thanks.
 
Last edited:
from the description I'd say its getting too hot and stopping. Watch the temps and see if temp is causing it
 
It's not the temp but for some reason it's not being reported on the gui.

Ran screen -r cgminer in terminal and it shows as running. So there's something with the API thing.

It shows Overheat detected on GPU 0, increasing fan to 100%

But it's at 75c at max... is this normal?
 
You do have these set: "temp-cutoff" : "85",
"temp-overheat" : "75",

try a different USB stick OS either LTCrabbit SMOS or BAMT 1.4 because without actually seeing what the core temp is we have no idea
 
I'd take your username out of the config, people may attempt to get into the pool with it. (change your address / whatever)
 
You must log in or register to reply here.
Back
Top