TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: Ellen K
from: Rich
date: 2003-11-06 22:15:36
subject: Re: kernel stack inpage error ?

From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_04FE_01C3A4B3.81323B80
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Based on the 0xC000000E status code I suspect it is either the disk =
controller or the controller portion of the drive instead of the =
platters.  The error is STATUS_NO_SUCH_DEVICE which I would expect if = the
request to read from the page file fails because the drive appears = to
have disappeared at least temporarily.  If this is a one shot failure = it
could also be bad memory.

Rich

  "Ellen K"  wrote in message =
news:a09de7.6684ad{at}harborwebs.com...
  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.=20

  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
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  PAGEPAGEPAGEPAGEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  GEPAGEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  =
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAG
  =
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPA
  =
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEP
  =
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGE
  PAGEPAGEPAGEPAGEPAGE
  PAGEPAGEPAGEPAGEPAGEPAGEp^B=EE
  =A4=C4
  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\
  =E8劖蒨龐萀Paralle
  Paralle耀
  ?9C<(R
  e system 
  ete PC M
  HeH=E4h=E2H=E4FFFFFFFFFFFFFFFF
  H=E4=E8 From: "Rich" 
  > This is a multi-part message in MIME format.
  > ------=3D_NextPart_000_0478_01C3A455.9CA79670
  > Content-Type: text/plain;
  > charset=3D"iso-8859-1"
  > Content-Transfer-Encoding: quoted-printable
  > I have seen this with both a problem disk and a problem disk =3D
  > controller.  It is also possible to see when loading something over =
the =3D
  > network if there is a network error.  It should be an I/O error of =
some =3D
  > form or another.  If a disk error I would expect to see disk related =
=3D
  > error events in your event log.
  > Rich
  > "Ellen K."  wrote in message =3D
  > 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
  >>=20
  >> The instruction at "0x%08lx" referenced memory at
"0x%08lx". The =
=3D
  > required data was not placed into memory because of an I/O error =
status =3D
  > of "0x%08lx".
  >>=20
  >> The simple answer is that this error occurs when there is a fatal =
I/O =3D
  > error paging in memory from disk in response to a page fault.
  >>=20
  >> Rich
  >>=20
  >> "Ellen K"  wrote in message =3D
  > news:109dd7.65a92a{at}harborwebs.com...
  >> What is a kernel stack inpage error?  I can't find anything on =3D
  > MSDN.
  > ------=3D_NextPart_000_0478_01C3A455.9CA79670
  > Content-Type: text/html;
  > charset=3D"iso-8859-1"
  > Content-Transfer-Encoding: quoted-printable
  > 
  > 
  >  charset=3D3Diso-8859-1">
  > 
  > 
  > 
  > 
  >    I have seen this =
with both =3D
  > a problem=3D20
  > disk and a problem disk controller.  It is also possible to see =
=3D
  > when=3D20
  > loading something over the network if there is a network =
error.  It =3D
  > should=3D20
  > be an I/O error of some form or another.  If a disk error I =
would =3D
  > expect to=3D20
  > see disk related error events in your event log.
  >  
  > Rich
  >  
  >  style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
  > BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  > "Ellen K." < =3D
  > =
href=3D3D"72322.1016{at}compuserve.com=">mailto:72322.1016{at}compuserve.com">72322.1016{at}compuserve.com=
&g=3D
  > t;=3D20
  > wrote in message  =3D
  > =
href=3D3D"news:8t1lqvg8846fhvp1n26lcvubgkgpd1lek2{at}4ax.com">news:8t1lqvg88=
46=3D
  > fhvp1n26lcvubgkgpd1lek2{at}4ax.com...So=3D20
  > do you agree with George that the disk is the likely source of=3D20
  > theproblem?On Wed, 5 Nov 2003 18:34:25
-0800, "Rich" =3D
  > <{at}>=3D20
  > wrote in message< =3D
  > =
href=3D3D"3fa9b324{at}w3.nls.net>:mailto:3fa9b324{at}w3.nls.net">3fa9b324{at}w3.nls.net>:
>&=3D
  > gt;  =3D20
  > The text description associated with the message =3D
  > is>>  The=3D20
  > instruction at "0x%08lx" referenced memory at
"0x%08lx". The =
required =3D
  > data was=3D20
  > not placed into memory because of an I/O error status of=3D20
  > "0x%08lx".>>The simple
answer is that this error =
occurs =3D
  > when=3D20
  > there is a fatal I/O error paging in memory from disk in response to =
a =3D
  > page=3D20
  >
fault.>>Rich>> 
"Ellen K" =
< =
href=3D3D"Ellen.K{at}harborwebs.com>">mailto:Ellen.K{at}harborwebs.com">Ellen.K{at}harborwebs.com>
=
=3D
  > wrote in=3D20
  > message  =3D
  > =
href=3D3D"news:109dd7.65a92a{at}harborwebs.com">news:109dd7.65a92a{at}harborweb=
s.=3D
  > com...> =3D20
  > What is a kernel stack inpage error?  I can't find anything =
on=3D20
  > MSDN.
------=_NextPart_000_04FE_01C3A4B3.81323B80
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Based on
the 0xC000000E =
status code I=20
suspect it is either the disk controller or the controller portion of = the drive=20
instead of the platters.  The error is STATUS_NO_SUCH_DEVICE which
= I would=20
expect if the request to read from the page file fails because the drive = appears=20
to have disappeared at least temporarily.  If this is a one shot =
failure it=20
could also be bad memory.
Rich
 

  "Ellen K" <Ellen.K{at}harborwebs.com>">mailto:Ellen.K{at}harborwebs.com">Ellen.K{at}harborwebs.com>
=
wrote in=20
  message news:a09de7.6684ad{at}harborwebs.=
com...The=20
  only thing in the event log was:The computer has rebooted from a=20
  bugcheck.  The bugcheck was: 0x00000077(0xc000000e, =
0xc000000e,=20
  0x00000000, 0x00a2f000). Microsoft Windows 2000[v15.2195]. A dump =
was=20
  saved in: C:\WINNT\Minidump\Mini110503-01.dmp. The dump =
doesn't tell=20
  me anything, but that could be because I don't know whatto look =
for. =20
  Basically it kinda looks like a list of all the services etc =
thatwere=20
  running at the time.  (What on earth is kmixer.sys?)  Here's =
what it=20
  lookslike if I open it using Word's "recover text from any=20
  =
document":PAGEDUMPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPA=
GEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAG=
EPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGE=
PAGEPAGEPAGEPAGEPAGEp^B=EE=A4=C4PAGEPAGEPAGEPAGEPAGEPAGEPAGEPAGEP=
AGEPAGEPAGEPAGEPAGEPAGEkmixer.syskmixer.syskmixer.syskmix=
er.syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.=
syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.sys=
kmixer.syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.syskm=
ixer.syskmixer.syskmixer.syskmixer.syskmixer.syskmixe=
r.syskmixer.syskmixer.syskmixer.syskmixer.syskmixer.s=
yskmixer.syskmixer.syskmixer.syskmixer.syskmixer.sys<=
BR>kmixer.syskmixer.syskmixer.syskmixer.syskmixer.sys=
kmixer.syskmixer.syskmixer.syskmixer.syskmixer.sysGen=
uineIntelSystemtemRoot\j"j; =
OPNP_TDIParalleParalleCDROM=20
 
cltemRoot\&#36864;temRoot\&#57344;CDROM
clSCSI =

  clatemRoot\em Bus=20
  =
E&#20480;KeyboaKeyboaKeyboaKeyboatemRoot\=E8&=
amp;#21142;&#33960;&#40848;&#33792;ParalleParalle&#32=
768;?9C<(Re=20
  system&#8192;&#60765;ete PC=20
  =
MHeH=E4h=E2H=E4FFFFFFFFFFFFFFFFH=E4=E8<H=E4FFFFFFFFFFFFFFFFstem\Curvice\Net&#32768;&#60715;temRoot\-=E4=E8V9=E4=
ntdll.dllP,=E4OP     =20
  =
ntoskrnl.exentoskrnl.exehal.dllhal.dllBOOTVID.DLL=
BOOTVID.DLLACPI.sysACPI.sysWMILIB.SYSWMILIB.SYSpci.sy=
spci.sysisapnp.sysisapnp.sysintelide.sysintelide.sys<=
BR>PCIIDEX.SYSPCIIDEX.SYSMountMgr.sysMountMgr.sysftdisk.s=
ysftdisk.sysDiskperf.sysDiskperf.sysdmload.sysdmload.=
sysdmio.sysdmio.sysPartMgr.sysPartMgr.sysatapi.sysatapi.sysdisk.sysdisk.sysCLASSPNP.SYSCLASSPNP.SYSFas=
tfat.sysFastfat.sysKSecDD.sysKSecDD.sysNDIS.sysNDIS.s=
ysGernuwa.sysGernuwa.sysNaiFsRec.sysNaiFsRec.sysMup.s=
ysMup.sysagp440.sysagp440.sysVIDEOPRT.SYSVIDEOPRT.SYS=
ati2mtaa.sysati2mtaa.sysaw_host5.sysaw_host5.sysi8042=
prt.sysi8042prt.syskbdclass.syskbdclass.sysmouclass.sysmouclass.sysfdc.sysfdc.sysserial.sysserial.sysseren=
um.sysserenum.sysparport.sysparport.sysgameenum.sysga=
meenum.sysKS.SYSKS.SYSportcls.sysportcls.sysctlsb16.s=
ysctlsb16.sysCdr4_2K.SYSCdr4_2K.SYScdrom.syscdrom.sys=
Cdralw2k.SYSCdralw2k.SYSpwd_2K.SYSpwd_2K.SYSUSBD.SYS<=
BR>USBD.SYSuhcd.sysuhcd.sysel90Xbc5.SYSel90Xbc5.SYSwi=
nachcf.syswinachcf.sysModem.SYSModem.SYSaudstub.sysau=
dstub.sysrasl2tp.sysrasl2tp.sysndistapi.sysndistapi.sysndiswan.sysndiswan.sysTDI.SYSTDI.SYSraspptp.sysrasp=
ptp.sysptilink.sysptilink.sysraspti.sysraspti.syspara=
llel.sysparallel.sysswenum.sysswenum.sysupdate.sysupd=
ate.sysflpydisk.sysflpydisk.sysusbhub.sysusbhub.sysND=
Proxy.SYSNDProxy.SYSFs_Rec.SYSFs_Rec.SYSNull.SYSNull.=
SYSBeep.SYSBeep.SYSvga.sysvga.sysawlegacy.sysawle=
gacy.sysmnmdd.SYSmnmdd.SYScdudf.SYScdudf.SYSMsfs.SYS<=
BR>Msfs.SYSNpfs.SYSNpfs.SYSUdfReadr.SYSUdfReadr.SYSra=
sacd.sysrasacd.systcpip.systcpip.sysmsgpc.sysmsgpc.sy=
swanarp.syswanarp.sysnetbt.sysnetbt.sysnetbios.sysnetbios.sysrdbss.sysrdbss.sysnicm.sysnicm.sysmrxsmb.=
sysmrxsmb.sysNtfs.SYSNtfs.SYSEFS.SYSEFS.SYSdump_W=
MILIB.SYSdump_WMILIB.SYSdump_atapi.sysdump_atapi.syswin32=
k.syswin32k.sysAWDDI.DLLAWDDI.DLLati2dvaa.DLLati2dvaa=
.DLLawvid5.dllawvid5.dllnwlnkipx.sysnwlnkipx.sysnwlnk=
nb.sysnwlnknb.sysresmgr.sysresmgr.sysafd.sysafd.sysnwlnkspx.sysnwlnkspx.syswdmaud.syswdmaud.syssysaudio.sy=
ssysaudio.sysParVdm.SYSParVdm.SYSFips.SYSFips.SYS=
nwfs.sysnwfs.sysNWSAP.sysNWSAP.sysnwdhcp.sysnwdhcp.sy=
ssrv.syssrv.sysnwsipx32.sysnwsipx32.syssrvloc.sys=
srvloc.sysCdfs.SYSCdfs.SYSipsec.sysipsec.sysNaiFiltr.=
sysNaiFiltr.sysNWSNS.sysNWSNS.sysnwslp.sysnwslp.sysNWHOST.sysNWHOST.sysnwdns.sysnwdns.syskmixer.syskmi=
xer.sysTRGD>=20
  From: "Rich" <{at}>> This is a
multi-part message in MIME=20
  format.>
------=3D_NextPart_000_0478_01C3A455.9CA79670>=20
  Content-Type: text/plain;>
charset=3D"iso-8859-1">=20
  Content-Transfer-Encoding: quoted-printable> I have seen this =
with both=20
  a problem disk and a problem disk =3D>
controller.  It is =
also=20
  possible to see when loading something over the =3D> network if =
there is=20
  a network error.  It should be an I/O error of some
=3D> =
form or=20
  another.  If a disk error I would expect to see disk related =
=3D>=20
  error events in your event log.> Rich>
"Ellen K." <72322.1016{at}compuserve.com&g=">mailto:72322.1016{at}compuserve.com">72322.1016{at}compuserve.com&g=
t;=20
  wrote in message =3D> news:8t1lqvg8846=
fhvp1n26lcvubgkgpd1lek2{at}4ax.com...>=20
  So do you agree with George that the disk is the likely source of =
the>=20
  problem?> On Wed, 5 Nov 2003 18:34:25 -0800,
"Rich" <{at}> =
wrote in=20
  message> <3fa9b324{at}w3.nls.net>:>&=">mailto:3fa9b324{at}w3.nls.net">3fa9b324{at}w3.nls.net>:>&=
gt; The=20
  text description associated with the message is>> =
>> The=20
  instruction at "0x%08lx" referenced memory at "0x%08lx". The =
=3D>=20
  required data was not placed into memory because of an I/O error =
status=20
  =3D> of "0x%08lx".>>
>> The simple answer =
is that=20
  this error occurs when there is a fatal I/O =3D> error paging =
in memory=20
  from disk in response to a page fault.>>
>>=20
  Rich>> >> "Ellen
K" <Ellen.K{at}harborwebs.com>">mailto:Ellen.K{at}harborwebs.com">Ellen.K{at}harborwebs.com>
=
wrote in=20
  message =3D> news:109dd7.65a92a{at}harborwebs.=
com...>>=20
  What is a kernel stack inpage error?  I can't find anything on =
=3D>=20
  MSDN.>
------=3D_NextPart_000_0478_01C3A455.9CA79670>=20
  Content-Type: text/html;>
charset=3D"iso-8859-1">=20
  Content-Transfer-Encoding: quoted-printable>
<!DOCTYPE HTML =
PUBLIC=20
  "-//W3C//DTD HTML 4.0 Transitional//EN">>=20
  <HTML><HEAD>> <META
http-equiv=3D3DContent-Type=20
  content=3D3D"text/html; =3D> =
charset=3D3Diso-8859-1">> <META=20
  content=3D3D"MSHTML 6.00.3790.88"
name=3D3DGENERATOR>>=20
  <STYLE></STYLE>>
</HEAD>> <BODY=20
  bgColor=3D3D#ffffff>>
<DIV><FONT face=3D3DArial=20
  size=3D3D2>&nbsp;&nbsp; I have seen this with both =
=3D> a=20
  problem=3D20> disk and a problem disk
controller.&nbsp; It =
is also=20
  possible to see =3D> when=3D20> loading
something over =
the network=20
  if there is a network error.&nbsp; It =3D> =
should=3D20> be an=20
  I/O error of some form or another.&nbsp; If a disk error I would =
=3D>=20
  expect to=3D20> see disk related error events in your event=20
  log.</FONT></DIV>>
<DIV><FONT =
face=3D3DArial=20
 
size=3D3D2></FONT>&nbsp;</DIV>>
=
<DIV><FONT=20
  face=3D3DArial
size=3D3D2>Rich</FONT></DIV>>=20
  <DIV><FONT face=3D3DArial=20
 
size=3D3D2></FONT>&nbsp;</DIV>>=20
  <BLOCKQUOTE=3D20> style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT: 5px;=20
  MARGIN-LEFT: 5px; =3D> BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
  0px">> <DIV>"Ellen
K." &lt;<A=3D20> =
=3D>=20
  href=3D3D"72322.1016{at}compuserve.com&a=">mailto:72322.1016{at}compuserve.com">72322.1016{at}compuserve.com&a=
mp;g'>mailto:72322.1016{at}compuserve.com">72322.1016{at}compuserve.com</=
A>&g=3D>=20
  t;=3D20> wrote in message
<A=3D20> =3D> =
href=3D3D"news:8t1lqvg8846=
'>news:8t1lqvg8846fhvp1n26lcvubgkgpd1lek2{at}4ax.com">news:8t1lqvg8846=3D>=20
  fhvp1=">mailto:fhvp1n26lcvubgkgpd1lek2{at}4ax.com...So=3D20">fhvp1=
n26lcvubgkgpd1lek2{at}4ax.com</A>...</DIV>So=3D20>=20
  do you agree with George that the disk is the likely source =
of=3D20>=20
  the<BR>problem?<BR><BR>On Wed,
5 Nov 2003 18:34:25 =
-0800,=20
  "Rich" =3D>
&lt;{at}&gt;=3D20> wrote in=20
  message<BR>&lt;<A=3D20>
=3D> href=3D3D"3fa9b324{at}w3.nls.net&gt;:<=">mailto:3fa9b324{at}w3.nls.net">3fa9b324{at}w3.nls.net&gt;:<=
BR'>
<BR><BR>&=3D>=20
  gt;&nbsp;&nbsp;=3D20> The text
description associated =
with the=20
  message =3D>
is<BR>&gt;<BR>&gt;&nbsp;=20
  The=3D20> instruction at "0x%08lx" referenced
memory at =
"0x%08lx". The=20
  required =3D> data was=3D20> not placed
into memory =
because of an=20
  I/O error status of=3D20>=20
 
"0x%08lx".<BR>&gt;<BR>&gt;The
simple answer is =
that this=20
  error occurs =3D> when=3D20> there is a
fatal I/O error =
paging in=20
  memory from disk in response to a =3D>
page=3D20>=20
  =
fault.<BR>&gt;<BR>&gt;Rich<BR>&gt;<BR>=
;&gt;&nbsp;=20
  "Ellen K" &lt;<A=3D20>
href=3D3D"Ellen.K{at}harborwebs.com&gt'=">mailto:Ellen.K{at}harborwebs.com">Ellen.K{at}harborwebs.com&gt'=
>
t;=20
  =3D> wrote in=3D20> message
<A=3D20> =
=3D> href=3D3D"news:109dd7.65a92a{at}harborwebs'=
>news:109dd7.65a92a{at}harborwebs.com">news:109dd7.65a92a{at}harborwebs.=
=3D>=20
 
com</A>...<BR>&gt;&nbsp;=3D20>
What is a =
kernel stack=20
  inpage error?&nbsp; I can't find anything on=3D20>=20
  =
MSDN.<BR></BLOCKQUOTE></BODY></HTML>=


------=_NextPart_000_04FE_01C3A4B3.81323B80--

--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
SEEN-BY: 633/267 270
@PATH: 379/45 1 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.