kernel_data_inpage-error on atapi.sys followed by PAGE_FAULT_IN_NONPAGED_AREA

[news.microsoft.com]

I accidentally put this message in setup_deployment where no one has picked
up on it so I hope no one minds that I am re-posting now that I have another
symptom

It concerns a BSOD which I haven't seen before and which defies googling!
kernel_data_inpage-error on atapi.sys

I did find some arcane references to something like it
(kernel_data_inpage-error without atapi.sys) at
http://support.Microsoft.com/kb/913379 but it seems to be a reason why an
OS wouldn't work from the start, rather than being a reason for it to die
while working (It is REALLY arcane!)

Does anyone know what I can do about it besides hope the system doesn't BS
again please? I presume that the atapi.sys reference is important?

I am a bit reluctant to put in another message for fear that people might
think that someone has responded to my first one but on the next day, with
this treackly slow system I have had another BSOD, this time a
PAGE_FAULT_IN_NONPAGED_AREA which to me sounds pretty non-specific. Does
anyone have any idea if this might have something to do with the
kernel_data_inpage-error on (atapi.sys) please? Today's BSOD MAY have been
related to WinFaxPro 10.03 which was trying to print a page in photo mode
when the fault occurred

Or do all these page faults mean that my operating system is rapidly
disintegrating and now hasn't got the vaguest idea how to manage it's
hardware memory blocks?

 

[Thee Chicago Wolf]

I accidentally put this message in setup_deployment where no one has picked

up on it so I hope no one minds that I am re-posting now that I have another
symptom

It concerns a BSOD which I haven't seen before and which defies googling!
kernel_data_inpage-error on atapi.sys

I did find some arcane references to something like it
(kernel_data_inpage-error without atapi.sys) at
http://support.Microsoft.com/kb/913379 but it seems to be a reason why an
OS wouldn't work from the start, rather than being a reason for it to die
while working (It is REALLY arcane!)

Does anyone know what I can do about it besides hope the system doesn't BS
again please? I presume that the atapi.sys reference is important?

I am a bit reluctant to put in another message for fear that people might
think that someone has responded to my first one but on the next day, with
this treackly slow system I have had another BSOD, this time a
PAGE_FAULT_IN_NONPAGED_AREA which to me sounds pretty non-specific. Does
anyone have any idea if this might have something to do with the
kernel_data_inpage-error on (atapi.sys) please? Today's BSOD MAY have been
related to WinFaxPro 10.03 which was trying to print a page in photo mode
when the fault occurred

Or do all these page faults mean that my operating system is rapidly
disintegrating and now hasn't got the vaguest idea how to manage it's
hardware memory blocks?

That would be weird for atapi.sys and the WinFax to have caused this
kind of error. But, it is Windows so who knows. Do you happen to have
mixed RAM modules in your machine by chance? What version is your
atapi.sys currently? Page faults are usually memory related or to some
degree state of the memory when some application crapped out in it. If
you get the BSOD again, get the alphanumeric code preceding
PAGE_FAULT_IN_NONPAGED_AREA (something like 0x000520 or some such
cryptic code) as you can actually look up those codes on MS....er,
somewhere and find out what it is.

The only KB article I see on Page Fault errors for XP SP2 is:
http://support.microsoft.com/kb/924809/en-us
It references an update to win32k.sys.

The KB with the most current win32k.sys is
http://support.microsoft.com/kb/941880
You can always request it, for free, from MS.

Check your event viewer and see if your error shows up in there. It
might give you more info on what the cause is.

- Thee Chicago Wolf

 

[Guest]

this is another either missing or corrupt file. First if your system does not
boot normally try to run in safe mode if not call computer manufacture. If it
does run seach for atapi.sys to find its location. If you install windows
yourself you can call MS for help. You can also go to my computer properities
and find as is mine it is your ATA/ATAPI IDE Hard Drive controller Driver. If
you can't boot to HD use your CD recovery to reinstall drivers for your
system. Good Luck!