> From: jan.stolarek@p.lodz.pl
> To: trinity-users@lists.pearsoncomputing.net
> Date: Mon, 27 Jul 2015 22:10:20 +0200
> CC: office@klepp.biz
> Subject: Re: [trinity-users] Debugging stability
>
> > You checked your hardware and it's OK?
> No, I have not checked. In the case of first machine I'm nearly 100% certain that this is not the
> fault of the hardware. I'm not so sure about the second machine - it's an old computer and it has
> experienced minor hardware problems. Not sure what exactly I should check and how should I do it.
> I was thinking about running hard-disk checks - if anyone can recommend good program for doing
> that it would be great.
>
> Still, are there any KDE logs that could be helpful in searching for the cause?
>
> Janek
>
> ---
> Politechnika Łódzka
> Lodz University of Technology
>
> Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata.
> Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę
> prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
>

Hi,

To test a computer's reliability, a good test is to run memtest86+ on it.
You can download the iso and burn it to a disc, or it often comes as one of the options on the grub menu of many livecds. If after 10-15 minutes you see no red on your screen, the you can be sure that the path between the cpu-chipset-ram is good to go.

Remember also that older TDE releases (such as 3.5.13.2) and old KDE3 is not thread-safe. This means that on multi-cores computers, troubles may happen where an app is waiting on another and it creates lock-ups. My Asus EEE X101CH is a special case where I had many thread lock issues. Most of these has been solved on newer TDE releases (such as the soon-to-be-released R14.01).

Hope it helps!
-Alexandre