January 19th, 2003, 06:43 PM #1
Guess I finally pushed my luck too far
I seem to have damaged a component during my latest overclocking attempt. Oddly enough I really dont know what is broken.
Here is why:
Last night I got the bright idea to unlock my new AthlonXP 2000. Now, I didn't really need more speed for anything, I just wanted to see what it would do.
I covered the pits between the L1 bridges with tiny dots of superglue (got this idea from some overclocking site) and connected the bridges with some defroster grid repair paint just like a normal Athlon or Duron.
I stuck the processor in, powered it on, and was greeted by the smell of cooking electronics. No POST of course.
Wake up this morning and run to CompUSA to buy an XP1800 (yeah, I got raped on the price ) stick that one in , clear the CMOS, and.....nothing.
I then try a damaged 1.4 T-bird I have in the closet that would POST and boot into DOS but not into windows. It will still POST on this mobo.
Figuring the 1800 may be defective I swap it for another one, stick that one in, clear the CMOS, and.....nothing.
Nearing the end of my rope I run to work and grab a 900 Duron out of one of the office machines, stick it in, clear the CMOS, and well...I am typing this on the computer in question. (i.e. it booted just fine)
So what is the deal. Did I fry some part on the mobo needed to allow it to run an AthlonXP? It posted on a 1.4 T-bird, It's booted on a 900 Duron, but it didn't do anything with either 1800XP's that were new in a retail box.
Compatibility isn't a question, it's a Soyo Dragon Ultra that has been running a 2000XP for a month or so. Any ideas? Maybe reflash the BIOS?
January 19th, 2003, 06:53 PM #2
maybe you fried something needed to run at 266mhz, but it will still run at 200. Not really sure.
Just a guess
BCThe impossible takes more time,and costs more money.
Check out my band Saving Silence
January 20th, 2003, 01:17 AM #3
Well I have an answer to this problem. Sort of. I looked around on Soyo's site and found a new bios that addresses a boot issue with t-bred processors (my XP2000 was a Palimino) I tried that bios and still no luck but when I went to the forums I found that this is fast becoming a common problem. According to SOYO this mobo is supposed to work with T-breds but apparently it does not.
On the bright side I know where the problem is now.
Link to my problem if anyone is interested.
Last edited by Aaron_J; January 20th, 2003 at 01:19 AM.
January 20th, 2003, 01:26 AM #4
well i'm glad to heard the chip was not damaged.
soyo is a decent enough brand from what i've heard, but i've always thought better boards could be had for cheaper (if you're a budget buyer) or for better features (for the performance buyer).
January 20th, 2003, 02:53 AM #5
- Join Date
- Oct 2002
Well I have a T-bred xp 2400 and have had no problems whatsoever. I have a soyo kt333 plat and updated the BIOS, which doesn't allow for the them to run just so that it recognizes the higher XP's (2400's and 2600's)
January 20th, 2003, 03:00 AM #6
Oddly enough, several people are using the XP2400 with no problems, it seems to be most common with the 1700-1900's.
January 20th, 2003, 03:09 AM #7
WOAH! WAIT! HOLD ON!!!!
I just bought the Soyo Kt400 Gragon Ultra (Black Edition) and a Athlon XP 2400+! I can't use the chip unless I bios flash it? How the heck do I do that if I have other chip? Am I totally lost, or totally screwed? How can a brand new kt400 board not support T-bred chips?
AWWWW!Abit AW9D-Max | E6300 | XP-120 | Panaflow 120mm | 2x 1GB G.Skill DDR2-800 | BFG 8800GT | Corsair 650w
January 20th, 2003, 09:34 AM #8
Lol, you are gonna be fine. My board is the older K7V Dragon Plus.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)