Is this temp too hot for a 1.33 T-Bird?

[psteng19]

does anyone know the operating and idle temp of a T-bird 1.33 Ghz off the top of their head?
or know of a website that shows the operating/idle temp of AMD cpu's?


sigh... now i know why you don't build systems for friends. He claims it's overheating because it freezes/restarts about twice a day. He says it's at 65 C during idle according to the BIOS. and this was built over a month ago, and these "crashes" just started occuring.

Asus A7V133, 1.33 Mhz T-Bird, Enlight EN-72370X3 300W PS, Live value, GeForce 2 Pro 64 DDR, Linksys LNE100TX, Kingston 256 MB Value RAM, IBM 60GXP 40 Gig, WIN ME, IIRC...

EDIT: Cooler Master's DP5-6I31A - rated for up to 1.4 Ghz T-Bird. He's running default speed @ default voltage.
i know i know... but Volcano II was out of stock at that time...

 

[Siva]

65 is too hot, what kinda heatsink is on it?

 

[Siva]

I'd take off the heatsink, make sure it was attached well, make sure there isn't too much or two little silver (unless you are using a thermal pad which you should scrape off and replace with silver anyway) and if problems persist get an svc golden gate (www.svcompucycle.com). Great heatsink for the price.

 

[NesuD]

make sure that case has a couple extra case fans in it. case cooling is just as important as the heatsink with the big birds. Did he pay you to build that system? If not tell him to get off your ass and that you will see what you can do. if he insists on bugging you about it tell him to kiss off. On any system you build for someone though you should do a burn in of at least 24 hrs but 48 is better with some kind of stressfull program running to check temps and stability. Then when they call and say there is something wrong with that crap computer you built them you can with a straight face ask them what they were screwing with to mess it up.

 

[RambleOn]

my Tbird 850@935 runs at 34c at idle, 42c heavy load.

 

[psteng19]

i always build systems for friends and relatives for free. i mean, what are friends for, you know?

i built it in august and it was running fine for the hours that I was there (built it at his house). didn't do any stressful tests on it, but I'm sure he's been using it for several days at a time with no problems. now all of a sudden problems come up a month later and I'm responsible..? argh...

i can't look at it right now because I'm 350 miles away from his location...
so is there a site with more info?

(my duron system runs around 40 C all the time... )