hi, I ran a test on the memory with mem386 and it doesn't look good at all. I'm not saying this is the sole reason of the crashes but it might be a big factor in the whole process. This is the output ( test was still running) of what i received on screen: 1. wall time: 2:02:12 2. cached: 160 M 3. Rsvdmem: 64K 4. memmap: e820-std 5. cache: on 6. ecc: off 7. test: std 8. pass: 2 9. errors: 654 (!!!!!!!!) 10. ecc errs: 0
OUCH bigtime. This doesn't look good. I'll have to try and see what memory is responsible for this and try to take some out as you suggested. > what chipset is on the card? I remember reading a while back about > how some Nvidia chipsets draw too much power for some older AGP > slots. Even though you have PCI only, if the card is a high powered > video card it may be drawing more power then the board can take. > In 3D graphics your bottleneck will be the CPU, theres not much > point in putting a modern video card in such an old system, the > cpu won't be able to feed the card fast enough to take advantage > of it. A overheating video card wouldn't cause the system to > shut down I don't think. I've had video cards overheat and for me > at least it either locked up the system, or rebooted it(hard reboot), > but didn't power down. It's a Riva Tnt2 M64 32MB card. I think i still have an old Matrox Millenium 2, 4MB lying around somewhere. I'll put this one in just to be on the safe side. I didn't know these could draw to much power. It would exactly surprise me either. > there is CPUBurn, which comes with a few tools, I don't think it's > available in debian but its available, run a search on google or > freshmeat. CPUBurn also comes with a chipset testing utility and > a memory testing utility. For disks, I use bonnie++. Running that > in a loop for a few days can produce a good amount of wear on a disk. i had a look at the tools mentioned and they look fine indeed! thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]