The only thing in the event log was: The computer has rebooted from a
bugcheck.  The bugcheck was: 0x00000077 (0xc000000e, 0xc000000e,
0x00000000, 0x00a2f000). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\Minidump\Mini110503-01.dmp. 

The dump doesn't tell me anything, but that could be because I don't know
what to look for.  Basically it kinda looks like a list of all the services
etc that were running at the time.  (What on earth is kmixer.sys?)  Here's
what it looks like if I open it using Word's "recover text from any
document":

PAGEDUMP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGE
PAGEPAGEPAGEPAGEPAGEPAGEp^BŒ
éŽ
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
kmixer.sys
GenuineIntel
System
temRoot\
j"j; O
PNP_TDI
Paralle
Paralle
CDROM cl
temRoot\退
temRoot\
CDROM cl
SCSI cla
temRoot\
em Bus E倀
Keyboa
Keyboa
Keyboa
Keyboa
temRoot\
Š劖蒨龐萀Paralle
Paralle耀
?9C<(R
e system 
ete PC M
HeH„hƒH„FFFFFFFFFFFFFFFF
H„Š From: "Rich" 
> This is a multi-part message in MIME format.
> ------=_NextPart_000_0478_01C3A455.9CA79670
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> I have seen this with both a problem disk and a problem disk =
> controller.  It is also possible to see when loading something over the =
> network if there is a network error.  It should be an I/O error of some =
> form or another.  If a disk error I would expect to see disk related =
> error events in your event log.
> Rich
> "Ellen K."  wrote in message =
> news:8t1lqvg8846fhvp1n26lcvubgkgpd1lek2{at}4ax.com...
> So do you agree with George that the disk is the likely source of the
> problem?
> On Wed, 5 Nov 2003 18:34:25 -0800, "Rich"  wrote in message
> :
>> The text description associated with the message is
>> 
>> The instruction at "0x%08lx" referenced memory at
"0x%08lx". The =
> required data was not placed into memory because of an I/O error status =
> of "0x%08lx".
>> 
>> The simple answer is that this error occurs when there is a fatal I/O =
> error paging in memory from disk in response to a page fault.
>> 
>> Rich
>> 
>> "Ellen K"  wrote in message =
> news:109dd7.65a92a{at}harborwebs.com...
>> What is a kernel stack inpage error?  I can't find anything on =
> MSDN.
> ------=_NextPart_000_0478_01C3A455.9CA79670
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> 
>  charset=3Diso-8859-1">
> 
> 
> 
> 
>    I
have seen this with both =
> a problem=20
> disk and a problem disk controller.  It is also possible to see =
> when=20
> loading something over the network if there is a network error.  It =
> should=20
> be an I/O error of some form or another.  If a disk error I would =
> expect to=20
> see disk related error events in your event log.
>  
> Rich
>  
>  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
> BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> "Ellen K." < =
>
href=3D"72322.1016{at}compuserve.com&g=">mailto:72322.1016{at}compuserve.com">72322.1016{at}compuserve.com&g=
> t;=20
> wrote in message  =
>
href=3D"news:8t1lqvg8846fhvp1n26lcvubgkgpd1lek2{at}4ax.com">news:8t1lqvg8846=
> fhvp1n26lcvubgkgpd1lek2{at}4ax.com...So=20
> do you agree with George that the disk is the likely source of=20
> theproblem?On Wed, 5 Nov 2003 18:34:25
-0800, "Rich" =
> <{at}>=20
> wrote in message< =
>
href=3D"3fa9b324{at}w3.nls.net>:&=">mailto:3fa9b324{at}w3.nls.net">3fa9b324{at}w3.nls.net>:&=
> gt;  =20
> The text description associated with the message =
> is>>  The=20
> instruction at "0x%08lx" referenced memory at
"0x%08lx". The required =
> data was=20
> not placed into memory because of an I/O error status of=20
> "0x%08lx".>>The simple
answer is that this error occurs =
> when=20
> there is a fatal I/O error paging in memory from disk in response to a =
> page=20
>
fault.>>Rich>> 
"Ellen K" <
href=3D"Ellen.K{at}harborwebs.com>">mailto:Ellen.K{at}harborwebs.com">Ellen.K{at}harborwebs.com>
=
> wrote in=20
> message  =
>
href=3D"news:109dd7.65a92a{at}harborwebs.com">news:109dd7.65a92a{at}harborwebs.=
> com...> =20
> What is a kernel stack inpage error?  I can't find anything on=20
> MSDN.

--- BBBS/NT v4.01 Flag-5