From: NoEMail@home.org   
      
   Rich  wrote:   
   > root  wrote:   
   >> Rich  wrote:   
   >>> But, a Chrome process consuming 12+GB of ram is not unheard of.  You   
   >>> could, possibly, still have an "out of memory, with no swap" situation.   
   >>>   
   >>>   
   >>> You state you've replaced everything except the Nvidia card.  So if it   
   >>> is hardware, the only common hardware is the Nvidia card itself.   
   >>> Which, of course, because it is in common, /could/ be the culprit   
   >>> (i.e., you have not ruled it out, neither have you confirmed it to be   
   >>> the culprit).   
   >>>   
   >>> One way this /could/ be a hardware problem, and only just now manifest   
   >>> itself, is:   
   >>>   
   >>> 1) filter capacitors on the on-board voltage generators for the Nvidia   
   >>>    card have been slowly degrading, and have now reached the point   
   >>>    where their filtering is allowing just a bit too much ripple through   
   >>>    - which would cause a "runs fine for years, then starts failing"   
   >>>    situation.   
   >>>   
   >>> 2) cooling for the nvidia card has gotten poor (i.e., dust clogging   
   >>>    card) - which would also cause a "runs for years, then starts   
   >>>    failing situation".   
   >>   
   >> The video card is only 2 years old. It is a fanless card with a   
   >> large finned heat sink.   
   >   
   > In that case, does it get enough airflow inside the case for its   
   > cooling needs?  A clogged PSU fan, reducing airflow through the box in   
   > total, would also reduce airflow for the fanless card.   
      
   The box has 4 4-inch fans, the and one three inch fan, along   
   with the cpu fan. During the day the cpu temps stay about   
   37 degrees.   
      
      
   >   
   >>> Both are guesses.  And it could be an out of memory with no swap issue   
   >>> (which would not be the Nvidia card).  Which is also a guess.   
   >>>   
   >>> We depend upon you to test, and tell us which guess is ruled out.   
   >>   
   >> Thanks for responding.  I am currently working on the hypothesis that   
   >> it isn't a hardware problem.  I am looking into the software side.   
   >   
   > Your other post about switching to a node.js application from your own   
   > C code implies that this switch might be the cause.   
      
   I'm looking into that possibiity even as we speak. I have disabled   
   the .js code and now have to wait for the system to crash. It   
   may take several days.   
      
   Thanks for following.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)