Quote from: Wepp on October 02, 2011, 02:20:45 PM

Hi there. I'm running a Windows 7 x64 machine and dual 6990's. I just switched to cgminer after having used poclbm directly launched from the command line for about 3 months without issues. Since switching, I have three problems:

1) Without fail, every time I [Q]uit the miner, it causes a BSOD. The driver reporting a failure is atikmdag.sys. I was trying Catalyst 11.5 when it started happening. Updated to Catalyst 11.9 and the behavior is the same. The only way for me to safely exit the program is to KILL the process, and then I use another program to bring the fan speeds down to normal, or reboot.

2) Attempting to set the memory clock speed to anything below 950Mhz causes instability. Anything below 900Mhz and the system locks up instantly. I've found the best course of action is to leave it at the default setting.

3) Fan speed. NO MATTER WHAT I DO, one of the fans eventually reaches 100%. Ambient temperature in the room is 68º. I never had this problem using poclbm directly. Here are my settings:
--auto-fan --auto-gpu --gpu-engine 800-900 --gpu-fan 60-75 --temp-target 85 --temp-overheat 90

I believe what is happening with the fan speed problem is that cgminer is attributing each fan to the wrong GPUs. Invariably, GPU 0 and GPU 2 are cool, at around 75º, while GPU1 and GPU3 are hot at around 89-91º. My guess is that 0+2 is one card, and 1+3 is the second card, but cgminer is thinks that the cards are 0+1 and 2+3 respectively. Therefore, it is not associating the GPU temperatures with the correct GPU fan speed settings. In fact, 0+2 used to run hotter than 1+3, because the card is physically on top of the other card in the machine. It is only so cool now because the fan is blowing so hard.

1. Well that's very unlucky. Not sure what I can do about it though, software shouldn't be able to take out your entire machine (unless you're doing dangerous clocks and shit).
2. Some hardware really doesn't like the memory being much slower than the gpu clock speed. 69x0 cards in particular usually ignore lower settings to avoid that from happening.
3. The 6990 has dissociated sensors on the 2nd core so it really doesn't know what the fan speed is. Furthermore, the ATI drivers and the ATI display library do NOT have a way of agreeing on what the device numbers are, so we're left to *hoping* they coincide in order. However, the temperature and fan speeds reported by ADL are coming from the same device so even if your GPU number listed doesn't correspond with the fanspeed you think, the temperature/fanspeed combination listed for one card is definitely the temperature and fanspeed for that core. Bear in mind, though, that the 2nd core of 6990s doesnt have a fanspeed and is just sharing the fanspeed from the 1st core. Thus any fanspeed it's reporting will likely be a percentage value that is being ignored and the fan of its corresponding partner core in RPM is the real fanspeed.