i have tried this and can say that it does work. before i couldn't get into windows @ 2500mhz on my 3500+ cbbgd 0504 w slk948u; now, @ 1.4v @ 110%, im at 2500 stable. thanks for the tip.
i have tried this and can say that it does work. before i couldn't get into windows @ 2500mhz on my 3500+ cbbgd 0504 w slk948u; now, @ 1.4v @ 110%, im at 2500 stable. thanks for the tip.
Yeh YOU! :lol: :ROTF:Quote:
Originally Posted by andyOCZ
You need to got ta dfi-street.com and learn Rgonian, then y'all can spek proper-like :D
It kills them in a very short time.Quote:
Originally Posted by bachus_anonym
Really? How short :confused:Quote:
Originally Posted by GregP24
Mine started losing it's OC after about 2 1/2 months. I went fom a rock solid 2.72ghz down to 2.68ghz.Quote:
Originally Posted by DarkManX_BG
Not OLDER but already nice performer (2,65 benchable on air, 2,97 pi1m under phase) CBBHD 0450 chip is now priming for about 5 minutes at 2,6ghz @ 1,35 + 23% (1,6v) against maximun 2,52 @ 1,5+13% (1,61) ... damn just failed hehehhe but I'm 99% sure earlier it was instant faillure. Will reboot set at 26% and report back (god bye "will sleep early tonight )Quote:
Originally Posted by IvanAndreevich
:D
Really??? And how are you 100% sure that your Winnie's OC capabilites diminished due to higher vcore?Quote:
Originally Posted by GregP24
I've had my Winnie for, I think, over 4 months now and it even got better :lol:
It's been running with 1.70v since day1 on my Neo2 @ 2.62Mhz and now it sailes along with my DFI NF4 with 1.71v @ 2.67GHz... Always air-cooled with XP-90 + 92mm quiet fan - temp max 48C under LOAD... How about that???
--- Ivan ---
FYI... increasing VCore using the "Special VID Option" (using +%xx) is *not* changing the VID. And there will be an upcoming article ;) Patience grasshopper.
well now @ 2,6ghz - 26%+ it primed for 9 minutes and failed, and is now about 20mins priming @ 2.55 seems it can go all night (will check tomorrow and report), now to sleep.
oc-cba same here Mines at 2610 mhz prime failed at the 9th hour but 2565mhz go all night :)
I am experiencing the exact same voltage woes as you guys. This is with the Opteron 252, no fine vcore adjustments. Either 1.45 or 1.6v, pretty much. Unfortunately I don't have % adjustments in BIOS, and nothing sticks. I cannot hit 1.5v, 1.525v or 1.55v and it's driving me crazy. :rolleyes:
p.s. I'm at 2834 (218x13) with ~1.45v.
A crappy 0451 CBBID Winnie here (max 2300 Mhz Prime stable), will try this trick tonight as well to see whether it carries me somewhere :banana:
i run 1.55v x 104%, which is 1.612v
ive been tryin some other combinations yesterday and below 1.6v my cpu didnt like at all...
it did work when using 1.425v x 113%, which is about 1.61025 (a very lil less then 1.55v x 104%)
but when occt'ing i noticed that this last setting gave a variable voltage...
when idling smart guardian said it was 1.56v, but after occt'ing awhile it started quickly switching between 1.56v and 1.58v in smartguardian
1.55v x 104% gave me a stable 1.56v in smartguardian
so while 1.425v x 113% should normally be a lil less then 1.55v x 104%, it wasnt... it was actually more and variable...
so i switched back to the original 1.55v x 104%, since more cpu vid = more heat
this is 1.72 V !!! Are you aware of that ??Quote:
Originally Posted by andyOCZ
I said I set that, not that I RUN that. I use 1.35 VID x 123% and this is 1.62v in BIOS. No problems should result from that.Quote:
Originally Posted by flexy
So? 1.72V Really isn't that big of a deal when his load temps are under 50 degrees.Quote:
Originally Posted by flexy
Got a CBBID 0503, on new DFI NF4... starting the learning process now from my old Socket A.
So different. Get ready for questions guys.
Who will explain me what the F is going on
Yesterday i did this
http://img.photobucket.com/albums/v3...0-dfi-155v.jpg
I was supprised so i wrote down all setting and tried to do the same today but it didnt work out
http://img.photobucket.com/albums/v3...4/27-sp2k4.jpg
9x300 boot and sp2004 1,43V
BUT
16M max only 9x305 . temp , with winter cooling max 29C
1M only 9x307 doesnt matter what vcore :mad:
on MSI neo2 i reached 2810 9x312 mem 281 2,5-3-3-7-1T
mobo dfi ultra-d , bios 03/10
Could more people please post their experiences with the voltage of a winnie relating to its lifespan? I am getting pretty worried here... :eek: :eek: :eek:
:toast:
Hey guys, i thought i didnt have the bug becuase cpuz was showing the correct voltages, but i went into sandra and mbm5 as andy did and i found some pretty wierd results. it says my voltages for my cpu are 2.9volts... now that is in no way shape or form correct. is it possible that this is the bug and im not really giving my cpu 1.6volts.. i will do the 123% thing to see if i got hte bug, but im interested as i got another winnie 0506 that wont go over 9x255 (2.3ghz~) without crashing.
http://www.xtremesystems.org/forums/...id=26970&stc=1
--- Maxx ---
Trust the multimeter ;) The surface mount ceramic caps between the socket and the Vcore FETs is a good place to measure on the DFI.
From the looks of it, MBM is displaying your Vmem voltage, lol. Change the selected sensor.
lol.. except for the fact that the k8n neo2 cant go up that high on the mem voltage.. where do you check the cpu voltage on the k8n neo2? i will check the place that you said in hopes of some luck
i found a few places where there were caps missing. i checked them. i was getting 1.64 volts or so.. so voltage is not an issue for me.. my winnie just sucks hardcore.
LOL... have had DFI on the brain from bench work, sorry :)
Never had a Neo, so don't know... but in general the area described is a good possibility. There'll usually be a small group of them all together by the socket. Just be careful not to short your probes to anything or each other. :toast:
My "unnoficial" recomendation is don't go too much over 1.6v and you should have no issues. I have run mine at that and see no ill effects.Quote:
Originally Posted by One_Hertz
EMC2, care to share your findings? Are you saying that the +xxx% doesn't actually raise vcore or something? I am confused.Quote:
Originally Posted by EMC2
Cheers!
Dan.