minidump file question

Well this article only matches the ExceptionCode. Not sure it fit your situation though.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q276409

Are you getting a Blue Screen error as well. If so please post contents of the error. Also some times the error will make it to the event logs. See if the Event Viewer has logged any errors that seem to happen at the time of the error. If so please post that info as well.

Also see here
Gathering Blue Screen Information After Memory Dump in Windows 2000 or Windows NT
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q192463

Open Handles Cause STOP 0x0000001E or STOP 0x00000024
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q195857

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q301330
Stop 0x0000001E" Error Message Printing with Hewlett-Packard DesignJet Printer Driver from a Terminal Services Client

Stop 0x0000001E" Error Message When You Mount a Volume
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q287524

STOP: 0x0000001E" Error Message When You Load Windows 2000 System Registry Hive
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q289001

"Stop 0x0000001e" on Windows 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q279640

"Stop 0x0000001E" Error Message in Ntoskrnl.exe
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294690

Stop 0x0000001E in Win32k.sys When Using Animated Mouse Pointers
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q278999

In the "Gathering Blue Screen Information After Memory Dump in Windows 2000 or Windows NT" MS KB it mentions how to use the  Pstat.exe from the Resource Kit to gather the info about the drivers.


"Note that not all sections will give the same information. This will depend on the type of stop code. The information above tells you the stop code (0xc000021a) and the parameters (0xe1270188, 0x00000001, 0x00000000, 0x00000000), as well as the address of the driver that called the exception (0x8014fb84). This address can be used to identify the driver name by using the output from running Pstat.exe, which can be found in the Resource Kit.

Dumpchk.exe will also verify that the dump is valid.
Using Pstat.exe to Identify Driver Information
Pstat.exe, a Resource Kit utility, will give you a picture of the processes and drivers currently running on your system. For these purposes, the most useful information will be the list of loaded drivers that appears at the end of the output. All you need to do is run Pstat.exe from the command line. The information given by Pstat.exe can be piped to a file by using the following syntax:
pstat.exe > filename
This is an example of the driver list at the end of the output


By using the starting address shown above under the "load addr" column, you can match the exception address to the driver name. Using 8014fb84 as an example, you can determine that Ntoskrnl.exe has the nearest load address below the exception address and is most likely the driver that called the exception. With this information, you can go to the Microsoft Knowledge Base to look for known issues that match your situation."

If for some reason you don't have Pstat you can get it here.

http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/pstat-o.asp

My guess is that the problem is in the ntoskrnl.exe which may indicate faulty RAM or the RAM modules are loose or the connections are dirty.

Running Pstat gives the address of the ntoskernel as the area of problem as you say. Now does this really mean faulty RAM ? I have exchanged the RAM after a recent crash which actually gave a BSD with this message.
kernel_data_inpage_error
Dumpcheck showed this was the same address.
so... RAM ???
Is that the final solution ?





-----------------------------------------------------------------------------
ntoskrnl.exe 80400000  442368   97216  775488 Sat Apr 14 08:52:32 2001
     hal.dll 80062000   31488    8192   21280 Wed Nov 29 11:34:09 2000
 BOOTVID.DLL F4010000    5664    2464       0 Thu Nov 04 08:24:33 1999

Well according to this article SP3 may correct the problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294690

I am trying to accept the above as an answer but I am getting a 'servlet error'. I will try again later.

I am trying to accept the above as an answer but I am getting a 'servlet error'. I will try again later.