Only enable HPET if you're on Windows Vista.Quote:
Originally Posted by jonspd
And set all PCI-e lanes to "Auto".
Printable View
Only enable HPET if you're on Windows Vista.Quote:
Originally Posted by jonspd
And set all PCI-e lanes to "Auto".
Quote:
Originally Posted by Hosser
did that already, anyways enabling those HPET would help boost your performance?!
here's what i did transferred those 40mm right at the mosfet, removed the circupipe sticker...
from this
http://i140.photobucket.com/albums/r...e/DSC01295.jpg
to this
http://i140.photobucket.com/albums/r...e/DSC01300.jpg
:D
HPET has nothing to do with performance, it's just new high resolution hardware interrupt timer. Can only be used by Windows Vista and some modern Linux kernels. Windows XP does not make use of it.Quote:
Originally Posted by madfaze
Nice cooling solution, though I'd imagine it's quite loud? How has it affected temperatures/overclockability?
it was already enabled and the others where already on auto :D
I recommend disable HPET if you're not using Windows Vista.
I left it as it was defaulted to. Maybe KTE can explain more or why or why not I have a pci-e 2.0 card so I do what it to run the correct bandwidth.
thanks! :)Quote:
Originally Posted by Hosser
noise is tolerable when you get to use of it... (8k rpm) :D
for temps im not quite sure about it however can you monitor this?...
I doubt there are any software monitoring methods available; could use a finger maybe? Check to see if they still get hot? :DQuote:
Originally Posted by madfaze
HPET is seperate from PCI-e 2.0 and not required for its operation.Quote:
Originally Posted by jonspd
Quote:
Originally Posted by Hosser
:shocked:
nah its not that warm anymore... :D
tictac: what was that about left shift+tab F1 right shift+tab F2 or something you were saying... ? :p:
Hehe, nice find. But they give no specs we're after there. :(Quote:
Originally Posted by madfaze
You only need one slow big fan really, low noise and moves decent air.
Should be approved very soon. ;)Quote:
Originally Posted by Hosser
Only the PCIe you use (1 usually) needs to be put to Auto and HPET timer is best disabled.Quote:
Originally Posted by jonspd
I have a 60mm 8k RPM fan, I know damn well how much screaming noise they make! :eek:Quote:
Originally Posted by madfaze
Why not mount a 1k RPM 120mm fan near the back of the case instead, low noise, good cooling? You guys over in Asia do have far higher temps than we do here though, so you need it much more.
Stick a thermocouple inside the slots in the MOSFET heatsink until you feel it hits a MOSFET. Be running something like P95 at that time, the temps will fly high, usually plus 65C (which is still OK). :)Quote:
for temps im not quite sure about it however can you monitor this?...
BTW that above setting I had to switch off (game) at 20hrs P95 stable ambient varied from 30-20C:
http://img220.imageshack.us/img220/6...2722400zs1.png
Have been trying to finally find high end stability at 22C ambient...
2.8G (200x14) boots easily at 1.35V but it's unstable.
1.40V = unstable
1.450V = unstable
1.50V = unstable
1.56V = unstable
Never tried more, this is air, and for air even that was too high. MHz limit @ cooling (stock cooler).
As a test I tried 1.47V at 2.3G (idles 35C, max fanspeed) and it was also unstable. So we see, Phenom hates high voltage on air at these ambients, at least mine does. 1.456V was max which would run without giving errors.
Tried (207x13.5) 2.794G next;
1.40V = unstable
1.450V = unstable
1.488V = unstable
Tried (206x13.5) 2.78G next;
1.40V = unstable
1.450V = unstable
1.488V = unstable
Stopped right there. Previously I've had upto 2.756G fully stable. So now I'm trying the same MHz again to see if it is still stable.
Right now testing 1.39V idle/1.368V load and it's 2.756G stable.
I'll drop volts next to find lowest it's stable at... but you can already see that at 1.27V easily stable for 2.63G, for just 135MHz more (+5.13%) you require more than +0.2V (1.488V -- +17.17%) and you still cannot get perfect stability (fails after ~2-3 hours P95 small FFT). That's what you call a processor limit. ;)
On H2O, I do think you can get 2.8G stable with lower volts with this chip and possibly bench +2.9G.
EDIT!:
-2.756G passed 1.392V 5hr and then, whilst gaming, it froze the system = unstable :(
-2.7G used to be fully stable for anything around 1.320V around 10 days back for over a week that I tested: Original Stability Report
Now, unfortunately it failed P95 at 2hr20min and repeatedly failed playing a simple Youtube video at 1.360V. :(
This may however have something to do with the temps. Phenom may not like these temps much, before I was using the same cooler but with a good mount and solid paste. Now I was idling over 10C higher since the paste was 1/3 of original left and reused. Will throw my Zalman onto it to check how it does... 50-54C are not temps which will make Phenom core error, so if it is finding instability at >50C it'll be because the core temp probe is reading minimum -10-15C from the real value. This'll have to be tested...
Coming up next...
At what <monitoring tool> temperatures does a stable Phenom at stock start to error? :p:
Quote:
Originally Posted by KTE
What are you gonna do add heat :shocked:
Great testing you are still doing to this day. Glad that someone is still trying to figure out the ropes of this quad...
or just turn down the fan speed
Or just... have no fan at all. :D
Heatink with some passive air keeps it relatively "up there" IMO.
or hair dryer on top of cpu fan.. hehe..
Well well.. we're making good progress. ;)
See the above 2.6G 20hr stable?
I run that setting daily... replicated it just now at 30C, 35C, 40C, 45C, 50C and 55C BIOS (70% load)/EVEREST -> results:
30C idle/load -> stable
35C idle/load -> stable
40C idle/load -> stable
45C idle -> shaky
45C load -> stable
50C idle > no boot!
50C load -> shaky
52C idle -> no boot!
52C load -> mostly errors
55C idle -> no boot!
55C load -> full of errors!
Shaky = Errorful on and off but altogether unstable (freezes/hard locks)
We have established a temperature bottleneck with Phenom guys. Achim (justapost) experienced something very similar and I've never had high temp readings to be able to tell but today my temps were simulated as high as his were before and what he found is exactly what I'm finding...
Freezing/hard locks are known as a very possible temp issue on any setup.
I could not measure the IHS temp nor did I have probes with me but I used the normal method made for us to use: software monitoring tools. The temperatures reported were the above with software/BIOS.
However, I do not think that was the real temperature. To me it looks highly likely MSI board/Phenom is reading 10-15C below the actual core temps as we know and there is no CPU I've seen which fails POST 20C below max danger temp limit. In Phenoms case, that's 70C, anything below that (real) should run fine. Those temps of 50C must have been 60-65C real IMHO.
Jack (JumpingJack) briefly mentioned relatively high stock temps with his Phenom sample too and that I couldn't corroborate with Gigabyte/MSI/DFI+Phenom testings but I kept checked around and found two other ASUS+Phenom pairings and they both idled/load pretty high up according to software at same MHz/Volts as us, like him. Thus, to me it seems highly likely that the ASUS boards have the correct temp. calibration for Phenoms and that the MSI boards show 10-15C below actual. Otherwise, 50C will never fail POST and freeze whilst in the BIOS.
One other thing I tested but could not measure for lack of equipment with me was MOS/inductor cooling: yes you do need it or you'll fail stability testing at stable MHz easy. Especially at load, typically lower ambient/PWM/CPU temp will get good stability it seems. Guess I better get my skating shoes on. :)
Gack I was certainly surprised.
how do u get it to be at 30C load? if its not having problems reading the temps, then your doing a great job cooling it, or is that some kind of weird chiiller setup you used to do that
-2C ambients 3x Delta 220CFM 1x Delta 102CFM 1x 20inch fan do the trick very well. ;)
I'm thinking of testing it under more cold now. Depends on how the Wolfdale pan out. If the new ones they send us are also bugged with temps then will have to stick with this yet because my boss won't accept it.
My last 9600BE and 9500 didn't have this temp problem. I'd been upto 60C software reading with those stable.
I just booted the 9600 BE while ambient was 27C, very interesting that it booted up faster than usual straight into the BIOS inside I would say 3 seconds and it read 19C (and moving up quick) in HWM within the BIOS. This is very likely 29C actual, thus a -10C deficit since processor started off at 27C (ambient) and can't be less. I modified my 9500 to verify its temps but I don't want to do the same with this.
Wow, Thanks KTE for helping me get privledges!!! I've been reading this forum for a while now and I've found it very helpful!
But I just have a broken 9600BE or something because I can't overclock worth anything. The most I've booted was 12x on the multiplier. Thats it. I dont know what I'm doing wrong. I'm back to the 1.1 bios. Didn't like the beta ones. Maybe you guys can help out! :)
Heres my rig:
MSI K9A2 Platinum 1.1 bios
Phenom 9600BE 2.3ghz (stock)
eVGA Geforce 8800gt SC
2x2gb G.skill DDR2-1000
Seagate Barracuda 7200.10 250gb
Antec Earthwatts 500W PSU
i think thats it...
:welcome: D4!!
Pretty sure everyone would agree the 1.13 Betas are by far the best Bios, although I haven't used the 1.1's, I did try 1.2 and went right back to 1.13..
What the... Tornado Sirens are going off here, better check the weather channel...
Welcome. :)Quote:
Originally Posted by d412k5t412
I would move over to the 1.13 BETA as Dave suggested, it is much better for oc and will give good performance compared to the others.
Have you modified VID/Volts with your oc's yet?
What about trying the HT ref.?
What CPU cooling are you using and what are the case ambient temps like?
What is your stock VID/Voltage?
Does AOD work for you?
When you oc, leave the RAM in Ganged DCT mode for starters. ;)
Dave, if a tornado strikes be sure to pack off your Phenom to me before that! :p:
does pcie speed lock @ 100mhz on this board?cant see any option at the bios...
That was wierd!! I'm no pup, and I've never seen weather like that in February before, it actually got pretty scary for a few minutes.. :eek:Quote:
Originally Posted by KTE
D4, the thing that helped me most was lowering CPU VID to 24 (1.25v). Stock on my machine was 28 (1.20v). Every Phenom seems to have it's own personality, but If I had a BE I would leave CPU VDDC at Auto and just lower CPU VID when needed, although I'm not sure anything under 18 (1.325v) would offer much extra...
KTE posted a table of VIDS/FIDS a few pages back (Very Helpful!)
I actually typed a more detailed message but my machine locked up...:(
I've been running these settings for a few days and I really thought it was stable... :brick:
http://i30.photobucket.com/albums/c3...206_254x10.jpg
At boot-up, yes. ;)Quote:
Originally Posted by madfaze
how about when you oveclock?!Quote:
Originally Posted by KTE
is it still locked @ 100mhz?:confused:
Yes, unless you change it manually.
are there any choices @ the bios? i cant seem to find one...:(Quote:
Originally Posted by KTE
I was gonna start a new thread, but I'm buzzed again, so I thought I would run it by you folks in here first... Your all cool people!! :D
There are 3 things that the Phenom Platform needs:
1. A better power system for the Mobo's, voltages fluctuate alot, and Phenom seems to be real sensitive to that.. I think the K9A2 keeps the MOSFETS cool enough, but those Inductors get way too hot!! (I'd consider an aftermarket option...)
2. A little more work on the BIOS, especially the option to disable the TLB Fix... And I mean totally disable it!! TLB will go down in history as the most overblown eratta in history... I can see where it would affect Servers, but on the desktop? I can't say for sure, but I don't see myself ever running Virtual Machines...
3. We need a piece of monitoring software that shows ALL the options, NB/CPU VIDS/FIDS, NB/CPU/HTT Multis, the VDDC Tweaks applied, HTT Ref./Volts, temps from all the sensors and what they apply too... I bet the guy who did CrystalCPU could whip this out in a few days.. :D
There are so many options on Phenom, #3 may very well be the most useful, at least you could send one ss that would show folks all your settings.. ;)
@ MADFAZE, I really don't think the PCI-e clock is gonna make much difference anyway, I know it didn't do anything accept cause problems on the K8, so I haven't even messed with it on K10 yet, but If you want to play with it, I'd be interested in the results... :)
No PCIe choices in the BIOS's so far madfaze. :(
PCIe speed will improve perf. in GPU benches. Up-to 140MHz I know will show gain but use an IDE drive if you move it past 120MHz and not a SATA.
Dave, I reckon this board needs some revamping. The PWM area is weak for plus 2.7G oc with Phenom IMO and then starts to need much extra cooling.
The options you're wanting to see can all except NB VID/Multi be seen in AOD you know. Even CPU VID/Vcore is shown there. But the best half of what you mention is the multi's and VIDs selectable within the tool and shown in digital form. That would be best. ;)
My Phenom reports wrong temps now, this is a new thing since the last couple of days. Idling at 2kRPM fanspeed 1.272V 2600/2400/533 (MHz), it is showing 24C idle across all cores whilst the room ambient is 25C and the heatsink ambient is 28C. I would call that a minimum real temp. of 35C of all cores since a) core IHS is always hotter than heatsink ambient b) at over 70W TDP in even idle c) core internal is always minimum 10C even hotter than the Tcase d) most parameters including voltage is increased much so imagine what the stock temperature readout would be -> sub-20C for sure. The image speaking most words =>
Attachment 71918
THUS from now on, I'm only going to report all temps +10C offset from all s/w readouts.
Yuk, watch thisQuote:
Originally Posted by KTE
http://www.abload.de/thumb/hot4594.jpg
I assume the 70° limit is for core temp.
Running at stock voltages my system ran stable for an hour at ~80° cpu-temp reading. Everything (mosfet's, nb, mem) was nearly too hot to touch.
With lower temps I always had temp spikes ~+7-10°C. With temps above those spikes in general there where no such spikes anymore.
Temperatures only become an issue once vcore is increased.
Achim, those temps look OK to me. :confused:
Can you try to run stability testing at 70C for each core, +10C what you have there and see if it holds?
(core diode readings [DTS] are the individual ones that we're concerned with, socket diode reading is the first one labeled CPU - ignore this when you have the individual core temp readings from the DTS functioning)
And yes, EVEREST devs can't read separate Phenom core temps because they only know how to access one, that's the reason you have only one temp. feedback for all the cores synchronously.
Also, you're at much lower CPUV/NBV and speeds than me, you have better cooling and lower ambients and you have higher load temps... quite impossible. It means either mine are minimum Tcore+15=Treal or yours are at least >5C too high. Cores aren't individually calibrated at a separate high Tcase, it's fixed at 70C and monitored by a separate TCC diode and feedback to those which initiates core shutdown by pulling the Vdd pin supply.
Can you try booting with a fan on the heatsink keeping a temp probe on the IHS in between them, getting into the BIOS monitoring very quickly and then disconnecting the fan to see at what probe/BIOS temperatures it shuts down? Don't let it get past 85C BIOS... :D
Just got the new mobo, gimme a few hours to get familar with it. :DQuote:
Originally Posted by KTE
I tested stability with a config whom was stable for at least 12 hours priming. I removed the extra 12" fan and ran the cpu fan at lowest possible speed, that's why my temps are so hot.
DMM with temp probe should arrive in a few days.
Oh, I see.
So you have the mighty Sapphire now? :D
KTE... press left shift+F2 with left alt+ F3 at DigiCell to unhidden settingQuote:
Originally Posted by KTE
http://img515.imageshack.us/img515/2...encysa1.th.jpg
I took my CPU to 2.6 using KTe's settings except I ran the htt @ 2000 and my memory benchmarks have dropped and lantency is poor. This bench is running back at 2.5 which was before the overclock getting much lower latency any ideas. I ran stress testing for over an hpur at 2.6 and it was pretty stable then I shut it down as was just messing around and started running the benches and noticed the poor mem performance. I also got a BSOD during the testing so I backed it and even went to stock settings and got the same poor memory performance am i missing something? Is is possible the memory controller is damaged?
jesteronyer6: latency is totally dependent on your CPU speed, NB speed and RAM speed/timings/mode + TLB boost.
So depends what you chose. I don't even get those high latencies at 2.2G CPU, 1.8G HT/NB, 400MHz 5-5-5-15 RAM with AOD button=Green, they are too high. I get those only with the TLB fix enabled BIOS's. ;)
Hence what is happening there, what are your total settings?
What latencies were you getting before?
Switch all off, close EVEREST and start AOD then click the caching button twice until it turns red. Then close it and run EVEREST again... what do you now get?
IMC doesn't get damaged if it's stable, temperatures good and voltages within a safe range. You are running 600-400MHz lower IMC than I do daily, that can't damage nothing.
tictac: it doesn't do anything. :(
I'm currently checking out the AutoXpress BIOS setting.. it has CPU Boost, RAM Boost, GPU Boost options underneath it. If you choose all 3 your system idles 32W AC above idling with them disabled (all extra's kept constant) yet the cores have 0% usage and TLB caching button is green and performance is also the green state... however the cores are idling 10-12C higher too. Max load wattage is also 5W AC higher. ;)
Dave: I hope you weren't living in the four States beaten up badly tonight - wishing safety. :)
KTE
I am using the 1.13 beta bios I didnt think it had the TLB fix?
NB = 2000
CPU = 2500
Timings = 4-4-4-15 2T
Nope, it doesn't.
As I mentioned, click the AOD button to red and then re-run and let me know what you get.
You can overclock PCI-e bus from AOD though?Quote:
Originally Posted by KTE
I will do that when I get home tonight, something is really weird with my setup as teh cores show #f00001 or somehting like that instead of a temp. And now the memory has gone south since overclocking the CPU, I wonder if the BIOS is b orked maybe a reflash will fix it because I was getting high meme scores and good latencies right up untill I took it to 2.6 and primed for an hour with the higher nb voltages of 1.3.Quote:
Originally Posted by KTE
am i the only one to see his name from D412K5t412 as DARKSTAR
Yep. I've had max AOD MHz earlier in this thread. ;)Quote:
Originally Posted by Hosser
Since when though? And in what app exactly? Have you tried cross checking multiple apps? Please explain fully with all details and testings any problem or I am clueless as to what you mean exactly.Quote:
Originally Posted by jesteronyer6
As I asked earlier, why makes you say your mem is degraded? What scores are you comparing those to? You need to troubleshoot in a fixed clear way or it's just going to confuse you. Mem has nothing to do with the multiplier overclocking you did as you didn't touch it. The only other problem that can happen is if you degrade your IMC running high volts, not 1.3VID though, which is around 0.02V higher than stock. The only MEM degradation I've heard is when you run higher than 2.2VDIMM on RAM with low VCore and even that was only found by a select number of MB MFG employers, no one else to date. But in the end, this is oc, not warrantied and anything can happen as you are always warned - only you are liable yourself for what happens. :)Quote:
And now the memory has gone south since overclocking the CPU, I wonder if the BIOS is b orked maybe a reflash will fix it because I was getting high meme scores and good latencies right up untill I took it to 2.6 and primed for an hour with the higher nb voltages of 1.3.
Are you deciphering it yourself or actually seeing that? :p:Quote:
Originally Posted by Manicdan
I see it as it's written: d412k5t412
http://img165.imageshack.us/img165/3934/tempsaq8.th.jpg
That is what I mean by the temps missing.
As far as performance I hit the red button and all the performance is back which brings the question of why is TLB fix enabled when I am using 1.13 Bios is it possible that SP1 RTM brings an automatic enabled TLB fix?
http://www.xtremesystems.org/forums/...d.php?t=176165
I think that's temporary; the core feedback looks slightly offbase. Check using EVEREST, AOD and Coretemps to see what the temps they show. TMPIN0 is the core temp too for your reference. ;)
The performance of that button has been shown in the last pages jesteronyer6. Without it performance is low on any board even without the TLB fix and even worse in Vista. With the TLB fix you would be getting far higher latencies when even using the red button in XP. Typically green is low and yellow/red are both high performance. Keeping it yellow for general running is best IMO and that's what I do.
You can check your MEM perf. by just running WinRAR multi-threaded benchmark. If it's plus 1300KB/s there is no TLB fix and if it's sub 800KB/s then their is 'the TLB fix'.
I've been over the SP1 changelog before and there is no TLB fix mentioned nor any specific update only for Phenom processors. The biggest chnages are all imporvement of performance but some will be implemented in the next few updates, such as:
And so on. ;)Quote:
Improves performance over Windows Vista’s current performance across the following scenarios:
25% faster when copying files locally on the same disk on the same machine
45% faster when copying files from a remote non-Windows Vista system to a SP1 system
50% faster when copying files from a remote SP1 system to a local SP1 system
Improves responsiveness when doing many kinds of file or media manipulations. For example, with Windows Vista today, copying files after deleting a different set of files can make the copy operation take longer than needed. In SP1, the file copy time is the same as if no files were initially deleted.
Improves the copy progress estimation when copying files within Windows Explorer to about two seconds.
Improves the time to read large images by approximately 50%.
I am trying V.POF Bios and it has a disable TLB option but it doesnt seem to be working, the good is that my DDR 800 is running at 1066 with a lil voltage bumps abd relaxed timings.
This is what your WinRAR bench should look like with no TLB fix.
http://i57.photobucket.com/albums/g2...s/5032fe8e.jpg
I know my temps may seem low, but I'm running 2x 120mm case fans, the Zerotherm nirvana blowing through towards the rear exaust fan, and 3 80mm case fans, 2 of those are assisting with gpu cooling on the Smilodon case. Not to mention it may be around 65f at the most right now in my apartment, it's cold down here right now in east texas.
Notice the crappy 12v rail output from the Raidmax PSU I have biting me in the rear. Has been the cause of some instability since installing the 3870.
And your memory should be similar to mine or faster depending on timings without the tlb patch at 2.6/2.4.
http://i57.photobucket.com/albums/g2...00x2400mem.png
when is the time you have to adjust the NB and HT voltages?what are safe number to adjust it?
nb has about the same limit on voltage as the cores as far as I've read. You can adjust the NB with the k9a2 plat bios through the custom p-states menu. I believe for 2.4ghz I've got mine set to nb fid=8, vid=24 (1.25v vid), DID=By 1.Quote:
Originally Posted by madfaze
I haven't been able to adjust the actual HT multiplier in bios yet, the setting that is supposed to for what ever reason changes the soft nb multi instead causing the ht ref to under clock.. Though technically any system based of HT3.0 should be able to safely set ht speed to 2.6ghz(ddr5.2ghz) without issue. Only thing limiting that being the nb speed, since htt can't be any higher than the nb/imc. Raising that up would probably give the cpu some of the extra bandwidth that it's starving for.
I checked out the AutoXpress BIOS options:
AutoXpress Boost Off - AutoXpress Boost On
http://img110.imageshack.us/img110/5...edaini4.th.jpg - http://img221.imageshack.us/img221/2...ailogq5.th.jpg
http://img113.imageshack.us/img113/3...bredmi5.th.jpg - http://img221.imageshack.us/img221/2...oostic8.th.jpg
Improvement with AutoXpress On:
2k1 = +2%
CB10 = -0.2%
WPrime32M = 0%
Pifast = -8.2%
I've no idea what they're doing deep under but these settings are giving better GPU perf. but lower memory perf. overall and no driver/hardware settings we can see are being changed.
Also, funnily I checked Hexus Pifast. Oc'd my GPU using AtiTool, yes GPU, and leaving everything else constant. I tried it 3 times for each run. Once the GPU was oc'd from 800/700 to 843/963 the time was consistently going from 48.7s to 46.5s. :confused:
Below score at same settings was with just GPU oc'd:
http://img98.imageshack.us/img98/921...bredmi5cu4.jpg
Now with no GPU oc a few minutes after:
http://img163.imageshack.us/img163/1...xredtlbgp9.jpg
Heck this is fully consistent too! :shrug:
BTW, a few personal updates.
My Phenom is now 1.24V 2.6G stable due to lower temps.
My RAM is running 1.98V real 5-5-5-15 tRC 11 tRFC 75ns 1066 Memtest 8hrs stable without extra cooling. :)
Mathos: Your PSU is poor but those volt readings are wrong anyway. It's the Fintek chip, it is always reading around 8V on the +12V rail, even when they're actually at 12V. Mine are 11.98-12.00 consistent measured with a DMM and software still shows 8.4V. Actual +12V line sub 11.4V and you'd have dead/damaged components pretty fast.
What kind of RAM do you have that requires 2.3V at 800 5-5-5-15? That's very high for 800 CAS5, usually you only need 2.0V for that at most.
madfaze: are you asking with Phenom or with a K8?
For K8, no NB/HT volts needs to be touched even at +2.0GHz HT.
Neither for Phenom, maybe HT volts are required when it's past 2.4G, I've not needed it yet at up-to 2.596G.
Quote:
Originally Posted by Mathos
hmmm i got amd 5200+ x2's system as you can @ my sig...does custom p-state menu available on my system?cant see any @ bios...
madfaze: your IMC/NB is locked at CPU speed and you don't have P-State options to configure. ;)
Quote:
Originally Posted by KTE
yup and who would have thought that this will be enable yet am just using x2's :D ...for now (still waiting for the b3's)
anyway regarding my inquiry KTE, when will be the time you have to adjust this NB and HT volt?...
anyway regarding my inquiry KTE, when will be the time you have to adjust this NB and HT volt?...
For Phenom?
Quote:
Originally Posted by KTE
both perhaps...:D
just wanna be safe and dont wanna fry or overvolt on somethin' inside the mobo...;)
NB/HT volts on K8 = none need to be adjusted unless going high on HT for added safety. I've done 2GHz HT with K8 on stock volts.Quote:
Originally Posted by madfaze
NB/HT/IMC volts on K10h;
NB volts don't need to be touched when oc'ing.
HT volts don't normally need to be touched till at least 2.5G or high HT ref. One bump up can usually settle 2.6G stable.
IMC volts need to be adjusted depending on the chips capability, requirement, speed and RAM speeds/timings. IME 1.25VID will be fine for <2.16G only, then a bump to 1.3VID will cruise to 2.4G fully stable. Past 2.45G starts demanding higher volts.
Quote:
Originally Posted by KTE
thanks KTE, so for now ill only adjust its vcore when OCing...:D
Check this, smart guardian reports 15° higher temps than the core readings on the sapphire. Had it on ~84° core temp for around a minute an hour later the cpu died.Quote:
Originally Posted by KTE
http://www.abload.de/thumb/250hot4g4k.jpg
Died for good?
:eek:
Attachment 71956 Attachment 71957
You can very safely say those temps are reported wrongly Achim; the RD790 chip and motherboard temp sensors is reading minimum 20C too high if your ambient is 20-24C. Those core temps readings are actually at 53C minus 30C offset as shown in the CPU diode label taken from the socket. :D
So it's 53/4C EVEREST continuous load that made your CPU dead? Mine would not boot 52C EVEREST..
Which means, those 53C readings are most likely ~63-68C IMO. By my calcs, 22C ambient, it shows 20C per core, adding minimum 12C idle at 130W TDP and you would get 50C load readings when its at 60-62C actual (approx).
Although your core temps read close to actual, they didn't do so out of internal feedback accuracy but out of another error: high BIOS offsets for all system temperatures.
Woe, are you sure it's the CPU and not your board that's dead? Tried in another board or another CPU in this board yet (your BE)?
Leave it for a a day or two or I suggest put the chip under some cold if you can. See if it fires back up with nothing connected but one RAM stick.
Smart Guardian reports ~55° in idle with fan at ~2000RPM oced to 2,62GHz.Quote:
Originally Posted by KTE
Assume it are ~30°-40° i might have ran at ~75°-85°.
I dont think that short heat test killed my cpu. I did a reboot and everything worked fine for an hour. I optimized memory timing short before and had it at ~500MHz 4-4-4-12-1T or so with 2,26V. Can be the High Voltage issue caused the cpu to die.
Mobo stops with C1 on the display, that should be a memory error. Tried different bios versions and different types of cmos clearing, as it's a know issue on the dfi mobo, but it did not fix the problem.
Tried the cpu in my other two mobos and it does not work.
Sapphire mobo works with X2 cpu. Had to use an X23800 first as the be-2400 hung at DMI pool stage.
Trying the cold thing now, but I guess i gotta rma that thing. Have no other phenom cpu but i assume the mobo has no problem.
Well, I can tell you that the readings on the Asus M3A32-MVP Deluxe are quite a bit closer to actual than the msi board. 1.3v gets me 48C load at about 2.8ghz, and I know that if it hits 60C everything freezes no matter what, so I'd estimate 10C below actual. Temps were the same on both my 9500 and 9600 BE, haven't done prime at that frequency on my regular 9600. I tried that technique of priming for a long period of time and then moving up the frequency, but I hit a wall at 2.82ghz on the BE. 2.9 needed more than 1.4v so I just quit there.
Now I know you guys have been against bumping up the NB multi on the regular phenoms cause it gives wierd readings. Well bump it up to 10x and tell me how fast your L3 cache is compared to at 9x or 8x. On my board it makes the L3 Alot faster. 13x cuts it down from 48 to 34ns according to the latency batch program with cpu-z. The 11x multi gives me 6.9ns in everest and 40ns in cpu-z. The only problem is how the cpu speed gets calculated...
HTT, NB multi is NB, CPU multi is CPU
NB Speed=9*HTT as long as NB multi is 9x or above
CPU Speed=((9*HTT)/NB)*CPU
In short it means that your cpu is going slower, meaning you need less vcore. But at the same time, your NB is working much better than at stock. Here's a simple pic of the efficiency...
http://www.geocities.com/ranger_x3/S...600-25.521.jpg
I kinda surprised myself with that run to be honest. Not quite comparable to a Core 2, but its on the road to being closer. 13x seemed to be comparable, but since the NB multi is higher than the CPU multi the cpu can barely overclock because it just keeps knocking the HTT limit down, from about 300 on this cpu.
I think that's good enough for a first post.
Yeah that's 35°C idling to 45°C idling maximum (-20 to -10). I would definitely think that's 35°C idling though based on what we've seen. So the load temps were 64°C-74°C there (-20 to -10). Again, knowing 60-65°C actual usually reboots/freezes Phenoms or doesn't POST, this would be inline even with my own findings (52C plus 10C offset) and those of Oldguy932 above.Quote:
Originally Posted by justapost
Have you ever ran above 2.2V (real) on the RAM before with this Phenom? Was your CPU voltage 1.4V?Quote:
I dont think that short heat test killed my cpu. I did a reboot and everything worked fine for an hour. I optimized memory timing short before and had it at ~500MHz 4-4-4-12-1T or so with 2,26V. Can be the High Voltage issue caused the cpu to die.
I can run all volt ranges pretty casually.
Hmm... so many days of priming and high VCore and you now have a dead CPU? :(Quote:
Mobo stops with C1 on the display, that should be a memory error. Tried different bios versions and different types of cmos clearing, as it's a know issue on the dfi mobo, but it did not fix the problem.
Tried the cpu in my other two mobos and it does not work.
Sapphire mobo works with X2 cpu. Had to use an X23800 first as the be-2400 hung at DMI pool stage.
Trying the cold thing now, but I guess i gotta rma that thing. Have no other phenom cpu but i assume the mobo has no problem.
Welcome Oldguy932 :)Quote:
Originally Posted by Oldguy932
We did many bench tests around 2 months ago, real applications rather than synthetic, a few of us with 9500/9600's and the truth was, that NB speed did not increase at all past 9x multi with them, CPU speed stayed at what it would be at 9x NB multi and so did HT speed. The readings were just being reported downlocked since you went past the setting NB can be placed at, hence why CPUZ won't validate those clocks and neither could you raise HT any higher than 9x. ;)
HT speed can be moved up to the maximum NB speed generally, up until 2.6G.
The only software which showed any gain was synthetic which bases its values on the speeds it detects, which picked up the wrong high values (maybe 2 apps). Remember, I could hit 3.1GHz NB using those methods right from the 1st week and those we soon found out to be wrong (false - even Sami realized this).
The 9600 BE run NB multi/speed high, it has unlocked NB multi (locked downwards AFAIK). I've had upto 2.596GHz on the NB with it (actual). So yeah, on those it's possible, all values stay perfectly as you set them and it really does affect perf. very well.
Looking at the above screenshot, you only mention having a 9500 and a 9600BE, so if that's a 9600 BE, I can't reconcile what AOD shows and what CPUZ shows? :confused:
Why is AOD showing 2.5G when CPUZ shows 3G? Have you stopped SMBUS and PCI detection in CPUZ so it's now picking up wrong values? Have you clocked one core to 14x 3G while the rest are at 11.5x 2.5G?
That's a 3.059GHz SPi 1M run there, AOD is well known to report downclocked values when they're not actually downlocked but the CPU speed will be as CPUZ reports it, NB speed will be what AOD reports it and so will HT. I can't make out the multi but switch on the PCI/SMBUS detection in CPUZ and validate it and we could tell what the various speeds are pretty easily. ;)
Just... I'm not trying to be a :banana::banana::banana::banana: man, but it sounds like you pretty much abused that chip.
Won't you feel bad about RMA'ing it? I know I would.....
Maybe it's just my nature... :rolleyes:
I'm starting to think the BE's might actually be "Cherry Picked" for their NB speeds rather than Core Speeds....
I've tried all sorts of combinations and the NB seems to get squirley around 2100Mhz. My chip is not a BE though, so I'm limited to 1.25v...
I did manage to squeeze a little bit more out of it, It hasn't crashed for a couple days... Seems stable.. :D
http://i30.photobucket.com/albums/c3...10x254_AOD.jpg
For the dead chip; well any oc is totally out of spec and anything can happen after that, MFG didn't guarantee it, we take risks and it's our fault what happens. Hardly any user wants to accept their liability though and the easiest way is to always just get a new chip free so that's what they do. Problem is, if AMD inspect that chip, they can tell if it was oc'd just looking at the voltage paths.
Dave, as I said much earlier, IMO the 9600BE are the 9700s and 9900s unlocked. The NB speed on these were originally supposed to be 2000MHz. Thus stock volts you can still get 2GHz NB. However most Phenoms I've seen incl. 9500/9600 can do 2.14G NB at 1.25VID. With a voltage bump, they do 2.4G and more voltage gets them 2.6G. Haven't been past that to date and neither have I seen more. I expect all of them to do 2.4G with voltage but without voltage the limits are the same on all I've seen yet.
However, 100% stable, 2G seems to be the limit for 1.25VID NB.
Yeah KTE, I really think I have this chip pretty well tweaked out, hey, it was 6 weeks of fun! :D
The sad thing is, I'm seriously thinking about spending some of my Tax Refund on a BE, and saving this 9600 for the HTPC and a 780G board... I'm a computer Junky man... :yepp:
I do worry about this mobo's PWM though. I'm going to MicroCenter this weekend and buying some heatsinks for those Inductors. It's kinda hard to figure out where the blame lays with Phenom performance...
BTW, thanks for your concern about the tornado's... I live in Cincinnati, it was the same line of storms, but the devistating stuff was well south of here...
Quote:
Originally Posted by Daveburt714
Must say I still feel been tricked by them with the tlb-fix impact. As I bought him the problem was known and public but the scale of speed decrease was made public later.Quote:
Originally Posted by KTE
Yeah i abused that chip but at the time the chips died i did not run so out of spec parameters. 2.62GHz/2GHz at 1,375V/1,3V did not make a chip die from all i have read.
It was the first day I could apply more than 2,25V to the ram and ram timings /voltages was what i was playing with as the chip died.
To me it looks like the chips died from too much voltage for the ram, whom ran only 0,05V above what they are rated for.
So i don't feel bad trying to rma that proc, they still can inspect the chip and decline my request. If they find out it was that memory issue killed my chip i guess they'l rma him.
Yeah Achim, I'd also like to see if and how it was the DRAM volts that killed the chip priming. I mean 2.25V is not a lot at all.
Three things where different that day.Quote:
Originally Posted by KTE
1. I did that temp torture.
2. Applied more than 2,2V to the ram
3. Ran at 2,6GHz (max before 2,55GHz on the M2A-VM)
AMD will indeed detect that i ran at high voltages. I don't know how close they inspect those chips they get for rma and if they can detect those memory caused failures. I assume they'l decline the request just because of the voltages and don't look any further, so just in case i ordered an 9600be. :rolleyes:
EDIT: these memory issues seem to have gone now, have not heard of chips dying in the last time. But mine was from an very early batch can be only thoose early ones where affected.
Which memory issues have gone now Achim?
I mean phenoms dying cuz of too high memory voltage. Last thing i heard has that an microcode update should fix this issue.Quote:
Originally Posted by KTE
You remember bingo13, he said he had a few dying cpu's whom had an early batch version. The ones he got back from rma where from an later batch and worked flawless.
Yeah his 0743 died but 0744 didn't but I had a 0743 at the same time too and ran 2.2V-2.9V on for a long while and nothing happened. Far too many others did, no one but one or two brand MFG workers reported these dying in moments. No common user has reported such problems to date and most run 2.2-2.4V every day.
The problems was also when they ran low CPU volts and plus 2.2V on RAM adjacently and upping the CPU voltage would offset this. You had 1.4V n CPU, so this is why it can't be and you only had it for a very short while.
Your case is very different to theirs TBH. They had done nothing but plus 2.2V RAM and killed their new chip in moments as they said, but you've had yours for long and ran it at high temps/volts/speeds above stock, especially the temps many times were high (I would take those as +60C). That means it's almost impossible for us to rule out how and why that no-boot occurred. :(
No, that was done with a regular 9600. My mobo actually locks the speed of the nb at 9*htt if I set the nb multi higher than 9. I realized that the BE was completely unlocked after I bought it, and it saddened me even more when it only hit 235htt max and it needed the 8x nb multi just to do it.
The point of increasing the nb multi isn't to make the nb faster, its to make the L3 cache run faster. Try it again for the heck of it, and I'll get some screens of everest and the cpu-z latency thing showing the difference.
Wait a minute... you can run NB at 8x with 9600 BE? Are you sure you're not getting them mixed up?Quote:
Originally Posted by Oldguy932
The 9500/2x9600 I had all run 9x NB multi max but are downward multi unlocked.
The 2x9600BE I had both are downward multi locked but upward unlocked.
Same MB, the same BIOS and the same as I've seen with many other users so far.
The 9500/9600 show high NB multi only in CPUZ (false). They never change above 9x actual.
They then show downclocked CPU/RAM speed in AOD/EVEREST but not in CPUZ.
CPUZ will not verify those speeds because they are all over and not true.
Same reason why you can't change HT to higher than 9x on any MB.
The actual CPU/RAM/HT speeds are how CPUZ shows it, but the NB speeds are as AOD shows them and not as CPUZ. ;)
We've been through this a few months back so I can recognize the speeds clearly. That's why I know your 1M run was at 3GHz rather than 2.5GHz as its a known AOD bug. Like this: http://img219.imageshack.us/img219/7721/jsjssk9.png
False NB speed, correct everything else.
CPUZ latency is synthetic and shows faster latencies based off CPUZ readings, nothing else will show any gains with 9500/9600 NB multi above 9x. Run a real-life benchmark and you'll see no change in NB speeds above 9x multi for Phenom 9500/9600 but you'll see big changes for 9600BE above 9x multi. Because for 9500/9600, they're not changing but they are for 9600BE.Quote:
The point of increasing the nb multi isn't to make the nb faster, its to make the L3 cache run faster. Try it again for the heck of it, and I'll get some screens of everest and the cpu-z latency thing showing the difference.
Already done many tests many pages back in this and a few other threads. ;)
The last time I tried NB oc was with the BE:
http://www.xtremesystems.org/forums/...&postcount=958
http://www.xtremesystems.org/forums/...&postcount=961
http://www.xtremesystems.org/forums/...&postcount=964
Do some real application tests and check the results. Higher NB will be better results. Easy way to check is, run EVEREST mem/cache bandwidth and it'll show a high NB compared to a low one easily.
Max is 9x NB on Phenom 9500/9600, that's why you can't move HT above 9x on any MB with those CPUs. And max you'll have with stock NB volts is lower than what you get with the 9600 BE with added voltage/multi. Phenoms that can have plus 9x NB multi can run higher HT multi easily, like 9600BE. If you have a 9600BE, try it.
My 9600BE boots 250HT ref. max at 9x NB multi.
9500 did 272HT ref. max at 6x NB multi.
It where the 9600's dying immediately the 9500's required more time. Can be that issue is somehow related to the 790FX chipset and that's why I had no problems with 2.2-2.25V on the M3A.Quote:
Originally Posted by KTE
The chip is rated for max 1,5V and 70°C. It's really odd that he died at ~50° and 1,375V. But nevermind i joined the 9600BE-bingo, just receiped the confirmation that the 9600BE i ordered few hours ago is already on his way. With a little luck i'm on k10 again tomorrow. :cool:
A DMM with a temp probe just arrived. If i put the probe on the BE2400's IHS I measure ~27°C. Smart Guardian reports 42° C. That's only a 15° difference whould mean my phenom ran at 85°C minimum when SG reported 100°C.
Must say I expected prime to fail before the cpu dies if that high temps where the cause.
Once we had an air con problem on a hot summer in our server room.
CPU temps where above 85° every now and than case temps above 60° where also no rarity and the servers powered off on a daily base. A few HD's died but no cpu or other component.
Achim: if you measure IHS temp, you'll have to modify the IHS and install HSF on top sitting with a good flush contact and the probe underneath at the geometric center of the chip within the IHS. So the temps will be higher than taking any side measurements. X2 works differently to K10h since the core DTS can give different temperature feedbacks and the BIOS interprets them differently.
SmartGuardian is +20C wrong pretty easily looking at the various values. The next time you get the Phenom, open HWMonitor as well to checkup the various readings. Plus your CPU temp in EVEREST only showed ~53C actual around -10C with M3A readings and what every other Phenom gets. Every Phenom I've seen so far gets far lower temps than those at similar volts/speeds.
Measure the RD790 temp when you get Phenom, that was giving it a 52C reading. From personal experience I know RD790 is a 10W TDP chip and never reaches even 40C at <30C ambient, so those are near 32C actual temps it was reading as 52C, a +20C offset.
I don't think the temps/speeds killed the CPU IMHO, but I'm not sure if feeding the CPU/RAM high volts and priming it did. What's the max CPU VID and voltage you've ever fed it?
Kinda strange why it doesn't boot. :shrug:
BTW, your sig reads you have a Phenom 9500 running a Phenom 9600 multi. :D
That's why I said minimal. :D If you look at my 100°C screeny you see that smart guardian seems to read from what everest reports as aux and seems to be an externel sensor in or below the socket so the reading should be cpu independant.Quote:
Originally Posted by KTE
Must use somthing different than speedfan (kills pci functionality on dfi mobo) hwmon will be a good replacement.Quote:
Originally Posted by KTE
That cpu temp on the sapphire mobo is indeed strange. The mobo allows to specify an offset for temp reading. I left it at the default 0. Never checked that offset in the cpu registers on the m3a. :(Quote:
Originally Posted by KTE
He died as mysterious as he lived. :shakes:Quote:
Originally Posted by KTE
Ever? 1,525V on the M2A-VM in the first week, later never more than 1,475V on the M2A-VM (max stable voltge) and not more than 1,425V (few minutes) on the sapphire.Quote:
Originally Posted by KTE
A few days before I just had verified my oc results on the m2a-vm and could not find any signs of long term degradation.
Ups, fixed don't have a 3GHz phenom running.Quote:
Originally Posted by KTE
I'm just wondering on this, but has anyone noticed an effect on their max htt, max nb speed, or max cpu speed from using chilled water or phase on their cpu? I remember reading about macci doing some dice runs, but does that mean I won't have a cold bug? I have a vapochill, I just need to order the am2 mount for it and I can do some testing with it. If no one knows...I guess I can be the guinea pig.
I might... might still throw a Vapochill on it lying around. It hasn't been used since around mid 2006. I've been considering for some time but I did a few basic cold runs as an initial checkup and my last 9500 and 9600BE still did not boot 20MHz more than air at -30C/-20C/-10C/0C/5C/10C/15C (IHS), frustrated me after all the effort, so I haven't bothered again. AM2 mounts here were impossible to find for the VC, I have to order from more than 7000 miles away, wait 4 weeks and the cost was the same as buying a good WC setup so I withheld -> unless someone can show me some very healthy gains.
Water usually gains quite a bit of MHz, especially stability. Most guys can validate and small bench 3.1-2.95GHz with water and get 2.7-2.9G fully stable.
I'd like to see any cold runs by anyone even Sami if they could get 10MHz more than air/water with Phenom. :yepp:
Hehehe :DQuote:
Originally Posted by justapost
Hmmm I don't tend to run plus 1.35V on mine. I'm very weary and will drop the temps to 0-10C ambients before I run above that and throw 3 more plus 100CFM fans around it.Quote:
Originally Posted by justapost
If you could still get the same as you had before on the chip a few days back, then I don't understand how it just blanked out.
Does anyone have the factory version one K9A2 Plat bios? I beleive its version 1.1? Does the factory bios NOT have the TLB fix btw?
I just ordered the AM2 mount for my vapo, should be here by next wednesday.
im still using the 1.1 bios and i think anything after 1.13 has the fix
The 1.1 bios is the factory bios, correct? Anyone have a link to download the 1.1 bios?Quote:
Originally Posted by Manicdan
1.0 is the factory bios, there is still available @ the msi global site ;)Quote:
Originally Posted by batmang
I'm dumb lol. ThanksQuote:
Originally Posted by madfaze
Sorry for not responding fast KTE. Been busy with school. Im not able to overclock at all the FSB. I used the picture in the post for what the numbers should be in that one menu (i forget, kinda tired lol). I tried my best to work out the perfect voltage and multiplier. I dont know what to do, I crashed on everything. This 113 bios is alot better, becuase I've noticed better stability. But I still end up crashing. Don't know what to do. Are there any bios' that support DDR1066 yet? Good ones, atleast. Thanks!
Lol, with 1,35V I could reach 214x11 on the M2A-VM same as max at stock on the M3A. Everyday oc was 220x11 at 1,4V without extra fans but not in a case.Quote:
Originally Posted by KTE
Odd isn't it. I mean ok it's a fact that oc can kill the chip but i don't see an obvious cause in this case.Quote:
Originally Posted by KTE
Well, I put my regular 9600 back in a few nights ago. Right now its priming at 11.5x248 @ only 1.3v. And here's a pic of my extreme wPrime times...
http://hwbot.org/signature.img?iid=84927&thumb=false
The NB multi was at 10x, so the actual speed is what wPrime has shown, I took the ss before I got the new version of cpu-z that actually works with my mobo. I really can't wait to get the vapo running now...
Edit: Make that 250x11.5=2875, same volts.
1.0 and 1.1. Everything after P0C has the fix, on the latest ones you can disable the fix but you still lose perf. when disabled.Quote:
Originally Posted by batmang
Yeah, the latest ones run all stock DRAM MHz (P0F, P0H) but they don't allow most oc options (AM2+ P-States). I'm waiting for a good BIOS now with friendlier working options andQuote:
Originally Posted by d412k5t412
I'm still thinking this through but best would be if I had the chip to experiment with. :DQuote:
Originally Posted by justapost
Oldguy932: The pic/bench you posted is at 266x11.5 3.059GHz and your NB is at 266x9 2.394GHz like I've said before which most of us already know about by now. No 10x NB multi on Phenom 9500/9600 only on 9600BE. If air gets you 3.059G then 3.5G should be in reach on vapo, maybe even 4G. Await the results.
oldguy.. test your nbspeed with cpuz latency test. see if you gain anything with that higher nbspeed multiplier. ok!
I tried to explain this before. On my board, the asus, I can use any NB multi from 4x to 18x. But if you do use one above 9x, for example here's the comparison...
9x
9*200=1800mhz nb, 11.5*200=2300mhz cpu
10x
10*180=1800mhz nb, 11.5*180=2070mhz cpu
This is why 2753 shows up in the bench.
10x nb multi
9*266=2394 --> 2394/10=239.4 --> 239.4*11.5=2753.1mhz cpu
To get to use the higher nb speeds, you have to actually oc to get back to stock speeds. The nb is also locked to a maximum of 9*htt on the regular phenoms. I would get back to testing the latencies, but I'm finding the max actual overclock on this cpu, and 266 is my max bootable with 9x, 10x, and 11x nb multis, 260 is rock stable with 10x and 11x, I haven't gotten there with the regular nb multis cause I'm about to start testing 252x11.5. But if you guys are right and I was running it at 3.06ghz, then dang I got a good chip...
why dont you go straight to 18x nb multi. see if it post?
I never got anything over 13x to boot reliably. 14x worked a few times, but I never got it to even boot to windows. 15x worked once but then it restarted and never booted there again. The perfect phenom would have an unlocked cpu multi but still have the nb speed locked where it is on the regular chips. The records for amd cpu's would be broken so fast it wouldn't be funny. Here's why...
NB 10x, HTT 266, CPU 11.5x
CPU Speed=2753mhz
Super-Pi 1m was 25.472 (didn't take ss cause the next spot on hwbot is 24.8)
NB 11x, HTT 266, CPU 11.5x
CPU Speed=2502mhz
Super-Pi 1m was 25.521
The times are within .05 of each other, but the cpu speed of the faster one has 250mhz over the slower. If the one with the higher NB multi was able to run at the faster speed, it would most surely win. This is where the unlocked cpu multi would come in handy. First you find the max cpu overclock, then you try and keep getting that speed with the higher nb multis. I know its been proven that a higher nb speed will beat a cpu same speed with a slower one, but what I'm doing just makes the speed difference alot more noticable.
Yep, we used to call that scenario "downclock" before.
Leave you NB at 9x and you'll get 3.059GHz with the same volts. ;)
Your NB will still be highest I've seen yet on 9500/9600 incl. your chip: 3.059G and 2.394G
If you want to check NB speed, just run Sandra memory bandwidth and EVEREST cache/memory bandwidth so we can verify. As I've said, I've been through this 3 months back. Sami and I both know the approx. mem/cache scores possible through the range of frequencies. I know up to 2.596G NB and 2.83G CPU 1252 4-5-5-15 RAM and Sami probably knows up to at least 3.1G CPU and 2.6G NB. I don't think NB goes much higher than 2.6G on Phenoms on air/wc, I know HT won't.
You can do some RightMark Multi-Threaded Memory Tests and they'll show NB speeds clearly. Big difference between one multi change.
As for 1M: 3.059GHz can easily get 23s and below. Your 1M efficiency is quite bad because you have low NB/RAM speeds but high CPU speed.
HT ref. doesn't drop below 200MHz on 9500/9600, only multi can drop.
Here's what I remember getting last time I was running benches
Everest Cache and Memory
L1: 1.0ns
L2: 3.0ns
L3: 6.5ns
Memory: 57.4ns
I need to get some better memory, but thats not as important to me right now. The memory was running 4-4-3-5-2T @ 707mhz. It does up to around 860 at those timings.
if you cant boot with 18x nb speed that mean nbspeed is actually working on your board. actual with non-be phenom max nb multi is 9x. the nb speed multi will still remain at 9x eventhough you set it higher. that mean it will bootup even we set it to 18x. but yours wont. got it?
And I probably won't be able to hit 3.5ghz, my htt maxed at 300 when I tested it on this cpu the other day. That would only give me 3450 at most, which would be amazing for a phenom, but even just 2.9 at 1.3v is giving me 50-51C load with small fft's, meaning around 56-57C true max.
Well, I guess I'm one of the few that can play with the nb multi. That and anyone else with the 0801 bios for my board.
This is Phenom 9500 (max nb multi = 9x) with 5.6GHz NB speed... it boot up ... Biostar TA770.... i guess it is not working.. because if it work it wont post at 5.6GHz NB speed....Quote:
Originally Posted by tictac
http://www.lejabeach.com/pics4/TF770A2+020908-2.JPG
but benchmark show improvement over slower NB speed.... i am still wondering why... :confused:
What's it showing for your cpu speed though?
Edit: I just started trying 267*11.5. @1.3v it failed prime on the first core in 6 seconds, @1.325v it failed in 55s, and @ 1.35v the last two cores don't even start. I just realized I had processor to nb voltage left on auto, set it to 1.3 and I'm gonna see what happens next. Oh and if this setting doesn't work I'll at least get a screenie of 3ghz stable with 1.3v.