so just curious whats the fasted 1M time so far? I have a x2 6400+ that can do a 22.75 and wondering if a phenom will ever beat it.
so just curious whats the fasted 1M time so far? I have a x2 6400+ that can do a 22.75 and wondering if a phenom will ever beat it.
Time depends on clock speeds most, simple as that. If you want to see 1M times, then Wolfdale is the way because AMD is never been fast at it.
Throw a 2.8GHz clock speed and get your best 1M and post it back.![]()
BIOS P0F: v.bad for oc
*Problems:
Only boots 1066 at 1.8V - runs nothing less than 1:2.66 divider
NO CPU DID/FID/VID options anymore
NO CPU NB voltage options
NO NB FID/DID/VID options anymore
RAM voltages still increment in 0.1V (In BIOS)
CPU voltages still increment in 0.05V
HT is set to 1.225V on stock bootup when its supposed to be 1.2V
Low HT ref. limit.
AOD oc'ing still freezes the system yet (even when downclocking from 2350->2300)
Higher than 1.26 VID makes system reboot/unstable at stock frequency, higher or lower.
What the heck MSI!
*Good additions:
At least boots 1066 and CAS3.
TLB patch is user choice in BIOS
Allows CPU/HT multi choosable in decimal figures
Shows current CPU/RAM speed and DCT mode
RAM voltages go up in 0.05V in AOD now
CPU voltages go up in one lower increments between 1.24V-1.5V
*We WANT:
All the above *problems fixed please
Boots 1.8V, why not 1.9/2.0V to allow more RAM compatibility?
RAM voltages to go up in 0.025V
Lower CPU voltage increment (not ~0.05V but 0.015V)
Lower tRP tRTC tRAS options
I've not had a Phenom boot since 14hrs now since flashing that BIOS and setting 200 13.5x (2700) @ 1.45V...
How many of you notice that your Phenom (like mine) has a problem with high VCore/VID and high multi specifically?![]()
Meaning any of these at low CPU speed can cause a crash/no boot/freeze.
Last edited by KTE; 01-17-2008 at 02:33 PM.
yep I have noticed that also with higher multi for sure.
I seem to have another issue when I set 2.3 for ram it changes in HWmonitor. when I set 2.2 it changes to that also but when I set 2.1 it doesn't change I haven't tried lower 2.05 or 2.0 but I thinking that I might be stuck at a 2.2vddim as my lowest allowable.
I would for sure like to see a more wide spread voltage pattern as I dont like changing ram with .1 increments.
Good afternoon Tye how are you feeling since the accident?,Hey what kind of ram are you running to get cas3?
SuperMicro X8SAX
Xeon 5620
12GB - Crucial ECC DDR3 1333
Intel 520 180GB Cherryville
Areca 1231ML ~ 2~ 250GB Seagate ES.2 ~ Raid 0 ~ 4~ Hitachi 5K3000 2TB ~ Raid 6 ~
I'm good Bro, Crucial RAM sticks do 4-4-4-4 600 easy at 2.2V on P35, so 2.2V 1066 boots 3-5-5-15. I mean 1.8V 1066 5-5-5-15 boots perfect.
ATM this BIOS doesn't allow over 550 on RAM speed, it just reboots. And it seems RAM can only boot 2.1V and its setting bootup stock speed as oc'd (below).
Look at this for one core fluctuations![]()
This is what I said messes oc up badly.
Well I played with vmware and smp clients last night still gonna play around some today but the adapter for my better cooling should be here soon and hopefully there after I will be able to come back around and post a better overclock with the system
untill then fold and clock on!!!
Yeah, quick update part 5000:![]()
*It 'aint the AMD CPU which is freezing. It's something other related to either MB/RD790/PLL/AOD. Because my chip has now started going whacko and boots stock (defaults) at 1.184V 2369MHz and 1.8V DIMMs. So when I try to underlock it to 2.3G after bootup, it freezes at 2.32G, 2.34, 2.35G.
This is why I said it's all just so flocked up and convoluted!!
*Also, I tried some cold at work v.quickly and whilst it booted -15C, the oc limit was still the same and now my temp sensors inside the cores have stopped working -> stuck at 0C. Even the internal tjunction sense is reading a little too low, usually it was at 33C idle in this environment 1.192V and now its at 23C, which is ambient. So its incorrect.
*And whilst my chip never booted 1.184V (reboot loops) I thought I'd get into Windows and P95 test and bench 1.184V idle/1.176V load 2.3G to see what happens. Well whadya know, it runs it perfectly fine, I gamed it after that:
This just makes no sense![]()
So now I'm curious to know why the hell it won't boot with 1.184V.
*BIOS P0F even wth the patch disabled through the BIOS still degrades perf by a long margin. 1880KB/s compression to 666KB/s.
*People talk about "IPC" a lot but I don't know if they're unaware or not understanding enough but IPC is never constant and differs with every sort of software (instructions) used because some instructions are more complex and do more useful work than other simple ones, thus most software never utilizes max IPC capability of a core even for 1% of the runtime. Thus some software only utilize 0.8 i/c while others can get 2 i/c out of the same core. Those utilization near the maximum of the architectural limit show better perf. quite obviously and higher CPU power usage.
For instance. I ran benches and looked at IPC and L1/L2 accesses. Any benchmark/software which accesses L1 greatly with high IPC=higher power draw. As an example, Super Pi 32M only used maximum IPC of 0.8 i/c whilst EVEREST FPU Julia used 2.5 i/c and Prime95 utilized 1.7 i/c fixed (hence the power -> v.high each core utilization). Any software which can utilize near the maximum IPC limit with complex instructions will in effect perform far better than if it used simple instructions with low IPC usage. You can see P95 above and EVEREST FPU Julia here:
*Another problem I noticed whilst debugging SuperPi on this platform. There's an unnecessary delay hence the times are slower than they should be (which doesn't happen on X2/P4/C2). No idea about others but this is the case with mine. Writes to HD by SuperPi are being denied which is adding latency/wasting clock cycles because until that data is written the calculation doesn't move on. Out of 37,xxx events a minimum of 500 (v.reserved there) were write failures and another 500 were just rewrite attempts. Why? The reason given was "too fast I/O". See below for what I mean:
More confusion, more problems.
Here's some Pi 32M action for you to compete with.![]()
1.5minute compared to 32minutes for SPi mod 1.5, talk about inefficiency.
![]()
KTE very nice find, driver issue? somesort of bug? im confused now![]()
A64 2800@ 9x279 # Abit kv8pro 3rd EYE (vtt and vmem modded) # 2x256 mb TwinMos memory( with old winbond ch-5 max:240@3.5v) # 2x256mb KHX 3000 memory (with old winbond bh-5 max:270@3.7v)
9600 Pro LE with vgpu mod
Good Job!
No higher with cold, it was a 10 minute test at work mainly to check for CB. In fact not even a hair over 2.5G this time. Dropping the chip off in 2 hours and starting my Q6600 G0 up instead.
As for temps, I have no idea. See: http://www.xtremesystems.org/forums/...9&postcount=19
Temp. sensors work fine now, I rested it for a few hours and restarted it briefly at work 10 minutes ago. Back to normal it seems, idling 33C.
Spi problem occurs because? IDK, it shouldn't happen, it slows any short bench down.
Don't have a RAMdisk Achim.
Gained ~50MHz here lowering the load temps from 64° to ~40°. Have you tried it with a lower vddc?
EDIT: Saw you did in your other post
EDIT2: Have you tried the latest coretemp should handle temps in the range -49° - 206° maybe it's an everest issue.
I mean a software based ram drive. Might fix the too-fast io issue. Link.
BTW: Your mobo also has an promise sata controller. Have you benched your hd on that controller?
Last edited by justapost; 01-18-2008 at 07:54 AM.
This is one thing I have to try yet, I've been planning to but not found the time. I'll try it later today to see if different volts/VIDs gets different oc.
I have it, just waiting to get a new Phenom now. Shouldn't be too long. Thanks for the link too.I mean a software based ram drive. Might fix the too-fast io issue.
Those above tests were with the Promise controller in IDE mode (AHCI causes BSOD). I don't remember the perf. with SB600 and I can't find any saved pics of it either. I'll give it a try soon.BTW: Your mobo also has an promise sata controller. Have you benched your hd on that controller?
EDIT: thanks for the CoreTemps headsup. I stopped using it because the previous versions were so errorsome but the new version works fine.
![]()
Last edited by KTE; 01-18-2008 at 08:14 AM.
Lol, just tried it here and gained 3s in sp1m at stock, ~1s in xs sp1m.
EDIT: Had CnQ enabled, without it this difference is marginal ~0,1s. Do you know if super pi counts while disc operations?
Make shure you set Start=1 for the FastFat Service in the registy (HKLM\System\CurrectControlSet\services\FastFat).
Installed system with the drivers integrated and sata in ahci mode. It worked and I can boot into windows but it freezes after ~1 minute. Did not yet look into it again, as ide mode worked.
NP
Last edited by justapost; 01-18-2008 at 08:51 AM.
@KTE ...& Gang.....Hey, guys do any of you know what these settings are on the new architecture and if they are related to Phenom or new chips? I know you guys have different board but perhaps you may have insight asto what these HT Settings pertain too and what they relate to. I know what the First 2 settings are for obviously but what of the remaining four?
SuperMicro X8SAX
Xeon 5620
12GB - Crucial ECC DDR3 1333
Intel 520 180GB Cherryville
Areca 1231ML ~ 2~ 250GB Seagate ES.2 ~ Raid 0 ~ 4~ Hitachi 5K3000 2TB ~ Raid 6 ~
I have no Idea the flowcontrol I think is network related.
2xlclk has to have something to do with some kinda timing IMO
google doesn't offer much support![]()
You can read the specs at www.hypertransport.org.
Sorta like 120 pages, so I did not yet read it.
Thanks brother I'll do that![]()
SuperMicro X8SAX
Xeon 5620
12GB - Crucial ECC DDR3 1333
Intel 520 180GB Cherryville
Areca 1231ML ~ 2~ 250GB Seagate ES.2 ~ Raid 0 ~ 4~ Hitachi 5K3000 2TB ~ Raid 6 ~
GL 120 pages is worse then this thread
running 2 vmware ubuntu clients with smp client on each and graphical F@H to take up the left over 3-8 % gonna see what PPD I can crunch.
Got it at 10x250 ATM for stability.
I can't find the quote now, But your gonna leave us for the Dark Side KTE? (Q6600)....![]()
Have Fun!! D*mn, I wish I could get free stuff to play with... Thanks for all your help with Phenom though man!! I'm pretty sure you'll be back...
Phenom is just too much fun.....![]()
AMD FX-8350 (1237 PGN) | Asus Crosshair V Formula (bios 1703) | G.Skill 2133 CL9 @ 2230 9-11-10 | Sapphire HD 6870 | Samsung 830 128Gb SSD / 2 WD 1Tb Black SATA3 storage | Corsair TX750 PSU
Watercooled ST 120.3 & TC 120.1 / MCP35X XSPC Top / Apogee HD Block | WIN7 64 Bit HP | Corsair 800D Obsidian Case
First Computer: Commodore Vic 20 (circa 1981).
Brother, didn't I PM details on those settings, or were they different?![]()
New Phenom BE coming soon, dropped off old one a day ago... for now, I'm running a Q6600 G0: http://valid.x86-secret.com/show_oc.php?id=299471
Good thing is, this board runs 1066 PL4 stock volts.
One of my friends pulled my arm quite unexpectedly and with force whilst I was carrying the MSI RD790 down 6 blocks of stairs from my flat and it flew down a flight of concere stairs (naked). I don't know if it's surivived.![]()
TBH, I preferred the GFX and the temps on the Phenom platform but I prefer the consistency, ease and overclock performance on the C2Q one. It's at 3GHz now with 1.28V passing 12hr load testing with ease.![]()
Also, I don't really see it as some onliners seem to. To me, they're just two companies. I choose and use what I want. At home I use a laptop nearly all the time anyway, and at the work places I use both alternatingly. They both cost different and Phenoms are selling like hot cakes here just because of the low platform costs. OEM is where all the majority desktop sales take place and those customers don't oc, they look at cost before anything. I'll still keep up with the news here since I'll have another BE very soon.![]()
BTW, for the old Phenom 9600 BE...
Max 24/7 stable was (stock volts/VID): http://valid.x86-secret.com/show_oc.php?id=299789
Max verified was: http://valid.x86-secret.com/show_oc.php?id=299791
![]()
Nice and I got my adapter today![]()
gonna be putting some better cooling on this thing in about 30 mins when this SMP finishes.....
Bookmarks