Thread: Burning in?
View Single Post
  #6 (permalink)  
Old 23rd October, 2002, 04:05 AM
Áedán's Avatar
Áedán Áedán is offline
Chief Systems Administrator
 
Join Date: September 2001
Location: Europe
Posts: 12,248

Re: Burning in?

Quote:
Originally posted by slack
Ok I just got myself an Athlon 1333 TBird and it rocks against my old Duron 800 :-D

But....I've been having quite a few lockups since installing it (today) a few on the XP desktop, but most in games. The game will just bomb out back to windows as if it had never been running, or on one occasion, just reset my machine altogethor.
So I'm wondering if its either:
a) Ye old KT7A mobo can't handle being at 133FSB (ie its stretching the board to its limit)
b) The CPU needs burning in???? (Dont even know what that means)
c) My power supply (300W Aopen) is just not up to the task

Any ideas much appreciated.

Cheers peeps
Slack
The KT7A had the revised KT133A, which could actually handle the 133Mhz FSB, so you should be fine at 133. Ignore the crud about burning in the CPU. Your 300W PSU should be up to things...

So, that leaves other parts. It's been suggested to check your RAM and it's settings. If you had a Duron it's possible your RAM clock was set to CPU+PCI, which would result in 133MHz for a 100MHz FSB. If you move up to a 133FSB, then you want the RAM clock to be CPU.

Given that your FSB is at 133, then the PCI and AGP clocks should be correct. That doesn't really leave very much other than RAM!

AidanII
__________________
Reply With Quote