Hi Guys,

I was speaking to someone the other day who said as a rule of thumb,
BSOD errors are generally related to either :
(a) Memory
(b) Bad sectors on critical parts of the HDD.

Anyone care to add there opinion to this?

Cheers

-Al

On 28 Jan 2007 01:52:29 -0800, (E-Mail Removed) wrote:

> I was speaking to someone the other day who said as a rule of thumb,
> BSOD errors are generally related to either :
> (a) Memory
> (b) Bad sectors on critical parts of the HDD.
>
> Anyone care to add there opinion to this?

Also driver problems.

--

.... Brendan

#15641 +(3774)- [X]

<superwoman> I had a boyfriend once that made me suck him off while I had a
mouthful of beer.
<GrandCow> HAHAHAHA that was me bitch!
<superwoman> DANNY?!?!?!
<GrandCow> MOM?!?!?!?!


Note: All my comments are copyright 28/01/2007 11:12:01 p.m. and are opinion only where not otherwise stated and always "to the best of my recollection". www.computerman.orcon.net.nz.

On Sun, 28 Jan 2007 01:52:29 -0800, BigAl.NZ wrote:

> Hi Guys,
>
> I was speaking to someone the other day who said as a rule of thumb,
> BSOD errors are generally related to either :
> (a) Memory
> (b) Bad sectors on critical parts of the HDD.
>
> Anyone care to add there opinion to this?

Why the cross-posting?

I would have said BSODs indicate poor memory management by the OS, becuase
they indicate where a process attempts to access memory that properly
belongs to another process.

The fact that BSODs aren't so common anymore indicates that the memory
management has improved.

I would have expected some other error message for a disc read/write/access
error.


--
Dianthus Mimulus

Microsoft's business practises exposed in court:
http://www.maxframe.com/DR/Info/full...#_Toc447960918

Wasn't it <(E-Mail Removed)> in message
news:(E-Mail Removed) , who said
something like......???
> Hi Guys,
>
> I was speaking to someone the other day who said as a rule of thumb,
> BSOD errors are generally related to either :
> (a) Memory
> (b) Bad sectors on critical parts of the HDD.
>
> Anyone care to add there opinion to this?
>
> Cheers
>
> -Al


A rule of thumb is that if you speak to hardware specialist they'll give you
a hardware explanation for the errors, and a software specialist will give
you a software explanation.

--
Jon

(E-Mail Removed) wrote:

> Hi Guys,
>
> I was speaking to someone the other day who said as a rule of thumb,
> BSOD errors are generally related to either :
> (a) Memory

May be.

> (b) Bad sectors on critical parts of the HDD.
>
As well.
Happened to a co-worker a week ago. I could ghost the drive with the
ignore-bad-sector switch, to another one, then make a xp repair install yet
still it came up only in safe mode, with a BSOD otherwise.
Had to dig the drivers directory and move out any non-microsofties first (it
helps to change the detailed-view properties for that task), then reinstall
all the graphics, directcd and other stuff from media, and reapply the xp
updates/fixes.

Still don't know which one of the drivers got stuffed and wasn't recognized
by the repair install.

> Anyone care to add there opinion to this?
>
There are a quadzillion reasons for them, like
- bad software, in particular drivers
- malfunctioning cpu or mainboard, due to
-- many reasons, including PSU failures
-- memory mismatches
-- overclocked chipsets
-- overheated cpu or chipsets

--
vista policy violation: Microsoft optical mouse found penguin patterns
on mousepad. Partition scan in progress to remove offending
incompatible products. Reactivate MS software.
Linux 2.6.17-mm1,Xorg7.1/nvidia [LinuxCounter#295241,ICQ#4918962]

Dianthus Mimulus wrote:
> On Sun, 28 Jan 2007 01:52:29 -0800, BigAl.NZ wrote:
>
>> Hi Guys,
>>
>> I was speaking to someone the other day who said as a rule of thumb,
>> BSOD errors are generally related to either :
>> (a) Memory
>> (b) Bad sectors on critical parts of the HDD.
>>
>> Anyone care to add there opinion to this?
>
> Why the cross-posting?
>
> I would have said BSODs indicate poor memory management by the OS,
> becuase they indicate where a process attempts to access memory that
> properly belongs to another process.

You'd be mistaken. BSODs suggest a number of fatal error conditions, and
memory "management" is only one class of error here.

(E-Mail Removed) wrote:
> Hi Guys,
>
> I was speaking to someone the other day who said as a rule of thumb,
> BSOD errors are generally related to either :
> (a) Memory
> (b) Bad sectors on critical parts of the HDD.
>
> Anyone care to add there opinion to this?

Just about any serious hardware fault. Drivers are, as someone said already,
a pretty common cause.

(E-Mail Removed) wrote:
> Hi Guys,
>
> I was speaking to someone the other day who said as a rule of thumb,
> BSOD errors are generally related to either :
> (a) Memory
> (b) Bad sectors on critical parts of the HDD.
>
> Anyone care to add there opinion to this?
>
> Cheers
>
> -Al
>


Of all the BSods I've seen over the years, some were caused by
defective memory, none by bad sectors on the hard drive (although I'll
concede the possibility, just haven't encountered it), and most by
corrupted/damaged/incompatibile device drivers.


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell

On Sun, 28 Jan 2007 17:29:52 +0000, Robert Moir wrote:

>>> Anyone care to add there opinion to this?
>>
>> Why the cross-posting?
>>
>> I would have said BSODs indicate poor memory management by the OS,
>> becuase they indicate where a process attempts to access memory that
>> properly belongs to another process.
>
> You'd be mistaken. BSODs suggest a number of fatal error conditions, and
> memory "management" is only one class of error here.

Would you care to elaborate further on this?

What are all the fatal error conditions that you are referring to?


--
Dianthus Mimulus

Microsoft's business practises exposed in court:
http://www.maxframe.com/DR/Info/full...#_Toc447960918

Dianthus Mimulus wrote:
> On Sun, 28 Jan 2007 17:29:52 +0000, Robert Moir wrote:
>
>>>> Anyone care to add there opinion to this?
>>>
>>> Why the cross-posting?
>>>
>>> I would have said BSODs indicate poor memory management by the OS,
>>> becuase they indicate where a process attempts to access memory that
>>> properly belongs to another process.
>>
>> You'd be mistaken. BSODs suggest a number of fatal error conditions,
>> and memory "management" is only one class of error here.
>
> Would you care to elaborate further on this?
>
> What are all the fatal error conditions that you are referring to?

ALL? Hah! You don't want to know ALL the BSOD errors. Here's a short list of
common BSOD stop errors:

http://www.geekstogo.com/forum/Windo...es-t43519.html

You want more?

http://safari.oreilly.com/0596004168/winxpannoy-APP-E

You want ALL? Buy a book.