Re: The Blue Screen of Death

I didn't even think of the memory (duh!). I'll go on-site tomorrow and check
it out. Thanks Danny.

Ya, I did't think that there was any way of "saving" the current environment
and restoring it. It was worth the question though.

Tom Brewer

"Danny Sanders" wrote:

I have been evualating (and troubleshooting with the vendor) some backup
software for some time now (Back4all) and every time it runs on a
customers
Win 2000 server the computer stops with the old Blue Screen

<Snip>

I thought that it was being caused by the backup software,
but today I was trying to install SP4 and the same thing happened.

Both of these actions use a lot of memory. A lot of stuff gets loaded into
RAM. It's possible that you have a bad chip on one of the memory sticks that
under normal everyday use does not get used, but under a heavy memory load
that chip gets accessed and when that happens it causes a blue screen.

I would suggest either testing by replacing the memory with known good
memory or taking half the memory out, test for blue screen, depending on the
results, through a series of removing and replacing memory you can narrow it
down to a certain stick, if memory is the problem.



here's the hitch. It's a domain controller (intranet) with 8 workstations
networked. How can I save all of the security, user settings, user data,
etc.? Then how do I apply them to the new installation? Also, if you
replace
the server in a Domain what happens to all the workstations? Will they
all
simply attach as part of the Domain and all users will be able to logon as
normal. Ya, RIGHT!

With 8 workstations, it's almost easier to start the domain over from
scratch.
I would eliminate memory as the culprit before undertaking recreating the
domain.


hth
DDS

"TomB" <TomB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3D79AFBD-8955-4FE4-9B8A-E5F8BAB0B86E@xxxxxxxxxxxxxxxx
I have been evualating (and troubleshooting with the vendor) some backup
software for some time now (Back4all) and every time it runs on a
customers
Win 2000 server the computer stops with the old Blue Screen, creates a
dump
and then restarts. I thought that it was being caused by the backup
software,
but today I was trying to install SP4 and the same thing happened. FYI, I
backed SP4 out (to SP3) and the computer again is running as an server
again
and I turned it over to the customer to use. But, I just know that there
is a
timebomb inside of it waiting to go off.

I have a dump (MEMORY.DMP) of it, but I don't know how to read them and
also
I'm not sure that it's worth spending the time to try to fix it.

So, my question is what to do now. What I "think" I want to do is to
backup
the applications and data and just do a total fresh install of the OS.
But,
here's the hitch. It's a domain controller (intranet) with 8 workstations
networked. How can I save all of the security, user settings, user data,
etc.? Then how do I apply them to the new installation? Also, if you
replace
the server in a Domain what happens to all the workstations? Will they
all
simply attach as part of the Domain and all users will be able to logon as
normal. Ya, RIGHT!

Help! Is there a procedure available that will guide me through this
process? Domains are nice, but not in this situation.

Tom Brewer



.

Relevant Pages

  • Re: Terminal Server 2000 pausing
    ... Is the server itself pausing or is it actually the network side of things? ... Have you run perfmon gathering everything over a period and then analysing ... This should also tell you if memory is ... > You caould also suspect improperly installed Office 2000 install or faulty ...
    (microsoft.public.windows.terminal_services)
  • Re: how to correct http 502 Proxy Error "no buffer space is supported", "64-Host not availabe",
    ... It looks like some kind of memory leak issue to me. ... You should install the ... ISA Server already ... > and all clients can connect internet Well. ...
    (microsoft.public.isa)
  • Re: 2003 R2 SETUP2.EXE generates "Program too big to fit in memory
    ... It is from CD2 of the Select Media for Windows ... The install of Windows was a clean install on one server and an upgrade on ... Normally when I see "Program too big to fit in memory" this is a corrupted ...
    (microsoft.public.windows.server.setup)
  • Re: The Blue Screen of Death
    ... Win 2000 server the computer stops with the old Blue Screen ... but today I was trying to install SP4 and the same thing happened. ... Both of these actions use a lot of memory. ... the server in a Domain what happens to all the workstations? ...
    (microsoft.public.win2000.general)
  • Problems installing 5.1A on XP1000
    ... The drive I'm attempting an install to is an IBM ... 640 MBytes of System Memory ... isa0 at pci0 ... DUMP: Warning: no disk available for dump. ...
    (Tru64-UNIX-Managers)