From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0369_01C2E8B3.6EFCB380
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   So you are getting I/O errors on IdePort1.  Is there a hard disk on =
this port or not?

   I'm confident that you are not getting bugcheck 0x00000007 =3D=3D =
INVALID_SOFTWARE_INTERRUPT.  I believe you can only see this on a = checked
build of the Itanium kernel.  The displayed arguments are = consistent with
a KERNEL_STACK_INPAGE_ERROR.  Specifically you are = seeing this on
pagefile #0 (probably your only pagefile) at file offset = 0x0178A000.  If
your pagefile is larger than 4GB then you only know the = low 32bits of the
file offset.

   How much RAM you have and how little you expect to page doesn't mean =
much.  You can still page.  If you don't want to page, get rid of your = pagefile.

Rich

  "relayPoint"  wrote in message =
news:rnfv6v0c7dv7j16lnhv2e607mtfiaacrf6{at}4ax.com...
  On Wed, 12 Mar 2003 14:38:06 -0800, "Rich"  said all this:

  >   0xC0000185 =3D=3D STATUS_IO_DEVICE_ERROR.  This means
  > that a hardware device reported an error.

  I'd agree, but a port 80H card says 'nothing wrong.'

  >   I think you have a typo.  KERNEL_STACK_INPAGE_ERROR =3D=3D
  >  0x00000077 not 0x00000007. =20

  This is not a typo. This is exactly what it is reporting - 0x00000007,
  not the expected 0x00000077. Yes, I know it's weird, but that's
  exactly what it's saying. I checked. Twice. :/

  > This means that the hardware error occured when trying to page=20
  > back in from disk a paged out kernel mode stack.

  Which I honestly do find very hard to believe. The system has 512MB of
  physmem with another 512MB of swap. Unless something is memleaking as
  fast as it possibly can - ie; IE - I don't touch swap save on very
  rare occasions. The system is usually sitting around 180-200MB of
  physmem used.=20

  >   I suggest looking in your event log to see if you are getting any =
other=20
  > I/O errors reported.  You should also try a CHKDSK /F /R.

  Ran chkdsk /F /R three days ago, for the fifth time, and SFC as well,
  just in case. Event log has only the following:

  The device, \Device\Ide\IdePort1, did not respond within the timeout
  period.=20
  0000: 0010000f 00640001 00000000 c0040009
  0010: 00000100 00000000 00003258 00000000
  0020: 00000000 00000000 00000000 00000000
  0030: 00000000 00000007=20

  Same every time. This is caused by buggy firmware interacting with
  audio CDs. (Kenwood 52x ATAPI) Play CD, pause CD, forget I have it in
  that drive, drive stops responding. Other than that? Nothing. No atapi
  errors, no warnings, nothing. :/

  _rP
  INSERT INTO news.barkto(post) VALUES ("above::post");
------=_NextPart_000_0369_01C2E8B3.6EFCB380
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   So you
are getting I/O =
errors on=20
IdePort1.  Is there a hard disk on this port or
not?
 
   I'm
confident that you are =
not getting=20
bugcheck 0x00000007 =3D=3D INVALID_SOFTWARE_INTERRUPT.  I believe
= you can only=20
see this on a checked build of the Itanium kernel.  The displayed
= arguments=20
are consistent with a KERNEL_STACK_INPAGE_ERROR.  Specifically you = are=20
seeing this on pagefile #0 (probably your only pagefile) at file offset=20
0x0178A000.  If your pagefile is larger than 4GB then you only
know = the low=20
32bits of the file offset.
 
   How much
RAM you have and =
how little=20
you expect to page doesn't mean much.  You can still
page.  If = you=20
don't want to page, get rid of your pagefile.
 
Rich
 

  "relayPoint" <rpoint{at}error404.nls.net>">mailto:rpoint{at}error404.nls.net">rpoint{at}error404.nls.net>
= wrote in=20
  message news:rnfv6v0c7dv=
7j16lnhv2e607mtfiaacrf6{at}4ax.com...On=20
  Wed, 12 Mar 2003 14:38:06 -0800, "Rich" <{at}> said all=20
  this:>   0xC0000185 =3D=3D =
STATUS_IO_DEVICE_ERROR.  This=20
  means> that a hardware device reported an
error.I'd =
agree, but=20
  a port 80H card says 'nothing
wrong.'>   I think =
you have=20
  a typo.  KERNEL_STACK_INPAGE_ERROR =3D=3D>  =
0x00000077 not=20
  0x00000007.  This is not a typo. This is
exactly what it =
is=20
  reporting - 0x00000007,not the expected 0x00000077. Yes, I know =
it's=20
  weird, but that'sexactly what it's saying. I checked. Twice.=20
  :/> This means that the hardware error occured
when trying =
to page=20
  > back in from disk a paged out kernel mode
stack.Which =
I=20
  honestly do find very hard to believe. The system has 512MB =
ofphysmem with=20
  another 512MB of swap. Unless something is memleaking asfast as it =

  possibly can - ie; IE - I don't touch swap save on veryrare =
occasions. The=20
  system is usually sitting around 180-200MB ofphysmem used.=20
  >   I suggest looking in
your event log to see if =
you are=20
  getting any other > I/O errors reported.  You
should also =
try a=20
  CHKDSK /F /R.Ran chkdsk /F /R three days ago, for the fifth =
time, and=20
  SFC as well,just in case. Event log has only the =
following:The=20
  device, \Device\Ide\IdePort1, did not respond within the =
timeoutperiod.=20
  0000: 0010000f 00640001 00000000 c00400090010: 00000100 =
00000000=20
  00003258 000000000020: 00000000 00000000 00000000 =
000000000030:=20
  00000000 00000007 Same every time. This is caused by buggy =
firmware=20
  interacting withaudio CDs. (Kenwood 52x ATAPI) Play CD, pause CD, =
forget I=20
  have it inthat drive, drive stops responding. Other than that? =
Nothing. No=20
  atapierrors, no warnings, nothing.
:/_rPINSERT INTO=20
  news.barkto(post) VALUES
("above::post");

------=_NextPart_000_0369_01C2E8B3.6EFCB380--

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