Burning in?

[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

[Allan]

If you are running at default speed, you shouldn't really need to burn it in. In fact, it has never been scientifically proven to do any good.

What voltages are you getting?

Try backing the FSB down (underclocking) and see if that helps.

Whats your CPU temp? The high end Tbirds run HOT HOT HOT!

[Staz]

If all you did was swap out CPU's then it is mostlikely a heat problem. What are your temps? What kind of HSF are you useing. If it is an AXIA T-Bird you should be able to get 1.4GHz with good air cooling.

As for your MB. I have an Iwill KK266 which is almost a clone of your board. Those KT7a were some of the best KT133A chipset based boards. They should be able to hit 145MHz FSB without a hiccup. So I don't think it's your MoBo.

Since you had a Duron in there befor, did you also have PC100 RAM. Maybe it's your RAM. Is it generic or is it good quality stuff? You may want to try backing off your memory timings.

And your PSU should be up to the task. I have a 1GHz T Bird @ 1.4GHz @ 1.85v, A 7200RPM HDD, CD ROM, CD-RW, Radeon 8500, a delta 68cfm screammer on the CPU, and 4 80mm case fans. I'm sure I am forgetting something else but anyway. It is all on an Antec 300w PSU and I have never had a power related problem.

I still think it is most likely heat.

[unclemojo]

I doubt it's the board or the chip. The memory seems it may be the culprit. If it's an AXIA Y, you'll get a heck of a lot more than 1.4. Mine does 1.7 easy on air (on a KT7A). Check the ram first off though. THe temps could be a factor, but unless you're over 60* C you won't see any issues, even then its not likely, just scarey to see. Is the heatsink on squarely? Maybe give that a look see also

[Áedán]

Originally posted by Allan
If you are running at default speed, you shouldn't really need to burn it in. In fact, it has never been scientifically proven to do any good.

Warning: Thread Highjack attempt.

Actually, burn in is much misundersood. There is a good reason for burn in, but it's nothing to do with stability! It's down the the failure curve of electronic components. It follows the traditional bathtub curve. There's a higher failure rate within the first 24 hours or so, tapering off to a constant failure rate, and then rising towards the end of the equipment's life.
See NIST SEMATECH for a quick overview of the bathtub curve and failure rates!

AidanII

[Áedán]

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

[slack]

Ok, thanks for your replys

My full load CPU temp is 57, so heat shouldn't be a problem.

The memory modules are both 133 chips, both used to run at CPU+PCICLK but obviously now I'm running them at just CPU CLK. SiSoft Sandra reports my AGP and PCI buses running at the correct speed, so I dont think the problem is there.

I'm gonna have to fiddle tons with the RAM settings I guess, as I think thats the culprit too.

One of the problems with the KT7A is that there are so many settings I can play with. Does anyone know what the setting "PCI Bus Master Time-Out" does?

Thanks
John

[Áedán]

The PCI Bus Master Time-Out setting should set the maximum length that a PCI Bus master can be granted the PCI bus. After this time, the bus master has to release the bus and attempt to re-aquire it. The bus controller should enforce this. Of course, with VIA's track record, there's no knowing what really happens.

AidanII

[slack]

The problem defintely lies in the RAM. I took out my 128 stick and left the 256 stick in...all crashes etc gone! Weird thing is...the 128 stick was expensive crucial cas 2 PC133 RAm, while the 256 stick is some unbranded generic stuff!

Thanks for your description of the PCI time out Aidan, I couldnt find a web page out there that describes it.

[cloasters]

Some mainboards are more finicky than others about RAM. Abit's are often in the "more finicky" category.

[Staz]

Originally posted by slack
I took out my 128 stick and left the 256 stick in...all crashes etc gone! Weird thing is...the 128 stick was expensive crucial cas 2 PC133 RAm, while the 256 stick is some unbranded generic stuff!

There is also a very good chance that if you put the 128MB Crucial back in and took out the 256MB generic it would still work just fine. Some of those boards are picky about what is in which slot. And multiple sticks of RAM have proven to be unstable even when both sticks are stable by themselves.

Glad you found the problem though.

[unclemojo]

On my KT7A I could get away with running a 128 in the first slot and a 64 in the second. I tried the 256 in first, 128 second and also failed. I kinda miss that board, but I know the person who's got it now is really going to like it, so I feel good parting with it.

I think you'll have a pretty nice setup once you get it finished. It may not be the million dollar rig some others have, but a damn fine machine. You'll like it

[Áedán]

I've had issues running differing brands of RAM together before.

I have a stick of 128MB generic RAM, which works fine on it's own. Put it with a 256MB stick of Crucial, and the machine doesn't even boot!

Now, I tried this on an Abit KT7 and an Abit KT7A board, and got the same results. So, in desperation, I tried it on an Abit BX6 (the original board), and still got the same results. Tried it on an el cheapo Via based board, and once again, didn't post. Came to the conclusion that there was something funny about the 128MB generic RAM, which meant it wouldn't co-exist with anyone else's memory.

Moral of the story: I don't run differing makes of RAM, unless they're all brand name. Incidently, I don't buy non-branded RAM any longer either.

AidanII