I see a lot of people with Nvidia GPU's and downclocking problems. I simply used PowerMizer Manager and disabled Nvidia's power saving features. Works great with 270 series drivers and should work with newer drivers. It's a simple program, just run once and done. You can probably find other solutions with a google search but this is so simple it's a no brainer.

http://somemorebytes.com/wp/index.php/software/nvpmmanager/

I have no affiliation with the software or anyone that worked on it.. This isn't a sales pitch:)

Nice find, Zule!!

Although I haven't had downclock issues recently, I am checking on another possible fix.

I'll take a look at nvpmmanager, too.

Thanks!

Lt

Unfortunately, the program won't run on my pc. Starting it results in an error message, "More than TWO keys identified. Can't be sure which one to modify. This was not expected as from version 0.98 Powermizer Manager added experimental support for SLI/Hybrid systems. You can try to reinstall your video drivers. This may fix any registry mess that's causing this problem. You can contact devs and send debug info using the [Problems?] button and contribute to solve this problem."

I didn't see anything in the FAQ to explain this, yet. I will send off a Problem report if I can't find a fix.


Lt

Unfortunately, the program won't run on my pc. Starting it results in an error message, "More than TWO keys identified. Can't be sure which one to modify. This was not expected as from version 0.98 Powermizer Manager added experimental support for SLI/Hybrid systems. You can try to reinstall your video drivers. This may fix any registry mess that's causing this problem. You can contact devs and send debug info using the [Problems?] button and contribute to solve this problem."

I didn't see anything in the FAQ to explain this, yet. I will send off a Problem report if I can't find a fix.

Have a look at http://support.microsoft.com/kb/315539. If the problem is down to the card being installed twice this tells you how to remove the one that is no longer present.

Hey, that's a neat trick!!

It did display my old 7600GT, which I uninstalled. Only the 460 is listed now.

I thought the problem might be related to the tv card, or it could just be the result of this being an old XP install which has been through many changes, video and otherwise. I do use ccleaner and other utils to try to keep the registry 'cleaned-up'.


If it's any help, here's the Full error report:

(***) --> ***** Welcome to NVidia PowerMizer Manager***** 
(***) --> Initializing...
(PMZMGR) --> Looking for suitable keys...
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0001.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{272BB893-12FC-4E27-B26C-87D98151F724}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{272BB893-12FC-4E27-B26C-87D98151F724}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{272BB893-12FC-4E27-B26C-87D98151F724}\0001.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{272BB893-12FC-4E27-B26C-87D98151F724}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{51B06A4A-B844-4513-952B-2721379F571E}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{51B06A4A-B844-4513-952B-2721379F571E}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{51B06A4A-B844-4513-952B-2721379F571E}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8626A51C-F032-4FDD-BDC2-AC3B9557495A}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8626A51C-F032-4FDD-BDC2-AC3B9557495A}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8626A51C-F032-4FDD-BDC2-AC3B9557495A}\0000\VolatileSettings.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8626A51C-F032-4FDD-BDC2-AC3B9557495A}\0001.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8626A51C-F032-4FDD-BDC2-AC3B9557495A}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8B6D7859-A639-4A15-8790-7161976D057A}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8B6D7859-A639-4A15-8790-7161976D057A}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8B6D7859-A639-4A15-8790-7161976D057A}\0001.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8B6D7859-A639-4A15-8790-7161976D057A}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B06C24F6-418B-458E-9E86-D8BBA9D0283C}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B06C24F6-418B-458E-9E86-D8BBA9D0283C}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B06C24F6-418B-458E-9E86-D8BBA9D0283C}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{C76456D7-7C36-4655-A8F3-0C30C8619DC4}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{C76456D7-7C36-4655-A8F3-0C30C8619DC4}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{C76456D7-7C36-4655-A8F3-0C30C8619DC4}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0001.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{EE3987E7-2D76-422F-ABC8-20BFF5EB0BBA}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{EE3987E7-2D76-422F-ABC8-20BFF5EB0BBA}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{EE3987E7-2D76-422F-ABC8-20BFF5EB0BBA}\Video.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{F3253DDA-F948-436D-B0B5-A8BC6293C5CF}.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{F3253DDA-F948-436D-B0B5-A8BC6293C5CF}\0000.
(REGMGR) --> Retrieving all the keys matching \0000\ from key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{F3253DDA-F948-436D-B0B5-A8BC6293C5CF}\Video.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{272BB893-12FC-4E27-B26C-87D98151F724}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{51B06A4A-B844-4513-952B-2721379F571E}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8626A51C-F032-4FDD-BDC2-AC3B9557495A}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8B6D7859-A639-4A15-8790-7161976D057A}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B06C24F6-418B-458E-9E86-D8BBA9D0283C}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{C76456D7-7C36-4655-A8F3-0C30C8619DC4}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{EE3987E7-2D76-422F-ABC8-20BFF5EB0BBA}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <ProviderName> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{F3253DDA-F948-436D-B0B5-A8BC6293C5CF}\0000.
(REGMGR)	--> Value not found.
(PMZMGR)	--> Changing to alternate Nvidia root key identification... (Not fully tested. Please provide feedback)
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000.
(REGMGR)	--> Value not found.
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{272BB893-12FC-4E27-B26C-87D98151F724}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{51B06A4A-B844-4513-952B-2721379F571E}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8626A51C-F032-4FDD-BDC2-AC3B9557495A}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{8B6D7859-A639-4A15-8790-7161976D057A}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B06C24F6-418B-458E-9E86-D8BBA9D0283C}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{C76456D7-7C36-4655-A8F3-0C30C8619DC4}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{EE3987E7-2D76-422F-ABC8-20BFF5EB0BBA}\0000.
(REGMGR)	--> Success...
(REGMGR) --> Retrieving value <Device Description> from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{F3253DDA-F948-436D-B0B5-A8BC6293C5CF}\0000.
(REGMGR)	--> Success...
(PMZMGR)	--> More than TWO keys identified. Can't be sure which one to modify. This was not expected as from version 0.98 Powermizer Manager added experimental support for SLI/Hybrid systems. You can try to reinstall your video drivers. This may fix any registry mess that's causing this problem. You can contact devs and send debug info using the [Problems?] button and contribute to solve this problem.

Lt
edited...

@red-ray,

After looking through the error report registry Keys, only 4 of them (in each ControlSet branch - there are 3 of those, 001, 002 and Current) reference the 460.

This value appears in each 460 key:

Name Type Data
DisableDynamicPstate REG_BINARY 00 00 00 00


I'm tempted to backup the CurrentControlSet branch and change the data to 1.



(Maybe, I should warn my neighbors to head for their bomb shelters first!! :))

Lt

I've sent a problem report.

Also, I saw this in the program FAQ yesterday:

"
•I have a multimonitor setup and the video card is always at max speed even with PowerMizer disabled.


When the graphic card detects two or more monitors, it will clock itself to Max. performance profile no matter what the PowerMizer parameters are. This is in the NVIDIA specs."


Which is another reference to a setup with a 2nd (or more) monitor attached ensuring maximum performance. But, that config doesn't seem to work in XP (not here anyways).


Lt

"•I have a multimonitor setup and the video card is always at max speed even with PowerMizer disabled.

When the graphic card detects two or more monitors, it will clock itself to Max. performance profile no matter what the PowerMizer parameters are. This is in the NVIDIA specs."

Which is another reference to a setup with a 2nd (or more) monitor attached ensuring maximum performance. But, that config doesn't seem to work in XP (not here anyways).

No. With 2 monitors a single GTX 460 the GPU dropped to P-State 12 on my system. I suspect it all depends on which Power Scheme you use and how much you have changed things. I only get the issue when I plug 2 monitors into a secondary card. With SLI enabled GPU-0 will drop to P-12 but GPU-1 only drops to P-3. I currently have 4 GPUs and 4 Monitors and can always find a way to get all the GPUs to drop to P-12.

"•I have a multimonitor setup and the video card is always at max speed even with PowerMizer disabled.

When the graphic card detects two or more monitors, it will clock itself to Max. performance profile no matter what the PowerMizer parameters are. This is in the NVIDIA specs."

Which is another reference to a setup with a 2nd (or more) monitor attached ensuring maximum performance. But, that config doesn't seem to work in XP (not here anyways).

No. With 2 monitors a single GTX 460 the GPU dropped to P-State 12 on my system. I suspect it all depends on which Power Scheme you use and how much you have changed things. I only get the issue when I plug 2 monitors into a secondary card. With SLI enabled GPU-0 will drop to P-12 but GPU-1 only drops to P-3. I currently have 4 GPUs and 4 Monitors and can always find a way to get all the GPUs to drop to P-12.

P-3 and P-12, sorry but how about in English? Does either one relate to full power?

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

No. With 2 monitors a single GTX 460 the GPU dropped to P-State 12 on my system. I suspect it all depends on which Power Scheme you use and how much you have changed things. I only get the issue when I plug 2 monitors into a secondary card. With SLI enabled GPU-0 will drop to P-12 but GPU-1 only drops to P-3. I currently have 4 GPUs and 4 Monitors and can always find a way to get all the GPUs to drop to P-12.

The keyword in this combination is: multi-monitor with different resolution/timings. Is this the case?

---

- Performance is not a simple linear function of the number of CPUs you throw at the problem. -

"•I have a multimonitor setup and the video card is always at max speed even with PowerMizer disabled.

When the graphic card detects two or more monitors, it will clock itself to Max. performance profile no matter what the PowerMizer parameters are. This is in the NVIDIA specs."

Which is another reference to a setup with a 2nd (or more) monitor attached ensuring maximum performance. But, that config doesn't seem to work in XP (not here anyways).

No. With 2 monitors a single GTX 460 the GPU dropped to P-State 12 on my system. I suspect it all depends on which Power Scheme you use and how much you have changed things. I only get the issue when I plug 2 monitors into a secondary card. With SLI enabled GPU-0 will drop to P-12 but GPU-1 only drops to P-3. I currently have 4 GPUs and 4 Monitors and can always find a way to get all the GPUs to drop to P-12.

P-3 and P-12, sorry but how about in English? Does either one relate to full power?

P0 is full power, max clock settings. P3 is a step down (1/2) in core/shader clock rates. P8 is a volt reduction and reduction of all clock rates. P12 is lowest voltage/slowest clock rates.

P states are visible in Nvidia Inspector's display.


Lt

@red-ray - Yes, that's basically what I saw happen.

"•I have a multimonitor setup and the video card is always at max speed even with PowerMizer disabled.

When the graphic card detects two or more monitors, it will clock itself to Max. performance profile no matter what the PowerMizer parameters are. This is in the NVIDIA specs."

Which is another reference to a setup with a 2nd (or more) monitor attached ensuring maximum performance. But, that config doesn't seem to work in XP (not here anyways).

No. With 2 monitors a single GTX 460 the GPU dropped to P-State 12 on my system. I suspect it all depends on which Power Scheme you use and how much you have changed things. I only get the issue when I plug 2 monitors into a secondary card. With SLI enabled GPU-0 will drop to P-12 but GPU-1 only drops to P-3. I currently have 4 GPUs and 4 Monitors and can always find a way to get all the GPUs to drop to P-12.

P-3 and P-12, sorry but how about in English? Does either one relate to full power?

P0 is full power, max clock settings. P3 is a step down (1/2) in core/shader clock rates. P8 is a volt reduction and reduction of all clock rates. P12 is lowest voltage/slowest clock rates.

P states are visible in Nvidia Inspector's display.


Lt

Well I'd like to keep any 590 supporting driver at P0 24/7 instead of having to fiddle with some setting, is this possible? I did download the 267.91 driver today which is the earliest driver to support the 590.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Well I'd like to keep any 590 supporting driver at P0 24/7 instead of having to fiddle with some setting, is this possible? I did download the 267.91 driver today which is the earliest driver to support the 590.

Hiya Victor,
In General, with Fermis, later driver related downclocking hasn't been a problem for quite some time, due to application changes present in x41g & some earlier builds. There is 'something else' going on here than choosing driver versions.

On long shots, given you are going multi-card so likely under PCI express bus contention, check these 2 things:
- See if you have a PCI latency timer BIOS entry, and if so, try a higher setting than the default of 32 cycles (best setting would be different for every system)
- Post a screenshot of DPC latency checker, taken while crunching at full bore. It can possibly point to firmware & driver issues.

If power, temps, cards, apps & system are all in good order, you should never get any downclocks during crunching, with newer drivers (dvi sleep bug notwithstanding).

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Well I'd like to keep any 590 supporting driver at P0 24/7 instead of having to fiddle with some setting, is this possible? I did download the 267.91 driver today which is the earliest driver to support the 590.

Hiya Victor,
In General, with Fermis, later driver related downclocking hasn't been a problem for quite some time, due to application changes present in x41g & some earlier builds. There is 'something else' going on here than choosing driver versions.

On long shots, given you are going multi-card so likely under PCI express bus contention, check these 2 things:
- See if you have a PCI latency timer BIOS entry, and if so, try a higher setting than the default of 32 cycles (best setting would be different for every system)
- Post a screenshot of DPC latency checker, taken while crunching at full bore. It can possibly point to firmware & driver issues.

If power, temps, cards, apps & system are all in good order, you should never get any downclocks during crunching.

Jason

That Bios setting does not exist on the Asus P7P55D Pro motherboard Jason, I've looked before, nothing. The EVGA P55 Classified 200 motherboard does though.
The cards are 3 MSI 1GB GTX460 Cyclones, Temps are in the 80's for the left most card, middle card is in the high 90's(around 98C, but it takes It no problem) and the right most nearest to the cpu runs in the mid 70's.

Power is good here I'd think as I have a Silverstone 1500w psu in place, apps are x41g and system I guess is Win7 Pro x64 with up to date drivers.

I'll have to take the screen shot(downloaded it before too), not like I can adjust that latency setting You mentioned here, that just isn't a setting the 2003 Bios has.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

That's alright, the DPC latency is a different thing (not a BIOS setting) related to chipset, firmware & drivers, so not out of options yet.

~90 degress Celcius is a bit too warm for 460's (though fine & dandy for 480's)

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

That's alright, the DPC latency is a different thing (not a BIOS setting) related to chipset, firmware & drivers, so not out of options yet.

~90 degress Celcius is a bit too warm for 460's (though fine & dandy for 480's)

Jason

The reason for that is the spacing of the slots and the Cyclone is normally clocked at 726MHz, even without an overclock the middle card will get to about 98C, I've read the max for the 460 gpu is 104C though.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

That's alright, the DPC latency is a different thing (not a BIOS setting) related to chipset, firmware & drivers, so not out of options yet.

~90 degress Celcius is a bit too warm for 460's (though fine & dandy for 480's)

Jason

The reason for that is the spacing of the slots and the Cyclone is normally clocked at 726MHz, even without an overclock the middle card will get to about 98C, I've read the max for the 460 gpu is 104C though.

That would be theoretical max before it either shuts down or blows up. I've had my 480 past that in specially crafted test pieces (Furmark is a wuss ;) ), stable crunching only lasts up to about 96/97 on my 480 though then there is compute &/or VRAM corruption, so I try to keep it under 90 & it's rock solid. 480 is built to take it, with all associated power, heat & noise. 460 will not sustain those levels.

High nineties is bad & IMO a big part of your problem... as soon as you have a DPC chart for me, that will confirm all drivers & firmware are non-broken, and addressing temperature issues can begin.

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

That's alright, the DPC latency is a different thing (not a BIOS setting) related to chipset, firmware & drivers, so not out of options yet.

~90 degress Celcius is a bit too warm for 460's (though fine & dandy for 480's)

Jason

The reason for that is the spacing of the slots and the Cyclone is normally clocked at 726MHz, even without an overclock the middle card will get to about 98C, I've read the max for the 460 gpu is 104C though.

That would be theoretical max before it either shuts down or blows up. I've had my 480 past that in specially crafted test pieces (Furmark is a wuss ;) ), stable crunching only lasts up to about 96/97 on my 480 though then there is compute &/or VRAM corruption, so I try to keep it under 90 & it's rock solid. 480 is built to take it, with all associated power, heat & noise. 460 will not sustain those levels.

High nineties is bad & IMO a big part of your problem... as soon as you have a DPC chart for me, that will confirm all drivers & firmware are non-broken, and addressing temperature issues can begin.

Jason

Well until I can get another EVGA GTX460 2WIN card, I'll just have to plug away as I'm setup then, as I don't have the money right now to do so. As their about $327 at the moment... Like May or June will be when I could buy one. Although the date could be push up a bit, if I'm lucky enough to run into about $328 or so and I might, maybe.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I can lower the voltages to the gpus to lower the middle 460 card temp into the 80's and the clock speed, but that's it.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Temps are 71-72/82-83/65-66C on the 3 MSI GTX460 Cyclones at stock speed(726MHz core/1452shaders/1900mem) and 1.025v on the gpu cores, stock ram speed is 1800MHz.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's