Kunaak, did you by chance happen to have 2.9v selected in bios on any of them?
Printable View
Kunaak, did you by chance happen to have 2.9v selected in bios on any of them?
Quote:
Originally posted by Karnivore
Xtreme is growing really fast, since about December it seems to have really taken off, I've posted a few threads regarding spam, personal attacks, etc. The replies from the folks running Xtreme made much sense, They simply don't catch all the problems, and trouble. A simple suggestion was offered, use the report this post button, it works, and they WILL deal with it.
Maybe they need a few more mods, dunno, but until such time as they have the manpower to cover every single thread, exercise the "REPORT THIS POST OPTION" I certainly do agree with you that much uncalled for actions are being made by members, It is kind of like the Neghborhood watch thing, unless the community gets involved it won't work...
we do our best but being so large now ... community feedback has becom the weapon against spam and flamming .... I am personally watching this thread and ask anyone who has been here how I feel about flamming.
and as for RMA ... its best to not even post about it cause if I get the scent of illegal doings then it will not be a pretty picture dealing with me.
This is Xtreme ... a place for those who know what they are doing and for those to learn ... this is NOT [H] or Tom'shardware sellout...
get the pic guys? Karnivore I'm not picking on you here ... but just adding to your post.
thanks man!
What is [H] ? Sorry I'm not familiar with them :rolleyes:Quote:
Originally posted by JBELL
we do our best but being so large now ... community feedback has becom the weapon against spam and flamming .... I am personally watching this thread and ask anyone who has been here how I feel about flamming.
and as for RMA ... its best to not even post about it cause if I get the scent of illegal doings then it will not be a pretty picture dealing with me.
This is Xtreme ... a place for those who know what they are doing and for those to learn ... this is NOT [H] or Tom'shardware sellout...
get the pic guys? Karnivore I'm not picking on you here ... but just adding to your post.
thanks man!
edit - whoops
lol Bmorin...i think he knows what [H] is....
Why is [H] So bad? there reviews are ok... better than Tom could ever do and its a good starting place, before finding better reviews. I never believe in one site anyway.
Anyone killed one since micky posted about the vdimm issue?
Not that I know of, my 3200+ will be here in say half hour to 1 hour from fed ex, newegg shipped out out on I think thursday and I've been tracking my order like a hawk.Quote:
Originally posted by STEvil
Anyone killed one since micky posted about the vdimm issue?
We'll see how this new 3200+ handles in terms of OC.
My A64 3200+ came just now, gonna put it in and see what it does.
Don't remember the week but its a green chip MC at the last two.
Will update after I look at it again.
Found these statements over at another site (not sure about crosslinking here, so i just say OCW)
Don't know how good the writer can back his claims, but this seems to correspond reasonably well with what some people have been experiensing here.Quote:
..Be careful, the Athlon64 does not tolerate high voltages! Anything above 1.7 Volt will be dangerous to the CPU and the mainboard power supply circuit. AMD rates 1.65V as the maximum...
..The memory voltage can be set from 2.5 to 2.65 Volt within the Bios. This voltage powers the DDR memory as well as the memory controller interface of the Athlon64 CPU itself. AMD rates 2.9V as the maximum....
..Be careful not to exceed 2.9 V as this is the absolute maximum rating for the Athlon64 memory controller...
Please look at my sig for system specs. Hey all I am new and this is a weird problem. I have talk to Amd and Chaintech. This is the second znf3 motherboard I have had throught rma. When I start up the computer it will go for a minute or two and then it will freeze. Then I push the restart button. When it restarts it comes with a beep code. Chaintech said it was the memory problem beep code. Then I clear the cmos and it will boot for the same time and then freeze. I have ran the memory in a different system for 6 hours each stick and the test came out perfect. Chaintech meantioned about it might be overheating. Just to throw this out there I might have overtightened the prommie when I remounted it. Thank you for helping.
512mb chips are double sided or 2 banks each aparently most A64 boards dont like that (well 4 banks anyway full anyway)
try it with just 1 mem chip
Sorry my sig was wrong. It is right now. I have tried both chips in and I have tried swapping them out one at a time. Thanks you for the reply. Again sorry about my sig. It is right now.
Mmmm..It's a real strange prob.
I killed a 3200+ I runned 1.95v and 3.1v vdimm and I had a 3.3+ line at 3.65v (On a GA-K8NNXP)
I heard it could be the High 3.3+ line so I backed it down to 3.4v
when I got a 3400+.
Now this 3400+ died also was running 1.95v and 3.6v vdimm 3.3+ line at 3.4v (On Shuttle an50r) (I used 2x1k and 2x10k for vmods)
Strange thing on a site note...they all started with having reboots, untill they died after a couple of constant reboots.
1.95v ?!....
...i wonder why :)
Sry to hear about that Jvlk, did you leave your bios vdimm on "auto" and adjust your voltage using the trimmer? And you are right, they always seem to die on a reboot.
This is the first I have heard of Athlon64 dieing, I guess I will wait awhile and watch this thread for the cause.
-Milkmover
Yes left my volts in bios on AutoQuote:
Originally posted by BMORIN
Sry to hear about that Jvlk, did you leave your bios vdimm on "auto" and adjust your voltage using the trimmer? And you are right, they always seem to die on a reboot.
As far as I know, you are the first one to lose a cpu while adjusting vdimm the safest way, so that is a little unsettling. Are you going to give it another shot with the same vdimm after you get a new chip?
I guess I got a Tough A64 3200+.. Killed the AN50R (twice) but the cpu is still running strong
ADA3200AEP5AP
CAAMC 0339XPMW (brown)...
Had the Vcore up to 2.1V and the Vdimm to 3.8V...
I'm not sure if my 3000's dead or not yet. I did a bios flash with everything stock using Alt-F2 about an hour ago, it went to reboot after writing successfully and hasn't been seen since. :( 8hda3+ board
Edit: reason I'm not sure is the on board display says C1, memory error. Swapped in the memory from this machine but no go.
well memcontroller is in your chip so that might have been fried and passed away...
Sounds like it. At least some of it still works though :P
Ok, I haven't killed mine yet, but yesterday while I was messing around with the shuttle's vdim mod, by slowly turning the pot to increase the Vdim, it jumped from 3.1 to 3.66. stayed there for about a sec, and then it came back to 3.1...
That's weird, eh? is there any chance that the Vdim's mosfets can't handle the extra voltage/heat, so they're crapping out eventually?
Onto my third A64 3200+
I got another greeny this time:
last two letters = KC week 333
First one was : MC week 343 (brown)
Second one : AC : week 341 (green)
Wish me luck I'm now on as follows:
Gigabyte K8N Pro (Instead of ASUS K8V Deluxe)
A64 3200+ KC 333
2x 512 Mushkin lvl 2 3500 || 2x 256 Corsair XMS3200LL rev 1.1 || KHX3000/2x256
PCP&Cooling 425W (3.3 = 3.6 | 5v = 5.46)
Radeon 9800 Pro
80GB Maxtor ATA133
Was Vdimm set to auto in bios while you turned the pot?Quote:
Originally posted by RootX
Ok, I haven't killed mine yet, but yesterday while I was messing around with the shuttle's vdim mod, by slowly turning the pot to increase the Vdim, it jumped from 3.1 to 3.66. stayed there for about a sec, and then it came back to 3.1...
That's weird, eh? is there any chance that the Vdim's mosfets can't handle the extra voltage/heat, so they're crapping out eventually?
I really want to do the Vdimm mod but all these dead CPU's scare me. :(
Yes, after reading this thread and Mickey Mouse suggestion, I didn't change the Vdimm value from bios... was set to auto before I started turning the pot.... and I was turning it real slow.... 3.0, 3.05, 3.1 and suddenly, both the multimeter and the bios screen showed 3.66....just for a sec or two, without touching the pot, it came back to 3.1.... The psu is a pc-power&cooling 475, with modded lines which are solid no matter the load....Quote:
Originally posted by Zeus
Was Vdimm set to auto in bios while you turned the pot?
I really want to do the Vdimm mod but all these dead CPU's scare me. :(
Scary stuff mate! :eek:Quote:
Originally posted by RootX
Yes, after reading this thread and Mickey Mouse suggestion, I didn't change the Vdimm value from bios... was set to auto before I started turning the pot.... and I was turning it real slow.... 3.0, 3.05, 3.1 and suddenly, both the multimeter and the bios screen showed 3.66....just for a sec or two, without touching the pot, it came back to 3.1.... The psu is a pc-power&cooling 475, with modded lines which are solid no matter the load....
Looks like anything over 3.5V can kill the memcontroller, so even the "mickey mouse method" isn't safe....?
Strange how some ppl can run over 3.5VDimm for over months and how some CPU 's get killed instantly by spikes.
Could it be a combination of high Vdimm/high HTT?
I don't mind doing the Vmod but i don't want to take out a €450,- chip for the sake of 0.2V more Vdimm.
Man, i just wish there was a safe way of Vmodding this board. :(
Well, this is what happened to me, if others don't verify it then something went wrong to my setup and MM's method should be considered safe.Quote:
Originally posted by Zeus
Scary stuff mate! :eek:
Looks like anything over 3.5V can kill the memcontroller, so even the "mickey mouse method" isn't safe....?
The HTT was default when I upped the Vdimm... another strange thing is that the voltage don't seem to fluctuate at any other point, mem@load or not, only when adjusting the pot and/or change the setting from the bios....Quote:
Originally posted by Zeus
Could it be a combination of high Vdimm/high HTT?
Haven't clk'd my 3200+ much 227fsb max and about 2.9 - 3.0vdimm on a kv8 max3. CPU has also been on a k8nnxp but even less clk and volts. On the possitive side it's been running strong for 4months or so now.
This vdimm thing sounds like a surge from changed the vdimm via bios or pot, and oscillating before dropping back or up and down. Seems that the reg or mosfet is on the limit or maybe even the CPU mem controller is overheating or transistor junction breaking down and drawing high current/ voltage subsequently killing itself :confused: .
I like the idea of the onboard mem controller improving performance, but it does seem to have some drawbacks.
Just curious, has anybody tried overclocking an A64 board without doing any extreme volt mods and just using the voltages in the bios?
Before you throw things at me for asking that, I'm just curious from a testing standpoint if anybody has killed anything just using bios settings.
Thanks,
Kosmic
Not sure, but truth be told, you're asking the wrong forum since most everyone runs a vmodded vdimm. We can't hold a piece of hardware longer than 24 hrs without slapping the solder gun on it.
Lol yea, I figured that was the case, but I just wanted to see if anybody had tested it at stock to see if any deaths resulted. I personally have a bit of solder-phobia so if I decide to go with 754 I can report back in here. Might be a while though...
Meh I'm running my 4Th A64 right now un modded.
Stable @ 2.3Ghz 1:1 ram no effort, priming 8 Hrs so far no errors.
Will be voltmodding come early AM :D
I would love to get the chance to try overclocking one of these. My first died during a bios flash.Quote:
Originally posted by Kosmic
Lol yea, I figured that was the case, but I just wanted to see if anybody had tested it at stock to see if any deaths resulted. I personally have a bit of solder-phobia so if I decide to go with 754 I can report back in here. Might be a while though...
I got my RMA today and it died within an hour. Changed the CAS rating of the mem from 2.5 to 2 and away she went . I'm getting sick of this. Both stock, both auto with no mods.
I'm using Corsair XMS3500. What are other folks using when they're dying?
Try another motherboard, it might be the CPU'S aren't dieing but the motherboard playing up from a bad flash. Either way I'd be trying a new CPU/ MB combo.Quote:
Originally posted by dod
I would love to get the chance to try overclocking one of these. My first died during a bios flash.
I got my RMA today and it died within an hour. Changed the CAS rating of the mem from 2.5 to 2 and away she went . I'm getting sick of this. Both stock, both auto with no mods.
I'm using Corsair XMS3500. What are other folks using when they're dying?
Sorry to hear that dod, that really really sucks. I don't see how it is possible for the CAS rating to affect the chip. Sounds to me like you have a bad mobo that's doing the killing, but that's just a guess.
could it be that your VR is not a 'precision VR'?Quote:
Originally posted by RootX
Yes, after reading this thread and Mickey Mouse suggestion, I didn't change the Vdimm value from bios... was set to auto before I started turning the pot.... and I was turning it real slow.... 3.0, 3.05, 3.1 and suddenly, both the multimeter and the bios screen showed 3.66....just for a sec or two, without touching the pot, it came back to 3.1.... The psu is a pc-power&cooling 475, with modded lines which are solid no matter the load....
i mean, normal pots are supposed to stick to the before set resistance, but they don't guarantee linear resistance while actually TURNING the VR!!!
Only precision VRs are supposed to act in a linear way while changing.
So - if you change the resistance on the VR under current you take the risk of wrong values for a short time.
just a thought...
This is what I'm running right now:
http://www.gonad.org/upload/images/240x10.jpg
LDT @ 2.5, Ram 1:1 slot 1&3 :up:
schroet, you could have linked to your 2nd post.
no offence.
I'll do that from now on, thanks for the heads up :toast:Quote:
Originally posted by Goldlocke
schroet, you could have linked to your 2nd post.
no offence.
Any idea if this affects Socket 940 Opterons and Athlon FX'es?
I'm going to buy:
Opteron 240
ASUS SK8V
512MB PC2700 Regd'ed ECC.
I'd prefer Opteron so I can move back into Dual heaven later on, and having a server processor makes you feel so much more badarse :)
Last thing you want is your machine crashing at 12 midnight in a middle of a game
U're probably right mate, this could be an issue but I've been using the same pots for alot of mods, including my 9800's ones and something like this has never happened before...Quote:
Originally posted by Goldlocke
could it be that your VR is not a 'precision VR'?
i mean, normal pots are supposed to stick to the before set resistance, but they don't guarantee linear resistance while actually TURNING the VR!!!
Only precision VRs are supposed to act in a linear way while changing.
So - if you change the resistance on the VR under current you take the risk of wrong values for a short time.
just a thought...
Better safe than sorry though, so no more "live" tuning for Vmem, :)
Never encountered any problems whilst raising the voltage, i just turned the VR's very very slow and the voltage came up nice without ever spiking or anything.
I used 2x 1K 15turn pots and had to give them a lot of turns to start off but then the increase in voltage happend faster and faster.
So once it goes over 3V turn it very gently, it will raise fast.
Hey Jeff I didn't have that happen to me last week ( heheh)...Quote:
Originally posted by Jeff
Sorry for being on the rag today but I know of at least two other threads that would have benefitted from some A64 "brainstorming" where basically nobody replied. If people are affraid of sounding like an idiot, get over it... I'd rather hear from an idiot than from nobody at all(or someone after the fact saying "yeah, I had that happen to me a few weeks ago"). ;)
I dunno why it's dying bro, but I would hope someone that had it happen would chime in as Randy and Bowman have......
Good to see you guys.
m
Anyone killed an A64 specifically by raising the 3.3v rail too high? My vdimm is chillin at 3.38v right now, but I'm still having issues getting my memory bus up very high, i have to run a 4:3 divider or higher, my HTT bus doesnt have any problem going up now, but still not much luck on the mem bus. Only getting about 210mhz at 3.38v 2-2-2-5 and this is bh-5?? what gives?
Try and take 1 block of memory out and only use 1 stick in slot1.
Ya i already know that that allows me a higher mem bus now...but I'd rather take a hit on my mem speed then have to go down to only 512megs...Planetside would die...
just wanted u guys to know, the 3000+ CG stepping boxed is available by now
edit: its already a newcastle
You were right. RMA finally got approved yesterday. Don't know what the fault was though.Quote:
Originally posted by BMORIN
Sounds to me like you have a bad mobo that's doing the killing, but that's just a guess.
Well, glad to see that you isolated it. A mobo killing chips is not an easy thing to isolate.
is this chip good?....im new to amd64 though...need some advise... :D
i do. im running this an50r with no volt mods. i run my memory at 2.9v cpu 1.6v the rest set to auto. the oc is done thru the bios using 230x10 2.5 LDT 1:1 so far nothing has died? been about two months so far so good. ill let you gys know if anything dies from me using just what the bios has to offer?Quote:
Originally posted by Kosmic
Just curious, has anybody tried overclocking an A64 board without doing any extreme volt mods and just using the voltages in the bios?
Before you throw things at me for asking that, I'm just curious from a testing standpoint if anybody has killed anything just using bios settings.
Thanks,
Kosmic
later perc,
Very similar to mine.Quote:
Originally posted by BuLkHy
is this chip good?....im new to amd64 though...need some advise... :D
ada3200aep5ap
caamc 0347vpmw
9359625k30176
Not the best of clockers but i think it might be something to do with my psu. It did 2349mhz 3d on water 1.65v. In my gigabyte k8n. And 2269mhz on air.
i think my 3000+ cg newcastle is dying too, but why?
i got a vmodded an50r (vdimm/core) and changed the VRs live, but never had/noticed spikes (bios reading).
max vcore was like 1.75 and max vdimm 3.2, never went above. wtf is up with the 64s?!
but hey at least the cg was supposed to have an enhanced mem ctr l:stick: :D
friggin stuff, i'm pretty frustrated right now
One word: diodes.
Care to elaborate a bit on that?Quote:
Originally posted by STEvil
One word: diodes.
sure: 0.3v drop.
Hm I'm thinking of getting an A64 system, now I'm a bit scared of sudden deaths. :P
So is any NF3 board safe to overclock, because I don't want these damn pci/agp dividers. I got some kickass BH-5 ram here and I don't want it to end up at 200mhz :P
So what about NF3+High FSB+High Cpu Clocks ?
And maybe should I wait for socket 939 ? (don't have that much money)
I sat back for a bit to see different peoples results from the various NF3 boards.While the shuttle boards seemeed tempting because of their price, they also seemed flaky at times. I opted for the gigabyte K8n-pro and aside from a bios issue I had from the original revision of the board (which was resolved when i got a newer rev board) I hvaent had any other problems. As far as sudden death syndrome, I havent seen any of the symptoms, I have my 3.3v rail at 3.7, and my vdimm voltage at 3.35v and so far so good, only thing holding me back for now is my cooling solution. I havent really decided on the whole s939 thing, as I am not all that convined that dual channel is gonna help all that much, let alone the fact that all the 939 athlon64s will only have 512k l2 cache. So unless you wanna put down the "cache" for an 939 FX, I would recommend sticking with the s754 solution, as it seems it'll be around for awhile.
oh btw: High HTT frequencies dont really seem to bother asny of my system components, just look at my sig for my clocks :)
So I should get a Gigabyte board ? What mods did you do to it ? And on what cooling are you ?
I would definately recommend it, im sure alot on here would agree with me, its a solid board, a lot of features and until I got this board, I never like gigabyte. As far as mods, I modded my 3.3v rail on my PSU, did the vcore mod, and also did vdimm. I'm only on a lowly koolance exos with an extra radiator looped in, it cools my cpu, chipset, and GPU for my radeon 9800xt. Fully modded and overclocked, I'm at nearly 2.5ghz and broke 25K on 3dmark2k1 :D w00t
Hm please check my new Thread in "A64 sys, need advice" need some knowledge, I'll post some new questions
I have exactly the same steppingQuote:
Originally posted by BuLkHy
is this chip good?....im new to amd64 though...need some advise... :D
2800Mhz with 1.9v
my A64 runs with 3.35V-4.2V-dimm and 1.7V-2.1V-core --> no problems.
I just put together an A64 3200+ CAAPC CG with a Gigabyte K8Npro. The vdimm is modded to my +3.3v rail to give a constant 3.34v to the ram. So far with basic watercooling and vcore mod I can do 253x10 math stable, and 250x10 3D stable all at 2.5x LDT. I was able to get 230x10 at stock voltage. Gonna do the vcore mod soon, and get this CG up to atleast 2.7ghz , hopefully further.
At 1:1 my 2x512 oc pc3200 OCZ eb did 261x9 2.5-2-2-11. With a bios update to F12 I was able to get my Mushkin L2's to 267 2-2-2-11. I hear a lot of other boards have problems with 512 sticks, but the K8N just gobbles em up no prob.
I was a little worried at first to, but I have had smoothe sailing. I am quite enjoying this board. Didn't have this much fun with my P4C800-E and 3.2C or 2.4C
my 3200+ runs at 2600mhz 1.7v, mem 3.4v 260x10, rock stable:)
it does 2800mhz at 1.9v no probs.
so far so good with my shutle:D
whats the max this baby can go on a possible abit ultra 250 board?
i think it depends wich cooler u use and the cpu...
i give u one exp.... mine gives 2800mhz and i have a friend with prommy aswell that only goes to 2750mhz:rolleyes:
and the mobs are the same:)....
my opinion, its like amd´s....its pure lucky:)
thanks crazy
So is 3.2VDIMM and 2Vcore safe on a bencg rig with chilled water? Can I use a bit more Vcore if needed?
Mobo is a VNF3-250.
I have a pretty nice 3000+ and I cnat afford to replace it.
i think vdimm its ok, but 2vcore:eek: ....Quote:
Originally posted by afireinside
So is 3.2VDIMM and 2Vcore safe on a bencg rig with chilled water? Can I use a bit more Vcore if needed?
Mobo is a VNF3-250.
I have a pretty nice 3000+ and I cnat afford to replace it.
u like ur cpu??:p:
the max that mine works its a 1.9v... i tried 2v, and even 2.1v and don´t make diference...;)
.15V probley wont get me much more :p: We will see...
did u guys experience with the same voltage but diff cooler gives u diff result?....
when i was getting +2C celcius at 2.655ghz....1.78vcore...it is nv stable... oni for 2.6ghz stable...but with same voltage ...same clock... with 8c improvement ... -6C LOAD... 2.677ghz stable....
nah...i have a prommy modded with r404:D ...Quote:
Originally posted by BuLkHy
did u guys experience with the same voltage but diff cooler gives u diff result?....
when i was getting +2C celcius at 2.655ghz....1.78vcore...it is nv stable... oni for 2.6ghz stable...but with same voltage ...same clock... with 8c improvement ... -6C LOAD... 2.677ghz stable....
always at -56º:banana: ....(260x10, 1.7vcore), with folding@home working 100%, then drops to -50/49º stable 24h:)
so no point trying another cooler:p:
my cpu don´t pass the 2815mhz:(
Ok, I just got an Oddball stepping 3200+.. wondering if it will Overclock.. will have to find out:
The stepping is
ADA3200AEP5AP
DAAOC 0414RPCW
Anybody seen these before?
Looks interesting ;) , CO stepping, but very new. Good luck!Quote:
Originally posted by hag6br
Ok, I just got an Oddball stepping 3200+.. wondering if it will Overclock.. will have to find out:
The stepping is
ADA3200AEP5AP
DAAOC 0414RPCW
Anybody seen these before?
Quote:
Originally posted by hag6br
Ok, I just got an Oddball stepping 3200+.. wondering if it will Overclock.. will have to find out:
The stepping is
ADA3200AEP5AP
DAAOC 0414RPCW
Anybody seen these before?
The one I had managed 2.5 under a mach I, not quite as much as the Newcastle 3200+ did on boxed cooling :stick:
Well with new technology there is always the learning curve. Since many of the people on XS forums are into pushing their systems to the max it is natural for components to die prematurely. Such is the nature of the game. How do you know how far is too far if you don't try it?
I just hope people don't read threads like this and think that AMD64 CPUs are unreliable in any way. Yes they require very very good DDR in order to function at a high level reliably. This is the price you pay for having a super fast on-CPU memory controller (rather than a chipset based controller as was the norm).
would it be possible so summarize the general findings of this thread?
It a bit of a long read 8pages!
I didnt bother reading the whole thread, but at this point it is now common knowlege that DO NOT raise the vdimm past 2.9v and dont do any mods, especially not vdimm mods! The a64's ondie memory controller hates 3v and higher. I wont tell you not to vdimm mod, some will for high benchmarks but they pay the price in dead cpus. keep the vdimm at 2.9 or below even if you can get higher
actually its not common knowledge because there are several people that have been running 3.2v+ with no problem.
Thread resurrection is bad.
No, many people vdimm mod and go higher. I've been running mine at 3.5v for a month without any signs of a problem. Also you I've read that you're looking at the Chaintech 250. Just to let you know I've never seen anyone happy with that boardQuote:
Originally posted by Geforce4ti4200
I didnt bother reading the whole thread, but at this point it is now common knowlege that DO NOT raise the vdimm past 2.9v and dont do any mods, especially not vdimm mods! The a64's ondie memory controller hates 3v and higher. I wont tell you not to vdimm mod, some will for high benchmarks but they pay the price in dead cpus. keep the vdimm at 2.9 or below even if you can get higher
so I guess me running 3.3vdimm for a few months 24/7 is just a fluke? :rolleyes:Quote:
Originally posted by Geforce4ti4200
I didnt bother reading the whole thread, but at this point it is now common knowlege that DO NOT raise the vdimm past 2.9v and dont do any mods, especially not vdimm mods! The a64's ondie memory controller hates 3v and higher. I wont tell you not to vdimm mod, some will for high benchmarks but they pay the price in dead cpus. keep the vdimm at 2.9 or below even if you can get higher
Quote:
Originally posted by rro
would it be possible so summarize the general findings of this thread?
It a bit of a long read 8pages!
yes.. high vdimm (3.3v) is okay for 24/7 use.. high 3.3v line (3.6V +) is bad but up until a few month ago it was needed. At least for the gigabyte series :)
eshbash needs to read this thread, I can vouch for him, he lost 2 a64s to high vdimm volts of 3.2v or $700+ of cpus in 3 months. hes mad and done with vdimm mods! what is so bad about the chaintech? the only other alternative is the epox at $40 more and that one seems to be even worse :(
hmm my 3 months at 3.6V 24/7 on an AN50R must be a miracle then :rolleyes:Quote:
Originally posted by Geforce4ti4200
I didnt bother reading the whole thread, but at this point it is now common knowlege that DO NOT raise the vdimm past 2.9v and dont do any mods, especially not vdimm mods! The a64's ondie memory controller hates 3v and higher. I wont tell you not to vdimm mod, some will for high benchmarks but they pay the price in dead cpus. keep the vdimm at 2.9 or below even if you can get higher
It's just like the guy at OCAU... Pulling unsubstantiated facts from thin air to make a point. And on both occasions, from people who don't have A64 setups :rolleyes:
My AN50R is Vdimm modded, i'm pushing 3.15V trough the mem 24/7 for 3 months now, have been as high as 3.3V for benches, still everything works 100% ok.
The difference is in the Vmod itself and the way of increasing voltage methinks.
Oh, and indeed, that Chaintech board sucks, why not just go for the older NF3 150?
Anyone ever noticed a difference?
I think I may have killed my 3000+. I was bored this morning and wanted to do some benchmarking and stuff so I pumped up my vcore to 1.82v and vdimm to 3.1v using my trimmers (normally I run 1.75v and 3.0v) to try for my maximum benchable OC. After having not much luck improving on my current 2.5ghz I quit and turned back down the voltages. Then I started up again at my normal speeds and I was playing BF Vietnam and my system went to a black screen. I thought that was wierd and rebooted and tried again and the same thing after about 10 minutes. I rebooted and did Prime 95 which failed in under a minute when I am normally stable. Dropped my OC down to 2.4 from 2.5 and it failed as well. Tried again at 2.2ghz and after a few minutes my system went to a black screen again. Temps never above 45C even under load with my watercooling. Sounds bad doesn't it?
Update: Looks like it was a false alarm. Unplugged everything and let it sit overnight and now everything is working fine again. Weird.
I've been running 3.3Vdimm for about 2 months no probs, recently bumped upto 3.4Vdimm. I doubt the 3.3Vrail affects the CPU at all. Maybe the mobo.
Well, I really hope my FX53 is not going to die from high Vdimm voltages (I don't plan to go over 2.9v) and hopefully it gets along well with the NForce 3 250 chipset. *Crosses fingers*
i know a dude who is running 3.8vdimm for..... 4 months on his a64 now, no problem at all...
Hm I'm guessing there's still no real conclusion here, some say high I/O voltage is bad, others say that this voltage doesn't affect the cpu at all. So what's right and what is wrong ? help me ! :(
who said a high 3.3v rail is bad? :confused: only hjas_bjorth mentioned that and im not sure what he means but afaik a high 3.3v rail doesnt matter at all.Quote:
Originally posted by sai
Hm I'm guessing there's still no real conclusion here, some say high I/O voltage is bad, others say that this voltage doesn't affect the cpu at all. So what's right and what is wrong ? help me ! :(
just like most people here mentioned most of the cpus probably died from either bad mods ,bad mobo design or stupidity from using the bios to set a higher vdimm when you have a vdimm mod in place. all 3 things probably resulted in vdimm fluctuations wich killed the cpus.
my theory is that its a vref/vdimm problem. as most of you know all the new boards (afaik) have a fixed vref , or vref doesnt increase past ~1.4v (2.8v vdimm)
sometimes (:D) mobo makers know more than us and im sure they found out that an unbalance of vdimm and vref killed the onboard memory controller. that would perfectly explain all ive heard about it so far. a bad mod (too high pot=too big increasment from a small turn) a bad mobo design or chaning vdimm in bios when a mod was in place probably resulted in a fast jump in vdimm and short but strong fluctuations. vref probably couldnt keep trck and was still low while vdimm jumped up. then vref jumped up to keep track, but vdimm dropped down (fluctuations) and vref and vdimm bounced like this very fast for just a milisecond wich was enough to get vref high and vdimm low.
we all know about the dead video memory on videocards from too much vref, and i think its the same thing we are seeing here. maybe it wasnt really the memory that died on our videocards like everybody always believed, maybe it was the onboard memory controller of the gpus that died from too much vref, just like the memory controllers of the a64s are possibly dioeing from too much vref nowadays.
again vref alone doesnt matter. it only gets dangerous when it is more than 50% of vdimm, this also explains why some people can run such a high vdimm without a problem. either vref doesnt keep track and stays low while vdimm is high=no problem , or vref does keep track, but it always stays at 50% of vdimm, so its fine.
if this is true then on most boards running vdimm above 2.8v is even safer than running 2.8v! because on most boards vref doesnt increase afaik, so if you increase vdimm the cahnces that vref wich is fixed at ~1.4v gets higher than 50% than vdimm by accident or a fluctuation gets lower the higher vdimm is :)
just an idear :)
Can anyone put their word that running 3.3volts through the ram will NOT kill the cpu?
Mixed opinions here, what out ways what?
just read this last page, there are more than 6 people here who have run 3.3v or higher for months.
thats safe enough for me...
now i wish i had an a64 to prove it as well :/
good enough for me :D
good enough for me :D
been running 3v + since january and 3.3+ since march.. and yes saaya.. thats what I meant :)
hehe, I benched my 3400 with 3.9 running through the ram and it didn't die :banana: And I run it at 3.5v 24/7 and it still lives :)