I didn't mean to imply that 60C is normal operating temperature, but rather the highest observed peak:
SYS Temp: +37.6°C (limit = +80°C, hysteresis = +70°C) CPU Temp: +40.8°C (limit = +60°C, hysteresis = +55°C) On Sun, 2002-10-27 at 06:38, Robert Crawford wrote: > Jack, > I've got experience with KT133 and KT266A, AMD athlons. I've researched it for > about 2 years, and the consensus is overwhelmingly that what AMD says about > cpu temps is wrong in practical terms. As my own experience (and that of many > others) shows conclusively, anything over 45C. is going to cause problems. > Most AMD users who are knowlegable will not tolerate anything over 45C. This > is the number one cause of random odd problems with AMD systems. If your cpu > is really running at 60C., you have a major, major heat problem. I would > immediately do something about cooling both the case air with a ducting > modification, better case fans, and a better heatsink/fan for the cpu. > Robert Crawford > > On Saturday 26 October 2002 06:36 pm, Jack Coates wrote: > > Hi, > > > > I have a machine (naturally a fairly important one) which I built and > > which is fairly unstable -- give it ten to twenty days, and it will > > suffer a video lock up or a disk error that forces a reboot. > > > > FIC AZ11 with a VIA KT133 chipset. > > Athlon 900 MHz > > 768MB PC100 RAM > > Voodoo3 3000 AGP card > > Maxtor 92049U6 (20G 7200 RPM disk), etx3fs on all partitions. > > Polaroid CD-RW IDE3212 > > (2) Lite-On Communications Inc LNE100TX PCI tulip NICs > > > > The system runs MDK 9.0 and ran 8.2 before that. I keep an eye on it > > with lm_sensors, and it doesn't go over 60C, so I've tentatively ruled > > CPU heat out as a cause. I've also run memtest86 several times for runs > > of up to 12 hours, with no RAM problems detected. > > > > today's reboot was caused by a corrupt wtmp that prevented logins. fsck > > fixed it. > > > > At this point, I'm suspecting the motherboard's IDE controller, the hard > > disk itself, the video card, the RAM, gremlins :-) I'm just not sure > > where to go next in troubleshooting the system, and I don't want to > > replace everything one part at a time. > > > > any ideas for narrowing this down? > > > ---- > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com -- Jack Coates Monkeynoodle: A Scientific Venture...
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
