Printable View
Yeah I have both a P6T and a Deluxe and waking from S3 sleep is like a craps shoot, not sure why it doesn't work all the time or with any consistency.Quote:
Originally Posted by Schlotkins
As for the manner in which you wake the system can be enabled in the bios which are all disabled by default, I use the spacebar to wake or attempt to wake.
I've given up on sleep mode for the time being and its a shame considering how useful a normally operating sleep mode is.
Before I leave my P6T-D, running a 4711MHz and 4677 passed SPI 1M with water cooling, then I will switch to DFI X58 DK :)
Mine was stopped everything at 225bclk! But it is still a fair good MB. I think.
http://img8.imageshack.us/img8/5210/4677superpi1m.jpg
http://img8.imageshack.us/img8/6964/4711validation.jpg
http://valid.canardpc.com/show_oc.php?id=529047
Thanks for the reply highoctane. Is it just mean, or is it a little ridiculous that a $300 motherboard after 4 months can't suspend properly? I guess I should really be complaining to Intel since this appears to be a X58 problem....
well done :)Quote:
Originally Posted by TinTin
unfurtunatly I can not read sthe settings....can you post a bigger screen shot please or write the settings you set? thank's :)
http://img6.imageshack.us/img6/5210/4677superpi1m.jpgQuote:
Originally Posted by okorop
As u wish,:)
PCI-e = 115
same settings for 4711MHz capture.
thank's :)Quote:
Originally Posted by TinTin
great result....let' see what you can do on the dfi then :)
is 115 pcie even safe with an adaptec card installed?
how do i update the bios?
RTFM :))))Quote:
Originally Posted by 2slick4u
Quote:
Originally Posted by DarkSlayer
ha ha yeah i got it
LOL!!!! RTFM always seems to be the best and most problem solving advice possible. :DQuote:
Originally Posted by DarkSlayer
Just to follow up on this, I'm going to assume the board keeps the pcie at its normal speed when overclocking automagically... ?Quote:
Originally Posted by ewitte
Quote:
Originally Posted by TinTin
Good God! How high are your temps running at those voltages?
it is official asus p6t series will have all the cpu ratio at 21x and 23x for i7 920 and i7 940!!!!!
this is the new bios released for asus p6t ws revolution look what they wrote :) great!!!!!!
P6T6 WS Revolution BIOS 0407 - 2009/03/16 update
1. Updated CPU micro code(s):
* M03106A5_0000000F - Intel Nehalem-EP D-0 Nehalem-WS 1S D-0 Bloomfield D-0
* M03106A4_0000000F - Intel Nehalem-EP C-0 Bloomfield C-0
2. Support i920 CPU ratio up to 21 and i940 up to 23 in BIOS setup.
Cool but are they going to fix the issue of the multiplier dropping back to 20x under heavy load???Quote:
Originally Posted by okorop
I do not know....but where do you see the multiplier changing? I use cpuz and it is always at 21x real temp the same everest as well.....is there another program?Quote:
Originally Posted by 003
In RealTemp. This is with bclock at 191Mhz and cpu voltage at 1.4125v set in BIOS, water cooled. If I run LinX with these settings, the multiplier drops to 20x in RealTemp and the PC will crash shortly thereafter because 20x is significantly less stable than 21x.
I use bios 1303 on P6T Deluxe and it already has the 21x multi implemented. You can now not only choose 20x but 21x as well. That way it won't automatically revert to 20x and will stick at 21x when set at that value in the bios.
it happends like this also in my case.....I think 003 set something wrong in bios :)Quote:
Originally Posted by Pisklink
Quote:
Originally Posted by Pisklink
No, you are both incorrect. I am well aware of how to use the 21x multiplier. I have it keyed in directly for the CPU Ratio in the Ai Tweaker section of the BIOS.Quote:
Originally Posted by okorop
I have disabled SpeedStep, C1E, CPU TM Function and Turbo Boost.
Under idle conditions, and moderate to heavy loads, the multiplier remains at 21x as it should. However, under extremely heavy loads, such as linpack in 64-bit mode with the maximum amount of memory being used, the multiplier drops to 20x. The drop shows up in RealTemp and CPU-z and Everest.
Prime95 does not cause the multiplier to drop to 20x. So far, linpack (using LinX) is the only load that causes it to drop that I have found. And not surprisingly, linpack also gets the temperature a good bit hotter than Prime95 as well.
This is directly related to the TDP and current limitations on the non-EE i7 CPUs. The Asus BIOS does not properly disable them, so when the CPU is loaded heavily enough and set at a high enough voltage and clock speed, the multiplier will drop.
Set your P6T Deluxe to 191 bclock with the 21x multiplier and use 1.4125 core voltage, and load the CPU with LinX using the maximum amount of memory, and monitor the multiplier with the latest version of RealTemp.
For me, it drops almost immediately after LinX initiates the full load (takes a few seconds after you hit start).
I run 21x191 and when under load mine never drops from the 21 multiplier whether its Linx or two days of prime95.
EDIT: I am on water cooling for that rig though and temps peak in the low 70ish area.
I am also on water cooling and my temps have peaked at 82C with LinX. This should not trigger throttling though as I have TM Function disabled. The only explanation is the current and TDP limitations of the non-EE i7 CPUs. And what voltage do you use? Try with 1.4125v. And of course, make sure HT is enabled.
Try to set the power policy in windows Vista/7, both min/max to 100%Quote:
Originally Posted by 003
I have run and prime tested at 191x21 at 1.425 originally and have since lowered the vcore to 1.3875 since it seems I only need 1.425 to run 20x200, HT is on as indicated in my sig. I have SS's of the rig running well over 24hrs while priming at 191x21 at 1.3875 vcore, HT enabled.Quote:
Originally Posted by 003
I'm not disputing your issue but I'm simply stating that during weeks or I guess months now of tinkering and stability testing my P6T Deluxe rig at various settings it has never throttled down from the 21 multiplier under load. Systems can be qwerky sometimes and its not always possible for somebody else to duplicate a seemingly problematic issue that somebody else is having.
If I get a chance I'll up the vcore and double check if there is any throttling on my particular rig even though I know there isn't just for the sake of clarity.
I am using XP x64. Also, I am not the only one who has this issue. Look a bit back into the thread, there is at least one other person to notice it as well.Quote:
Originally Posted by TinTin