I missed it. Didn't know FSX could reach 100% on a quad. Nice to see >2 cores used with significant load to each.
Printable View
Yeah many times, easily.
But 626 is tops stable, which is 150MHz too low for the RAM.
It's fine for long now, board BIOSes are what make it react crap. ;)
Which OS is that in?
Something majorly wrong there bud, your scores are very low for even 2.6GHz.
3563 CPU is what I get with a 9500 at 2.42GHz: http://img73.imageshack.us/img73/453/2k62420bo4.png
:confused:
Very far from higher MHz perf. 2.68G hits 4k.
2990MHz hits around 4400: http://img233.imageshack.us/img233/8956/2k62990sb3.png
The difference is probably due to the resolution I did the test at. I stated it so there'd be no mistake about directly comparing my scores to "normal" ones. The monitor on that machine maxes at 1024x768 while 3DM defaults to 1280x1024. Because of that, I had to run at a lower, non-standard resolution.
Also keep in mind that 3DMark doesn't serve very well as a CPU benchmark. Other workloads will benefit more or less from the multiclocked config--your mileage will vary. Besides, if the extra speed is free and you can see it manifest, why not take advantage of it? :)
We know its not exactly a good CPU bench but for the intended purpose here, 2k6 can show the CPU speed very well actually as it scales with it. Thats how we can compare it to one another ;)
I'll check out the lower res results and see what it gives, if it has any quirks.
Oh, I forgot to answer the question of what OS I use: Windows Server 2008 x64 Enterprise
dude you use Vista, Server 2008 and Vista uses the same codebase, heck Vista SP1 kernal = Windows Server 2008 RTM kernal
Windows Server 2008 with workstation pack = vista basicly, so Windows Server 2008 is stripped vista
anyway, Vista and Server 2008 will have lower 3dmark score vs xp and xp x64
server os sounds good... would it be worth me switching from my os?? ive got vista home premium...
server 2008 = vista
you can use the workstation pack to transform it to vista :ROTF:
did someone get a nice 3dmark vantage score?
my default is http://service.futuremark.com/home.a...&resultType=19
looks like the new 3dmark likes phenom alot :D
You don't need to install any sort of workstation pack. Just re-enable the theme and sound services and you've got a working desktop system.
Vantage likes MCP78 more than 780G though ;)
Particle:
i see you're running windows server 2008 and you seem to like it a lot. i've been running the 64bit version for weeks now and i can't imagine going back to vista. of course, i turned it into a vista look alike workstation. i even did some hacks such as enable superfetch and such. do you know how to get readyboost to work? so far, i like ws 2008 a lot. i like it so much, i even put the 32bit version on my acer laptop which is a celerom M170 or something. it runs well on my laptop too.
Good catch, dng. I need to re-enable superfetch myself. But yes, I really do enjoy it. I used Vista Business x64 for a long time and found myself going back to Server 2003 x64. I ran that for a long while, but '03 kept eating the filesystem on my RAID-5. The second time that happened, the RC for Server 08 was available so I tried it. All I can say is that I've been hooked ever since then and can't imagine going back to XP64, Vista, or Server 2003. I've tried them all.
^ As it should be, thanks for the update :)
Odd how one driver can totally twist things the opposite way around.
Wow, Phenom is pretty sensitive for subtimings!
I thought I could set a few subtimings right away since I had these with the X2. But I went gaming and got every hour a freeze, got pissed about it and thought it was a dieing NB. So lowered NB multi, ran Prime Blend. Error straight away. Added Vnb and Vcore, error.
Added a lillte bit of Vdimm, still error. Removed the subtimings from Memset and it's still going... Wicked lol.
These timings are crap though in the way off resulting in instability. Set too strong tCL, tRAS etc is very obvious. Freeze with memset and no boot via BIOS. Same for things as MAL/MRL. But some timings just go do like a lot of things and then suddenly so their ugly face and crash your system...
Now I 'just' got to find out what timings caused it:shrug:.
Or do more investigation, now it crashed after 1h and 10 minutes. Maybe NB or DDR1066 related...
Thanks for the article Tony! It did straighten out a couple of sticking points for me. I'll certainly try lowering the HT Link to increase the OC.
A quick question for anyone - what is the Mem VDDQ in AOD? It doesn't match the BIOS setting for vDIMM but doesn't seem to be effecting the (DDR2-800) RAM OC in any way. :shrug:
Thought I'd chime in here with my Phenom results so far - 3010 (215x14) ~ 1.34v; NB running 10X @ 1.34v. CPU-Z Validation
Not yet confirmed stable though 3008 (188x16) is confirmed by two days of steady crunching with ~22 CPU hours of validated work on the books ...
What's your Vcore at?
Also, best way to test, I just noticed, is really using it as your 24/7 system:(.
Ive done a lot of testing and in the end, I started to play some game today and it froze... Tried changing subtimings, even removing them... Changed from DDR1066 to DDR800. But in the end, now Im running HTT200 for a while, CPU multi 13.5 and NB multi at 11 and it's still playing now. Although Ill play a lot longer before I consider it stable, but Phenom stability is actually very hard to test lol.
As KTE and justapost did, you got to search for instability really. I hope this is stable so I can go back to previous settings and just set a lower NB multi and be done with it.
[EDIT] Just as I made this post and went back to the game (windowed), it froze again... NB now at stock, if it happens again Ill try and see if it might be my HD3870... That one is running quite high but I did a 2h+ FUR stability test yesterday... but you never know.
what started out as a sign of hope, has turned into desperation. it looks to me people are really having a hard time ocing this B3 phenom. hopefully the new chipset coming in june will bring more hopes. maybe this 790fx chipset can't handle the higher tdp 9850. i read that ocing the 9850 can kill your board due to the higher wattage that the board can't handle. anyone measure the tdp when ocing the 9850? maybe amd will finally get it right with the 45nm deneb. maybe there's still problem with the TLB, just my thought. i'm definitely holding out and keep my eyes on this B3 revision.
I agree that you really have to search for instability. I had the following settings clocks:
Core0: 3100
Core1: 3000
Core2: 2900
Core3: 3000
I used it in daily activities (checking mail, surfing the web, playing CS and Supreme Commander) then I ran an 8 hour OCCT test and it came back stable. Then after about 30 hours of normal use I went to rip a CD and BAM!!!! it crashed. Well, crap...thought it was stable.