possible fried 2600+?

[allcoholl]

Well, I had been overclocking with a thermaltake volcano 12 (arctic silver 5 paste) and I had oc'd my 2600+ barton to 3200+ speeds. It was stable for a very long time, but I clocked it back to 2600+ speeds. I did that numerous times (switched back from 2600 speeds to 3200 speeds) and then I switched to 3200+ speeds one more time just now, and no POST, no beeps, no nothing. I took out the processor to look at it and it looks the same as before.. there are no burn marks or any signs of frying up. It looked the EXACT same as it was when I first got it. I tried resetting the CMOS; no luck. I tried clearing the cmos 10 times (literally) and got nothing. I tried taking the processor out, cleaning it, and reapplying paste and putting the heatsink back on, as before, and still no luck. I just put in an RMA request.. so on about monday or tuesday I should know when to send it in. anyway, I have an A7N8X Deluxe (in case you guys need to know), and before I send the processor in, is there any possible thing I could do? Has anyone had and FIXED this problem? Thanks, guys.

[c627627]

I did it dozens of times by unplugging everything from the wall and walking away for a few hours.

Do the same, make sure everything is seated correctly, it happened to all of us, sometimes it's serious, most of the time it starts up again.

[allcoholl]

yeah, well it's been a bit, so we'll see what happens. it's unplugged and stuff, and I recleaned everything, reseated everything, and now I'm just kinda waiting. Yeah, this is gay.. but oh well. Sometimes I just don't understand things. Why the hell would it fry when it was running at 40C? Seriously, that's an awesome temperature, and it fried. (or I'm thinking it fried, because I've got nothing else to really conclude about it) And plenty of people have pushed theirs much harder than I was pushing mine, without any problems. Some people have pushed their 1800's up to 3200 with no problems at all. And here I am, pushing my 2600 to 3200 and I suddenly fry it. I don't know.. things are just so awful sometimes. This can really add to your depression when you're deprived of money and things to do.

[BowerR64]

i hate problems like that.

yesturday i picked my rig up off the floor and put a screw into the nic that i had been putting off for about 2 months now and when i sat it back down and fired it back up one of the drives started going into this tick tick tick loop like what the drives do when they go bad. I said to myself WTF? i shut it off wiggle a few wires and its been fine all day.

These are the kinda problems that p*ss you off.

I thought i had fried my 1900+ the other day also. I was trying to see what i could get out of this chip on this new board i got and was trying more voltage, higher FSB different ram speeds and i got it to a certin point i felt was the end and it was locking in the bios so the next time i got into the bios i cranked it to 1.9 and rebooted it real quick and as it booted it went threw that *warning do not turn off the power while bios is saving the settings* and it started beeping and i thought OH NO! :eek:

When i went to reboot it was dead. wouldnt post at all. i cleared the bios, no boot i was about to tear it apart but i tried one more thing. I cleared the cmos pulled the battery and unplugged the power from the board pushing the power button randomly at different times. Put it all back to gether and it fired up WHOOOOOW!:o

as soon as it didnt post i instantly thought DAMN SANTA IS GONA HAVE TO BRING ME A NEW CHIP! lol:D

[allcoholl]

yeah, the battery.. I did the battery thing too, and I had no luck.. but yeah, I'm gonna keep trying, because that's exactly what's happening to me, so my processor is probably fine.. just needs to be fired up, once. I guess..

[allcoholl]

Thing is, though, I did what Bow did, and got no luck. This sucks; now I have to RMA, send it in, etc. I just hope it's not somethin else besides the chip. The reason I think it's the chip is because as soon as I clocked it to 3200 for the last time, it wouldn't boot and has not since. I don't know. there doesn't look like there's damage to the board, so I don't think it's the board.

[BowerR64]

you dont have any other parts to test the rest of the stuff?

would suck to wait a few weeks for a new chip to find out its somthing else. Somthing that dont clock as good

it comes on but no post? like lights and the drives spin?

before you send it back tear it all down, pull the board out and look at the back. put it all back together if it still dont fire up then send it off.

I had an Athlon some kid gave my brother that was pretty chipped up but didnt look fried but it was.

[altec]

Something similar happened to me once. I picked up my case off of the floor, put it on the desk (because it was a more conveinent location), and then tried to turn it on. Nothing. I reset the CMOS 5000 times. Nothing. So eventually I took everything apart, re-did the entire machine, and it worked. My best guess is that when I moved the case, I somehow jarred it and the motherboard shifted on the mounting screws. This would cause the board to short into the case, and therefore, no POST. Try to re-mout your board, and see if you can find any of the plastic spacers to keep the board away from the case.

Best of luck ;)

[allcoholl]

ah, you're in philly, eh :P I'm from Philly, too. I know that's off subject but I felt like tellin ya :P Yeah, I'll try re-mounting the board and such. I just don't at all see why it would work so well for such a long time and then suddenly just stop. Only reason I can see is the processor is fried, because I was overclocking a lot.

[altec]

Like I said, you may have simply jarred the case in some way, and shifted the motherboard's mounting enough to create a short between the board and the metal little mounting screws, which in turn will short it into the case.

Im just trying to exhaust all the options befor eyou have to RMA your CPU, and wait until you get a new one.

Best of luck ;)

[allcoholl]

bah, I tried remountin.. no luck. I don't think I moved the board or anything anyway. It makes total sense taht the cpu is ****ed, because right when I tried to OC it, it wouldn't work anymore. I had OC'd so many times before, and now it's screwed. Bah, well, they'll RMA it, becaues it doesn't even look fried. Plus; the 15 day warranty isn't up yet :P

[BowerR64]

15 days? lol dang that didnt take you long

[brennan77]

I don't mean to be on a moral crusade here, but it really hurts the market, and is pretty lame to RMA something you broke. You overclock it, you take the risks, you take the responsibility.

On another note, it doesn't sound fried. Often times, clearing the CMOS can be tricky if proper procedure isn't followed. To be sure, follow the exact directions in the manual for the motherboard. Pulling the battery doesn't always work.

[allcoholl]

oh yeah, I'm sure it hurts the market so bad. I don't even think you know what you're saying, considering it costs so little to make these chips, let alone they sell them for so much, because hardly anyone out there knows how/has the materials and tools to make one. It hardly hurts the market at all. I'm not even sure if I broke it, that's the thing. RMA doesn't necessarily mean an automatic return/refund/replacement, anyway, and I'm still under that 15 day warranty. I don't know, if you're going to tell me about how it's lame to RMA something, then go bitch to the stores about giving us the ability to RMA in the first place. I made this thread to see if any of you guys had any ideas about this processor, not about how it's lame to RMA. Go tell someone who cares.

And by the way, the first time I reset the cmos, I did it the way the manual told me to. You first set the jumper, then take out the battery. Then alter it back to where it was before. I did that every time I reset the cmos, anyway.

[Joe Camel]

my idea on your chip:
i think your chip should be fine......
i think you should RMA it
i think they should send you a chip somebody DID fry and RMA
over and over again....karma baby

good luck

[allcoholl]

now see, at least Joe Camel's criticism made sense. :P I mean, really, if you're gonna criticize, you should at least make sense. I laughed :P

[7keys]

I would try another CPU in that board before I rma’d that Chip. Doesn’t the A7N8X Deluxe have a history of bios corruption when overclocking?

I would make sure it was the chip before sending it back.

[AL Romero]

maybe i didnt see it but does you pc boot into bios, cuz if it doesnt i would you corrupted you bios. and need a 20 dollar survival kit from excaliberpc.com. i just did the same thing and got the kit today and now im back in bidness. hehe

good luck...

[AL Romero]

you might also have a bad IDE drive. my system was freaking out when i change cpu setting by not booting and it got worse and worse so i called excal. they did some over the phone tests with me and came up with a ****ed cdrw. now that its unpluged she runs fine. i too was worried it was a mobo or chip issue but all it was was my 40 dollar cheapo iomega. that sum bitch need to be taken out an shot anyway. shes so old. hehe

good luck dude....

[Nanidin]

My pc did this. It turned out to be that I corrupted my bios. Easily fixed it by finding someone that has the same board as you and flash your bios in their motherboard. Look up "hotlfashing" for more info.

[georgelogy]

Here is a good site which gives more information than you ever wanted to know about hot flashes:

http://www.hot-flashes-control.com/

:)

[P2P]

Originally posted by 7keys
I would try another CPU in that board before I rma’d that Chip. Doesn’t the A7N8X Deluxe have a history of bios corruption when overclocking?

I would make sure it was the chip before sending it back.


my guess is the bios too yrt and find any old amd chip from a friend to test first b4 sending yours in

[allcoholl]

someone needs to give me a site on hotflashing. I don't wanna screw anything up. ;/ But it does make sense that the bios is screwed. I'm on extreme-overclocking forums right now, and I'm looking at a thread about a similar issue:

http://forums.extremeoverclocking.com/showthread.php?s=&postid=677161#post677161