On 12/01/2014 22:49, Uncle Peter wrote:
On Sun, 12 Jan 2014 11:52:03 -0000, John Williamson
wrote:

On 11/01/2014 19:32, Uncle Peter wrote:
On Sat, 11 Jan 2014 19:08:13 -0000, tony sayer
wrote:


No great fan of m$ but we still have a couple of olde WIN2K machines
one
has been up for 8500 odd hrs and as to the main machine WIN 7 and I
really can't fault it at all!...

Plus the odd couple of XP machines no problems there either..

M$ gets blamed for blue screens. 99% of them are due to faulty memory.
Always run 3 passes of memtest on a new machine.

Most BSODs that I've had have turned out to be faulty hardware drivers,
mostly video card ones, and the others to badly written programmes or HD
corruption. I've never yet had one that could be traced to faulty memory.

I've found brand new cheap memory to be faulty 10% of the time. And
decent memory to be faulty 3% of the time.


Which suggests that you are handling improperly and causing the failures
you observe (or attributing some other fault to memory)

I don't recall having any failure on new memory devices from a range of
manufacturers, after many hundreds of installs.


--
Cheers,

John.

/================================================== ===============\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\================================================= ================/