BSOD - Rule of thumb?

  • Thread starter Thread starter BigAl.NZ
  • Start date Start date
B

BigAl.NZ

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
 
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?
Click to expand...

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.
 
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?
Click to expand...

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.
 
Wasn't it <[email protected]> in message
, 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
Click to expand...


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.
 
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
Click to expand...

May be.
(b) Bad sectors on critical parts of the HDD.
Click to expand...
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?
Click to expand...
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
 
Dianthus said:
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.
Click to expand...

You'd be mistaken. BSODs suggest a number of fatal error conditions, and
memory "management" is only one class of error here.
 
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?
Click to expand...

Just about any serious hardware fault. Drivers are, as someone said already,
a pretty common cause.
 
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
Click to expand...


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:



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
 
You'd be mistaken. BSODs suggest a number of fatal error conditions, and
memory "management" is only one class of error here.
Click to expand...

Would you care to elaborate further on this?

What are all the fatal error conditions that you are referring to?
 
Dianthus said:
Would you care to elaborate further on this?

What are all the fatal error conditions that you are referring to?
Click to expand...
A BSOD is analogous to a 'kernel panic'. Any kernel level condition that
cannot be handled can lead to a 'kernel panic' or 'BSOD'. In both the
Unix model and the Windows model you cannot have a part of the address
space that belongs to more than one process, unless that part of the
address space is specifically defined to be in shared space. Very often
the cause of a serious kernel level is trying to access a part of the
address space that has not been defined, probably because of a corrupted
or non-initialised pointer. An error in an error handler such that the
error could not be handled by a lower level handler would cause a
'kernel panic' or 'BSOD'.

Cheers,

Cliff
 
Bruce said:
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.
Click to expand...
Could be bad sectors causing corrupted drivers. Consider, a sector goes
bad, gets read (badly) as part of a driver loading. The driver is now
'corrupt' and fails on every load. Reinstalling the driver makes it use
different sectors, and the problem goes away.

Cheers,

Cliff
 
Enkidu said:
Could be bad sectors causing corrupted drivers. Consider, a sector goes
bad, gets read (badly) as part of a driver loading. The driver is now
'corrupt' and fails on every load. Reinstalling the driver makes it use
different sectors, and the problem goes away.
Click to expand...


I concede the possibility, certainly. Although, so far, diagnostics
run on the hard drives of machines with driver failures haven't reported
any such problems. I'm not saying bad sectors can't cause a BSOD, just
that it hasn't yet happened to me.


--

Bruce Chambers

Help us help you:



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
 
WhzzKdd said:
<quote>
generally related to either :
(a) Memory
(b) Bad sectors on critical parts of the HDD.
</quote>

should be dismissed as totally wrong.
Click to expand...

Hmmm. In terms of percentage of options on the list of things that can cause
an error you are, of course, totally correct.

In terms of percentage of things that actually occur day to day, I'm willing
to bet memory and disk errors take a good fair share of scalps, but of
course they don't tell the whole story by any means.
 
Enkidu said:
Could be bad sectors causing corrupted drivers. Consider, a sector
goes bad, gets read (badly) as part of a driver loading. The driver
is now 'corrupt' and fails on every load. Reinstalling the driver
makes it use different sectors, and the problem goes away.
Click to expand...

Certainly a good candidate but my experience of "bad drivers" has been "bad
in the sense that the programmer was apparently wearing boxing gloves and
drunk off his head while coding" more than anything else.
 
Robert said:
Hmmm. In terms of percentage of options on the list of things that
can cause an error you are, of course, totally correct.

In terms of percentage of things that actually occur day to day, I'm
willing to bet memory and disk errors take a good fair share of
scalps, but of course they don't tell the whole story by any means.
Click to expand...

Well, in my experience, memory issues (faulty memory, memory management
errors withing Windows) has been way down the list. Most frequently BSODs
have been issues with drivers, second most frequent are because of hard
drive errors that have occurred.

As always, YMMV. I would guess a lot of that might depend on what hardware
is most often on someone's workbench.
 
Enkidu said:
Could be bad sectors causing corrupted drivers. Consider, a sector
goes bad, gets read (badly) as part of a driver loading. The driver
is now 'corrupt' and fails on every load. Reinstalling the driver
makes it use different sectors, and the problem goes away.

Cheers,

Cliff
Click to expand...

Not at all infrequent. Not only drivers, but other primary components of the
OS can be corrupted by failing sectors. I've had systems on my bench for
that exact problem several times in the last year.
 
A BSOD is analogous to a 'kernel panic'. Any kernel level condition that
cannot be handled can lead to a 'kernel panic' or 'BSOD'. In both the
Unix model and the Windows model you cannot have a part of the address
space that belongs to more than one process, unless that part of the
address space is specifically defined to be in shared space. Very often
the cause of a serious kernel level is trying to access a part of the
address space that has not been defined, probably because of a corrupted
or non-initialised pointer. An error in an error handler such that the
error could not be handled by a lower level handler would cause a
'kernel panic' or 'BSOD'.
Click to expand...

Yeah - that is very much like what I thought. Thanks for the more detailed
explanation.
 
Back
Top