Same. Using VECTORS4 drops my hash rate from 385 to 310 on my 5870. Using VECTORS WORKSIZE=128 brings it back up to about 380.

I still don't know why people are doing "VECTORS VECTORS2". VECTORS is an invalid argument for diapolo phatk ever since 8-04. The only valid arguments are VECTORS2 and VECTORS4.

No update yet? It's aug 8 now <.<

I thought windows was limited to 4 video cards. Linux can operate 8 IIRC.

Still the only thing that comes to mind that may be the problem is the board is unable to assign bandwidth to -all- lanes due to the 16x slots being used. My theory stands that when both PCI-E 16x slots are using 16x PCI-E lanes each, the chipset/bios/whatever "turns off" the PCI-E 1x lanes so the 16x slots can have 16x bandwidth.

This may be something better suited asking a professional on asus forums too.

Could you try 1 card in the main 16x slot and 2 more cards in the 1x slots? If you did this already, I didn't know.
Also most motherboards will post something on the second screen (The one before it loads windows but after the one that shows your memory and hard drives) showing what devices are connected. Verify that it's actually a board issue (doesn't show up in that device list) and not a windows issue by seeing if 3 video card devices are connected there.

What was it? Or not saying? <_<

You don't need VECTORS VECTORS2. Just VECTORS2

They've already been sold for a long time now. Mod please lock this thread or OP please change title to SOLD

Are they still 6.5 btc?

Could possibly be motherboard power issue. Have you tried supplementing the power draw form the motherboard with a molex's 12v? There's a ribbon cable that has a molex connector to supply 12v power.

Also didnt bother looking up the board, but I thought early PCI-E boards were really finicky when it came to spreading bandwidth across multiple slots (Like 16x-1x-1x-1x single card and 8x-0x-8x-0x if doing crossfire/SLI)

Is there a way to set up GUIMiner to restart crashed/frozen miners in the case of unstable overclocks? I'm trying to max out my system, and it really frustrated me to set an OC, go to work, and come back 8 hours later to learned the miner froze 10 minutes into mining because the display driver had to reset and recover.

I've gotten "Hardware problem?" errors often since the __init__ patches of 7-17 diapolo and phatk 2.0+, but they don't seem to cause any decrease in mhash, or crashes, or increased stales, so I'm not too worried about them. I'm assuming it causes "Hardware problem" when 1 hash isn't quite right, and getting 1 "bad" hash error every 10 minutes while doing 330 million hashes every second... you can probably see where I'm going with this.

If it matters, reducing my memory clock from 370 to 350 drastically reduced my "Hardware problem?" errors. I've gone from 1 every ~2 minutes to 1 every ~30 minutes.

MTGOX prices have rebounded up a bit to 10.85/BTC as of writing this, which wold be 9.21658986 BTC, so to make it a shorter number, 9.3BTC/card ok?

Use PCI-E Ribbon cables and custom built case. Cards can then hover far above the motherboard and have more than enough space between each card for ventilation. The only problem that may arise is each PCI-E slot is specced to supply 75W of power, and fully loading all slots may cause serious problems. You can get a PCI-E ribbon cable with a 12v molex connector wired into the ribbon cable to supplement the power to the motherboard, but they aren't exactly cheap.

If it's relavant, I have not had any increase in stales. GUIMiner v2011-07-01, built-in phoenix, phatk 2.1, catalyst 11.7, 2.5 SDK, 1 5870 + 5 5830's using these extra flags in GUI miner: -k phatk VECTORS BFI_INT WORKSIZE=256 FASTLOOP=false AGGRESSION=14

So far tests indicate the first "sweet spot" is ~220 MHz with VECTORS WORKSIZE=128. The next "sweet spot" (and fastest one yet) is ~370-380MHz with VECTORS WORKSIZE=256. Will keep you guys posted as I run through more combos.

Since I really liked the graph on the front page but thought it lacked granularity, I'm going to take a shot at making a graph too. I'll be doing tests on a 5830 instead of a 5870 though (My 5830 seems a LOT more stable when it comes to memory speeds compared to my 5870).
They'll be based on...
GUIMiner v2011-07-01
Built-in Phoenix miner
11.7 Catalyst
2.5 SDK
phatk 2.1 kernel with..
BFI_INT FASTLOOP=false AGGRESSION=14 and varying worksizes, memory speeds, and VECTORS vs VECTORS4.

Stay tuned

Edit: Here's a work in progress spreadsheet. It's updated as I test more combos (need to manually test and update spreadhseet manually).
https://spreadsheets.google.com/spreadsheet/ccc?key=0AjXdY6gpvmJ4dEo4OXhwdTlyeS1Vc1hDWV94akJHZFE&hl=en_US

I was planning to put in worksizes of 192, 96, and 48 too, but phatk 2.1 doesn't seem to support it. Less work for me though

They arent 5850's. They are 6570's. Read the whole thread next time.

kind of ok price if you want to game with it, but really bad if you just want to mine with it. :x

Just lowering memory clock for lower temperatures isn't the sole point. The heat is generated from electricity. Less electricity used = less heat, and also smaller power bill, which means more money in your pocket at the end of the day.

You might want to look at the graph found here. It's pretty interesting. It's concerning memory clock speeds, different kinds of vectors, and different work sizes. YMMV
https://bitcointalk.org/index.php?topic=7964.0