Printable View
Has anyone figured out what is killing all these A64's? Seems like I hear alot of people getting inexplicable failures on them - running them a day or two then losing them. Has anyone isolated some areas that seem suspicious.
Thought I'd get a little feeback here before I put one together this week.
:confused: Great and I just ordered mine yesterday
have you noticed most of these deaths are at extreme temps and high voltages? ;)Quote:
Originally posted by BMORIN
Has anyone figured out what is killing all these A64's? Seems like I hear alot of people getting inexplicable failures on them - running them a day or two then losing them. Has anyone isolated some areas that seem suspicious.
Thought I'd get a little feeback here before I put one together this week.
Quite possibly to do with high RAM voltages as well as it kills the MMU on the A64...
Talk to bowman about this - he's had some die at stock voltages too and fast. A weird phenomena for sure...and one that gets expensive.
.
I have lost 6 as of right now....some were high voltage,some stock,some extreeme cold,some not....but all were on my chaintech motherboard(except one that died from a known problem..power suppy blowing up)...and all die from the onchip mem controller dieing...
the chaintech i was trying to figure out why it is killing them.the cpu and mem mod was off and stock voltage the last 2 that died.
powersuppy on the last couple was running 3.33v 5.25v 12.24v so i know it wasnt that.and if the chips are going out because of a high 3.3 line then someone needs to fix something..because if i am not wrong...the spec motherboard and powersupply makers go by is 3.3v 5.0v 12.0v and thay all are allowed a 10% margin of differance...and that would =3.63v on the high side.
then i relized the chaintech ..i had modded the chipset...the nf3 chipset was modded and set to 2.2v...this has to have a direct relation to the chips dieing...
but i am not going to try my idea and remove the mod and then try another chip...not right now at least.
i am whating on another 3400 to play on and thats it for a while...
6 = gotta be that board or more likely the chipset mod.
Must be the board. That's just too many chips for them all to be defective.
so am i right to assume that it is the vDimm that is killing the A64s as a result of the onboard mem controler?
thanks.
Thats expensive man, like 6 X $400 at least $1200-$2400
:slobber:
.
I think Bowman was saying it may have been the "Chipset Mod" that was to blame. Not a vdim mod.Quote:
Originally posted by Total Immortal
so am i right to assume that it is the vDimm that is killing the A64s as a result of the onboard mem controler?
thanks.
well i have posted in a few threads about mine....
but i dont have time alot to check the threads at work.....i do have to work...not play all day...so i hope that wasnt directed to me...:confused:
i ran accoss this one by accident....and i am still not sure on the death issue.....i have 3 boards so i am not going back to the chaintech until i get chaintech to take a look at it...i have emailed the company direct.
all i know for sure it is the mem control going out..not the basic cpu.
it starts with lots of windows errors and then it wont reload a fresh copy of windows.i pulled 2 chips from the chaintech after the first errors accured.and one just contunied to reboot....all the time..one the gigabyte it would almost make it to the desktop and then it rebooted...in the shuttle it just rebooted constantly...
the other chip started just getting errors in my wndows until i rebooted it one more time..and then i got the black screen of a64death...
so they are fun to play with...and yep i have depleted my funds...i got caught up in getting one to bench with,,and the mader i got the more determaned i got to get one going...and the more i purchaced....
after my chips come in next week i want to weed out the weeker ones and keep one setup...sell off the rest at reduced price to get something back..
and yes...the chipset voltage is the only thing the chaintech has that the shuttle and gigabyte dont/
so i am leaning towards high chipset voltage doing it...since that is directly connected to the hypertransport..
I'm on A64 # 5.
As Bowman, mine have all died on an Nforce3 board, The Shuttle AN50R.
I did run crazy high voltages to the memory on mine, for obvious reasons. I also run a high 3.3v line, many times in the 3.5v range.
My assumption is I took out the memory controller. 1 of the 4 dead CPU's stopped my debug card at "detecting the memory". The last one lasted a day....not even pushed except with 3.5v+ to the memory, low multi high FSB under 2.2ghz. It ran fine that night, shut it off, next day no post. FF on the debug card...swapped the chip to an Abit KV8-Max 3...same thing...FF.
I haven't pushed high Vcore thru mine..1.79v max at 2400Mhz.
I have my latest residing on the KV8-Max3 for now, as I'm trying to see what kind of performance I can wring out of it, not many have messed with this board, and I've had it for months now. The Shuttle was too easy to push the FSB and fun...but at the expense of me killing CPU's. No doubt I'll prolly be working with that board soon again but with a little less volts;)
Randi:D
Certainly a cause of some concern..
Anybody else willing to admit to joining the 1337 band who have killed an A64?
I was thinking that it might have something to do with the psu rails or chipset voltage. But obviously Mr. Icee hasn't done anything with the chipset.
I've noticed that CCC is going strong with his 3400+ running 3.6vdimm and high FSB on An50r, but I think he's keeping his rails conservative. No need for increased 3.3v on that board. Maybe the 3400+ is just a little better chip, I don't know.
One thing I haven't heard anyone talk about is the possibility of extreme cold killing these things. Don't know if that could have anything to do with it since most people on the forum are using phase change, period.
How many people have lost this chip on stock cooling? And yes I'm surprised this issue hasn't surfaced as a thread already.
Here's an addendum: the 1 A64 that I had great luck with and lasted the longest(1 month+) was an older CAAKC. The others died much faster and endured only a few hours of playtime before they would not post, those 3 were CAAMC, same as the one I recieved yesterday.
Randi:D
Try and keep it till the weekend at least m8 :P
i have a running list of all my chips that i own and which ones died so far..i can post tonight if anyone wants to see...
Has anyone had this happen on a Via board?
I´m starting to have exactly the same problem. Have vcore and vdim mods done.Quote:
Originally posted by bowman1964
it starts with lots of windows errors and then it wont reload a fresh copy of windows. one the gigabyte it would almost make it to the desktop and then it rebooted...
Problem started when I tried to increase vdim from 3V up
MOBO: K8N Pro
CPU: A64 3000+
I can only confirm tomorrow night if CPU is KO or not
I hate to say it, but it's pretty obvious that these chips don't like high voltage like the Athlon XP did. So if you want to keep your chip and not hose your system, keep the voltages down.
i'v benched with mine 3200+ with +3.3v @ 3.8v and with v-dimm @ 3.5+- several times and it's all ok
i'v tested with asus k8v and gigabyte k8n np
i'm waiting for a 3.4+ let's see if it lives :S
regards
Well, when I get my K8N Pro or AN50R I'm not going to volt mod it because I can't afford to buy even one extra cpu.
Will the maximum voltages that are allowed in the K8N/AN50R bios not kill the cpu?
.
mine was due to being stupid, smoldered my board, litterally. i rma'd it.. no prob.. and if my cpu dies.. id rma that too.. not cost out of pocket but 5 bucks for shipping, which i will do from work, for free. after reading this i sure as hell am goign to turn my rails down tho =)
curious tried useing memtest86 3.0 and memtest86+ 1.0 with these dying or dead cpus when they showed these windows booting symptoms ? - just trying to get an idea of memtest reported errors/symptoms.. as i don't load windows with my systems until i can get memtest errror free for a few days hehQuote:
Originally posted by bowman1964
well i have posted in a few threads about mine....
but i dont have time alot to check the threads at work.....i do have to work...not play all day...so i hope that wasnt directed to me...:confused:
i ran accoss this one by accident....and i am still not sure on the death issue.....i have 3 boards so i am not going back to the chaintech until i get chaintech to take a look at it...i have emailed the company direct.
all i know for sure it is the mem control going out..not the basic cpu.
it starts with lots of windows errors and then it wont reload a fresh copy of windows.i pulled 2 chips from the chaintech after the first errors accured.and one just contunied to reboot....all the time..one the gigabyte it would almost make it to the desktop and then it rebooted...in the shuttle it just rebooted constantly...
the other chip started just getting errors in my wndows until i rebooted it one more time..and then i got the black screen of a64death...
so they are fun to play with...and yep i have depleted my funds...i got caught up in getting one to bench with,,and the mader i got the more determaned i got to get one going...and the more i purchaced....
after my chips come in next week i want to weed out the weeker ones and keep one setup...sell off the rest at reduced price to get something back..
and yes...the chipset voltage is the only thing the chaintech has that the shuttle and gigabyte dont/
so i am leaning towards high chipset voltage doing it...since that is directly connected to the hypertransport..
Ive had one died on me and I think its the same reason as MrIcee, toasted memory controller.......at that time I was using the stock cooler and 1.7v and ran my vdimm to around 3.5v..... during 3dmark, it died on me....... my second one with my chiller cooling it is still alive and has done benches at 4v vdimm and 2v on the vcore...... if you guys are planning to run some high vdimm, make sure your cpu is cooled well.......
It´s not a cooling problem I guess. Mine was cooled by promy @ R404a.
looks like there are good and bad chips...
Remember, that the 3.3v rail is generally used for the system I/O, I'd guess a high 3.3v rail could easily kill the I/O of the chip, I.E. the memory controller, makes sense to me.
yeah, much like high vDIMM. Also with the chipset being linked directly to the Hypertransport bus, high chipset voltage can cause problems, as bowman has proved.Quote:
Originally posted by Walrusbonzo
Remember, that the 3.3v rail is generally used for the system I/O, I'd guess a high 3.3v rail could easily kill the I/O of the chip, I.E. the memory controller, makes sense to me.
*Interesting thread, hits subscribe button*
I'm sceptical of High VDimm.... VDimm should only affect the RAM's voltage, I can only think that on the boards that people have done VDimm mods it must be affecting another voltage, I.E. Hypertransport.
Definitely though, high chipset V, high hypertransport V and high 3.3v, DONT DO IT :)
Well, so far, it seems to safe to say that it's not the wisest thing to raise the chipset voltage or the 3.3v rail.
But one thing none of use will ever stay safe on is vdimm - no matter the risk, lol. There some guys running extreme vdimm with no problem yet. I'm thinking this may have more to do with the stepping on the 3200+ than we think.
I'm also very curios about the 3400+. I know not many have this chip yet, but it doesn't seem anyone has killed this one yet. Has anyone used the 3400+ with a high 3.3v, Vchipset, & vdimm?
LUIHED, was there a difference in stepping between the one you killed and the one you currently have that is running strong along with a 4v vdimm?
Has anyone experienced this with the FX?
YEP i killed one 2 days after they hit....:(Quote:
Originally posted by BMORIN
I'm also very curios about the 3400+. I know not many have this chip yet, but it doesn't seem anyone has killed this one yet.
.
I asked about the FX wondering if it's the memory controller that's burning up.
Quote:
Originally posted by Jeff
No offense Bowman but... maybe you should try a new hobby. :stick: ;)
...[/i]
you got that right.......i sure do need to go back to bass fishing...but spent money on that too.;)
I still do both but it is realy stretching the budget! I'll trade you a guided day on Buggs Island for one of those dual evaps!Quote:
Originally posted by bowman1964
you got that right.......i sure do need to go back to bass fishing...but spent money on that too.;)
sounds very familiar to me - allthough I´v fixed the problem by not keeping DMI data.. very odd actually..:rolleyes:Quote:
Originally posted by bowman1964
it starts with lots of windows errors and then it wont reload a fresh copy of windows.i pulled 2 chips from the chaintech after the first errors accured.and one just contunied to reboot....all the time..one the gigabyte it would almost make it to the desktop and then it rebooted...in the shuttle it just rebooted constantly...
i killed my cpu last night.. first my board in 43 min 2 days ago, rma for new board then my cpu after a couple hours. i booted up to bios and noticed 3.78 on the vdim.. oops.. i must have tutrned the vr wrong way. tunr off. disconect pot, boot back up into bios. turn the pot which would be lowiring it, touch it to ground poof. off goes comp. hmm thats wierd i say. check the the pot and it was at 1.0 wonder how much volts that was? to many i guess... doesnt boot up, rma'd both. so ive killed a mobo and now ive killed a cpui/mobo (dont know which but i suspect the cpu) sent back both anyweays, replacement in a couple days.
3400+
AN50R
Have you posted it yet? On another thread?Quote:
Originally posted by bowman1964
i have a running list of all my chips that i own and which ones died so far..i can post tonight if anyone wants to see...
You people, well Opp, Mr Ice and Bowman must be made of money if you can go through 6 A64's and still buy more !:slobber:
I would be extremely happy if I had one A64!
Can anyone donate a A64 to a poor college student? I would be very greatfull! :D :D
are you that good of a guide...LOLQuote:
Originally posted by 2fast4u
I still do both but it is realy stretching the budget! I'll trade you a guided day on Buggs Island for one of those dual evaps!
it may be worth it...you may get a pm from me in the spring..i need to get my 21ft stratus back out on the water...LOl:D
as far as the stepping on the ones i have murdered..here goes.
3200's
caakc week 33 still alive
caamc week 43 brown
caamc week 41 brown
caamc week 39
caakc week 30
caamc week 42
lost a 3400 but i cannt find the stepping..i will look
they all died from the chipset mod on the chaintech..i am sure..
it was running 2.2v all the time..i had forgot i had it that high...
it is directly tied to the hypertransport and mem controller..i havent had any trouble since i stoped using the chaintech.
Me too. I am afraid the tires on my trailer are flatspotteed from sitting in the garage for 2 months! I would take you just for a chance to pick your brain, but you could throw in the dual evap if you wanted too! heheheheQuote:
Originally posted by bowman1964
are you that good of a guide...LOL
it may be worth it...you may get a pm from me in the spring..i need to get my 21ft stratus back out on the water...LOl:D
as
Is this related to the Inductive heating problem and are there hot spots within the memory controller? Is this related to the SOI layer? Have there been any nonmemory modded processors failing? how many?
I killed a 3000+ (week 29) and a 3200+ (week 47)so far.
I removed the Heatspreader from both CPU's.
The 3200+ produces memory errors, ( Vdimm was @ 3.7V )
The 3000+ does nothing anymore.
I don't think high 3.3V rails kill the CPU's, cuz the 3200+ died on a shuttle an50r which needs no PSU mod on 3.3V.
.
I'm thinking it could be the high Vddr that is killing all those A64's,
Maybe there's a simple solution to it:
On my k8v a thick trace is going to the cpu from the mem that is reading the same value of my Vddr. Is it possible to cut this trace and put a wire on it (on the cpu side) that gives 3.0V to the memcontroller on the cpu?
The 3V could be generated from a second psu or from a self build circuit with a LM regulator.
I'm thinking moreso that it's mainly to do with the NF3 boards. As I've yet to see anyone killing a CPU/MOBO with the K8T800 by running a high 3,3 line or high vdimm.
Correct me if I'm wrong please though :)
YoupY:
Your idea doesn't seem bad at all, but considering all the excess work to even get that done I would rather just kill the board and RMA it :D
Seems like I got a good stepping from newegg for my A64 3200+,
CAAKC week 37 :) wish me luck :toast:
I wish you luck :toast:
Those are quite some frightning stories, but there's not so many chance that I'll run my cpu up so high... (haven't picked up an A64 yet, but planning to...)
so its a weak point in the nf3 design? guess it has to do with the vmods as mm suggests...
I killed my first A64 3200+ on my an50r
i got the stupid blue screen error of death when trying to boot into windows.
I tried two different hd's, had no luck.
i had my chip at 1.66v and my vdimm at 3.6v
my vdd was kept on auto the whole time.
Im thinking its my vdimm that killed the chip.
I have 2 questions:
1) Has anyone killed one WITHOUT doing the vdimm mod?
2) Has anyone killed one on a VIA chipset?
1: I believe Bowman has
2: dont think so yet
:-)
MickeyMouse your idea worked perfectly, only reason my CPU died was cause of my stupidity.
I did the mod so perfectly, I was so proud of myself.
Set the VR 1.984K Ohm, booted in @ 3,17 Vdimm stable.
Then windows rebooted for some weird reason so I thought I would "fix" the problem by changing VDDR from "auto" to 2.6
ROFL did not help at all!!
Next thing I know I'm reading the mosfet and its spiking upwards 3,78 and then randomly falling and flying up again in a span of 5 seconds.
I was like "OMG NOOO STOP CPU YOU NOT SPOSE TO DO THAT!!"
But now she won't boot so I got an RMA approved to send her remains back :)
EDIT: Yes I'm on a K8V Deluxe K8T800 and I have a VMod on my board and I'm pretty sure my CPU is dead dead dead ;)
PRanganathan, nice job on reading those voltages while it was happening. I think that's the first real proof we've seen all this time of a possible voltage malfunction causing this.
so let me get this right.
if we leave it to auto, then it's all fine? because mine was working fine until i changed it from auto to 2.7 which really was 3.6v
i cant decide to keep my shuttle motherboard or not, i just took off the vdimm and vcore mods?
So you mod the board, kill the hardware, then RMA what you killed. Did you take the mods off or do you send it back as is??Quote:
But now she won't boot so I got an RMA approved to send her remains back
I was reading in a forum a couple days ago, one place didnt accept a guys MB on RMA, they are starting to look for known solder points i guess. They caught it, and asked if he would like to pay for return shipping on his Modded board.
Guess retailers are getting tired of this.
But good luck with your RMA.
Quote:
Originally posted by Tedinde
So you mod the board, kill the hardware, then RMA what you killed. Did you take the mods off or do you send it back as is??
I was reading in a forum a couple days ago, one place didnt accept a guys MB on RMA, they are starting to look for known solder points i guess. They caught it, and asked if he would like to pay for return shipping on his Modded board.
Guess retailers are getting tired of this.
But good luck with your RMA.
Bad thing is all deaths caused my botched mods, and over stressed components, then RMA'd is going to make it damn difficult for legit returns. If ya can't afford the loss you shouldn't be doing it.....
First, removing solder = easy.
All you do is apply heat, and use a bulb to suck up the hot solder.
Easy as that.
Second my board still works fine, just the stupid CPU that died.
Oh ya I forgot my third point.
Point #3: It seems those of us with Vmods have very stable Power Supplies that don't have fluctuating voltages going thru our lines.
Many of our Power Supplies are of very high quality: PC Power & Cooling for example.
Before I even started the VDimm mod on my board, I checked my 12v, 5v, and 3,3V lines. Because my Asus Probe was reading my 12v and 5v lines very low.
Just to make sure I checked the 12v and 5v thru the molex, both came out rock stable 12v was @ 12.08V, and 5v was @ 5,04v.
My 3,3 line was perfect also coming in @ 3,31V (measured thru mosfet)
When my VDDR was in "auto" my VDimm line never fluctated, always stayed very stable @ 3,17 Vdimm. It was only when I set it to 2,6 Vdimm that my volts started going out of control, upwards 3,78 VDimm which eventually killed the onboard controller on my CPU.
It seems that while the Motherboard can handle the volt spikings for a longer period of time being showing signs of wearing down, the CPU cannot because of mem controller being inside the CPU (which of course we all know :)). So the only solution to this problem as of right now, as MickeyMouse stated, is to always leave your VDDR @ "auto" NEVER EVER CHANGE IT! If you need to change your Vdimm volts ALWAYS change it thru your Volt Mod and not through your Bios.
Everything else will be peachy!
Well, it will be interesting to see if we continue to get deaths after people follow this advice.
Only thing I killed was the CPU, no mods were done to it.Quote:
Originally posted by Tedinde
So you mod the board, kill the hardware, then RMA what you killed. Did you take the mods off or do you send it back as is??
I was reading in a forum a couple days ago, one place didnt accept a guys MB on RMA, they are starting to look for known solder points i guess. They caught it, and asked if he would like to pay for return shipping on his Modded board.
Guess retailers are getting tired of this.
But good luck with your RMA.
I sent it to them with the TIM still applied on the CPU and fan, just to let them know I used the stock HSF.
I don't see why you guys are against Vmodding boards and sending it for RMA.
First off they get products at retailer prices, they still make a big margin of profits off of selling it to us.
Secondly only a very small percent of customers RMA their product, compared to the percent of people who buy the product.
I know honesty, and being a nice good boy is what most people want to see. But frankly I know that the company can afford to send me a new motherboard because the one I got didn't meet my expectations ;) .
To be completely honest, I think the more they start receiving Vmodded mobo's the more they realize they should just give in to us and let us use higher volts thru bios.
overclocking IS against the warrenty and RMAing something that you've voided the warrenty on it really stealing....Quote:
Originally posted by PRanganathan
Only thing I killed was the CPU, no mods were done to it.
I sent it to them with the TIM still applied on the CPU and fan, just to let them know I used the stock HSF.
I don't see why you guys are against Vmodding boards and sending it for RMA.
First off they get products at retailer prices, they still make a big margin of profits off of selling it to us.
Secondly only a very small percent of customers RMA their product, compared to the percent of people who buy the product.
I know honesty, and being a nice good boy is what most people want to see. But frankly I know that the company can afford to send me a new motherboard because the one I got didn't meet my expectations ;) .
To be completely honest, I think the more they start receiving Vmodded mobo's the more they realize they should just give in to us and let us use higher volts thru bios.
im a overclocker to, but never sent something back that I broke
Thats very true, kudos to you on noting that.
But it still doesn't change my perspective on RMA'ing parts that don't meet my expectations.
Buy a car lately? If it doesn't meet your expectations would you keep it? I wouldn't, because when I pay for something I have certain criterias that must be met, if they don't meet them then the manufacturer hasn't fulfilled his end of the deal, as a result I don't fulfill my end of the deal as an end user.
What if a manufacturer did not come close to your expectation but did not advertise as such to start with? I mean if you have bought Honda Accord expecting to do an engine modification to be able to run 250 miles per hour. And when it doesn't you think they would accept the return of a burned out car if they could prove what you have done???Quote:
I wouldn't, because when I pay for something I have certain criterias that must be met, if they don't meet them then the manufacturer hasn't fulfilled his end of the deal, as a result I don't fulfill my end of the deal as an end user.
Would you tell to RMA guy when you are doing RMA that the CPU/mobo died because of what has been done or you just pretend it was all by default?
I find this RMAing to be a fraud much like insurance fraud people do with cars. If this was more of a mainstream activity I think there would be laws on books to penalize it. It might be anyway but the guys that do this are lucky that manufacturers/resellers aren't interested to chase small time crooks for one CPU. In either case it is certainly unethical at least.
this forum is called "Xtremesystems", not "RMA ethics"!
Joe and Overlag go back to http://www.community.tomshardware.com ;)
I didn't really intend to discuss ethics, just the fact that he claims, for some reason, how he is right to do the return while manufacturer "did not fulfill his expectation." Ridiculous at least.
If one expects somebody else to take the financial responsibility for one's botched hardware experiments that one ought not to expect everybody else to buy his infantile reasoning.
@ wich point ill have to measure the vdimm with a multimeter?
ill set the vdimm in bios to 2,9v then via VR up to 3,6v:eek:
exacty hotwheelz! look here @ OC.at ;)
CONFIRMED!
Over @ OC.at we too got a little "A64 killer". Hotwheelz just confirmed PR's findings about highly fluctuating VDimm when set at 2.9V in bios!here he states fluctuation from 3.1V to 3.8V. Already killed a 3200+ and a 3400+ :eek:
(owned by himself ;) )
So ill have a Shuttle AN50R
In Bios i set the vdimm to 2,9v and then with the VR up to 3,1v
when i measure the vdimm its jumping from 3,1 up to 3,8v
:eek:
and my two A64 (3200+ / 3400+) wont go higher then 2500mhz with mach2 so ill killed them!:stick: :(
Noooo don't kill them :(Quote:
Originally posted by hotwheelz
So ill have a Shuttle AN50R
In Bios i set the vdimm to 2,9v and then with the VR up to 3,1v
when i measure the vdimm its jumping from 3,1 up to 3,8v
:eek:
and my two A64 (3200+ / 3400+) wont go higher then 2500mhz with mach2 so ill killed them!:stick: :(
Set your VDDR in bios to 'auto', using your trimmers increase/decrease your voltage running through your ram.
If you want a stable VMod instead of using the 50K trimmer, just use either 2x 1K 15 turns, or a 1K 15 turn VR + 1k resistor in conjunction, the mod will be stable, and not to mention save you time from having to turn your VR 50 million times ;).
Joe, to be honest if you think my RMA'ing "botched" parts is "fraud", "dishonest", and "not reasonable", then you my friend are in the wrong place. I understand your point of view, and I have no quarrels with it. But you also need to remember that no matter how wrong or right you think something is, its still mainly your thought. You trying to either become a catalyst in changing my views or you trying to 'enlighten' me is not going to change my actions. In my mind I find my cause just, because I am trying to get the most performance out of a product any given manufactuer puts out and until they (the manufacturer's) start putting out more durable products I won't have any reason to stop what I'm doing.
That will be the end of that topic for me, I will no longer respond to this thread because we are here to OC not belittle one another :toast: .
Hmmm,...I took the time and did some measurements on the mosfet too.
I have NO FLUCTUATION. I set Vdimm bios setting from AUTO to 2.7V/2.8V and 2.9V giving me 3.08V/3.18V and so on effective VDimm. At no time was the V jumping here.
I even tried upping Vdd, VAGP, VLDT to the max.
2 thoughts:
1.) OK, I'm a coward - tested only up to 3.4V Vdimm.
2.) I got another PSU (that maybe produces no spikes?)
I don't think its the PSU's that are causing it.
And not being able to replicate the problem is weird.
Most of us were using around 3,4-3,6+ VDimm when we changed thru Bios from auto to 2,X
Even though you encountered no problem with that, I wouldn't advise you to keep doing that method to wait and see if your chip dies ;)
But I'm just happy you didn't roast your CPU lol :toast:
I think I noticed one similarity between all those dead chips, when the settings were changed everyone was running over 3,0+ volts thru VDimm when they decided to change it, and since your increment was only .10+ and you still started sub 3,0 VDimm, you were still in the safe because you weren't going over the spec'd VDimm supported by the CPU + M/B
dude, i overclock xtremely too, but i NEVER RMA something I broke...but then i dont steal things out of shops either......Quote:
Originally posted by Goldlocke
this forum is called "Xtremesystems", not "RMA ethics"!
Joe and Overlag go back to http://www.community.tomshardware.com ;)
overlag <---
yeah sure you do - It clearly shows in your sig. ;-)
anyway think you guys are missing the point between stealing and RMA. I´v believe that almost everybody besides you two saints tries to RMA their stuff. Broken by intention or not. Just to get something better - Yes maybe its a low standard to you guys but remember that next time you´r gonna exhange something (tv etc.) and pushed to get the next new product in line cause the one your having is outdated - I honestly dont believe you´ll settle for the average - No ofcause you want the best thing- Follow my drift?
But stealing - Thats a whole new catagory. :)
:rolleyes:Quote:
Originally posted by bias_hjorth
overlag <---
yeah sure you do - It clearly shows in your sig. ;-)
anyway think you guys are missing the point between stealing and RMA. I´v believe that almost everybody besides you two saints tries to RMA their stuff. Broken by intention or not. Just to get something better - Yes maybe its a low standard to you guys but remember that next time you´r gonna exhange something (tv etc.) and pushed to get the next new product in line cause the one your having is outdated - I honestly dont believe you´ll settle for the average - No ofcause you want the best thing- Follow my drift?
But stealing - Thats a whole new catagory. :)
so what, a board with no AGP/PCI lock, and a ATI9700pro that doesnt like over 72mhz AGP?
what am i supposed to do? get a freaking Geforce FX? :eek:
i taking a rest from extreme overclocking, im stuck at 10x215 with my A64 3200....
Quit crappin, stay on topic
When I killed my 3000+ I didn't have a VMod, but I was running at 2.9v on my AN50R...
hey Mrip, I know 2.9v doesnt require a mod, but did you have a vdimm mod?
Quote:
Originally posted by Overlag
:rolleyes:
so what, a board with no AGP/PCI lock, and a ATI9700pro that doesnt like over 72mhz AGP?
what am i supposed to do? get a freaking Geforce FX? :eek:
i taking a rest from extreme overclocking, im stuck at 10x215 with my A64 3200....
ROFL since when is 215 FSB xtreme? :D
kept me wondering to but did´nt mention it cause the dude should feel speciel ;)
sighQuote:
Originally posted by bias_hjorth
kept me wondering to but did´nt mention it cause the dude should feel speciel ;)
i said im taking a REST ffs :rolleyes: its a bit hard when yyour gfx card §§§§s up at 210 fsb :rolleyes:
and as BMORIN said, quit crapping, and stay on topic
Do you think your 9700pro is any better than a freaking FX5900u or FX5950u???Quote:
Originally posted by Overlag
:rolleyes:
what am i supposed to do? get a freaking Geforce FX? :eek:
I think not!! :rolleyes:
Just to stay ontopic; anyone killed his CPU on a nonmodded Shuttle AN50R board?
Quote:
Originally posted by Zeus
Do you think your 9700pro is any better than a freaking FX5900u or FX5950u???
I think not!! :rolleyes:
whatever....
...all this because i dont agree with RMA stuff that I broke, and dont agree with others doing so. :rolleyes: Tad sad IMO.. :rolleyes:
Not at all mate, it was just the way you talked about a geforce FX, like it was a pile of crap.
Everyone getting ATI cards doesn't mean the FX's aren't any good, plus they can take high AGP speed no sweat as an added bonus.
Whether you break it or not, there's a 15% restocking fee etailers apply to cover their own asses. Net result is - IT DOESN'T MATTER!
well yeah, i know that. But when i got my 9700pro, it was that or the 5800.... even now, id choose a 9800xt over a 5950u...and aparently newer ATI's can take FSB.Quote:
Originally posted by Zeus
Not at all mate, it was just the way you talked about a geforce FX, like it was a pile of crap.
Everyone getting ATI cards doesn't mean the FX's aren't any good, plus they can take high AGP speed no sweat as an added bonus.
im just disapointed on the amount of personal attacks at xtreme. This thread and the prescott thread are proof of this and im sure theres more. Coming from OCUK makes me used to being in a grown ups forum, where trouble makers (personal insults etc) are removed, making it a better alround place. sorry if you dont like my views on xtreme :(
true maybe... :toast:Quote:
Originally posted by WiCKeD
Whether you break it or not, there's a 15% restocking fee etailers apply to cover their own asses. Net result is - IT DOESN'T MATTER!
Quote:
Originally posted by Overlag
Coming from OCUK makes me used to being in a grown ups forum, where trouble makers (personal insults etc) are removed, making it a better alround place. sorry if you dont like my views on xtreme :(
true maybe... :toast:
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...
actually you guys are right at that point. Some of the newcomers seems to use the various forums for spam and already has almost twice the numbers in post the Im having - They think its about replying to as much post´s as possible and really practice the fanboyism. But hey its a public forum and everybody should have a chance -
(PS sry for beeing a part of destroying the thread but I just could stand some of the above post)
Ill stay on topic for now on..
is my a64 dead? memory controller dead?
I just sent a surge through my computer, my psu just sparked, its dead now.
right now im reformatting my hard drive with the same chip installed, new psu though.
i was able to boot to the windows setup repair screen and from there i reformatted. right now im about 40% done reformatting on the 120gig
is there still a possibility my a64 has fried its memory controller?
If your CPU fried its controller it wouldn't even boot, and since your actually using the same chip to re-do your HD your CPU is fine.Quote:
Originally posted by Alex08
is my a64 dead? memory controller dead?
I just sent a surge through my computer, my psu just sparked, its dead now.
right now im reformatting my hard drive with the same chip installed, new psu though.
i was able to boot to the windows setup repair screen and from there i reformatted. right now im about 40% done reformatting on the 120gig
is there still a possibility my a64 has fried its memory controller?
I killed 4 so far.
2 I have no idea what happend.
1 from running a 352 FSB.
not sure what happend there.
1 from running 3.7 volts into the ram.
the two mystery deaths AMD replaced despite what I said about overclocking and everything else.
the 352 FSB, they just laughed at me.
(probably)
the 3,7 death is now the most expensive desktop item I own :)
could you explain more on the "2 mystery deaths?" I mean, surely you weren't running completely stock and they just died, right??Quote:
Originally posted by Kunaak
I killed 4 so far.
2 I have no idea what happend.
1 from running a 352 FSB.
not sure what happend there.
1 from running 3.7 volts into the ram.
the two mystery deaths AMD replaced despite what I said about overclocking and everything else.
the 352 FSB, they just laughed at me.
(probably)
the 3,7 death is now the most expensive desktop item I own :)
sorry if i'm being a pain, just trying to get as much info as possible to be prepared when i get one.