OH jeez... Could I have screwed myself again allready??

[Frost]

If so I'm about to be very upset... I'm pretty upset at the moment actually. Well heres the story. I sent my a7v8x, and 2400+ back for rma like 3 weeks ago. Finally get it back today... whats the first thing I do? Unlock the chip of course and start overclocking. Well My first attempt to see if it was better than my old proc was 22.5x100 because my last chip would barely hit like 2200mhz... Anyway, it worked, so I tried 14x166 which yeilded me with 2.333ghz. I was happy But decided to go for more. I tried to do 15x166 which would have been a long shot, and I knew that so I bumped the voltage up to 1.8. No boot So i power down, and reset the cmos, power up everythings fine. I try to go with a little more moddest attempt of 182x13, which was only 33mhz over what I had booted into windows with previously, and ran 3dmark 03 just fine. Well it didn't boot either, so I said damnit! and powered down. Reset the cmos, and *tried* to power up again. Looks like bad news at this point. I didn't smell any smoke, or hear anything short or anything like that, but now it won't power up at all!! When I jumper the power switch, it just sits there, no fans, no lights, no noise, nothing that would lead me to beleive that the motherboard has any juice running through it at all. Which seems very odd, because just a few minutes ago when I tried to for for the 2.5ghz mark, all I had to do was reset the cmos and everything was fine. So I couldn't beleive that attempting something that is 133mhz less could harm it. Did the high fsb kill my asus or what?? I don't understand this at all, its not adding up. Any chance it'll spring back to life after sitting around unplugged for a while, or am I just SOL??? I sure would look stoopid calling them to rma, an rma the day I get it! sheesh

sad Frost

 

[n0cmonkey]

If you killed it overclocking you shouldnt get RMAs.

Buy a different processor and try. Do you have the chipset chips cooled and everything?

 

[DaveSimmons]

I sure would look stoopid calling them to rma, an rma the day I get it! sheesh

You would also be committing fraud it you RMA a perfectly good chip that you killed by running it too far above spec. Not to mention hurting AMD who really can't afford to keep replacing chips that you burn out.

Ethics are a Good Thing.

 

[Vic]

an unskilled, overly agressive overclocker and his equipment are soon parted

I would take it all apart, check out all the components, re-do everything, see what needs to be replaced, etc. Then practice proper overclocking - which involves burning in a day or 2 at stock speed (or otherwise known stable speed), then upping speed in small practiced increments, testing for stability with Prime95 at each step. When P95 fails, back down to where it is again stable. While it's a matter of opinion, I believe you should up the FSB first, then the multi, but each time should be done slowly, one increment at a time. Done properly, you should never OC so high that the system doesn't POST or boot.

 

[Frost]

Well let me clear this up a little... I know that, that would be fraud and unethicle (sp?) but I wasn't talking about my chip... If I killed it o/cing then I know thats my own damn fault... but what I don't understand is how this could kill my motherboard which is what it seems to have done! I checked my proc in another mobo and its fine but I also checked my motherboard with a different cpu and still nothing. The little green light turns on when its plugged in, but that is absolutly it... No fans, no hdd spinning, no nothing at all.

I mean motherboards (kt400) especially are designed to run high front side busses, and what I was doing (182) is well within spec for the chipset, its supposed to be able to handle 200, plus it gives you options to go even higher than that. This is VERY odd to me I don't understand what could have happend. Beside my motherboard apparently being dead now, I'm unhappy with the rma. They took forever to ship it back, I sent them a retail asus box, and received this motherboard in a white box, with no antistatic bag, on top of that two pins on the motherboard were were bent horribly! I mean they were at like a 30 degree angle with the board apposed to the 90 degree angle they should be at, sticking strait up. It looked to me as though something was plugged in and some dumb fvck just pulled on the motherboard not noticing there was anything attatched to it, and the wires finally came off after bending the pins enough. Also, (didn't check before this incident) but I've noticed what appear to be some either cut, or badly damaged traces, connecting to the south bridge chip... Which is very odd because I no for a fact I didn't hit them, nor was I working anywhere near those traces, didn't drop any screw drivers or anything.

I was kinda worried when I put the heatsink on cuz I was pushing the clip down really hard and the clip hit the mobo (I've killed numerous mobos by cutting traces near the cpu socket) but what I noticed and liked very much is that asus has now protected the traces around the cpu socket with some type of clear plastic/tape stuff Very smart indeed.

Anyways, what should I do here? I don't understand how this could have affected my motherboard at all... Its not like I was soldering things to it so I could get like 3v core voltage or some stupid thing, I didn't even go above 1.8v. And I didn't mess with any other voltages at all.... Oh what to do? :|

 

[human2k]

Originally posted by: DaveSimmons

I sure would look stoopid calling them to rma, an rma the day I get it! sheesh

You would also be committing fraud it you RMA a perfectly good chip that you killed by running it too far above spec. Not to mention hurting AMD who really can't afford to keep replacing chips that you burn out.

Ethics are a Good Thing.

I guess he can post in the "killed my tbred B by overvolting" thread now.

 

[human2k]

Originally posted by: Frost
Well let me clear this up a little... I know that, that would be fraud and unethicle (sp?) but I wasn't talking about my chip... If I killed it o/cing then I know thats my own damn fault... but what I don't understand is how this could kill my motherboard which is what it seems to have done! I checked my proc in another mobo and its fine but I also checked my motherboard with a different cpu and still nothing. The little green light turns on when its plugged in, but that is absolutly it... No fans, no hdd spinning, no nothing at all.

I mean motherboards (kt400) especially are designed to run high front side busses, and what I was doing (182) is well within spec for the chipset, its supposed to be able to handle 200, plus it gives you options to go even higher than that. This is VERY odd to me I don't understand what could have happend. Beside my motherboard apparently being dead now, I'm unhappy with the rma. They took forever to ship it back, I sent them a retail asus box, and received this motherboard in a white box, with no antistatic bag, on top of that two pins on the motherboard were were bent horribly! I mean they were at like a 30 degree angle with the board apposed to the 90 degree angle they should be at, sticking strait up. It looked to me as though something was plugged in and some dumb fvck just pulled on the motherboard not noticing there was anything attatched to it, and the wires finally came off after bending the pins enough. Also, (didn't check before this incident) but I've noticed what appear to be some either cut, or badly damaged traces, connecting to the south bridge chip... Which is very odd because I no for a fact I didn't hit them, nor was I working anywhere near those traces, didn't drop any screw drivers or anything.

I was kinda worried when I put the heatsink on cuz I was pushing the clip down really hard and the clip hit the mobo (I've killed numerous mobos by cutting traces near the cpu socket) but what I noticed and liked very much is that asus has now protected the traces around the cpu socket with some type of clear plastic/tape stuff Very smart indeed.

Anyways, what should I do here? I don't understand how this could have affected my motherboard at all... Its not like I was soldering things to it so I could get like 3v core voltage or some stupid thing, I didn't even go above 1.8v. And I didn't mess with any other voltages at all.... Oh what to do? :|

you lucky bastard, no burned cpu.

 

[Frost]

Yeah I"m lucky there, but actually I'm starting to get pretty pissed at this company! Taking a closer look at the mobo (with a magnifying glass) i see what looks to me to be 4-6 traces cut clean through, and a few others damaged! :|:|:| How in the hell could it have worked with those like that, then all of a sudden crap out? I don't understand that at all. And this is deffinetly not good, after it being plugged in for like 10 minutes we'll say I unplugged everything and unhooked everything and I noticed that the area within about 2 inches on all sides (but mostly the two edges of the mobo) of the atx power connector were hot as hell!! this blows...

 

[Antisocial Virge]

I was pushing the clip down really hard and the clip hit the mobo (I've killed numerous mobos by cutting traces near the cpu socket)

 

[Frost]

yeah tell me about it, thats probably the face I woulda been making when that happend if I wasn't punching myself in it Right now I have a dead epox 8k7a, msi k7t pro2-a, Abit KT7a-raid, all dead due to different stupidities...

But this is not my fault! Serisously I don't know what I'm going to do about this. I'm thinking of e-mailing or phoning asus and explaining to them, the lame way that this company conducts business with their products, and that I would much rather get a new mobo directly from asus. Do you think that they would do that??

 

[magomago]

why you'd send in your box They told me NOT to do that because they won't return anything...

I sent mine in a cheap box and got back the white one also...and my RMA too me a week and 5 days...

so while i don't sympathize with you when you sent in your box, I do for a 3 weeks RMA

EDIT:

"22.5x100 because my last chip would barely hit like 2200mhz... Anyway, it worked, so I tried 14x166 which yeilded me with 2.333ghz"

You went from 100 to 166? ???

When i got my 1700+ I left it at deafult for a week, then i also jumped from 133 to 166 but i lowered the multiplier all the way and incrased it by 1/2 every two days (it runs at night p95) after a 3day "burn in" at 166*lowest_multiplier