Quote:
Originally Posted by Idoine
 Avast Home/Familial (the free one !) is good, for a free one, and in french ! But it has its limits (this is an opinion of "experts" in antivirus !  ). Nod32 is considered one of the bests by the sames... It's not mine, I have KIS personally, for years now, and as I'm pretty satisfied I don't see the reason to change ! 
For Teatimer, I had a problem once (before I turn it on, and before I purchased KIS in lieu of KAV !  ), it was my mistake (I installed a patch for Windows Messenger before verifying its safeness  ). Now, with both softwares, when I scan my computer, I'm happy with 0 spywares ! 
|
okay ! well, i think i'll stick with avast for now, free is good !

this computer stuff costs a lot of money so i'll take advantage of that when i can... but i'll turn that teatimer back on.
Quote:
Originally Posted by 6charlong
I've come to this thread late. There are so many things that it could be. But your description reminded me of a PC we had in the office with the same symptoms and thought to share what that one was.
It tracked back to the fact that there was a refrigerator on the same circuit as the PC. When the big old motor in the 'frig kicked on it created a power sag. Integrated circuits hate power sags. Actually, motors in heaters, air conditioners, fans, etc., create 'line noise' and some power fluctuations.
With a UPS your PC actually draws power from the battery, while the UPS recharges from your power main. If the problem is coming from the power source and if you decide to get a UPS, it might be wise to find out what replacement batteries cost for the model you consider. If the problem is power, that battery will keep on getting hammered and have to be replaced.
Just another one of the possibilities.
|
hm, thanks for that info. i'm not sure whether there could be anything else on the circuit, in this house anything is possible, but i doubt it's the refrigerator ; i'm pretty sure it has its very own circuit.
anyway it might not be the power after all ; this morning when i turned it on, i had a "serious error" in the nanosecond after it started the boot cycle (the monitor splash screen had just appeared, which is i believe the very first thing to come on the screen during the boot process) :
Code:
Type de l'événement*: Erreur
Source de l'événement*: System Error
Catégorie de l'événement*: (102)
ID de l'événement*: 1003
Description*:
Code erreur 1000008e, paramètre 1 c0000005, paramètre 2 bf951755, paramètre 3 a7a3dc00, paramètre 4 00000000.
Pour plus d'informations, consultez le centre Aide et support à l'adresse http://go.microsoft.com/fwlink/events.asp.
Données*:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 39 35 31 37 35 35 bf951755
0040: 2c 20 61 37 61 33 64 63 , a7a3dc
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000
i turned on the radio first, and it didn't shut off, so that makes me think it wasn't electrical. and it couldn't be the heat, because it is freezing here, so especially when it had been off overnight it couldn't have been overheated.
*sigh*
more testing...