🚀 go-pugleaf

On Mon, 30 May 2005 11:17:33 -0400, "Uncle Vinnie"
<vinrin57@nospam.optonline.net> wrote:

>Thanks again!  Yes, I've seen this link in the past... great site...
>
>How about this approach- what else tracks like Eventvwr?  Is there something 
>that tracks the BIOS problems?  Or how about Bios adjustments I could make, 
>usually I leave that alone... maybe some settings?  I also read something 
>about L2 cache issues....
>
>I'm getting desperate!
>

No there is nothing like Eventviewer that tracks BIOS
problems, but then outside of bugs they (hopfully(?) aren't
aware of and thus can't track) the rest of bios isn't a
matter of  errors per se, as it is user adjustable and
dictates things- it doesn't error but rather, errors would
result.  In effect, the hardware the host, the bios the
intermediary, and the OS the client- different roles.

You might try clearing the CMOS and updating the bios.
Rarely downgrading the bios can help.  You might try
reducing the FSB speed or increasing the vcore voltage (if
possible).  You could try several things but you mention not
whether you've ran tests like Prime 95 or Memtest86- it
would be good to get an idea of WHAT specifically is causing
these errors.  As for the startup issue, being that it seems
intermittent (else the system wouldn't run at all, right?)
it would seem either power or physical contact issues.

Since the Tualatin is yet another variable, IF you had
another (Coppermine) CPU available you might first
underclock the Tualatin and if there are still errors,
compare to a Coppermine running at same FSB & memory speed.

At a certain point it may not be worth the time to
troubleshoot the same parts- either substituting different
parts again, like a different CPU, or just cutting your
losses and selling it off.  There might also be some
Tualatin supportive motherboards in the market for fairly
cheap at surplus 'sites, you might recoup some of the cost
by selling the adapter.