You have a lot of GPU devices. You will probably need to disable certain system devices in the BIOS such as serial/parallel port, USB ports, audio, PS/2 support, and so on to make room for the GPU's to be mapped.

Card Manufacturer: ATI
Card Model Number: 5870
Card OEM: Asus
MHash per Second: 504.3-504.5 MH/s
Core Clock: 1090 Mhz
Memory Clock: 205 Mhz
Voltage: 1.200v
Average Operating Temperature: Varies. Usually Ambient + 38c
Ambient Temperature: Varies. Sits outside. Currently 8c as I type this.
Fan Speed: Dedicated 60mm delta FFB0612EHE @ 100%
Host OS: Win7 x64
Driver Version: 11.12 CAT
SDK Runtime Version: 2.1
Mining Program: Phoenix 2.0 Beta RC1
Command Line Flags/GUIminer Settings: phatk2, AGGRESSION=14, VECTORS=true, BFI_INT=true, WORKSIZE=128
Other Information: Stable for 1 month so far. Will reduce speed/volts as spring temperatures increase.

Pictures don't mean anything either these days. Escrow or gtfo.

You mean the example on the very first post of the very first page?  It's an example. It's not meant for you to copy paste. Understand it. Learn from it. Make your own to best suit your needs. I don't know what hardware you have or what parameters best suit your needs, only you do.

AFAIK, there aren't any really successful miners with GCN-friendly kernels that are compatible with 7970 and similar cards that are also compatible with the GUIMiner frontend. GUIminer itself is not a miner. It's just a GUI so people that are scared of command lines have something more familiar to grasp onto, but GUIMiner has to know how to understand what the miner is outputting in order to show you basic stuff like shares, mhash, and so on, so it won't work with every miner, but only with the ones it's been programmed to understand. There was some work on DiaKGCN, a phoenix-compatible kernel that's got optimizations for the GCD architecture, but I'm not sure if its phoenix 1.7.5 compatible (I only saw phoenix 2 variants, but I could be wrong. Phoenix 2 currently isn't compatible with guiminer due to how it's argument are stored in a config file now). If the card is also dedicated, you should probably ramp up the aggression so it doesnt fluctuate so much because it sounds like you are using the computer and have it at a low aggression

I dont understand how people can pop the fan part off of the metal and electrical parts like nothing. I broke 2 blower fans at the part that joins the triangle plastic thing to the PCB (actually, just before it, it leaves a circle piece of plastic left in the PCB part)

*Sigh* See, the problem is people just copy paste. They don't try to understand what a config file does or what you should put in there. Every time I see that autodetect line, I just facepalm.

300 is too fast for worksize 128 (much slower). Close trixx and reopen it and you should be able to select lower memory speeds. You should get like a 10 mhash increase at the least going from 300 to 205 with 128 worksize.

thanks

Hash speed seems to scale linearly per shader per MHz with proper memory speeds/settings/sdk/etc. With 735 core and 1440 VLIW5 shaders, you should get about 307 MHash, so you're pretty much close to the mark. I can suggest to run 205 MHz memory and 128 worksize (About 0.15% mhash loss, but the lower temperatures makes up for increased core speed headroom. I got about 4 watts less per 5830 going from 330 memory to 205 memory, about 1c less in temperature and allowing a small bump in core) and cranking up the core speed.

If you're wondering about where I got the memory speed from, I was bored one day and did an exhausting test of many memory mhz vz worksize. you can see it here https://docs.google.com/spreadsheet/ccc?key=0AjXdY6gpvmJ4dEo4OXhwdTlyeS1Vc1hDWV94akJHZFE&hl=en_US#gid=0 or in this picture of a graph.

Bullshit. Screenshot/movie  (fraps harder to fake) or gtfo

wait what? I missed 3930K? FUUUUUUUUUUUUUUUUUUUUUUUUUUCK

Would have been interested, but I've been scammed twice on these forums from people that -just- got out of newbie forums. Going to pass.

If you want to save about 10 watts worth of heat, instead of running 300mem and 256 worksize, try ~205 (or less, higher may be unstable/slower) and 128 worksize. I was able to save 13 watts at the wall 1 5870 and 2 5830's and lost maybe 1 mhash between the three (used to run 330 mem)

No. That is a gimmick and not 24/7 recommended. Heck its not even 2 hour recommended. Without something to swiftly move all the oil quickly across hotspots, it'll just overheat. Plus, all the oil will just soak up heat. It won't dissipate it. Thats what radiators are for in water cooling.

Well I have a good chunk of sample data at https://docs.google.com/spreadsheet/ccc?key=0AjXdY6gpvmJ4dEo4OXhwdTlyeS1Vc1hDWV94akJHZFE&hl=en_US#gid=0 but it's currently for 2.1 SDK. Would need to uninstall 2.6 and install 2.4 sdk instead (which is fine for me, dont use 2.6 anyways) and run all the combos the same way. Here's a pretty graph in case you don't want to read the spreadsheet.
Note: My sample is very incomplete. It requires a lot of time to test all the combos. Environment was Win7 x64, phoenix 2.0 RC1, phatk 2.2 kernel, 12.1 driver, 2.1 SDK, AGGRESSION=14 BFI_INT with varying worksize and vectors. Card used is an Asus Radeon 5870 @ 1035mhz core.

It only works like that because of your situation. You can install 2.1 plus ONE of the following: 2.4, 2.5, 2.6 (havent bothered with 2.2/2.3, people say its cpu bug) because 2.1 installs into an entirely different path than 2.4-2.6. 2.4, 2.5, and 2.6 all share the same install path and, afaik, you can't install 2 or more of them since the new one will overwrite the old one (also the installer refuses to downgrade, have to 2.4 -> 2.5 -> 2.6, can't go backwards without manually uninstalling)

Remember this is only temporary.
[/quote]

Reflow means melting the joints that join whatever is on the PCB to the PCB itself. In many heat/cool routines, the joints can become stressed and crack. Liquifying, or reflowing, them removes these cracks and completes the circuit.

Those memory clocks are exceeedingly high. 300-380 is the optimum range for 256 worksize. 128 worksize is about half that (150-190) but has slightly less hashes than 256 worksize.

wow, thanks for fast fix, thanks. eagerly awaiting next windows build.