From: relayPoint 

On Wed, 12 Mar 2003 14:38:06 -0800, "Rich"  said all this:

>   0xC0000185 == 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 ==
>  0x00000077 not 0x00000007.

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
> 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.

>   I suggest looking in your event log to see if you are getting any other
> 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.
0000: 0010000f 00640001 00000000 c0040009 0010: 00000100 00000000 00003258
00000000 0020: 00000000 00000000 00000000 00000000 0030: 00000000 00000007

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");

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