Open a cmd.exe command line and enter:
setx GPU_MAX_ALLOC_PERCENT 100
Topic: Having trouble getting 290x up (Read 688 times)
I think 4 gb ram is too few. Unfortunately I still have not understood why.
I just build a system with 2 r9 290x. I'm hoping someone can help me get this up as I'm having lots of difficulty here.
I'm using as ASRock FX 990 board with an AMD FX 4300 and 4gb ddr3 ram on windows 7 x64. I'm running 2 sapphire r9 290x but can't seem to get them to connect.
I've tried all different versions of CGMiner but the same error keeps coming up. According to others, the proper thread concurrency should be 32765. When I put that in, I get error 4 -
"Probing for an alive pool
Pool 0 difficulty changed to 32
Network diff set to 174
Error -4: Enqueueing kernel onto command queue.
GPU 1 failure, disabling!
Error -4: Enqueueing kernel onto command queue.
GPU 0 failure, disabling!"
Now the off part is if I try to lower the thread concurrency or intensity in the config file or from the command, it just hangs and I get nothing. Here is the config file. I would really appreciate any help.
I've tried running the line like this - cgminer --scrypt -o stratum+tcp://middlecoin.com:3333 -u xxx -p xxx --scrypt -I 16 -g 1 -w 256 --thread-concurrency 24576
I've tried reducing the intensity, reducing the thread concurrency and a combination of both. I'm getting nothing but a black dead screen. I've also tried different worksizes, etc. no help. I'm running the latest drivers and have tried CGMiner 3.1 and 3.7 as well.
I've also tried using this config file that I setup but it doesn't seem to help. Any help is greatly appreciated.
{
"pools" : [
{
"name" : "us.middlecoin.com",
"url" : "stratum+tcp://middlecoin.com:3333",
"user" : "xxx",
"pass" : "xxxx",
"pool-priority" : "0"
}
],
"expiry" : "120",
"hotplug" : "5",
"kernel-path" : "/usr/local/bin",
"load-balance" : true,
"log" : "1",
"no-submit-stale" : true,
"queue" : "1",
"scan-time" : "40",
"scrypt" : true,
"shares" : "0",
"gpu-threads" : "2",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"intensity" : "18,18",
"vectors" : "1,1",
"worksize" : "256,256",
"lookup-gap" : "0",
"thread-concurrency" : "32765,32765",
"no-pool-disable" : true
}
I'm using as ASRock FX 990 board with an AMD FX 4300 and 4gb ddr3 ram on windows 7 x64. I'm running 2 sapphire r9 290x but can't seem to get them to connect.
I've tried all different versions of CGMiner but the same error keeps coming up. According to others, the proper thread concurrency should be 32765. When I put that in, I get error 4 -
"Probing for an alive pool
Pool 0 difficulty changed to 32
Network diff set to 174
Error -4: Enqueueing kernel onto command queue.
GPU 1 failure, disabling!
Error -4: Enqueueing kernel onto command queue.
GPU 0 failure, disabling!"
Now the off part is if I try to lower the thread concurrency or intensity in the config file or from the command, it just hangs and I get nothing. Here is the config file. I would really appreciate any help.
I've tried running the line like this - cgminer --scrypt -o stratum+tcp://middlecoin.com:3333 -u xxx -p xxx --scrypt -I 16 -g 1 -w 256 --thread-concurrency 24576
I've tried reducing the intensity, reducing the thread concurrency and a combination of both. I'm getting nothing but a black dead screen. I've also tried different worksizes, etc. no help. I'm running the latest drivers and have tried CGMiner 3.1 and 3.7 as well.
I've also tried using this config file that I setup but it doesn't seem to help. Any help is greatly appreciated.
{
"pools" : [
{
"name" : "us.middlecoin.com",
"url" : "stratum+tcp://middlecoin.com:3333",
"user" : "xxx",
"pass" : "xxxx",
"pool-priority" : "0"
}
],
"expiry" : "120",
"hotplug" : "5",
"kernel-path" : "/usr/local/bin",
"load-balance" : true,
"log" : "1",
"no-submit-stale" : true,
"queue" : "1",
"scan-time" : "40",
"scrypt" : true,
"shares" : "0",
"gpu-threads" : "2",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"intensity" : "18,18",
"vectors" : "1,1",
"worksize" : "256,256",
"lookup-gap" : "0",
"thread-concurrency" : "32765,32765",
"no-pool-disable" : true
}
Jump to: