Windows 2000 Service Pack 4 shutdown/restart issue

  • Thread starter Thread starter Ryan
  • Start date Start date
R

Ryan

After installing Windows 2000 SP4 the following behavior
occurred on the systems listed below: (Yes I know, all
Dell's, but that's what we use here. If it isn't happening
on other manufacturer's machines, I will look to Dell for
the fix.)

Dell GX400
Dell Latitude C640
Dell Optiplex GX260 (one processor 2.4 ghz)
Dell Optiplex GX260 (hyperthreading enabled 3.06 ghZ
processor)


When shutting down or restarting the computers, we could
see a very brief blue screen flash.
The computer rebooted as expected or shut down, but when
examining the event viewer we noticed that a dump had
taken place and that a minidump log was saved.
An example of the event viewer message is shown below.
This message seemed to happen every other time the
computer was restarted or shut down. It shows up under
the "system" event viewer logs.

Source: Savedump
Category:None
EventID:1001
Description:
The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xbfd7ad16, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\Minidump\Mini071103-01.dmp.

After a few times of this behavior, the event log for
system is corrupted and unusable. (We saw this happen on
two of the systems before we decided to capture the
information)
The exact blue screen could be seen if you changed the
startup and recovery options to not reboot automatically.
Otherwise, you just get the brief flash of it, and event
viewer messages.
The blue screen is list below, forgive me though, I didn't
write down all the asterisks and such:

STOP: 0X0000001E (0XC0000005, 0XBFE85016, 0X00000000,
0X00000000) KMODE_EXCEPTION_NOT HANDLED
Address BFE85D16 base at BFE8500
Date stamp 3e25bc59 --- mup.sys
....
More information was listed, about getting the latest
bios, and making sure memory settings were not shadowed,
cached etc., but nothing too enlightening to me.

Next I ran a dump analysis of one of the minidumps that it
saved.

C:\WINNT>cd minidump

C:\WINNT\Minidump>dumpchk.exe Mini071003-01.dmp
***********************************************************
*****
**
** Windows 2000 Crash Dump Analysis
**
***********************************************************
*****
*
Filename . . . . . . .Mini071003-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x85e62000
PsLoadedModuleList . .0x80484520
PsActiveProcessHead. .0x80485c68
MachineImageType . . .i386
NumberProcessors . . .2
BugCheckCode . . . . .0x0000001e
BugCheckParameter1 . .0xc0000005
BugCheckParameter2 . .0xbfeaed16
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x80455a28



C:\WINNT\Minidump>

I'm not sure what else might prove useful, but I decided
to include information on the mup.sys file that the blue
screen references... maybe it will help figure out what's
going on.

Mup.sys file version 5.0.2195.6655
Size: 85.8 KB (87,888 bytes)
Size on disk: 88.0 KB (90,112 bytes)
Created: Thursday, March 14, 2002, 1:07:30 PM
Modified: Thursday, June 19, 2003, 12:05:04 PM
Accessed: Today, July 11, 2003, 1:46:14 PM

That's all I can think of. If you need more information I
will try to get it to you. I was just hoping to provide
the information so you guys could take a look at it, as
I'm sure that others might be experiencing the same thing.
We haven't rolled out SP4 here yet, as we wanted to test
it first and maybe improve on any things that might be
going on with it.
I hope the information helps and finds it way to the right
people.

Ryan V.
 
There's a problem with the MUP.SYS in SP4. As a temporary
work around set
HKLM\System\CurrentControlSet\Services\Mup\DisableDFS to 0

This gets rid of the blue screen. I found the fix on a
different board I posted on. Thought I would pass it along
for anyone who was looking at my first post. MS supposedly
working on a fix (updated MUP)according to another poster.
-----Original Message-----

After installing Windows 2000 SP4 the following behavior
occurred on the systems listed below: (Yes I know, all
Dell's, but that's what we use here. If it isn't happening
on other manufacturer's machines, I will look to Dell for
the fix.)

Dell GX400
Dell Latitude C640
Dell Optiplex GX260 (one processor 2.4 ghz)
Dell Optiplex GX260 (hyperthreading enabled 3.06 ghZ
processor)


When shutting down or restarting the computers, we could
see a very brief blue screen flash.
The computer rebooted as expected or shut down, but when
examining the event viewer we noticed that a dump had
taken place and that a minidump log was saved.
An example of the event viewer message is shown below.
This message seemed to happen every other time the
computer was restarted or shut down. It shows up under
the "system" event viewer logs.

Source: Savedump
Category:None
EventID:1001
Description:
The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xbfd7ad16, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\Minidump\Mini071103-01.dmp.

After a few times of this behavior, the event log for
system is corrupted and unusable. (We saw this happen on
two of the systems before we decided to capture the
information)
The exact blue screen could be seen if you changed the
startup and recovery options to not reboot automatically.
Otherwise, you just get the brief flash of it, and event
viewer messages.
The blue screen is list below, forgive me though, I didn't
write down all the asterisks and such:

STOP: 0X0000001E (0XC0000005, 0XBFE85016, 0X00000000,
0X00000000) KMODE_EXCEPTION_NOT HANDLED
Address BFE85D16 base at BFE8500
Date stamp 3e25bc59 --- mup.sys
....
More information was listed, about getting the latest
bios, and making sure memory settings were not shadowed,
cached etc., but nothing too enlightening to me.

Next I ran a dump analysis of one of the minidumps that it
saved.

C:\WINNT>cd minidump

C:\WINNT\Minidump>dumpchk.exe Mini071003-01.dmp
********************************************************** *
*****
**
** Windows 2000 Crash Dump Analysis
**
********************************************************** *
*****
*
Filename . . . . . . .Mini071003-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x85e62000
PsLoadedModuleList . .0x80484520
PsActiveProcessHead. .0x80485c68
MachineImageType . . .i386
NumberProcessors . . .2
BugCheckCode . . . . .0x0000001e
BugCheckParameter1 . .0xc0000005
BugCheckParameter2 . .0xbfeaed16
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x80455a28



C:\WINNT\Minidump>

I'm not sure what else might prove useful, but I decided
to include information on the mup.sys file that the blue
screen references... maybe it will help figure out what's
going on.

Mup.sys file version 5.0.2195.6655
Size: 85.8 KB (87,888 bytes)
Size on disk: 88.0 KB (90,112 bytes)
Created: Thursday, March 14, 2002, 1:07:30 PM
Modified: Thursday, June 19, 2003, 12:05:04 PM
Accessed: Today, July 11, 2003, 1:46:14 PM

That's all I can think of. If you need more information I
will try to get it to you. I was just hoping to provide
the information so you guys could take a look at it, as
I'm sure that others might be experiencing the same thing.
We haven't rolled out SP4 here yet, as we wanted to test
it first and maybe improve on any things that might be
going on with it.
I hope the information helps and finds it way to the right
people.

Ryan V.



.
Click to expand...
 
Back
Top