Well there are 3 versions (3 sizes) of the upright ones. I don't really want to buy one to find out I got the wrong one :brick:
Well there are 3 versions (3 sizes) of the upright ones. I don't really want to buy one to find out I got the wrong one :brick:
New Beta Bios is out 2008/02/12.
Major Reasons of Change:
Change SB600 Raid ROM back to 2.5.1540.33
http://www.dfi.com.tw/Support/Downlo...FLAG=B&SITE=US
yeh well they all list the measurements on the thermalright webpage so you can grab some calipers and measure your chips.
i'm going to pull of the stock cooller and measure some things and see whats better to go with. I might invest in all copper parts and a fan or two. I try not to skimp out on NB and SB cooling along with keeping these mosfets cool
does anyone know the temps on the CPL-3-50 chips near the top right of the motherboard?? they are near the Al huge finned heatsink? do they get hot?
I have fans I can put there but I was just thinking to go all copper as thats what works better in the first place.
http://www.tankguys.com/product_info...f4136814b0fa37
they have a KILLER deal on these things!!!!! 9.99 versus everyone elses 17.99 +
anyone got any more temperature results with these boards on the NB,SB and MOSFETS?? I want to kinda know what products I need to order to cool this sucker. I'm thinkings the thermalright HR upright (maybe 1 or 2) and then some Swiftech copper ramsinks (the smaller ones (set of 8))
Hmm, AOD seems to set vcore close to cpu vid during start. As CPU VID is always reported as 1.25V this means the vcore is set to 1.25V. That causes lockups oced here.
Just verified it, with prim95 running the consumption does not change if I switch modes with AOD.[/QUOTE]Quote:
Originally Posted by KTE
Did not touch em. Card i running at 800/700MHz with 31% fanspeed. Changing the fanspeed to 25% does not change the consumption.Quote:
Originally Posted by KTE
NP, so you got your BE finaly, have you had a change to test him. Also waiting for 780G will be an nice office chipset.Quote:
Originally Posted by KTE
http://www.thermalright.com/new_a_pa...l.htm#dfird600Quote:
Originally Posted by ZL1Killa
The cooling is the same as this modo P35 T2R http://us.dfi.com.tw/Upload/Product_...%20P35-T2R.jpg so what fits this will fit the 790FX-M2R
HR-09 S TYPE 2
Im going to use HR-05 IFX on the NB & HR-05 IFX or HR-05 SLI/IFX on the SB whichever fits best & try to keep the DFI Mosfet & Transpipe & use my HR-09 S TYPE 2 with some Akasa AK-TT12-80 Thermal Adhesive Tape on the digital phase chips in front as they get really hot.
Yeah the DK 790FX-M2R has the same IDE, FDD, SATA, DIMM, PCI/PCIe section as the RD600 CFX3200, and the Southbridge heatsink is the same one, however there's other differences and the peripheral ports and layout seem to be from the P35-T2R-S.
31% is low enough I gather. I get a difference from 24% to 51% fanspeed though.Quote:
Originally Posted by justapost
Had it for a while. Nope, not tested it, waiting for 780G. I'll test it out on that before testing it on 790FX. ;)Quote:
NP, so you got your BE finaly, have you had a change to test him. Also waiting for 780G will be an nice office chipset.
Easy enough - if I had calipers :p:Quote:
Originally Posted by ZL1Killa
Could you take a photo about the installed HR-09 S TYPE 2 ?Quote:
Originally Posted by Final8ty
Thanks
haven't installed them yet plus need a camera.
Well using the beta bios & now with RAID0 x4 Western Digital Caviar SE16 500GB SATA-II 16MB Cache - OEM (WD5000AAKS) + 2 More for DATA & Backup im well happy.
i will probably set up this board and my new PSU this week... LATE one night, LOL. I'm not going to worry about anything right now but getting it up and running. Knowing my luck I will buy all these coolers and then plug it in to go and it will C1 error on me forever and not work... SO. I will keep yall updated when i go to install it
hey cats, as mentioned, i decided to give this board another try and things have been going really well after exchanging with that board stuck at 133MHz. that is until i reached 281MHz HTT. 281MHz HTT is Prime/3D stable for hours on end, never a problem. going up to 282MHz HTT results in a hang at 25 during POST. this is with two Phenoms or the 3200+. same exact results with all three. BIOS i am running is the latest official 01/30 FWIW.
i would like to see if i can get above 281MHz HTT in Windows but not sure which version of AOD or ClockGen will work, any advice would be great.
obviously i would also like to get past this spot from within the BIOS as well. i have tried pretty much everything in Genie BIOS section and can't get 282MHz HTT+ to POST. here is the timing sheet i am working with right now, any help would be appreciated:
Code:Genie BIOS Settings:
Timing Mode.......................... - Disabled
Memory Clock......................... - DDR800 (1:2)
PCIE 3,4 State....................... - x16.NC
PCIE 2 State......................... - x2
AMD Cool & Quiet..................... - Disabled
CPU Clock Ratio...................... - Auto
Spread Spectrum...................... - Disabled
CPU Host/HTT Clock................... - 281MHZ
CPU Host/HTT Boot Up Clock........... - 250MHZ
CPU Host/HTT Adjust Gap.............. - 5
PCI-E Clock.......................... - 101MHZ
>DRAM Configuration:
MCT Memory Timing................... - Manual
2T Mode............................. - Enabled
Cas Latency Time.................... - 5
Pre Charge Delay (tRAS)............. - 8
DRAM RAS# Precharge................. - 5
DRAM RAS# to CAS# Delay............. - 5
Bank to Bank Cmd (TRRD)............. - Auto
TRC................................. - 13
TRTP................................ - Auto
Write Recovery (TWR)................ - Auto
Write-Read Command (TWTR)........... - Auto
TRFC0............................... - Auto
TRFC1............................... - Auto
TRFC2............................... - Auto
TRFC3............................... - Auto
Trdrd............................... - Auto
TrwtT0.............................. - Auto
Twrrd............................... - Auto
Twrwr............................... - Auto
CS/ODT Pin Fine Delay............... - Enabled
TLB Cache Mode...................... - Enabled
Bank Swizzle Mode................... - Enabled
Auto Tweak Performance.............. - Disabled
Optimal Performance Mode............ - Disabled
>ODC Control Mode:
DRAM Drivers Weak Mode.............. - Normal
Output Drivers Comp................. - Normal
>Channel A:
CPU On-die Termination.............. - 300 ohms +/- 20%
DQS Drive Strength.................. - 1.00x
Data Drive Strength................. - 1.00x
MEMCLK Drive Strength............... - 1.00x
Addr/Cmd Drive Strength............. - 1.50x
CS/ODT Drive Strength............... - 1.50x
CKE Drive Strenght.................. - 1.50x
>Channel B:
CPU On-die Termination.............. - 300 ohms +/- 20%
DQS Drive Strength.................. - 1.00x
Data Drive Strength................. - 1.00x
MEMCLK Drive Strength............... - 1.00x
Addr/Cmd Drive Strength............. - 1.50x
CS/ODT Drive Strength............... - 1.50x
CKE Drive Strenght.................. - 1.50x
>HT Link Control:
HT Link Width......................... - 16 bit
HT Frequency.......................... - 1.4 GHz (7x)
IH Flow Control Mode.................. - Disabled
HT Link Tristate...................... - Disabled
2x LCLK Mode.......................... - Disabled
Unit Id Clumping...................... - Disabled
>CPU Feature:
CPU DID............................... - 1
CPU FID............................... - 00 (8x)
CPU-NB DID............................ - 1
CPU-NB FID............................ - 03 (7x)
AMD CPU Stepping...................... - P0
>PWM Settings:
PWM Control.......................... - Enabled
CPU VID Control...................... - 1.30625v
CPU VID Special Add.................. - Auto
CPU NB Voltage Control............... - 1.25000v
CPU NB Vid Special Add............... - Auto
DRAM Voltage Control................. - 2.12v
SB PLL 1.2V Voltage.................. - 1.20v
NB Core Voltage...................... - 1.200v
NB PCI-E Voltage..................... - 1.120v
NB HT Voltage........................ - 1.040v
My 9600BE has freezing issues above 2.5GHz. No matter how I get there (ref HT vs. multi) the system freezes after ~3 hrs with just 2.52GHz.
Beside voltages/multis and the ref HT i tried to reduce the CPU/HTT clock Adjust Gap to 2MHz but it did not help.
Is there a known trick to get further? If not I might just have picked one of the bad clockers but those start to become unstable at ~2.55GHz and not at 2.5GHz.
So you're booting at 250HT and then after boot the system sets 280HT... far more than most 9600 BE's would go but then again, your board and BIOS are far better than many other boards and BIOSes people are trying. Maybe your chip is too.Quote:
Originally Posted by 3oh6
With two DIMMs, set these two values to at least 195ns if you want to push oc using high HT ref. on both X2 and Phenom.Code:TRFC0............................... - Auto
TRFC1............................... - Auto
yeah i have to set initial boot to 250HTT and then 281HTT otherwise i won't get post, again, this is the same for all three processors. setting 282HTT just hangs at 25 during POST. i see everyone else running around with 350HTT+ without issue on this board with non-Phenoms but my 3200+ i have laying around shows the same symptoms. i would have accepted the Phenoms being limited there but not the 3200+ :shrug:Quote:
Originally Posted by KTE
i have tried setting both to 195+ with no change in symptoms. thanks for the help though, i am stumped as to what is going on.
You're doing good so far, tweaking and working with Phenom is difficult and very time consuming. The biggest problem is each BIOS and MB itself has so many problems and shortages, so you can't really figure out exactly what's stopping you. There are way too many BIOS bugs yet.
I just cross-checked your NB HT voltage, you're running it below spec and you're running the NB core voltage above spec. ;)
IDK what RAM MHz you've chosen, but I'm sure you know to keep low clocks well within stable range on this platform -> Intel platform stable specs are not usually the same on these due to the IMC vs. MCH. So you can play with DS settings accordingly. You can use SPDTool to check out the rated DS and work up from that. Keep 195ns on both tRFC if you have two DIMMs installed and DCT Mode to Ganged (until you find your limit).
With Phenom, put your CPU NB voltage up to 1.300V when you're past 1.8GHz but below 2.3GHz (well within safe limits). K8 used to run both voltages and speeds in-sync but K10h doesn't and lets you manually control them. It'll let things span out more consistent.
Set the NB Core voltage to 1.1V as it's rated. You won't need to touch that.
Try setting NB HT voltage to 1.225V and leave tRTP to 3-5. I think you have two options, one of 2-4 and one of 3-5. High HT ref. clocks tend to need this setting high for some reason, mainly because of the bootup calculations Phenom runs. They're the ones which typically give you no POST or a failed overclock, if they're too low compared to what they should be.
See if that helps. You can also drop all three FIDs (CPU/NB/HT) lower to check out if you can oc on HT ref. more.
Quote:
Originally Posted by 3oh6
Quote:
Originally Posted by willyK
:shakes:Quote:
In this case, just like in all other experiments, we tested the system stability with 1-hour run of Prime 25.5 utility.
Odd 2.500GHz p95 fine for 14 hrs, 2.508GHz p95 freeze after ~3hrs. Trying different ram now, will try stability with linpack under linux tomorrow if that does not help.
thank-you very much for the detailed reply. i will get back to the Phenom and try some things you mentioned. for now though, i grabbed an X2 5000+ BE and have had no issues pushing past 281HTT...Quote:
Originally Posted by KTE
click for full size...
http://img.photobucket.com/albums/v2...tprime-1sm.png
so it is definitely just something with the Phenoms and more work will be required to get past it. i'll be playing with this 5000+ BE for a little bit though, it feels like so long since i have had some AMD fun :up:
BTW, thanks to BE for the BIOS configs on the first page. i basically started with those and adjusted from there. had this badboy cooking at 330HTT within an hour of opening the package. time to see what it will do with the CPU clocks now.
64000+ BE Stepping CCB8F 0736CPMW failed prime 45min 3520Mhz stock 1.36 Vcore.
Do some more testing later when i get the cooling sorted.
Wish i could take the IHS off this thing.
Too busy playing games atm :)
LMAO!!!!Quote:
Originally Posted by Final8ty
just sand it a tad and lap it ;) thats what I did and it def saved me 3-5C
Hi guys
I got the new DFI DK 790FX and got a problem with my ram placement. The CPU cooler is blocking the first two ram slots, now I have only the third and fourth ones which are yellow and orange in colour. Does that mean that dual channel wont work?
Hi,
I got the board and two cpu's : Phenom 9500 and Amd 6400+ (non-BE :()
Haven't got time yet to test the 6400+, but I cannot go higher than 220*9 even with high voltages.
It's such a long time (nf4 ultra-d) I haven't touched AMD Motherboards that I cannot get things worked.
Tomorrow I start testing the 6400+ to see if I can still achieve something...
What would you recommend for the tensions for a max screen with a 9500 and for a 6400+ ? Also, I've read that there is a relation between NB Speed and HT Speed, one should be higher that the other, right ?
Yes, this is correct. If you want to do dual channel then the RAM must be in the same color slots (i.e. put 1 stick in green, and one in yellow or whatever the color is, don't have board in front of me). Otherwise if you put the ram in slots #1 and #2 (they are actually the ones furthest from the CPU) then you will be running single channel. Either deal with the performance hit or get a new cooler.Quote:
Originally Posted by kwark
Hmm the cpu just needed a bigger step in voltages as i expected.Quote:
Originally Posted by justapost
Running at 2.55GHz now with 1.3V/1.25V 2.56GHz failed priming even with 1.35V/1.3V after ~3hrs. Starts to make me curious why it fails after 3hrs most of the time.
Removed the cooler and added my cpu's stepping to my sig.
You're welcome. I still believe it may push further, but can't tell what's limiting it. I didn't even do anything with voltages (auto) on the MSI and ASUS RD790 boards and managed +380 HT using an X2, it literally is simple with many X2 G2's as long as it's not a BIOS limitation especially with the 5000+ BE. Even ~1600 HT link didn't really cramp it at all.Quote:
Originally Posted by 3oh6
Looking at the ss, somethings holding it back. I reckon nearly all 5000+ should be able to do +350 HT with ease if BIOS/MB is ok, just how 450FSB on a Intel G0 chip is a breeze. I've not tried clocking an X2 in it but will get a Sapphire soon and then be able to speak better.
Keep pushing it, much harder to squeeze +1MHz than on C2/Penryn. :up:
I sorted mine out. It was nothing but CPU limit and all that it requires is more cooling or more voltage. :(Quote:
Originally Posted by justapost
Nice. 0743, that's why. ;)Quote:
Originally Posted by Oliverda
just received HIS 3870 to complete the spider platform and ive been unable to get over 11000 3dmark06 (highest 10949), whereas everyone else is hitting 13000+ but they are using other brand 790fx mobos... ive increased slot voltage limit to 150 and set gen2 high speed to autonomous with no difference in score... do i need to mess with "link aspm" settings? what else am i missing?
as for the 2/12 beta, i can run 234 ref with 1.2v SB once again
ive been unable to run 246 ref since the infamous 1/3/08 beta that everyone hated
Must say i'm not yet used to those small incremenst (0.00625V) for voltages that makes 0,025V increases look like huge steps. Makes me think it's something else keepen my oc back.Quote:
Originally Posted by KTE
What do you think about the 2/12 beta on the whole? Have you noticed any bug or problem so far?Quote:
Originally Posted by Iketh
have encountered no problems and NIC latency is back to normal unlike 1/3 and 1/30 bioses... settings in sig remain rock solid... however overclocking beyond 234 has gotten worse but im pretty sure it's because of the new memory im running and i havent bothered to get to know the sticks yetQuote:
Originally Posted by Oliverda
Uh, I think Thermalright's measurements as listed on their site show that none of their northbridge coolers will fit on the DFI 790FX-M2R... although I only used a tape measure instead of calipers on the NB sink, it's definitely a lot smaller than the P35's heatsink. Also, I e-mailed Thermalright, and got this as a response...Quote:
Originally Posted by Final8ty
Quote:
Originally Posted by Thermalright Support
I got home this weekend and am looking at my DFI 790FX-M2RS, 9600BE, and Corsair XMS2 and I'm drooling :slobber: Can't wait to put this stuff in but I can't do anything with it for a couple days yet :(
Your right the northbridge is much smaller.Quote:
Originally Posted by MotF Bane
So after I replaced the crucials with gskill 6400 hk's and switched from 800 to 667 mode for the ram i managed to run 2.6GHz stable (216x12 12hrs stable, 217x12 testing).Quote:
Originally Posted by justapost
:eleph: :party: :cheer: :banana3: :rocker: :toast2: :banana2: :banana: :dj: :guitar: :toast: :bounce: :bounces: :YIPPIE:
I remeber OldGuy said samething about much better oc in 667 mode.
Will try to find lowes possible voltages here and gonna post detailed settings then.
Idle general use it for over 3 days before you call it stable. Higher end above 2.55GHz, Phenom suffers from random freezes after 1-3 days use with most users.
I've tested 2.76GHz 1.3V stable, 24 hours but after 2 days and sometimes after 3 hours uptime, it will randomly freeze. Even 1.55V will not make it stable. 2.691GHz is best stable so far and you need 1.502V for it but 1.28V for P95 24hrs stability test. Big difference.
Here 12x217 with ram at 800 froze with 1,375V vcore 1,3V vcorenb after two minutes.Quote:
Originally Posted by KTE
With ram at 667, 1,35V vcore and 1,275V vcorenb 12x217 is running stable since 7hrs now. So t least i broke the 3hrs freeze wall i was affected by the last week.
So it seems to be more an divider/mem timing issue than an voltage issue here atm.
During all my tests with the 9600BE the system eighter froze after a few minutes or short after 3hrs never later. But I have not had a longer uptime that ~15hrs till now.
Now wailting three hours for prime95 was a long time, but three days? Urgh.
EDIT: stopped prime95 after 8hrs at 12x217 trying to lower settings till i get the 3hrs freeze again. Starting with memory first running 800 mode now.
EDIT EDIT: Ran stable for 3,5hrs at 800mode switched to 13x200 with same voltages for everything beside ram (now 2.0V).
Update: Above settings where stable over night (11,5hrs), lowered chipset voltages to the minimum and priming again now. The remaining difference to an unstable 13x200 setup are the core and nb voltage, the cooler (be-stock vs. BigTyphoon 120) and the ram (gskill vs. crucial).
I'm thinking we should start a new thread.Quote:
Originally Posted by SparkyJJO
Interested to know if overdrive works with phenom's, works poorly for X2's. Its cool and all but it doesn't see increased volts as set in bios and doesn't go above 1.375.
Besides the occasional Bios non-loads the board has been great. Sometimes when first starting the board the bios screen doesn't load or freezes.
I put the system together today - and found that I can't use my HR-05 on my northbridge! :( The bracket is too long, it needs to be a little shorter and then it'll work.
Stock works OK I guess but it is already warm at stock speeds.
I finally got my board back from dfi, they had it in their possession for 12 days, plus the 4 more for shipping...so 16 days without it kinda sucks. I was a little disappointed after my friend has returned his asus and evga boards and just got new boards in the mail(cables, io panel...everything new). I got my board packed in a crappy nf2 box, in a plastic sleeve, not even the anti static bag. Also they shipped it with another nf2 box that was empty. They never told me they were shipping it or anything. I am a bit disappointed in dfi, I didn't expect a new board, but I did expect to be notified that it was coming.
Hopefully in the next 48 hours I will get it back together and see what she can do finally.
Phenom still won't go higher, I have to further test it.
I tested my 6400+ non-BE, and I achieved 375Mhz of fsb (with 1.5v on the nb), and max screen of the cpu, for the moment, 3550Mhz...
What is the max vNB I should put ? (maxscreen and H24 ?)
Thanks !
AOD works party as long as you do not set higher vcores than 1.25V in the bios.Quote:
Originally Posted by Undersea
If you run at higher cpu voltages AOD sets the vcore to 1.25V on startup and that freezes the machine.
The board seems to eighter use allways 1.25V as CPU and NV VID or it does not set the MSR registers correct.
AOD seems to set vcore to cpu vid on startup.
Do you know any info about the CAAZB AA 0740MPMW ?Quote:
Originally Posted by KTE
Edit the files Achim and that won't happen. The values it loads on startup are in a configuration file.
Oliverda: I've not seen or tried anything before a 0743 yet, sorry. I suspect it'll be decent.
Thx, modified AODConfig.xml seems to take this value if i restart AOD but if i restart the machine and start aod it's at 1,25V again. :confused:Quote:
Originally Posted by KTE
I'll get back to you as soon as I can. Don't have system here and this womans about to butcher me for spending too much computer time on a holiday :D
NP, which country did ya choose for holiday?
Having a crazy glitch here, before i installed aod i idled around 165W AC with 219x12. Upped ref HT to 220 rebooted and now it's idling around 197W AC. Uninstalled AOD restored 219 ref HT but i still have an ~30W higher power consumption in idle now. Under load the difference is lower ~5W.
Also a cold boot did not fix the issue, gonna validate 219x12 once again now.
everyone keeps jumping in on these hr-05 and such coolers... why not just use several copper ramsinks that swiftech/evercool/ use... just the little copper blocksQuote:
Originally Posted by SparkyJJO
France first stop, had to pick someone up and then to Turkey. Have some business there too. :)Quote:
Originally Posted by justapost
Idling or load? That's very high for idle but I'm having a similar issue. I idled 114W AC at 2.75GHz 1.4V for over 10 days and now suddenly after many BIOS testings (I don't start AOD most of the time) I'm idling 135W AC at 2.613GHz 1.35V. I don't understand why. :confused:Quote:
Having a crazy glitch here, before i installed aod i idled around 165W AC with 219x12. Upped ref HT to 220 rebooted and now it's idling around 197W AC.
Have you checked if AOD button is set to yellow and if PCIe, IMC, NB, HT volts are actually low as you want?
Also check your fanspeed of your GPU, screen res. and what load it's at (if you've enabled AA, more power consumed).
Does your BIOS have CPU VID options? At bootup, what VID do you have?Quote:
1. AMD Phenom 9600BE@2.6GHz 1.35V/1.275V 2x 1GB GSkill F2-6400CL4-HKm@400MHz 2.0V
I think it's loading the default config each time as only that's 1.25VID for all 3 CPU's and causes problems. Make sure AOD Assistant is off.
Nice, that is and that's where i was on my last trip to france. :)Quote:
Originally Posted by KTE
Just went back to my lowest possible settings at 2.3GHz. Previous it required ~125W AC idle now it are 154W AC!! Load consumption changed from 195W to 202W AC. Also my cpu temps are now ~8°C higher in idle.Quote:
Originally Posted by KTE
I uninstalled it and i plan to reinstall windows to sort out an os/dll related issue.Quote:
Originally Posted by KTE
No it has only a voltage option for cpu and nb, no extra vid's. Those stay at 1.25V no matter what vcore is set (have not tried cnq).Quote:
Originally Posted by KTE
Also modified the DefaultConfig.xml file but i might have modified the wrong voltage there. An alternative whould be using an customized profile whom get's loaded at start.Quote:
Originally Posted by KTE
Ya when I get a Phenom think I'll skip overdrive unless I see you guys reporting it works great.
How are you measuring W AC?
http://www.abload.de/img/em5y5n.jpg
With an power meter for domestic appliances.
I already had the HR-05 already from my old system so I was planning on just swapping it over. Besides, the small copper ramsinks can't keep a northbridge cool.Quote:
Originally Posted by ZL1Killa
That's quite a lot. It can't be unless something is placing a load on the CPU or some voltage is high. Even if the NB is under load. Have you benchmarked EVEREST to compare L3 cache values at the same speed with bw before this phenomena?Quote:
Originally Posted by justapost
Yes, I was going to write you a customized file to try that's why I asked about voltages and VIDs. ;)Quote:
No it has only a voltage option for cpu and nb, no extra vid's. Those stay at 1.25V no matter what vcore is set (have not tried cnq).
Also modified the DefaultConfig.xml file but i might have modified the wrong voltage there. An alternative whould be using an customized profile whom get's loaded at start.
Can AOD change VIDs on your system?
I had planned to pick up the Sapphire as the next RD790 board but when you say it doesn't have VID options, that scares me. :(
Try this MSR: 0xC0010070
EDX = 0x00000000 (always)
EAX
0x3000400A = 1.150VID
0x3000385A = 1.200VID
0x3000375A = 1.212VID
0x3000350A = 1.225VID
0x3000300A = 1.250VID
0x3000285A = 1.300VID
0x3000275A = 1.312VID
0x3000250A = 1.325VID
0x3000200A = 1.350VID
It should change CPU VID and hence volts (check in AMD PM). ;)
I'm not sure of all the ranges because I've not played with it more but the pattern is obvious. It's very easy to change VID and voltage this way without problems (you can include it in RWE).
Yeah it's really weird. Had replaced the stock cooler with the big typhoon and the ram from gskill to crucials few hours before that, switched back but that did not make a difference.Quote:
Originally Posted by KTE
NP i'm familar with xml-files.Quote:
Originally Posted by KTE
Have neighter tried AOD nor WPCREDIT to change em, just noticed that they stay at 1.25V in AMD PM no mater what vcore an vcorenb i choose.Quote:
Originally Posted by KTE
Currently running an stability test with 219x12 will try the MSR way tomorrow and let you know if it works.
Has anybody gotten this board working with G.Skill 2x2GB 1066, or TeamGroup 2x2 1066? The G.Skill yields a C1, and the Team shuts down the board straight from Memtest after about 20 seconds of Memtest.
Haha thats what i did it dropped my temp ~2-3C and is roughly @ 40-42C under full load.Quote:
Originally Posted by ZL1Killa
I also have a 80mm fan blowing at the PMW heatsink.
Achim: I rebooted at the same settings and my power draw idling is now down to 107W AC again for about 3 hours. :shrug:
I am pretty sure it was IMC related because IMC performance is now also better.
Mine primed fine for 13hrs with the higher power consumption. Upped the ref HT for another MHz and the vcore to 1,39325V and testing 220x12 atm. The consumption in idle is still 30W higher. Decided to go till 222 cuz i'd like to have ~2,66GHz to compare it with the intel rig.Quote:
Originally Posted by KTE
Mine's now idling 30W AC lower and I'm slowly dropping the volts. At 1.272V for 2.613GHz for over a day and night to going to drop it lower. Stock all else volts.
Hmm I removed all additional stuff (fans,cdrom...) tried different slots for the ram and still had the +30W. Tried the 3850 from the intel rig and different pci-e slots without luck.Quote:
Originally Posted by KTE
Switched to the BE2400 and verified the same power consumption at 3.2GHz i had few weeks ago.
After switching to the 9600be the power consumption is now at 148W AC at 2.6GHz (13x200) running at 1,35V now, guess i can go lower.
So the issue is gone now. Puh, was 199W at 2.6GHz before.
Above 2.628MHz system is not stable with vcore below 1.4V, dont want to use higer vcore atm.
Trying 1.28V vcore for 2.6GHz now above the voltage requirements rise very quick.
I think i can reproduce something comparable to your idle freezing. If i run 3dmark06 with prime the system freezes if i submit the 3dmark results. That additional test shortens testing a little.
The freezing looks like it's a board/BIOS issue because people on other boards aren't getting it. It occurs with a fully +5-20 day 24hr Prime95, fully benchable setting. Nothing will make it error until you either play a Youtube video/SWF/Flash Game/Firefox or just idle it for hours randomly. At that moment power consumption jumps to around 80% max and CPU freezes (with or without the TLB errata patch). Some time you get it after 10 minutes uptime and at other times you get it after 3 days uptime. Very random. :shrug:
NM I'll have your board soon. What's best BIOS you're using? Have you tested BIOSes and their perf? Which one has TLB patch and which ones not?
No chance for such a long uptime here in the next two weeks, due to the amd intel comparison i plan.Quote:
Originally Posted by KTE
Thank you for clarifying the freezing issue, I thought it occured repeatedly after ~3days
Better get your own. :DQuote:
Originally Posted by KTE
Used the latest sapphire provided first, switched to the latest stable dfi bios (22/01/08) after the 9500 stopped working. Brother Esau posted the flags required to force the flash somewhere here in this thread.Quote:
Originally Posted by KTE
I did not do much beside trying to reach the cpu frequ limit the last weeks, that 3hrs freeze made that a long term task.
The bioses previous to 22/01/08 had all types of glitches with phenoms, so i did not yet try em.
You can enable/disable the tlb cache via bios. I currently check what MSR registers are affected. Will run the everest mem and cache benchmark we ran on the msi and asus mobo and add results here.
exactly. also for the NB.. i wouldnt' think a hr-05 would cool it either, but i will look into aftermarket copper heatsinks to see about mounting some there or somethingQuote:
Originally Posted by Jaivan
the cpl-3-150 chips are good until 125C..which i wouldn't ever want to get tooo but thats the highest they can operate.
whats the max temps for the NB /SB? by the chip manufacturer?
TTTTTTTTTTTTTTTTThhhhhhhhhhhhhhhhaaaaaaaaaaaaaaaaa aaaaaannnnnnnnnnnnnkkkkkkkkkkkkkkkkkssssssssssssss sss AAAAAAAAAAAAAAAAAaaaaaaaaaaaaccccccccccccccccccccc ccchhhhhhhhhhhhhhhhhiiiiiiiiiiiiiiiimmmmmmmmmmmmmm mmm!!!!!!!!!!!!!!!!!!!!!!!!!!!!
BBBBBBBBoooooooooooooooooaaaaaaaaaaaaaaaaaaaaaaaar rrrrrrrrrrrrrrrrddddddddddddddddd UUUUUUUUUUUUUSSSSSSSSSSSSSSSSSsssssssssssssssbbbbb bbbbbbbb iiiiiiiiiiiiiiiiiisssssssssssssssssssssssssuuuuuuu uuuuuuuuuuuuueeeeeeeeeeeeeeeesssssssssss.......... ......... :mad: :mad: :mad: :rolleyes: :down:
Cache and Memory Benchmark (TLB Cache enabled via bios, should akt like yellow mode).
http://www.abload.de/img/everestdjy.jpg
http://www.abload.de/img/everest2qif.jpg
M3A results
K9A2 Platinum results
Memory latency is better than on the M3A and comparable to the K9A2 P. All other results are slightly lower.
Checked the TLB fix, both registers are changed on all cores, so the fix is waterproof.
Also tried to modify the CPU VID. AMD PM reports the change but the power consumption does not change when I switching between 1.3V and 1.225V.
KTE, didn't you mention that vid's are not needed if the core voltages can be manipulated?
BTW: With those timings the 1T setting is not applied (tried Auto/enabled/disabled) on boot but can be changed with Memset. 1T/2T could not be modified on the M3A.
USB problem? Go on with smilies. :)Quote:
Originally Posted by KTE
OT: Lol, had to cmos flash the p5k-e yesterday cuz it did neighter recognize and usb nor an ps/2 keyboard.
Update: Damn having the power consumption issue again after i switched back to the 2.6GHz settings. It are 182W AC in idle now, thats +40W. :confused:
Oh really... Interesting. My system froze randomly on me a few times (this is all at stock speeds right now mind you), two times it was in firefox. System had been running FAH SMP no problems. I upped my ram voltage (rated at 2.0-2.1V, bios had it at 1.9V) so we'll see what happens with that but so far no freezes since.Quote:
Originally Posted by KTE
BTW, I forget which is better for speed/overclocking, ganged or unganged mode?
If that stock chunk of aluminum on the NB can keep it cool enough at stock speeds surely the HR-05 can keep it cool at overclocked speeds. Maybe need a fan at really high speeds but then again maybe not, we'll have to see. I'm thinking of fabbing up a custom bracket to mount mine with.Quote:
Originally Posted by ZL1Killa
Ganged mode means both dct's act as one 128bit-dct. It's faster for single threaded stuff.Quote:
Originally Posted by SparkyJJO
Unganged means both dct's operate independant, tha's better for multitasking. But that mode is harder to oc.
Sandra and RightMark Multithreaded Memtest are two examples whom profit from unganged mode.
Those two screenies i posted are ganged vs. unganged singlethreaded.
Idle power consumption is dancing on my nose today. Had to remove one HD for an other machine, so i had to reinstall. After that i had 150W again. Now comes the funny stuff. I plugged in my USB-Stick with Benchmarks and Utility stuff and voila back at 180W. That USB-Sticky requires around 2-3W more if i plug it into the m3a or m2a-vm.
Thanks for the results! :up:Quote:
Originally Posted by justapost
Interesting, the board is slower overall, especially in L2 and L3 and latencies. The Plat. benches a little higher than that as I bench with all software running to show ideal bandwidth there (AV/FW in background just paused). It will fall shorter of it which I didn't expect.
Yeah the TLB fix isn't applied there you can see by your L3 scores. If it is, the L3 is very low and slow or it doesn't run at all.Quote:
Checked the TLB fix, both registers are changed on all cores, so the fix is waterproof.
BTW does Memset not work fully for you? It was displaying wrong speeds there for some reason.
It's the correct register as I've seen in the guides, try 1.55VID and see if idle power shoots up. ;)Quote:
Also tried to modify the CPU VID. AMD PM reports the change but the power consumption does not change when I switching between 1.3V and 1.225V.
BTW, what does MSR C001_0064 show, do you remember? I've forgotten, it's something related to the NB IIRC.
True, they're only to allow you more intermediate, high and low volts, nothing else. So if you want a voltage between say 1.225V to 1.23V and your BIOS doesn't allow it, then changing VIDs will give you an option for that voltage in there.Quote:
KTE, didn't you mention that vid's are not needed if the core voltages can be manipulated?
Yea USB problems on this board and they crap out like that randomly. I was stuck because you can't press any key at all so you can't shut down but a power supply off while OS is running which I didn't want to do as it destroys system too much and I had many works unsaved.Quote:
Originally Posted by justapost
That's a lot for idle. Somethings wrong somewhere. It could be your PSU too, if it falls in efficiency steeply. :yepp:Quote:
Update: Damn having the power consumption issue again after i switched back to the 2.6GHz settings. It are 182W AC in idle now, thats +40W. :confused:
Checked to make sure all MSR's are modified.Quote:
Originally Posted by KTE
Did you run your benchmarks with weak or normal mode for the mem?
Ups, the readings have spikes, catched one by accident.Quote:
Originally Posted by KTE
Now that cpu should survive till k10.5 at least, so i tried 1.1VID at 2.6GHz. I expected prime95 to fail but it did not also no power consumption change.Quote:
Originally Posted by KTE
In case you missed cuz i updated an old post, i have an USB-stick requiring 30W. :rofl:
C001_ 0064h-0068h are the P-State status registers, first bit is interesting.Quote:
Originally Posted by KTE
It's zero here, that means the rest of this msr register is invalid.
You can modify vcore in steps of 0.00625V that is half of what you can do with VID's (0.0125V step size).Quote:
Originally Posted by KTE
Don't like USB keyboards, still causing issues i don't want to spend my time fixing. Good to have a vnc-service running in such a case.Quote:
Originally Posted by KTE
This board tried to kill my processor, ran 1.63 volts through the core by default. I definitely didn't tell it to do that. It's currently running old Ballistix 2x1, but I'd bet the Team 2x2 starts working now that the processor isn't hitting thermal limits.
This DFI doesn't like the TeamGroup RAM. :shakes: Try it with SuperTalent or Crucial.Quote:
Originally Posted by MotF Bane
What do you mean by weak and normal mode here? :confused:Quote:
Originally Posted by justapost
Hmm.. it modifies them on all Phenoms according to guide AFAIK. What voltage and VID did it give you?Quote:
Now that cpu should survive till k10.5 at least, so i tried 1.1VID at 2.6GHz. I expected prime95 to fail but it did not also no power consumption change.
Try 0x3000100A from 1.25VID, it should give you a ~10W AC idling increase in power. If not then something with your CPU MSR is going iffy.
Yeah I saw it, it's very weird and well, too high :eek:Quote:
In case you missed cuz i updated an old post, i have an USB-stick requiring 30W. :rofl:
Thanks but are you sure that's their only relevance?Quote:
C001_ 0064h-0068h are the P-State status registers, first bit is interesting.
It's zero here, that means the rest of this msr register is invalid.
Have you actually tried these work? Very good options if they do. What (%) Vdrop and Vdroop does the board have?Quote:
You can modify vcore in steps of 0.00625V that is half of what you can do with VID's (0.0125V step size).
Tried both, last time it was PS/2, both have same problems here. :(Quote:
Don't like USB keyboards, still causing issues i don't want to spend my time fixing. Good to have a vnc-service running in such a case.
DDR2 800 4-4-4-12 2.16V as of last night.Quote:
Originally Posted by Oliverda
http://www.abload.de/thumb/dramweakmoderiy.jpgQuote:
Originally Posted by KTE
Voltage (in CPU-Z and Everest) did not change, AMD Power Monitor showed what I wrote into the register. The board seems to simply not use VID's. Every board seems to have it's own implementation. Must read the clock-chip's specs.Quote:
Originally Posted by KTE
Gonna look into that tonight, happens on various power consumption's in idle so i can sort out psu efficiency jumps.Quote:
Originally Posted by KTE
K, I wrote down all the registers related to P-States and power. I'll post a list here soon with all the variables.Quote:
Originally Posted by KTE
Well the resolution of the super-io chips reading seems to have a lower resolution ~0.016V, so that can not be used for verification. But I had situations where an +0.00625V helped to get the system stable.Quote:
Originally Posted by KTE
I'll give ya a few examples:Quote:
Originally Posted by KTE
cpu frequency/bios/idle/load
200x11,5/1,1625/1,152/1,152
200x12/1,175/1,168/1,168
200x13/1,35/1,328/1,344
219x12/1,38125/1,376/1,376
200x13 might work with a lower voltage all others use the minimal possible voltage (~8hrs prime95+3dmark+internet+some cad work).
From bios to load it's in the rounding area. idle might sometimes be 0.016V lower.
Don't have those options at all, DFI BIOS has allowed so much options. DS are all 1.00x but DRAM Drivers show up as "Weak mode = Disabled" in AOD.Quote:
Originally Posted by justapost
Must be, VIDs in BIOS are used to provide higher/lower voltages. With VIDs you can access very low volt increases (if you check them all, they're lower than +/-0.005V). But some BIOSes have the option to override VID settings, so no matter what VID you have it gives you all the VID higher and lower voltage options combined. Yours seems to be one of them, DFI definitely does. Saves a lot of work. ;)Quote:
Voltage (in CPU-Z and Everest) did not change, AMD Power Monitor showed what I wrote into the register. The board seems to simply not use VID's. Every board seems to have it's own implementation. Must read the clock-chip's specs.
Nice, no vdroop which is excellent for stability testing/oc stability but bad for power consumption and CPU/MB wear out but you have some vdrop I'm not too fond of. The MSI has high vdroop but lower vdrop than that.Quote:
cpu frequency/bios/idle/load
200x11,5/1,1625/1,152/1,152
200x12/1,175/1,168/1,168
200x13/1,35/1,328/1,344
219x12/1,38125/1,376/1,376
If vid's are used i guess it's the voltage step mode.Quote:
P-State Current Limit Register
0xc0010061: 0x00000000 0x00000010
[6:4] PStatMaxVal (lowest p-state, highest value) 1
[2:0] CurPstateLimit (lowest temp related p-state, highest value, max from htc and stc p-states) 0
P-State Control Register
0xc0010062: 0x00000000 0x00000000
[2:0] PstateCmd (last written p-state) 0
P-State Status Register
0xc0010063: 0x00000000 0x00000000
[2:0] CurPstate (active p-state) 0
P-State 0
0xc0010064: 0x800001BC 0x3000300A
[63] PstateEn: 1 (register is valid after reset)
[41:40] IddDiv: 1 (10A)
[39:32] IddValue: 94
[31:25] NbVid: 0011000b 1,25V
[22] NbDid: 0 (1)
[15:9] CpuVid: 0011000b 1,25V
[8:6] CpuDid: 0 (1)
[5:0] CpuFid: 10
CPU COF = 2600MHz
P-State 1
0xc0010065: 0x80000187 0x30005047
[63] PstateEn: 1 (register is valid after reset)
[41:40] IddDiv: 1 (10A)
[39:32] IddValue: 135
[31:25] NbVid: 0011000b 1,25V
[22] NbDid: 0 (1)
[15:9] CpuVid: 0101000b 1,05V
[8:6] CpuDid: 1 (2)
[5:0] CpuFid: 7
CPU COF = 1150MHz
P-State 2
0xc0010066: 0x00000000 0x30000000
[63] PstateEn: 0 (register is invalid after reset)
P-State 3
0xc0010067: 0x00000000 0x30000000
[63] PstateEn: 0 (register is invalid after reset)
P-State 4
0xc0010068: 0x00000000 0x30000000
[63] PstateEn: 0 (register is invalid after reset)
COFVID Control Register
0xc0010070: 0x00000000 0x3000300A
[31:25] NbVid: 0011000b 1,25V
[22] NbDid: 0 (1)
[18:16] PstateId: 0
[15:9] CpuVid: 0011000b 1,25V
[8:6] CpuDid: 0 (1)
[5:0] CpuFid: 10
COFVID Status Register
0xc0010071: 0x00800001 0x3000300A
[63:59] MaxNbFid:
[58:56] CurPstateLimit: 0
[54:49] MaxCpuCof: 0 (no frequency limit)
[48:42] MinVid: 0 (no minimum specified)
[41:35] MaxVid: 0 (no maximum specified)
[34:32] StartupPstate: 1
[31:25] CurNbVid: 0011000b 1,25V
[22] CurNbDid: 0 (1)
[18:16] CurPstate: 0
[15:9] CurCpuVid: 0011000b 1,25V
[8:6] CurCpuDid: 0 (1)
[5:0] CurCpuFid: 10
Hardware Thermal Control (HTC) Register
F3x64: 0x127F0004
[30:28] HtcPstateLimit: 1 (p-state limit in htc mode)
[27:24] HtcHystLmt: 2
[23] HtcSlewSel: 0
[22:16] HtcTmpLmt: 127 (115,5 Tctl)
[7] PslApicLoEn: 0 (no interrupt used for low end change)
[6] PslApicHiEn: 0 (no interrupt used for high end change)
[4] HtcAct: 0 (Prozessor not in HTC state)
[0] HtcEn: 0 (Prozessor not capable of entering the HTC-active state)
Software Thermal Control (STC) Register
F3x68: 0x10000000
[30:28] StcPstateLimit: 1 (p-state limit in htc mode)
Power Control Miscellaneous Register
F3xA0: 0xA00A2800
[31] CofVidProg: 1 (VID and PID of the p-state had been applied to the prozessor)
[29] SlamVidMode: 1 (Voltage is slamed not stepped)
[27:16] PStateId: 0
[13:11] PllLockTime: 1010b (PLL need 16 microseconds to apply a new FID on a p-state change)
[8] PviMode: 0 (Serial VID interface selected)
[7] PsiVidEn: 0 (PSI_L is always high)
[6:0] PsiVid: 0 (unused cuz PsiVidEn is zero)
Reported Temperature Control Register
F3xA4: 0x1A1C9880
[31:21] CurTmp: 208 (26 ° * Tctl)
Note: (see BKDG 2.10.1)
Tctl is a non-physical temperature on an arbitrary scale measured in degrees.... It specifies the prozessor temperature relative to the point at which the system must supply the maximum cooling for the prozessor's specified maximum case temperature and maximum thermal power dissipation.
[17:16] CurTmpSel: 0 (CurTmp provides the read-only Tctl value)
[12:8] PerStepTimeDn: 18h (1 millisecond)
[7] TmpSlewDnEn: 1 (Slew the rate controls in the downward direction are enabled)
[6:5] TmpMaxDiffUp: 0 (Upward slewing disabled)
[4:0] PerStepTimeUp: 0 (raniging from 1 to 8 milliseconds)
Funny stuff:
MSR-Editor:
0xc0010064: 0x800001BC 0x3000300A (p-state 0)
0xc0010065: 0x80000187 0x30005040 (p-state 1)
Bios:
CnQ: Enabled:
CPU freq: Auto
CPU voltage: Auto
WinXP:
Power Saving mode
Now I have CnQ with 800MHz vs. 2600MHz. :)
Note: With CnQ enabled before MSR Editor modification the p-states have to switch once, then the modified values get used. Also the VID's are applied and CPU-Z shows the vcore also changes, but that can be the auto setting also. Will try NB speed modification with p-states now.
Thanks Achim. :)
I have some qs for you;
Where were you getting the NB VID and CPU FID from there?Quote:
0xc0010071: 0x00800001 0x3000300A
MaxNbFid:
CurPstateLimit: 0
MaxCpuCof: 0 (no frequency limit)
MinVid: 0 (no minimum specified)
MaxVid: 0 (no maximum specified)
StartupPstate: 1
CurNbVid: 0011000b 1,25V
CurNbDid: 0 (1)
CurPstate: 0
CurCpuVid: 0011000b 1,25V
CurCpuDid: 0 (1)
CurCpuFid: 10
The NB VID doesn't seem to the as the guide states in that register but that only seems to show the CPU VID in that MSR for me (?).
Have you tested changing DID with this MB?
How did you access that address?Quote:
Reported Temperature Control Register
F3xA4: 0x1A1C9880
CurTmp: 208 (26°C)
CurTmpSel: 0 (CurTmp provides the read-only Tctl value)
PerStepTimeDn: 18h (1 millisecond)
TmpSlewDnEn: 1 (Slew the rate controls in the downward direction are enabled)
TmpMaxDiffUp: 0 (Upward slewing disabled)
PerStepTimeUp: 0 (raniging from 1 to 8 milliseconds)
Also, if Tcontrol is reading 0 then that means the 26C CurrentT is real according to the probes (which is faulty). :confused:
Maybe this Tctl value can be changed to give more accrate temps.
So it is possible to define at least two p-states with individual CPU VID/DID, CPU FID and NB DID.
There are two other variables in the p-state registers IddValue and IddDiv. Those are used during system start in the prozessor-systemboard power delivery compatibility check (see. BKDG 2.4.2.7) to calculate the amps the processor needs in the p-state. The guide also mentions that for each p-state an acpi prozessor p-state object should be created. I assume those will use the amp value to decide when to switch to another p-state. If thats correct it could be used to detect the currently used amps by tweaking p-state 1 till the system switches to state 1 under load.
The first bit in each p-states register defines if the state is valid, so it might be possible to define more than two states.
CPU VID and NN VID are at 1.25V if i do not define em different in the p-state registers and apply em using cnq mode as described above.Quote:
Originally Posted by KTE
CPU FID are bits 0:5 (0Ah=10). Realized i better had added the bits to the previous post after i nearly finished. Hmm i'm lazy but i'm gonna edit.
A NB divider of two boots (9/2 with 800MHz HT) and shows up in the MSR register (..71) but not in cpu-z. Tried to change it on the fly with the msr editor and the system froze.Quote:
Originally Posted by KTE
That is on the same page as the nb multi in wpcredit (Device 24:Function 3) is F3xXX(X with baredit).Quote:
Originally Posted by KTE
Only skimmed over the docs don't have a good oversight over temperature handling atm.Quote:
Originally Posted by KTE
EDIT: Updated previous post added bits used for the variables and an info abou tclt (it's an delta and no absolute temperature)
Yeah that CnQ P-State 1 works realtime. I've messed about with it earlier - old value is RDMSR, new value is WRMSR (stable):
Attachment 73161
4x is lowest multi limit, freeze below that.
I'll edit post with a full reply in a while, bit busy yet. :D
EDIT (updated above pic):
That above is lowest voltage for NB/CPU stable too, any lower it freezes.
I'm running near enough exact settings as you Achim, especially CPU settings. My system idles 108W AC @ this:
Attachment 73162
And with CnQ enabled now in the first pic above, it idles 94W AC (2x HDs, 2x 5V fans). Very good options to access and edit these registers IMHO, don't you think? :yepp:
Here are my settings I run with those two:
V above = VID.Code:Current: MSR 0xC0010070
0x00000000 0x4800340A (1.100V NB/1.225V CPU)
P0: MSR 0xC0010064
0x800001BC 0x4800340A (1.100V NB/1.225V CPU)
P1: MSR 0xC0010065
0x80000187 0x48007040 (800/1800 0.850V/1.100V)
As you can see, VIDs is how the processor controls all volts internally even for CPU and NB in all P-States including boot states. So that 1.250VID NB is 1.232V/1.240V. But NB VID never changed in P-State 1 unless you do this manually. I know NB FID cannot be changed after boot and that's why it won't change where HTC is active where GCLK downclocks nor when you have CnQ enabled but ... messing with the NB VID register it works fully, like so:
Those are only ones I can access yet because I don't have my saved ss/txt files here.Code:NB VID Control
30h 0011000b 1.250V
....
38h 1.200V
39h 1.200V
40h 1.150V
41h 1.150V
42h 1.138V
43h 1.138V
44h 1.125V
45h 1.125V
46h 1.112V
47h 1.112V
48h 1.100V
49h 1.100V
50h 1.050V
I can change CPU DID to 1 and 2 real-time but anything higher is no go.
I've not tried NB DID yet.
Yep, power is controlled by the CPU VID, NB VID, IddValue and IddDiv which also sets the TDP and that changes the Tcontrol and Tcontrol max limits apparently.
BTW I know Tcontrol is not the actual temp value in degrees but just an arbitrary value to represent it. That's why it's allowed to read subzero at high ambients. :D
What happened was, my first 9500 which is the main one I experimented highly with temps, it read the temp in BIOS the same as the physical Tcase temp most likely because it was missing the offset, but the ones after that were all different. This 9600BE reads the register properly (sub-ambients).
Same with F3xA4, I asked about it because on the NB register access it read 0b for me so I thought there's another way. It reads correctly now but many times it blanks out or reads F's.
Thanks for adding the bits, makes me not have to read the guide. Although you did make me read up the guide once again you know... :D
Sorted out the usb power consumption issue. Removed one of the 4pin 12V connectors now the stick consumes ~5W AC.
Saw you messed with p-states must have missed that you looked into CnQ,sry. I'm pretty happy that it works that way. With 800MHz and ~0.9V the system requires ~110W AC idle, untweaked CnQ in idle 120W, 2600GHz ~1,28V in idle ~150W. (with one pwm fan and only one sata hd, everything else as in sig). So I save ~10W against CnQ and ~40W against normal oced 2.6GHz mode.
It's also a nice way to test higher multi/voltage combinations. Use a save setting for state 1 and the test setting in state 0, as soon as you stop load you are save. :)
Would be a great feature if the bios allows defining both p-states settings.
A = NB VID ,B = CPU VID
C = CPU FID/CPU DIDCode:78h: 0.80V
70h: 0.85V
68h: 0.90V
60h: 0.95V
58h: 1.00V
50h: 1.15V
48h: 1.10V
40h: 1.15V
38h: 1.20V
30h: 1.25V
28h: 1.30V
20h: 1.35V
18h: 1.40V
10h: 1.45V
08h: 1.50V
00h: 1.55V
Divisors of 2 only work if the frequency can not be described with a 1 divisor.
Pattern:Code:40h: 800 MHz
41h: 850 MHz
42h: 900 MHz
43h: 950 MHz
44h: 1000 MHz
45h: 1050 MHz
46h: 1100 MHz
47h: 1150 MHz
48h: 1200 MHz
49h: 1250 MHz
4Ah: 1300 MHz
4Bh: 1350 MHz
4Ch: 1400 MHz
4Dh: 1450 MHz
4Eh: 1500 MHz
4Fh: 1550 MHz
00h: 1600 MHz
51h: 1650 MHz
01h: 1700 MHz
53h: 1750 MHz
02h: 1800 MHz
55h: 1850 MHz
03h: 1900 MHz
57h: 1950 MHz
04h: 2000 MHz
59h: 2050 MHz
05h: 2100 MHz
5Bh: 2150 MHz
06h: 2200 MHz
5Dh: 2250 MHz
07h: 2300 MHz
5Fh: 2350 MHz
08h: 2400 MHz
61h: 2450 MHz
09h: 2500 MHz
63h: 2550 MHz
0Ah: 2600 MHz
65h: 2650 MHz
0Bh: 2700 MHz
67h: 2750 MHz
0Ch: 2800 MHz
69h: 2850 MHz
0Dh: 2900 MHz
6Bh: 2950 MHz
0Eh: 3000 MHz
AAxxxxxx NBVID
xxxxBBxx CPUVID
xxxxxxCC CPUFID/DID
A*2^24+B*2^8+C
I do not modify the bits [63:32] for the p-states. With above tables and the pattern i hope it's obvious how to define your own p-states.
Example:
p-state 0:
2.6GHZ 1.275V/1.1V
NBVID 1.1V 48h
CPUVID 1.275V 2Ch
CPUFID 2.6GHz 0Ah
MSRC001_00[64] Bits [31:0] 48002C0Ah
p-state 1:
0.8GHZ 0.85V/1.1V
NBVID 1.1V 48h
CPUVID 0.85V 70h
CPUFID 0.8GHz 40h
MSRC001_00[65] Bits [31:0] 48007040h
To apply it with RW-Everything use that script:
Note: The ">" must be in the text file.Code:>cpu 1
>wrmsr 0xc0010064 0x800001BC 0x48002C0A
>wrmsr 0xc0010065 0x80000187 0x48007040
>cpu 2
>wrmsr 0xc0010064 0x800001BC 0x48002C0A
>wrmsr 0xc0010065 0x80000187 0x48007040
>cpu 3
>wrmsr 0xc0010064 0x800001BC 0x48002C0A
>wrmsr 0xc0010065 0x80000187 0x48007040
>cpu 4
>wrmsr 0xc0010064 0x800001BC 0x48002C0A
>wrmsr 0xc0010065 0x80000187 0x48007040
>rwexit
Another Note: BKDG mentions that a NB DID must be the same in all p-states, as changing the NB FID requires an reboot NB frequency can not be modified via p-states.
Yep, just checked out the guide, quote BKDG:
MSRC001_0062 holds the P-State transition for each core so you can first define a separate P-State under MSRC001_00[68:64] and then using MSRC001_0062 set a separate P-State from 0-4 for each core individually. So P0 is maximum power state, P1 for core 0, P2 for core 1, P3 for core 2 and P4 for core 3. Quite nifty don't you think? ;)Quote:
The processor supports dynamic P-state changes in up to 5 independently-controllable frequency planes: each
CPU core (up to 4) and the NB; and up to 2 independently-controllable voltage planes: VDD, and VDDNB.
RWE doesn't work for me, it just gets stuck and deletes the file data. :(
Each core has five p-states. At least two of em work have not tried more. SoQuote:
Originally Posted by KTE
you can use it to define individual multis and volts for each core. In terms of the volts the max under all cores in a defined p-state is used. The multis realy apply individual.
Tried the CPU FID's with a two divisor. Not all of em work. Above 5Bh the system freezes.
What happens if you enter the commands (without the ">" character) in rwedit manual?
^Not tried it manually but the same thing happens if I remove the ">" prefix from the file. :(
I'll try it after I get some work done.
What's max HT ref you've tried with the PC-AM2RD790 Achim?
Tried to add a third p-state between the other two at 2.3GHz also modified the max p-state value in an other msr register (see above).
In Desktop mode it is possible to set the p-state for an core by writing the p-state number into MSR C0010062h.
Debug that thing. :DQuote:
Originally Posted by KTE
Was round 240MHz with 9500 have not tried max with 9600BE yet used 222MHz so far.Quote:
Originally Posted by KTE
EDIT: few more scripts
cpu part of p-state 0 for core 0-3 is defined in Local0-Local3. Local4-Local7 are for p-state 1.
Force p-state 1 with actual settings (works best in Desktop mode).Code:>Local0 = 0x280A
>Local1 = 0x280A
>Local2 = 0x280A
>Local3 = 0x280A
>Local4 = 0x6840
>Local5 = 0x6840
>Local6 = 0x6840
>Local7 = 0x6840
>cpu 1
>rdmsr 0xc0010064
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local0
>wrmsr 0xc0010064 LocalD LocalA
>rdmsr 0xc0010065
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local4
>wrmsr 0xc0010065 LocalD LocalA
>cpu 2
>rdmsr 0xc0010064
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local1
>wrmsr 0xc0010064 LocalD LocalA
>rdmsr 0xc0010065
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local5
>wrmsr 0xc0010065 LocalD LocalA
>cpu 3
>rdmsr 0xc0010064
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local2
>wrmsr 0xc0010064 LocalD LocalA
>rdmsr 0xc0010065
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local6
>wrmsr 0xc0010065 LocalD LocalA
>cpu 4
>rdmsr 0xc0010064
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local3
>wrmsr 0xc0010064 LocalD LocalA
>rdmsr 0xc0010065
>LocalA = and LocalA 0xffff0000
>LocalA = or LocalA Local7
>wrmsr 0xc0010065 LocalD LocalA
>rwexit
Force p-state 0 with actual settings.Code:>cpu 1
>wrmsr 0xc0010062 0 0
>cpu 2
>wrmsr 0xc0010062 0 0
>cpu 3
>wrmsr 0xc0010062 0 0
>cpu 4
>wrmsr 0xc0010062 0 0
>cpu 1
>wrmsr 0xc0010062 0 1
>cpu 2
>wrmsr 0xc0010062 0 1
>cpu 3
>wrmsr 0xc0010062 0 1
>cpu 4
>wrmsr 0xc0010062 0 1
>rwexit
Those scripts work with cnq disabled and cpu vid set in the bios. Both p-states must work with your ref HT because an switch betwenn em is required to apply the new values.Code:>cpu 1
>wrmsr 0xc0010062 0 1
>cpu 2
>wrmsr 0xc0010062 0 1
>cpu 3
>wrmsr 0xc0010062 0 1
>cpu 4
>wrmsr 0xc0010062 0 1
>cpu 1
>wrmsr 0xc0010062 0 0
>cpu 2
>wrmsr 0xc0010062 0 0
>cpu 3
>wrmsr 0xc0010062 0 0
>cpu 4
>wrmsr 0xc0010062 0 0
>rwexit
Does anyone know what could cause the vcore to reset back to standard? Had it set to 1.475 which showed alright on cpu-z, but after running 3dmark it was back to 1.375 :confused: I'm using the DK 790FX M2RS by the way.
Yeah those p-states are great for tweaking, running with one HD and 3xFans atm.Quote:
Originally Posted by KTE
CPU 2.6 (217x12) at 1.3V CPU VID
NB 2.17 (217x10) at 1.3V NB VID
MEM 578MHZ at 2.25V
idle: 157W AC
load: 270W AC
CPU .8 (217x4) at 1V CPU VID
NB 2.17 (217x10) at 1.3V NB VID
MEM 578MHZ at 2.25V
idle: 139W AC
load: 180W AC
Lowest possible consumption is cpu 200x4 at 0.9V nb 200x9 at 0.95V. In idle ~105W AC. So the board still needs more tweaking to beome more efficient.
A note aboute the NB multi. If CnQ is set to Auto in the Bios, the NB multi is always 9x. So it's required to up the ref HT to tune the nb.
However with above scripts it's possible to set the p-states and switch between em manual. Those work with CnQ disabled in bios.
A third p-state would be great, i'd like to have a low normal and high p-state.
Is 2.6GHz stable at 1.225V VID?Quote:
Originally Posted by KTE
The predefined p-states differ in the CPU DID and have the same CPU FID, can be it's faster to switch between the modes if only the DID changes.Quote:
Originally Posted by KTE
NB DID must be equal on all cores's and p-states, no way to change the nb speed on the fly.
Have you played with IddValue/IddDiv? I assume it can be used to define under which load the 0 p-state get's used.Quote:
Originally Posted by KTE
Do you know a stress-utility which can generate stress in steps? Maybe sandras energy efficiency test shows a difference.
It's like i expected. calibrated against the worst case temp with arbitrary scaling.Quote:
Originally Posted by KTE
Looking at the MSR registers HTC seems to be an feature of future steppings.
In terms of temps i rely on the external sensor on the mobo. This one reports the highest temps. The avreage is +10° over CPU temp. A probe next to the prozessor reads the same temps as the cpu sensor most of the time, so i assume this temp is actualy higher.Quote:
Originally Posted by KTE
Skimmed over the whole thing one time, just to get an outline and know where to look for what. Alot of extra research is required on my side to read that doc.Quote:
Originally Posted by KTE
Overdrive?Quote:
Originally Posted by kwark
so, finally got my 790fx-m2r m/b back from dfi RMA (actually I got it last week, but didn't get a chance to check it out (due to my crazy schedule). Anyway, I received it back from dfi RMA with the same indications (C1 stop error if memory slots are in #3 or #4 are occupied). It looks to me like the BIOS chip was changed out (wrote the numbers off of the old one) and they put a new revision code sticker on there (was R.AC0 before and now it's R.AD0) but other than that it looks the same....maybe they changed something and it didn't work, but who knows for sure.
kwark: AOD can do that, yup.
Achim: I'll check out those scripts when I get time. Been too busy yet.
Lowest I've had stable which is also my max stable yet (without freezes) is what I'm running since my last post.
Attachment 73233
Attachment 73234
Idle is still 94W but load is now lower. 186W P95 Small FFT. :eek:
Now typing in Firefox, 6 tabs open, with AV/FW engines running, AMD Power Mon and two text files open, I'm idling 96W AC.
P95/bench/firefox is all fine, just have to test a memory intensive game yet. First benchmark for L3 instability is EVEREST L3 bench. It will lock up if totally instable. The next best usually is rendering and better is a game. I've done some Apophysis fractal rendering fine. Next is a game.
It's been up for over 24hours so far without a problem. Problem for me is not P95 stability, that's quite easy. First 4 weeks 2.7GHz was 1.25V stable. The problem for me is avoiding the freeze after a day to three days idling. So far this is best yet. CPU seems to love low voltages over high ones. :shrug:
Running 1.225VID because I can then access lower voltages below 1.264V but above 1.24V. Like right now Idle vs. Load =>
Attachment 73235 vs. Attachment 73236
Wow, big differences to mine and we're at similar MHz. Maybe it's the PSU efficiency giving those results? Actually you have 578 2.25V on MEM, and I have 536 2.16V. That's only maximum 3W DC more though. You also have a high HT ref. compared to mine (201) and my NB is low, 1.038 in P-State 1 and 1.038 in P-State 0. Previously max I've had stable at 1800MHz IMC was 1.050VID 1800 at 1.27V 2.7GHz CPU. I also run HT at 1.2V. It looks like I must be running lower current than you are, only that can explain the huge difference (almost 100W AC load).Quote:
Originally Posted by justapost
These MSI BIOSes don't have VID options in BIOS (apart from old 1.13B).
Through testing I previously found, CnQ with low CPU VID/Voltage won't get much gains in dropping power compared to how much you gain by just dropping NB VID/Volts. I get quite a bit of gain by dropping NB VID/Volts, it is supposed to be a power hog which we knew since around June, and you can see that clearly. I have ran 2.211GHz max on 1.250VID NB stable so far, haven't tried more.
Make note: This was no way possible in first 3 weeks. 2GHz NB at 1.250V in them weeks would reboot.
If CnQ is disabled how do those scripts change between P-States and when?Quote:
Lowest possible consumption is cpu 200x4 at 0.9V nb 200x9 at 0.95V. In idle ~105W AC. So the board still needs more tweaking to beome more efficient.
A note aboute the NB multi. If CnQ is set to Auto in the Bios, the NB multi is always 9x. So it's required to up the ref HT to tune the nb.
However with above scripts it's possible to set the p-states and switch between em manual. Those work with CnQ disabled in bios.
A third p-state would be great, i'd like to have a low normal and high p-state.
See above, yep. VCore is higher, 1.248V idle, 1.240V load. I'm surprised myself. 2.639GHz froze idling after 2 days at even 1.3-1.48VCore. I only recently started trying these lower volts.Quote:
Is 2.6GHz stable at 1.225V VID?
Yeah, I've switched CPU FID and DID with P-States and manually in Windows. But not NB DID/FID, no way as guide mentions.Quote:
The predefined p-states differ in the CPU DID and have the same CPU FID, can be it's faster to switch between the modes if only the DID changes.
NB DID must be equal on all cores's and p-states, no way to change the nb speed on the fly.
I haven't, no. Is that register write enabled or only read? I thought it was auto set.Quote:
Have you played with IddValue/IddDiv? I assume it can be used to define under which load the 0 p-state get's used.
I don't really. Only one I recall is Intel TAT which does this. You can always go old skool and useQuote:
Do you know a stress-utility which can generate stress in steps? Maybe sandras energy efficiency test shows a difference.
...then just customize further and have four of them open to stress. :DCode:int main()
{
while (true);
}
I'll tell you what I use though. I use this utility I've attached. Can choose to stress different cores with it (can set affinity manually to get different cores and different loads). Works good, not Prime95 load, because those iterations are FPU intensive and this isn't, but it produces a variety of load and priority is set to 4 (IIRC), so it won't jam your screen apps unusable. It's probably the first test I use each time. It still doesn't go up in steps though.
The real TCASE temp actually is the same as the TCONTROL value we get at one point near 60C according to graph given in BKDG. But what is funny is that TCONTROL is supposed to be lower all the way than the actual TCASE temp until a certain intersection point whereby TCONTROL becomes higher than the real TCASE temp (IHS temp). So you guys seeing high temps at some point under load but low temps idle get everything reported correctly.Quote:
It's like i expected. calibrated against the worst case temp with arbitrary scaling.
Looking at the MSR registers HTC seems to be an feature of future steppings.
Yea true, Internal core temp will always be higher than TCASE temp (IHS). Usually minimum 15C higher.Quote:
In terms of temps i rely on the external sensor on the mobo. This one reports the highest temps. The avreage is +10° over CPU temp. A probe next to the prozessor reads the same temps as the cpu sensor most of the time, so i assume this temp is actually higher.
Hehe, you know the last guides were easier to read and make sense of than this one. I've heard many developers confused by this one and complain. :DQuote:
Skimmed over the whole thing one time, just to get an outline and know where to look for what. Alot of extra research is required on my side to read that doc.
Found my lowest stable settings:
CPU 201x12 1.225VID/1.248V lowest
IMC 201x9 1.038VID lowest
Power idle: 92W AC
Power load: 181W AC
But you can increase this further. I'm on this now at the same volts=>
Attachment 73257
Attachment 73258
Power idle: 94W AC
Power load: 192W AC
Big jump but I'm quiet happy. :cool:
Had the 3850 in my system yesterday, forgottt that in my specs. ALso had upped the chipset voltages. Here's what i can use save with stock ref HT.
MOBO: Sapphire Clone - SB 1,2V/NBc 1,12V/NBpcie 1,12V/NBht 1,04V
Note: Audio+Modem Card's coming with mobo attached and only one 4pin 12V connector used.
PROC: 9600BE
MEM: 2x1GB CB Tracers 6400 @ 1,8V 800MHZ 5-5-5-15
GFX: HD2600XT @ stock
COOLER: BigTyphoon 120 with 120mm ixtrema fan on zalman fanmate on lowest speed, 1xAMD stock cooler fan for PWM.
PSU: ZM460B-APS
HD: 1xWD1600YS 160GB SataII RE
DVD: LG-GSA10N IDE
p-state-0:
cpu: 13x 1.3V VID
nb: 9x 1.1V VID
http://www.abload.de/img/pstate0-idle-126wr0u.jpg
http://www.abload.de/img/pstate0-load-230wviv.jpg
idle: 126W AC / 100,7W DC
load: 230W AC / 187,5W DC
pstate-1:
cpu: 4x 0.9V VID
nb: 9x 1.1V VID
http://www.abload.de/img/pstate1-idle-108wzj4.jpg
http://www.abload.de/img/pstate1-load-127wq68.jpg
idle: 108W AC / 85,3W DC
load: 127W AC / 101,5W DC
If you disable CnQ in the bios you can still customize the two p-states for each core and force the settings to load by switching to that p-state via writing the p-state number to MSR register C0010062h.
Therefore I added two scripts whom set pstate 0 and the 1 or vice versa 1 and the 0.
If you are in p-state 0 writing 0 to C0010062h does not update the settings, so i have to switch to state 1 and back to state 0.
Thank you for attaching that stress utility. Unfortunately the attachment does not work.
What efficiency does your PSU have at 100W? Mine 100W ~78,6% 110W ~79%.
EDIT: Looking at my screenies i realize that prime95 failed on one core so i still need above 1.3V CPU VID to run stable.
Ah ok. Yes, that's true, you can customize MSR[...]62 to switch P-State manually without CnQ.
You don't need to disable CnQ in BIOS though, just change Power Options to Max battery and try in Windows. :yepp:
I haven't tried checking CnQ settings load watts. [added below]
Scripts don't work for me still. Debugging doesn't get far. RWE just freezes and you have to use Task Manager to kill it. Will need more time for it. :(
Your 1st power figures (2600) should read AC / DC.. you missed that but edit comes handy :D
You'll need more than 1.312V for 2600 P95 stable it seems. I'll update mine to a similar setup and then try and compare power consumption and work out why the difference. I'll use your volts and settings. I'll do it on this now and then with the Sapphire when I get hold of one (should be soon).
115V: PSU is 78.5% eff. at 110W AC and 81% eff. at 156-186W AC.
220V: PSU is 80.6% eff. at 110W AC and 84.3% eff. at 156-186W AC.
I'm going to pick up the Gigabyte GE-S550A-D1 PSU soon and use it's P-Tuner software which is pretty damn accurate (known problem is +25W DC showing and 12V3+ below 180W DC is wrong) to show me the amps/volts each rail is pulling and work out the DC power draw by the CPU 8-pin. ;)
So we'll know what the CPU is actually pulling alone and I'll put the GPU/MB/peripherals on separate 12V rails so we can work their draw out too. ;)
The attachment linked worked before but doesn't now :confused:
Attached it again anyway.
EDIT:
I just tried everything again, found a bug in CnQ. Good news. ;)
90W AC consistent right now with basic apps running. :cool:Code:1.
CPU 202 12x 2.626GHz @ 1.248V, 1.225VID
NB 9x 1.818GHz @ 1.038VID
HT 9x 1.818GHz @ 1.2V
2x 1GB RAM 538 5-5-5-18-20-75 2T @ 2.1V 1.25x all DS
Fan1 1510RPM @ 5V 400mA (stock) / 2300RPM load @ 7V
Fan2 810RPM @ 5V (120mm)
Sapphire HD 2600 XT 800/700 @ 1.26V/DK
32-47% GPU fanspeed
1x SATA II WD Caviar SE 76GB
2x USB ports (mouse/keyboard)
1x Gbit Ethernet port
Antec Earthwatts 430W
Power: 105W AC idle, 184W AC load
Power: 84.6W DC idle, 155W DC load
2.
CPU 202 4x 0.808GHz @ 0.864V, 0.850VID
NB 9x 1.818GHz @ 1.038VID
HT 9x 1.818GHz @ 1.2V
2x 1GB Tracer RAM 538 5-5-5-18-20-75 2T @ 2.1V 1.25x all DS
Fan1 1510RPM @ 5V 400mA (stock)
Fan2 810RPM @ 5V (120mm)
Sapphire HD 2600 XT 800/700 @ 1.26V/DK
32-47% GPU fanspeed
1x SATA II WD Caviar SE 76GB
2x USB ports (mouse/keyboard)
1x Gbit Ethernet port
Antec Earthwatts 430W
Power: 87W AC idle, 98W AC load
Power: 67.5W DC idle, 76W DC load
Compare power draws of this same system under different specs before:
15th January: http://www.xtremesystems.org/forums/...&postcount=693
25th January: http://www.xtremesystems.org/forums/...&postcount=839
1st February: http://www.xtremesystems.org/forums/...&postcount=950
Interesting things you're discussing here.. I'm not through with this thread as a whole so I dont know if the p-state-discussion evolved out of phenom problems or these are just nice possibilities to hold down your power consumption.. whatever, will get to learn that later..
I myself own the Board for about 2 weeks now and there are two questions remaining (specs in signature soon):
I can't run > 300mhz htt with integer cpu-multiplier (for example 10x) @ DDR667-Divider, no matter which ht-multi-setting, although CPU was successfully testet with prime @ 280x12 @ 800Mhz ht-multi, highest achievable ram speed ist 266x12 @ DDR800-Divider (so 1066) @ 1Ghz HTT prime stable..
> 300Mhz up to at least 340mhz htt is no problem with half cpu-multipliers (i.e. 10.5x) @ DDR667 ram speed - funny? I would be pleased, but ram performance is about half at half cpu-multipliers.. And theres no tref option or anything...
Suggestions/Answers? I'm just wondering.
I think it's the imc of my cpu, but would appreciate to hear your opinions..
If I got it right, cpu host/htt boot up clock can remain at 200mhz when playing with the cpu multi.. did not encounter any better behaviour if I set it to 266, which is the highest bootable setting with default 12x multi..
second question is could i do anything about my imc/ram related oc-problems with dram driver settings? I'm used to timings and dram data drive strenght, dram drive strength so far, but not one page of driver settings ;) although i any additional setting to play around with is welcome given good stability at optimized defaults, which this board definitely has..
any suggestions for playing around with these settings? weak/normal drive (i know since dfi nf3 ultra-D ;) ) have been already testet, so are the "normal" timings.. I can't get past 1066 substancially with my powerchip-based GSkill GBPQ.. I think 1100 would be possible if my imc wouldn't be that crappy..
Many thanks :D
signature... aah forgot: bios is 08/02/12 beta... same issues with 08/01/30 final..