Did I Fry My CPU ?

[Tommy]

This is what happended I decided to upgrade my CPU Athlon 900MHz
to an Athlon 1333MHz and after installing the 1333 my mainboard A7V133
PCB1.05 displayed it as a 1200MHz. I tried changing the BIOS settings
to match the CPU specifications (FSB = 133, multiplier 10.x) then she
wouldn't POST.


I then proceeded to chech the jumpers (jumperless mode JEN enabled) on
the board and only changed the DSW switches all to OFF from previous
all ON positions. She then POSTS and boots into Win2K. After 5-10 mins
of running it immediately shut down. Only the green power light on the
front of the tower kept flashing ON/OFF immediately after shutdown.
Tried powering back up but NO POST all tower lights come one i.e CDROM,
Power, HD fans all running. Swapped CPU's back to the 900 and she POSTS
and runs fine into Win2K and continues to run fine.


Running same CoolerMaster as for the 900 and power supply is a brand
new Sparkle 350W. Have two HD's, 1 x CDROM, 1 x CDRW, 1 x removable
rack.


What happened ? Anyone tell me did I fry the CPU by not using correct
heatsink + fan for a 1333 (which i inderstand requires more power and
probably runs hotter). ?


Many thanks

 

[edavid3001]

What did you do in that 5-10 minutes? Did you just start playing games
when it died? Where you idle?

A friend of mine just built a computer for a relative. He forgot to
put the fan/heatsink on the Pentium chip. Dumb mistake, distracted...
The CPU died right away.

My guess would be more likely that the wrong voltage or multiplier got
ya. But that is just a guess. The A1333 is supported by default per
http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us&model=A7A133


Have you tried putting the new chip back in with the same config you
started out with, and got 1200MHZ?

 

[Tommy]

What did you do in that 5-10 minutes? Did you just start playing games
when it died? Where you idle?

A friend of mine just built a computer for a relative. He forgot to
put the fan/heatsink on the Pentium chip. Dumb mistake, distracted...
The CPU died right away.

My guess would be more likely that the wrong voltage or multiplier got
ya. But that is just a guess. The A1333 is supported by default per
http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us&model=A7A133


Have you tried putting the new chip back in with the same config you
started out with, and got 1200MHZ?

I didn't do anything at all. Just left it running at the desktop thats
it. No screensaver just the startup apps i.e anti-virus, firewall,
etc..

The motherboard was already set to jumperless except for the DSW
switches don't know why that was. The DSW position was set to 100MHz
FSB not high enough to harm the 1333MHZ. The VCore jumper was set to
jumperless therefore not likely causes any issue for the CPU either.

After the system simply powered down it wouldn't power back up. My
guess is the CPU has fried and I don't know why.

Thanks again for the reply


Thanks again.

 

[Natéag]

I do not have that board, so I do not know the reason
it reboots.

Could be a memory or power supply problem.

Or it could just run too hot, for lack of sufficient
ventilation.

 

[Paul]

I didn't do anything at all. Just left it running at the desktop thats
it. No screensaver just the startup apps i.e anti-virus, firewall,
etc..

The motherboard was already set to jumperless except for the DSW
switches don't know why that was. The DSW position was set to 100MHz
FSB not high enough to harm the 1333MHZ. The VCore jumper was set to
jumperless therefore not likely causes any issue for the CPU either.

After the system simply powered down it wouldn't power back up. My
guess is the CPU has fried and I don't know why.

Thanks again for the reply


Thanks again.

You have to be very careful with the DSW settings and JumperFree.
When operating in JumperFree mode, the BIOS thinks the switches
(or jumpers, in the case of VID) are all in the OFF position.
When they are OFF, they are open circuit, unable to influence the
logic value on the signals they connect to. If any of the switches
are left in the ON position, while using JumperFree, the switch
will "win", and that logic signal will remain at zero, no matter
how the BIOS tries to drive it. And, that means the BIOS is no
longer in complete control, and some strange values could be sent
to the Vcore circuit or the clockgen chip. So, there is a possible
relationship between mixed up switch settings and a fried
processor. I really don't know how much higher in frequency
the clockgen goes than 133MHz, and knowing the full table
of values, would allow you to estimate how much overclock could
have been applied. A more likely culprit, might be the VID
jumpers - were they misplaced too ?

Paul

 

[Tommy]

You have to be very careful with the DSW settings and JumperFree.
When operating in JumperFree mode, the BIOS thinks the switches
(or jumpers, in the case of VID) are all in the OFF position.
When they are OFF, they are open circuit, unable to influence the
logic value on the signals they connect to. If any of the switches
are left in the ON position, while using JumperFree, the switch
will "win", and that logic signal will remain at zero, no matter
how the BIOS tries to drive it. And, that means the BIOS is no
longer in complete control, and some strange values could be sent
to the Vcore circuit or the clockgen chip. So, there is a possible
relationship between mixed up switch settings and a fried
processor. I really don't know how much higher in frequency
the clockgen goes than 133MHz, and knowing the full table
of values, would allow you to estimate how much overclock could
have been applied. A more likely culprit, might be the VID
jumpers - were they misplaced too ?

Paul

Paul no only the DSW switches were miplaced not any of the VID they
were set to default settings for jumperless mode. Thanks.