VDDC (VRM) temps are located on the sensors tab in GPU-z, usually toward the bottom.

I monitored the VRM temps with GPU-Z overnight. At full burn, VRM1 is at 70c and VRM2 is at 58c.The GPU temp is currently at 61c. I think it was as high as 71c last night while I was playing a game on the other card.Those temps all sound fine to me, what do you guys think?

It was the "Force Constant Voltage" setting. Before I checked it, changing the slider did nothing.

I tried that, and nothing changed. The "Core Voltage" slider is still unavailable.The "Power Limit (%)" slider is active, and currently on +20%.Any ideas how to undervolt this sucker? I'd love to reduce the power footprint a bit.At full burn on the miner and gaming on the GTX480, this rig pulls over 900W at the wall. I'd sure love to trim that a bit.

It was the "Force Constant Voltage" setting. Before I checked it, changing the slider did nothing.

I tried that, and nothing changed. The "Core Voltage" slider is still unavailable.The "Power Limit (%)" slider is active, and currently on +20%.Any ideas how to undervolt this sucker? I'd love to reduce the power footprint a bit.At full burn on the miner and gaming on the GTX480, this rig pulls over 900W at the wall. I'd sure love to trim that a bit.

enable unofficial overclocking = 2, and delete any files in the Profile folder.

A user at my pool retrying the same wrong password 10 times per second with DiabloMiner. Is that how it's supposed to run?

Might be an idea to give up and shut down if the password is wrong, or at least use a much longer delay. It may be that 10 times per second is because of running multiple instances, but still if it is once per second it is pretty extreme.

A user at my pool retrying the same wrong password 10 times per second with DiabloMiner. Is that how it's supposed to run?

Might be an idea to give up and shut down if the password is wrong, or at least use a much longer delay. It may be that 10 times per second is because of running multiple instances, but still if it is once per second it is pretty extreme.

Most pools do not follow the HTTP spec, so there is no way for DM to detect the difference between a malfunctioning pool and a malfunctioning user.

Plus, no one should EVER run multiple instances of DM.

If the user has added multiple pools, DM will just go to the next pool after a few failed attempts.

Most pools do not follow the HTTP spec, so there is no way for DM to detect the difference between a malfunctioning pool and a malfunctioning user.

Well, my pool does. If you get a 401 (Unauthorized) response I would recommend at a minimum setting a much larger delay between retries. Maybe 30 or 60 seconds? My own miner just pops up a password dialog, like a browser would.

I don't think any pools are so broken that they respond with a 401 when there is nothing wrong?