Is there any other mobo that doesn't affect by this multiplier throttling crap? may be time to ditch this thing... :D
Printable View
Well I have the V1 board and I was using it last Friday with no problems. And tell the gardner decided to cut my FIOS cable while he was trimming the trees and now I can not get my ethernet to work again. I tried everything, I think so far. I think it must of fried my 2 ports or something. I am using a second board to go online. Well now I have to setup a RMA through ASUS hope it goes well. Atleast I can throw in my new Bloodrage board for the time being. :(
Anyone has tried BIOS 0502 on P6T Deluxe V2? I had upgraded mine and unable to change mine DRAM Frequency setting except [Auto].
I'll most likely get the EVGA as replacement, not sure if I should get the A1 with 2yr warranty or spend more to get the classfied yet....is Asus going to fix the thermal throttling ever? before I get a replacement board I did a little comparison of my D0 in power consumption and here's what I found:
2.66Ghz @1.15v: 130w
4.00Ghz @1.22v: 219w
4.20Ghz @1.30v: 262w (underload throttling back to around 20.75x 200; 4.15Ghz)
4.30Ghz @1.35v: 289w (underload throttling back to around 20.5x 205; 4.2Ghz)
4.40Ghz @1.40v: 318w (underload throttling back to 20x 210; 4.2Ghz)
4.51Ghz @1.45v: 349w (underload throttling back to 20x 215; 4.3Ghz)
note:CPU wattage calculation from http://extreme.outervision.com/PSUEngine
For 24/7 I guess the sweet spot of my D0 is somewhere around 4.2~4.3Ghz with the least amount of heat load.
Ocz blade 3x2 gb 2000mhz cas9 are working really well on this board. I have just tried for 20 minutes and here the screens:
1800mhz cas 7 stable with 1.66 vcore
http://www.pctunerup.com/up/results/...35_Capture.jpg
And then 2000 mhz cas9 cas8 1.65volts
http://forum.hwproject.net/imagehost...1513203c5f.png
I tried also 2000 cas8, I will post the screen later :)
1531. I can set also 1149 and Auto
http://img514.imageshack.us/img514/5231/ram.jpg
Just want to ask a quick question.
It there thermal protection on the i7 or p6t deluxe v2 ?
I remember my old P6b deluxe has thermal protection (i.e, when the cpu reach a certain temp., it will buzz an alarm or shutdown the system. I dont remember which.)
I have same cpu, mobo and ram than yours. my D0 is at 1.35625v @ 205 x 21 = 4.3Ghz but i have never seen it throttling back.
I tried I7 Turbo program to check the throttling but never any issue.
My cpu is able to reach 80ºC on Air but it doesn´t throttle back, how do you check the throttling..?
Last night I did more testing, had the A/C cranking in a small room and brought down the ambient temperature to 16C, at 4.40Ghz with 1.40vcore it idle only around 32~33'C, underload in LinX were 66~67C on all 4 cores and the throttling nonsense still kicked in and multiplier dropped down to 20x. So this crap is definitely not temperature dependent. Maybe like 003 suspected....it was affected by the vcore in a certain range...
HT is enable.
Try with less V core, with this settings (that you already know) i got no throttle.
Ai Overclock Tuner: Manual
CPU Ratio: x21
Intel Speed Step: DISABLE
BCLK Freq: 200
PCIE Feq:101
DRAM Freq: 1603MHZ
UCLK Freq: AUTO
QPI Link Data Rate: AUTO
DRAM Timing Control: 8-7-7-24
CPU Voltage: 1.35
CPU PLL: AUTO
QPI/DRAM Voltage: 1.35
IOH Voltage: 1.22
DRAM Voltage: 1.66
Load-Line Calibration Enable
CPU Spread Spectrum: Disable
PCIE Spread Spectrum: Disable
C1E Support: Disable
CPU TM Function: Disable
HyperThreating: Enable
(All the rest: Auto/Default)
martinakerman: Can you post a screen shot of the i7 Turbo tool and CPU-Z while running LinX? Your bios setting is 1.35625v but your actual core voltage is likely a little less than that.
Turbo throttling is mostly controlled by core voltage and then MHz. At full load, a 5% increase in core voltage should increase power consumption similar to what a 10% increase in frequency (MHz) would cause.
As the maximum TDP is reached, Turbo mode will start to cycle rapidly, hundreds of times a second, on and off. When you really start pushing things hard on the Asus P6T, Turbo mode will mostly remain off. Software that only looks at your multiplier once per second will initially miss what's going on inside your CPU when Turbo cycling first starts to happen.
I have a few ideas to make the i7 Turbo tool better but I'm still waiting for some more feedback. If enough people complain about this then maybe Asus will get off their butts and fix this issue and give users a way to turn off TDP based Turbo throttling like most other motherboards allow you to do.
Post some screen shots so I can have a look and send a link to Asus to get them to wake up and admit that there's a problem here.
ben805: A $15 Kill-a-Watt meter is a great thing to have in the tool box for tracking down issues like this. It should be very clear when power consumption at the wall reaches a certain level that Turbo mode starts to cycle.
Edit: Here's an example of Prime Large FFTs at 4200MHz and 1.392 volts being enough of a load to start Turbo cycling. CPU-Z is still choosing to ignore that something is going on. The core temp is only 63C so that's not the problem.
http://img40.imageshack.us/img40/3954/throttle.jpg
We know this is related to turbo and the TDC/TDP limit on the non-EE Core i7 CPUs. Here is an article detailing it:
http://www.tomshardware.com/forum/25...ore-overclocks
But, the thing is, the motherboard manufactures can have the TDC/TDP limit disabled via the BIOS. DFI, Gigabyte and eVGA include the option on all X58 boards. It is only asus that limits this function to their "high end" Rampage series X58 boards. :mad::mad:
I realize that's not your problem. I suggested the Kill-a-Watt just as a different way to monitor throttling.
As you load your CPU and increase the core voltage and the MHz, at full load, a Kill-a-Watt meter will accurately show you how much power is being consumed from the wall. When running LinX, etc. at the desktop in 2D, it will indirectly give you a good idea of how many watts your CPU is consuming.
In theory, the throttling point should correspond very closely with how many watts your CPU is consuming. No matter what software, MHz or core voltage you're using; you will likely find that the throttling point is going to occur at the same power draw from the wall. This is just a different way to prove what you already know in case Asus is still in denial.