On Sun, 12 Jan 2014 22:01:10 -0000, polygonum wrote:

On 12/01/2014 11:52, 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 have recently been involved with a Dell that was BSODing. Took one
stick of memory out - OK. Obviously that as at fault. Make sure - swap
the removed stick back in and take the other one out. Still OK.

Ended up that both sticks were fine - and motherboard was happy with
either stick in either socket. But as soon as there were two sticks, it
BSODed again. Confirmed by Dell engineer (was still under warranty) -
and replaced.

You can also lower the clock speed to avoid a fault.

--
"An abstract noun," the teacher said, "is something you can think of, but you can't touch it. Can you give me an example of one?"
"Sure," a teenage boy replied. "My father's new car."