SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Dream Machine ( Build your own PC )

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Dave Hanson who wrote (7562)5/22/1999 10:42:00 PM
From: Spots  Read Replies (2) of 14778
 
>>BSOD...I'd suspect the memory (and that may still be it), but
...

One of the great debts (among others) I owe to Sean is his
persistent insistence that ECC memory is worth the price.
He convinced me. I also remember your description of how
you bought 66 mhz memory and ran it at 100 with no problems.
Chickens roosting at home now, maybe? <gg>

On all of my systems previous systems, at various times,
I've had BSOD errors that I couldn't explain. Random.
Not reproducible.

On my new systems (two bh6/300a @450), I split for all
ECC/100mhz memory. I will tell you that I have NEVER had
a BSOD on either of these machines, and one of them is
running my primary domain controller and hasn't been rebooted
more than twice since February. The other has been rebooted
more in the last three days than ever before as I experimented
with OS builds, etc.

I built these machines and took off on a business trip
in February, and I'll swear neither got rebooted again before
April.

I know this sounds like a
crock, especially considering that the great Jerry Pournelle
has to reboot his every day, but it is nevertheless true,
or nearly so. I may have forgotten one or two reboots, but
no more. The suckers just never go down. I have NEVER
rebooted except voluntarily. No BSOD, period.

I NEVER had this stability out of NT before, and I believe
it is owed to the ECC memory. I run essentially the same
NT versions on all my machines, with the exception of
NT server as the domain controller, which, in its
previous incarnation on a tyan motherboard with non-parity
EDO, went BSOD more than any other. This is not only the
same software, it's the same hard disk I put up out of
desperation (the backup domain controller's motherboard
went to that big parts bin in the sky ...<g>).

In short, I agree with your assessment. It's probably a
memory problem. I just had a BSOD today on my older
machine with very high quality (Kingston) no parity EDO
memory on an Intel motherboard. I get it every now
and again, not predictable, no reasonable cause, not
reproducible in any way I've discovered.

My advice: Get ECC memory and see if it
doesn't go away. I know it's not a cheap fix, but it's
my best answer nevertheless.

Spots
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext