Well, I tried GUIMiner and it seems to be working for now. However, I have 2 R9 290s and 1 R9 270X. Running both 290s gives me hash rates of 830-890 KH/s each, but adding the 270X crashes it all. Running the 270X lightly at 60 KH/s causes the 290s to drop to 700-800 KH/s.
Is it because of the 270X taking up more power? 1500 watts from 2 PSUs should be able to cover it, or is it because the 270X is providing the display for the monitor?
Topic: R9 290 can't go over 700 Kh/s (Read 494 times)
I had been searching around for my problem, but with no solution found yet. I have 2 R9 290s, one Sapphire R9 290, and one Asus R9 290. A 750w PSU supplies the power for the Asus R9 290 and the motherboard, while another 750w PSU powers the Sapphire R9 290. They are both connected to the motherboard through powered 1x to 16x risers. The system has 8GB of RAM and runs BAMT 1.62, the newest version.
Here's my problem. I can't overclock the R9 290s without BAMT freezing up or crashing. Without overclocking at the default clock speeds of 947 engine and 1250 memory, the Sapphire runs at around 650 KH/s, while the Asus runs at 600 KH/s. The power at the wall is at 650-700 watts. If I change the clock speeds to 1000 engine and 1450-1500 memory for example, cgminer runs for a few seconds than crashes the whole rig.
What would the problem be? Running at 90 C doesn't seem way too hot, as it should handle that. Windows 8 crashes as well, showing a BSOD saying asdikmag, using the latest AMD driver.
Here is the BAMT config:
1230 KH/s for both R9 290s with this:
and 1250-1330 KH/s without.
By adding the clock settings, it runs fine, but without it crashes as well.
Here's my problem. I can't overclock the R9 290s without BAMT freezing up or crashing. Without overclocking at the default clock speeds of 947 engine and 1250 memory, the Sapphire runs at around 650 KH/s, while the Asus runs at 600 KH/s. The power at the wall is at 650-700 watts. If I change the clock speeds to 1000 engine and 1450-1500 memory for example, cgminer runs for a few seconds than crashes the whole rig.
What would the problem be? Running at 90 C doesn't seem way too hot, as it should handle that. Windows 8 crashes as well, showing a BSOD saying asdikmag, using the latest AMD driver.
Here is the BAMT config:
Quote
"auto-fan": true,
"gpu-fan": "0-85",
"auto-gpu": true,
"temp-cutoff": "100",
"temp-overheat": "95",
"temp-target": "90",
"worksize": "256",
"gpu-powertune": "20",
"xintensity": "20",
"thread-concurrency": "32765",
"api-port": "4028",
"api-listen": true,
"api-allow": "W:127.0.0.1",
"failover-only" : true,
"no-pool-disable": true,
"no-submit-stale" : true,
"queue": "0",
"scrypt" : true,
"kernel-path": "/usr/local/bin"
}
"gpu-fan": "0-85",
"auto-gpu": true,
"temp-cutoff": "100",
"temp-overheat": "95",
"temp-target": "90",
"worksize": "256",
"gpu-powertune": "20",
"xintensity": "20",
"thread-concurrency": "32765",
"api-port": "4028",
"api-listen": true,
"api-allow": "W:127.0.0.1",
"failover-only" : true,
"no-pool-disable": true,
"no-submit-stale" : true,
"queue": "0",
"scrypt" : true,
"kernel-path": "/usr/local/bin"
}
1230 KH/s for both R9 290s with this:
Quote
"gpu-engine": "940-1000",
"gpu-memclock": "1250-1350",
"gpu-memclock": "1250-1350",
and 1250-1330 KH/s without.
By adding the clock settings, it runs fine, but without it crashes as well.
Jump to: