On the other hand, my experience with NT has been very good. I'm actually
running beta 2 of the Windows Terminal Server flavor of NT, but it still
just keeps running.
In my experience, the primary cause of BSOD is bad memory, followed by buggy
OEM-supplied device drivers. E.g. our dial-in RAS server was up for 337
days, until 3 days ago when it got a NMI memory parity error BSOD.
Unfortunately, most PCs don't have memory parity. As one researcher here
noted, PC manufacturers have negative incentive to use parity. If they use
parity, then their customers know when they have a hardware problem. If they
don't, then memory problems just look like a miscellany of software
problems.
- Joe
Joseph S. Barrera III <joebar@acm.org>
<http://research.microsoft.com/~joebar/>
Phone, Office: (415) 778-8227; Cellular: (415) 601-3719; Home: (650)
588-4801
The opinions expressed in this message are my own personal views and do not
reflect the official views of Microsoft Corporation.