Poor Overclocking Newer (ie:0503) Winchester Onwers - Check This Out!

OK here,

I bought an 0503 CBBHD Winnie and put it in my DFI NF4 Ultra-D only to be dissapointed by a low overclock (as I expected). Seems it would run memtest86 up 2650mhz, but no way would Windows load. I checked my voltage in MBM and Sandra and they were not following what I had set. I rebooted and changed the basic CPU VID value to 1.55v and I still had 1.42 volts (probably 1.45 which is default).

Frustrated by now, I decided to try lower the voltage to see if that would track. I tried 1.35v and it read fine in Windows. Hmmm..... so I set the voltage to 1.40v and the CPU VID Special Control to 123%. This read fine in Windows and i was able to hit 2610mhz stable in Prime95.

To sum up: I had a craptacular <2400mhz top overclock using the standard voltage adjustment in BIOS. By lower the voltage to 1.4v and using the overide at 123% I achieved 2610 P95 stable. Nothing ground breaking, but it turned a dissapointing CPU into the best one I have bought so far.

I have a few conspiracy theories floating around in my head here...........

Let us know if this helps you.

I really hate the way the MSI boards are presenting the voltage for overclocks with the percentages. I found issues with the Neo2 not applying any more voltage when moving from 1.45 to 1.50 to 1.55, they all reported about 1.48 in CPU-Z. I did like the Epox 9NDA3 that had increments not these stupid percentages.

Quote:

---

Originally Posted by dnottis

I really hate the way the MSI boards are presenting the voltage for overclocks with the percentages. I found issues with the Neo2 not applying any more voltage when moving from 1.45 to 1.50 to 1.55, they all reported about 1.48 in CPU-Z. I did like the Epox 9NDA3 that had increments not these stupid percentages.

---

same problem i got with an older 3200+ / neo2
no problem now since i've got a 0448SPAW @ 2.8 stock volt :D

Quote:

---

Originally Posted by andyOCZ

OK here,

I bought an 0503 CBBHD Winnie and put it in my DFI NF4 Ultra-D only to be dissapointed by a low overclock (as I expected). Seems it would run memtest86 up 2650mhz, but no way would Windows load. I checked my voltage in MBM and Sandra and they were not following what I had set. I rebooted and changed the basic CPU VID value to 1.55v and I still had 1.42 volts (probably 1.45 which is default).

Frustrated by now, I decided to try lower the voltage to see if that would track. I tried 1.35v and it read fine in Windows. Hmmm..... so I set the voltage to 1.40v and the CPU VID Special Control to 123%. This read fine in Windows and i was able to hit 2610mhz stable in Prime95.

To sum up: I had a craptacular <2400mhz top overclock using the standard voltage adjustment in BIOS. By lower the voltage to 1.4v and using the overide at 123% I achieved 2610 P95 stable. Nothing ground breaking, but it turned a dissapointing CPU into the best one I have bought so far.

I have a few conspiracy theories floating around in my head here...........

Let us know if this helps you.

---

Nice! I have a CBBID 0451 Winchester 3200+ that can only do 2350 at 1.6V! It automatically fails Prime at 2400 within minutes. If you can get 2600 out of yours, I'd say that's pretty good.

Wait a sec... that sounds a lot like my VNF4 where there seems to be a known bug that voltages between 1.45 and 1.6 (exclusive) are unattainable (ie. in neither the bios nor windows will any voltages set between 1.45 and 1.6 (exclusive) show up as such). Once I hit 1.6V+ the voltages actually change to that.

Well a lot of us have that crappy chip. Please report in and see if Andy's findings prove postive for others. :toast:

i got CBBID 0503 3500+
for super PI bench that proc can not pas 2700 Mhz ,in 1.55 v only benchable at 268x10 although i raise the vcore to 1.6 v the proc cannot get higher then 2680 Mhz.... :(

http://img214.exs.cx/img214/8287/sp85sr.th.jpg

Not bad

Well, someone fill me in here because I seem fail to understand something here :rolleyes:
What is the deal with people not giving Winnies more than 1.6v? What about 1.7v? Is it high temperature you guys are reporting or what?

I have a CBBFD 0441 Winchester that is Prime95 stable on my DFI @ 2670MHz and it needs 1.7v to do that. At low ambient temps (13C) it does 2760Mhz fully benchable. Voltage in BIOS is set to 1.425/1.55/110%. As we speak, at normal ambient temps (21C), mobo outside the case between two other mobos - that account for some higher ambient temp, XP-90 plus 92mm quiet Sanyo Denki fan - I don't ever see more than 45C under LOAD with D2OL crunching @ 2670MHz...

Are those "crappy CBBID Winnies" running exeptionally hot or something that you guys can;t just give it 1.7v and see what they can do then? Or people just hope that every Winnie should be doing 2700MHz @ 1.55v and any other is crap ???

Fill me in here, please... No seriously...

I have a cbbid 0451 3500, it also has a range in the voltage settings that read the same, but with so many variable ways to get almost the same voltage it is worked around. Mine don't do to bad though, in fact it seems to get better. Tonight I switched to 310p and got about 100pts increase in 3d01 to 24205.

Quote:

---

Originally Posted by bachus_anonym

Well, someone fill me in here because I seem fail to understand something here :rolleyes:
What is the deal with people not giving Winnies more than 1.6v? What about 1.7v? Is it high temperature you guys are reporting or what?

I have a CBBFD 0441 Winchester that is Prime95 stable on my DFI @ 2670MHz and it needs 1.7v to do that. At low ambient temps (13C) it does 2760Mhz fully benchable. Voltage in BIOS is set to 1.425/1.55/110%. As we speak, at normal ambient temps (21C), mobo outside the case between two other mobos - that account for some higher ambient temp, XP-90 plus 92mm quiet Sanyo Denki fan - I don't ever see more than 45C under LOAD with D2OL crunching @ 2670MHz...

Are those "crappy CBBID Winnies" running exeptionally hot or something that you guys can;t just give it 1.7v and see what they can do then? Or people just hope that every Winnie should be doing 2700MHz @ 1.55v and any other is crap ???

Fill me in here, please... No seriously...

---

I can't speak for other people, but I have tried up to 1.7V, but I have stock retail HSF so I dare not push it much more at least for extended periods. I did not gain any stability at 1.7V. Using 1.6V I could push to 2350, I went to 1.65 without being able to hit 2400, pushed a little further and noticed nothing as well. From what I can tell, my CPU is maxed out at 2350 without much superior cooling and even then who knows how much more I could get. Even if I could get more at 1.75V, I doubt it would be enough for most people to consider my CPU to be a decent overclocker.

2.68GHz is a VERY good clock for a cbbid but I guess the 3500+ are speed binned that way, most of the bad ones are the 3000+ and 3200+ speed binned. I see alot of people buying 3500+ cause there sick and tired of not hitting even 2.4GHz. I dont know how venice will be binned, but amd would be smart to do the same and force people to buy the 3500+ and 3800+ for the 3GHz overclocks while the 3000+ and 3200+ do 2.6 to 2.8

"What is the deal with people not giving Winnies more than 1.6v? What about 1.7v? Is it high temperature you guys are reporting or what?"


cause it makes no difference for the majority of winnies. they stop scaling past 1.55, sometimes 1.6v take mine for example, I can do 2.5GHz(or more) at 1.45v but I use 1.58v for 2.6GHz and more volts doesnt help, sometimes even prevents it from posting. I guess the new 90nm die just doesnt like volts, it does great at stock volts then rising the volts gains you just a bit more then thats it

interesing andy.. i just hope and pray to all the false gods of overclocking out there that I get a good 3000winnie...

I have had mine up to 1.796 (1.425x126) for testing. It did not do any better than it does where it is atm, 1.734 (1.275x136). It actually was not quite as stable. I don't know why. I use water and the temps are 32c - 34c only going to 35c when I had the voltage higher. One thing that keeps me from going past 1.8v even though the temps are low is the cost, $275.00 for the cpu. I know that going over 1.8v is not some magical number that if it is crossed it will ruin it, but if I can't see any diff. between 1.67v and 1.79v, I have not thus far seen a reason to go on. I've thought about the possibility of some sort of threshold that if passed will make a diff. but somethings can't be undone. (wussy) I'm still trying to get the most from here for now.

bachus anonym,

The point was that many have these NEW Winnies that are reportedly not responding to voltage. I suspect that something is causing the BIOS to "stick" at default voltages, or possibly revert back to default voltages when loading Windows.

My theory is that by lowering the voltages below default, and overriding it using a percentage (ie: 123%) I was able to get around this issue. It seemed to work in my case. Where I had been adding voltage before using the 1.55 max VID, this was getting me no where, so I gave up, thinking I had hit the limit for my CPU.

Many are reluctant to put 1.7v into thier CPU, or may have cooling that is not the best, causing heat issues. These CPU's are sensitive to heat. I don't mind the voltage, but I just tried 2650 at 1.7v and failed P95, so it seems my CPU like about 1.65v at the most. I guess 2610 may be my limit. I can live with that.

This is not rocket science, it's just something that might help anyone that gave up like I nearly did.

andyOCZ,

Pardon, for sort of hijacking your thread... I just couldn't help asking this here...

And personally, I think that the information u gave here is very valuable :thumbsup:

I found heat problem with my CBBID its realy hot 250x 10 in 1.4 Vcore in 24 C room temperature ,ini load cpu temp is 52 C ..i use HT 101 with 56 cfm fan....use XP-120 with 100 cfm hit 48 C...i tried any kind method to put AS5 and the result is same...

i tried to OC my CBBID again with window opened temp room 8 c :D
for max clock hit 2739 :D

http://img199.exs.cx/img199/6245/bessie39bc.th.jpg


i tried use 1.7 Vcore but while bench with sandra cpu aritmethic the cpu temp hit 71 so...the PC auto restart.... :D

9.5x multi sux, use 9 or 10 instead. I do 305*9 :D

http://img39.exs.cx/img39/8346/305x941ff.th.jpg

i have the same problem with the vcore issue, no matter what voltage i change it to, it doesnt hit higher then 1.55. right now its set to 1.55 x 9.9% and its still reading 1.53-1.55. im pretty much stuck at 2.6ghz, i want more vcore! too scared to do a vcore mod.

week 0501 CBBID
http://silentproject.com/stable.jpg

Quote:

---

Originally Posted by xavicl

9.5x multi sux, use 9 or 10 instead. I do 305*9 :D

http://img39.exs.cx/img39/8346/305x941ff.th.jpg

---

thats CBBID ? and what week ?

its CBBID 0450 :rolleyes: not so good, but no so bad than 0451. Stable is 300*9=2.7GHz

Will try that tomorrow in my piss-poor Winchester 3000+ that doesn't oc :banana::banana::banana::banana:... :/

Actually, 2.7 is in the top 1% of all winnies.

andyOCZ
I noticed a similar thing on my Neo2, I think. It has the VID up to 1.55V and voltage adjustment up to 10% workable on most bioses. I was running 1.45 VID + 10% = 1.60V stable. Then I recently tried 1.5V + 5% = 1.575 (actual more like 1.55V) and it was stable for 24hr prime95! 1.45 VID + 8.3% = 1.57 was NOT stable when I tested it earlier (it was colder too in the winter). So, I think we're onto something here?

So wait... how are you adding different %'s to your voltages? All I have is a list of numbers to choose from as far as I know...

it's possible that it's a board limitation, because something similar happens to my clawhammer.

the following is for 230x10.
at 1.45 +3% (a touch under 1.5v) is prime stable for about 15 min
1.5: instant fail

1.5 + 3% is primestable for 12+ hours
1.55 fails within 5-10 min.

i haven't played around with the higher voltages much because my chip is very insensitive to voltage (at normal room temp, i need 1.75v to get to 2.4ghz, and then the load temp is hitting 60c, which is too high for me)

3500 CBBID0451FPAW
http://img.photobucket.com/albums/v636/loc_oc/30.jpg

Absolute max on the XP120. Will try yr settings later Andy.

I got the same voltage problem with my MSI NEO2. The max i can go is 1.6v (10%+1.45) if i go above the 1.45 it dont respond, so i leave it at that, and use the 10% option to get the max of 1.6v...makes no sense


here is what i get with 1.6v

SIOUX
My Neo2 lets me have up to 1.65V when I set 1.50 for VID and +10%..

I still can't quite get over it but he's right, just tried a ex-sucky winchester (0502 / CBBID) 3200+ that wouldn't go pass 2200mhz with any volts / ram timings.

With Andy's settings its now priming @ 2500mhz and I dont think thats the ceiling yet, nice find man and thanks for sharing the info. :cool:

There must have been a reason why mobo makers decided to have the voltages based on a base value multiplied by a percent. This might have been it. They might not have been able to officially say it because of contractual obligations. (Like with Intel and PAT) I wish I had a winne for testing.

Quote:

---

Originally Posted by grenadier

So wait... how are you adding different %'s to your voltages? All I have is a list of numbers to choose from as far as I know...

---

what your mobo ?
maybe your mobo not provide to adding Voltage by %
for DFI NF4 it can change Voltage by %
:)

Thanks for the tip, but I'm already using 1.5V x 110% and it's tracking fine (SmartGuardian displays 1.61V while it should be 1.65V but not a big deal). Chip is still maxed out at 2.4Ghz 1.65V for stability, damn CBBID 0505 :(
(I can run 3DMark2001 at 2.5GHz 1.7V, haven't tried higher yet)
What's the max safe 24/7 voltage you guys would recommend? At 1.65V temps are always under 40C...

Quote:

---

Originally Posted by bachus_anonym

What is the deal with people not giving Winnies more than 1.6v? What about 1.7v? Is it high temperature you guys are reporting or what?

---

1.7v is = to ~2.0v on air for an XP. That is why. 1.6v = ~1.875v for an XP. So you'd be quickly killing the chip with that kind of voltage.

As for this issue, here's a link to someone who seems to be having the same problem: http://forums.extremeoverclocking.co...41#post1623641

It sounds like a board issue. Maybe the VID is not being applied correctly in bios, for whatever reason.

You know when I briefly had my 3200+ Winnie 0451, the board I had had no voltage control, so I was only able to adjust it via clockgen. However clockgen @ 1.55v only gave my chip 1.45v - same thing? :confused: I thought it was clockgen, but maybe not.

Interesting. Did AMD change the higher VID codes?

Quote:

---

Originally Posted by grenadier

So wait... how are you adding different %'s to your voltages? All I have is a list of numbers to choose from as far as I know...

---

I am not familiar with the chaintech mobo, but I have a similar method of changing core voltage within my nforce4 a8n-sli and have discovered that even though it looks like there is only one way to change voltage, the BIOS applies the percentages "behind the scene", so to speak...

Anyway the way to check for this is to load 1.4v in BIOS then boot into windows (with stock settings) use clockgen and record the VID value. Reboot and change the 1.4v to the next highest and repeat.

IN the asus board sometimes the VID for a relatively high (for this board) voltage ~1.6 will have a LOW VID but a ~1.5 will have a higher VID value. This means there is something else the BIOS is using to adjust the voltages. I am assuming it is similar to the other nforce4 boards, but since the asus was meant for all the noobs out there, they probably decided against adding another option for simplicities sake.

Is it best to run with a 1.6v that has a 1.35 VID on these boards vs a 1.6v with a 1.45v VID? (I haven't really done any testing on this, but it would be interesting to know...)

anyone else try this out?

The reason you set voltage with percentages is because A64s have two variables for setting the voltage.
First is CPU VID, and it is used for changing the voltage for C&Q. It is a function of CPU and not of a motherboard. It ranges from 0.8 V up to 1.55 V on 130nm CPUs and up to 1.45 V on 90nm CPUs.

The second is an usual CPU Voltage selector, used for overclocking. And it has to raise the voltage in percents, because it depends on the CPU VID selected. This feature depends on the board itself.

Hopefully i explained it right with my poor english :rolleyes:

I have a MSI neo2 Platinum. Stock settings for CPU VID is 1.500 which gives me about 1.376-1.392 volts according to CPU-Z. The sec cpu voltage is done by % in the following...
+3.3 gives me 1.424-1.440
+5.0=1.472-1.488
+8.3=1.520-1.552
+10=1.586-1.600

There is no other choice like 110% ect, though I never tryed lowering the CPU VID below 1.500, I will have to try that. I set it to 1.55 and there was no diff in voltage or stability.

I have one of the new 3500s and she is stable as a rock with +3.3 voltage@2.5 ghz by way of 11x multi and 228FSB. Now if I try 238FSB she crashes during 3DMarks cpu tests no matter what voltage I use up to 1.600. I can post and do CPU-Z @2.7+ but as soon as I run a program...Crash.

Things to note; in bios for CPU VID I can set it for AUTO as well, wonder if that will help. Why it is set by default to 1.500 in bios even though I have a winnie? Yet bios shows 1.4 voltage with that setting as well as CPU-Z and speedfan ect...

I knew there was something up since my cpu runs stable @2.5 with only 1.42 core, yet crashes@2.6 no matter what voltage.

One other thing, the weird part is if I use stock settings (no 3.3% over cpu vid) I idle at around 38-40. With 3.3% over (~1.42) I'm iding right now at 34 and max at 49. Seems like I'm using less voltage overclocked or something :p:

I'm going to try this on my 3000+ 0449 that wont clock past 2250 under water with a DFI NF4 when I get home. Will post my results. Thanks a lot for the tip, Andy.

Quote:

---

Originally Posted by Ref

The reason you set voltage with percentages is because A64s have two variables for setting the voltage.
First is CPU VID, and it is used for changing the voltage for C&Q. It is a function of CPU and not of a motherboard. It ranges from 0.8 V up to 1.55 V on 130nm CPUs and up to 1.45 V on 90nm CPUs.

The second is an usual CPU Voltage selector, used for overclocking. And it has to raise the voltage in percents, because it depends on the CPU VID selected. This feature depends on the board itself.

Hopefully i explained it right with my poor english :rolleyes:

---

Make perfect sense to me. Your english is fine. :)

Quote:

---

Originally Posted by andyOCZ

Make perfect sense to me. Your english is fine. :)

---

I love it how all the foreign people will add "Please excuse my english" at the end, when they did a great job.

Then people who should know how to speak english correctly type as if they don't know english! LOL!

It seems that only non-native speakers care to check if what they say/type is correct, ironically.

AFAIK, the Chaintech VNF4 Ultra does not have any % voltage settings. You can set VID and that's it. So, basically, I only have 1.4, 1.45, and 1.6 as viable settings. Chaintech needs to step up and come up with a better bios that fixes this!

Quote:

---

Originally Posted by Ackbar

I love it how all the foreign people will add "Please excuse my english" at the end, when they did a great job.

Then people who should know how to speak english correctly type as if they don't know english! LOL!

It seems that only non-native speakers care to check if what they say/type is correct, ironically.

---

I belev yoo was referrin ta mee?

Hey man, I'm tired :)

Not only can I finally determine that this proc's mem controller sucks, but I broke my previous SPi record held by an old P4 by 3 secs :). I think the score for 2700 is a bit low, but I blame the divided memory. VID set to 1.325 with +136% special control (~1.73v actual). To sum it up, this trick gained me close to 500MHz. Thanks again Andy! :toast:

1.7v is a bit high for Winchester don't you think? I use 1.5v max.

Quote:

---

Originally Posted by dX.

1.7v is a bit high for Winchester don't you think? I use 1.5v max.

---

If the temps are fine, why not give the CPU the voltage it wants? :p:

Quote:

---

Originally Posted by Gogeta

Not only can I finally determine that this proc's mem controller sucks, but I broke my previous SPi record held by an old P4 by 3 secs :). I think the score for 2700 is a bit low, but I blame the divided memory. VID set to 1.325 with +136% special control (~1.73v actual). To sum it up, this trick gained me close to 500MHz. Thanks again Andy! :toast:

---

Awsome news!

Quote:

---

Originally Posted by dX.

1.7v is a bit high for Winchester don't you think? I use 1.5v max.

---

At 33c load it's loving 1.7v :D

very intresting trick man

but i wonder:
does it only work when u clearly see in windows that my voltage changes in bios didnt work?

cause while testing cpu vid about 1-2 weeks ago, it really did work here (smart guardian reported higher volts and higher cpu temps when increasing volts in the bios (running 1.55x104% atm, tested till 1.55x110%)

The only thing I can imagine is that the mobo's increase the voltage in each of the cases BUT increasing the VID is better for some reason.

I think it's important to figure out exactly what we're on to here and then somebody should write an article on this. It could be very important!

Is there anybody with an OLDER Winchester who also received a nice gain?

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.

Quote:

---

Originally Posted by andyOCZ

I belev yoo was referrin ta mee?

Hey man, I'm tired :)

---

Yeh YOU! :lol: :ROTF:

You need to got ta dfi-street.com and learn Rgonian, then y'all can spek proper-like :D

Quote:

---

Originally Posted by bachus_anonym

Well, someone fill me in here because I seem fail to understand something here :rolleyes:
What is the deal with people not giving Winnies more than 1.6v? What about 1.7v? Is it high temperature you guys are reporting or what?

---

It kills them in a very short time.

Quote:

---

Originally Posted by GregP24

It kills them in a very short time.

---

Really? How short :confused:

Quote:

---

Originally Posted by DarkManX_BG

Really? How short :confused:

---

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 IvanAndreevich

The only thing I can imagine is that the mobo's increase the voltage in each of the cases BUT increasing the VID is better for some reason.

I think it's important to figure out exactly what we're on to here and then somebody should write an article on this. It could be very important!

Is there anybody with an OLDER Winchester who also received a nice gain?

---

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 )
:D

Quote:

---

Originally Posted by GregP24

It kills them in a very short time.

---

Really??? And how are you 100% sure that your Winnie's OC capabilites diminished due to higher vcore?
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

Quote:

---

Originally Posted by andyOCZ

Hmmm..... so I set the voltage to 1.40v and the CPU VID Special Control to 123%. This read fine in Windows and i was able to hit 2610mhz stable in Prime95.

---

this is 1.72 V !!! Are you aware of that ??

Quote:

---

Originally Posted by flexy

this is 1.72 V !!! Are you aware of that ??

---

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

this is 1.72 V !!! Are you aware of that ??

---

So? 1.72V Really isn't that big of a deal when his load temps are under 50 degrees.

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:

Quote:

---

Originally Posted by One_Hertz

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:

---

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 EMC2

--- 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.

---

EMC2, care to share your findings? Are you saying that the +xxx% doesn't actually raise vcore or something? I am confused.

Cheers!
Dan.

Quote:

---

Originally Posted by dX.

EMC2, care to share your findings? Are you saying that the +xxx% doesn't actually raise vcore or something? I am confused.

Cheers!
Dan.

---

He means they are 2 seperate "changes". He will have more details.

For our purpose using a % and lower VID works best. And yes that changes vcore.

man this is some good stuff, if only we could figure out if this is the bios or the cpu, maybe this has something to do with the cpu's not wanting to run the VID high so with the % increase your only raising the core's voltage...
man this stuff makes socket A overclocking look like childs play, i better upgrade before its to late and i have absolutely no idea what you guys are talking about!(VID??!)

This works, tested b/c when set to 1.5v or above in bios it reverts to 1.4 for me. Anyway, atm im not doing too bad, 100% benchable at 2.75, will boot windows at 2.8 with 1.6v...........gonna try one of the other bios and give it up to 1.7v to see what i can get outta it. Its a 3200+ cbbid 0507 on an msi neo 2 platinum. Not too bad for my first overclock where i have working agp locks.

i've test the setting using % and not raising vid but the result still the same duo to my lousy ram. not sure if i'm reaching my limits with 2.43. others i will test it out when i got better ram.

Quote:

---

Originally Posted by dX.

EMC2, care to share your findings? Are you saying that the +xxx% doesn't actually raise vcore or something? I am confused.

Cheers!
Dan.

---

Regarding my +xxx% and VID comments, I'll say this for now... VID is the 5-bit encoded setting to the Vcore controller IC. When you change the base Vcore in the BIOS, it changes the VID to the controller IC. However, when you use the +xxx%, it does not change the VID encoding to the chip, it adjusts the Vcore through a different method, leaving the VID encoding as set in the base setting.

Yes, when I'm done I will put up the complete info on everything I'm looking at... just taking a tad longer than anticipated for unsaid reasons. Won't put up anything till complete, checked, cross-checked, and organized ;) No half measures here.

Peace :D

aha so what i said does make some sense.. yes

Ok, tried the trick on my cpu. Not a single mhz more :brick: (still at 2300).

My Neo2 gave 1.33V @ 1.5V in BIOS. I now tryed 1.4V in BIOS + 5.0% and CPU-Z now neasures 1.440V! This is great, maybe I can now reach more than 2.25Ghz... :)

I'm still a little confused!

So if I lowered the volts to like 1.3 and set CPU VID Special to 100% - wouldn't it make 2.6 V?

Quote:

---

Originally Posted by DildePer

I'm still a little confused!

So if I lowered the volts to like 1.3 and set CPU VID Special to 100% - wouldn't it make 2.6 V?

---

No, if you set it to 100% you get 100% of the selected voltage. If you set it to 110%, you get 110% of the selected voltage and so on... so for 1.3V 110% you'd get 1.3x1.10 = 1.43V

This has given me some nice results! Im doing very nice Vcore now, when set to 1.425 i get 1.424 in CPU-Z! :)
Better clock aswell, Priming it right now. And I can for the first time clock with an official BIOS! (MSI Neo2 Platinum BIOS 1.5 Official)

Quote:

---

Originally Posted by DarkManX_BG

No, if you set it to 100% you get 100% of the selected voltage. If you set it to 110%, you get 110% of the selected voltage and so on... so for 1.3V 110% you'd get 1.3x1.10 = 1.43V

---

Now i get it, so what is CPU Startup VID for?

seems not working well on my proc. maybe this trick work good on dfi? or do i need to use other bios than 1.36mod. anyone on neo2 using 1.36mod managed to oc more with this trick do post the result.

This it is the best configuration that allows my processor (CBBID 0550) 1.55 + 104 % 2.6ghz pi stablly

http://img146.exs.cx/my.php?loc=img1...e=setpi4pc.jpg

My CBBID (0503EPMW) does 2550 mhz (max limit) with 1.65V but it isn't stable and it can't bench. Above 2550 does't load the OS.

It benchs @ 278x9 = 2500 with 1.6V (LINK) but it can't pass prime95 small fft test.

Max stable oc is 2300-2350 :(

Quote:

---

Originally Posted by DildePer

Now i get it, so what is CPU Startup VID for?

---

Dunno, I just set it to 1.55V...

Quote:

---

Originally Posted by DildePer

Now i get it, so what is CPU Startup VID for?

---

That's to insure you have enough vcore to boot up properly. This seems to be non-crtitical. I set mine to 1.5v and don't worry about it.

With my 3000 (cbbid 0504) i have to run it at 1.7v to get it to boot at 2430mhz. HTT is at 270 and memory is at 220. i have it on a soltek k8tpro.

Of course I'd like to run it at a lower vCore but...I need the speed. I was hoping pc4400 would fix something. I might try to sell this cpu/mobo and get a better a64 and one of those DFI boards. I dunno...I must admit I'm disappointed with the overclock. My 1700 was at 2.1 ghz for so long that I must have started to take 700+ mhz for granted.

temps are a bit high with the stock cooler. If I can find a place with the swiftech blocks actually in stock I'll be getting one of those.

I have the same issue on my new 05 FX55 it STINKS FOR OVERCLOCKING

nice