KT7A RAID mobo or CPU dead?

I have an old system that was KT7A RAID based and ran fine. A few
years ago when it simply stopped working, I just put it in storage. I
felt like tinkering, so I dug it out, and discovered a dead power
supply. I cleaned up the mobo, installed a new power supply and
promptly smoked something. I stripped everything off the mobo, and now
when I try to power it on, I get 4 long beeps, almost 1 very long
continuous beep. Without the CPU, it does nothing. Drop the CPU and
fan back in, and I get 4 long beeps again, so I'm thinking I fried the
CPU.

Questions:

With a system that used to work, but quit, then smoked the CPU (I
think), what would cause the CPU to fry?

How can I tell if the CPU is bad, or if it's the mobo that's bad?

Any known issues with this mobo either dying like this, or frying the
CPU?

Short of taking it to a computer shop for testing, is there anything I
can do to try to determine exactly what is bad? I'd like to get the
system going again, but I don't want to start replacing things
willy-nilly, without being fairly certain I am headed in the right
direction.

Thanks for any help.

Tim

<> wrote in message
news: ups.com...
>I have an old system that was KT7A RAID based and ran fine. A few
> years ago when it simply stopped working, I just put it in storage.
> I
> felt like tinkering, so I dug it out, and discovered a dead power
> supply. I cleaned up the mobo, installed a new power supply and
> promptly smoked something. I stripped everything off the mobo, and
> now
> when I try to power it on, I get 4 long beeps, almost 1 very long
> continuous beep. Without the CPU, it does nothing. Drop the CPU
> and
> fan back in, and I get 4 long beeps again, so I'm thinking I fried
> the
> CPU.
>
> Questions:
>
> With a system that used to work, but quit, then smoked the CPU (I
> think), what would cause the CPU to fry?
>
> How can I tell if the CPU is bad, or if it's the mobo that's bad?
>
> Any known issues with this mobo either dying like this, or frying
> the
> CPU?
>
> Short of taking it to a computer shop for testing, is there anything
> I
> can do to try to determine exactly what is bad? I'd like to get the
> system going again, but I don't want to start replacing things
> willy-nilly, without being fairly certain I am headed in the right
> direction.
>
> Thanks for any help.
>


Tim

If you're getting beep codes then you have a functioning CPU.
Not sure about the beep code. Try looking it up.
The KT7 mobos have lots of capacitor problems.
Are you aware of this ?
Are the capacitors distorted or have stains from leaking ?

Eric

--
Remove the dross to contact me directly

Yeah, I was reading up after I posted and found several posts about bad
caps. I'll look it over.

At http://www.bioscentral.com/beepcodes/awardbeep.htm there are some
submitted PSOT beep codes for Award BIOSes. One is listed for 4 long
beeps that indicates CPU fan is damaged or running too slow, but mine
seems fine. I'll try to swap it out and see where that gets me.

Thanks for the info, Eric.

Eric Parker wrote:
> <> wrote in message
> news: ups.com...
> >I have an old system that was KT7A RAID based and ran fine. A few
> > years ago when it simply stopped working, I just put it in storage.
> > I
> > felt like tinkering, so I dug it out, and discovered a dead power
> > supply. I cleaned up the mobo, installed a new power supply and
> > promptly smoked something. I stripped everything off the mobo, and
> > now
> > when I try to power it on, I get 4 long beeps, almost 1 very long
> > continuous beep. Without the CPU, it does nothing. Drop the CPU
> > and
> > fan back in, and I get 4 long beeps again, so I'm thinking I fried
> > the
> > CPU.
> >
> > Questions:
> >
> > With a system that used to work, but quit, then smoked the CPU (I
> > think), what would cause the CPU to fry?
> >
> > How can I tell if the CPU is bad, or if it's the mobo that's bad?
> >
> > Any known issues with this mobo either dying like this, or frying
> > the
> > CPU?
> >
> > Short of taking it to a computer shop for testing, is there anything
> > I
> > can do to try to determine exactly what is bad? I'd like to get the
> > system going again, but I don't want to start replacing things
> > willy-nilly, without being fairly certain I am headed in the right
> > direction.
> >
> > Thanks for any help.
> >
>
>
> Tim
>
> If you're getting beep codes then you have a functioning CPU.
> Not sure about the beep code. Try looking it up.
> The KT7 mobos have lots of capacitor problems.
> Are you aware of this ?
> Are the capacitors distorted or have stains from leaking ?
>
> Eric
>
> --
> Remove the dross to contact me directly

Now, I get no POST beeps - no nothing!

How do I determine if the mobo killed the CPU, or if the CPU just died
on it's own? I'd like to get it going again, but I don't want to buy
another CPU and install it, if the mobo is just going to smoke it too!

Thanks for any help!!!

Tim

TimInOhio wrote:
> Yeah, I was reading up after I posted and found several posts about bad
> caps. I'll look it over.
>
> At http://www.bioscentral.com/beepcodes/awardbeep.htm there are some
> submitted PSOT beep codes for Award BIOSes. One is listed for 4 long
> beeps that indicates CPU fan is damaged or running too slow, but mine
> seems fine. I'll try to swap it out and see where that gets me.
>
> Thanks for the info, Eric.
>
> Eric Parker wrote:
> > <> wrote in message
> > news: ups.com...
> > >I have an old system that was KT7A RAID based and ran fine. A few
> > > years ago when it simply stopped working, I just put it in storage.
> > > I
> > > felt like tinkering, so I dug it out, and discovered a dead power
> > > supply. I cleaned up the mobo, installed a new power supply and
> > > promptly smoked something. I stripped everything off the mobo, and
> > > now
> > > when I try to power it on, I get 4 long beeps, almost 1 very long
> > > continuous beep. Without the CPU, it does nothing. Drop the CPU
> > > and
> > > fan back in, and I get 4 long beeps again, so I'm thinking I fried
> > > the
> > > CPU.
> > >
> > > Questions:
> > >
> > > With a system that used to work, but quit, then smoked the CPU (I
> > > think), what would cause the CPU to fry?
> > >
> > > How can I tell if the CPU is bad, or if it's the mobo that's bad?
> > >
> > > Any known issues with this mobo either dying like this, or frying
> > > the
> > > CPU?
> > >
> > > Short of taking it to a computer shop for testing, is there anything
> > > I
> > > can do to try to determine exactly what is bad? I'd like to get the
> > > system going again, but I don't want to start replacing things
> > > willy-nilly, without being fairly certain I am headed in the right
> > > direction.
> > >
> > > Thanks for any help.
> > >
> >
> >
> > Tim
> >
> > If you're getting beep codes then you have a functioning CPU.
> > Not sure about the beep code. Try looking it up.
> > The KT7 mobos have lots of capacitor problems.
> > Are you aware of this ?
> > Are the capacitors distorted or have stains from leaking ?
> >
> > Eric
> >
> > --
> > Remove the dross to contact me directly