View Full Version : ok..i trashed another cpu...but i got another one
!-=sky=-!
08-30-01, 08:49 AM
i cracked a t-bird 1ghz with axia coding........
while that goes to rma so i got myself another one....i couldnt stand waiting without a comp
here is my problem....the new t-bird(ahjya 1ghz) wont boot in my epox 8kha but it's ok on my a7v
what can be the problem?
btw both boards work....i m using it as i type is(with duron 600)
Check the 100/133 jumper-dip switch.
!-=sky=-!
08-30-01, 10:35 AM
it wont boot on neither
but my duron works fine
Check the Epox site and see if there is a bios update.
i12bina3
08-30-01, 01:58 PM
OC the duron to 1gig ... problem solved ... :)
but im guessing you really wanna use the T Bird ... so my solution isnt a big help :)
!-=sky=-!
08-30-01, 09:36 PM
i did get the latest bios already
doesnt help
It does not make any sense.
Works with 700 and the 1 gig works in another board. It must be cursed.
I had the same problem when I bought my 1.0G as did someone else in these forums ("DAD" if I recall correctly).
I bought one of these proccessors at the local computer show and it wouldn't boot so I returned it the next day and had the same problem, with the show then closed and not to return until the next month, I tried penciling the bridges and VIOLA!. It's worked flawlessly since, overclocked to 1.4G. I posted this strange incident at the time and did have one response with the same problem, I haven't heard of it otherwise.
By the way, they were both "AXIA-Y 266FSB" CPU's. I set them both up on a running system using an ASUS A7V133
motherboard, replacing a 1.2G T-BIRD.
I hope this helps.
Good Luck!
!-=sky=-!
08-31-01, 01:01 PM
Originally posted by FRANK
I had the same problem when I bought my 1.0G as did someone else in these forums ("DAD" if I recall correctly).
I bought one of these proccessors at the local computer show and it wouldn't boot so I returned it the next day and had the same problem, with the show then closed and not to return until the next month, I tried penciling the bridges and VIOLA!. It's worked flawlessly since, overclocked to 1.4G. I posted this strange incident at the time and did have one response with the same problem, I haven't heard of it otherwise.
By the way, they were both "AXIA-Y 266FSB" CPU's. I set them both up on a running system using an ASUS A7V133
motherboard, replacing a 1.2G T-BIRD.
I hope this helps.
Good Luck!
thx for the suggestion...but it still wouldnt work....ok....i give up....forget it...hehe
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.