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