BSOD = kernel_data_inpage_error anyone gotten this?

[QueBert]

Fixed my XP (thought I did) it was locking up and I was having to manually reboot I got the BSOD in the topic once today, with atapi.sys listed as the file.

I did some Googling, and apparently this could be many things, I figured it was a memory/HD problem. But there doesn't seem to be any fixes, a few people said to delete atapi.sys and re-install SP2, but that doesn't seem like it would do anything if it's just replacing a file with the same file? reading all the tech documents on this helped me understand a bit better what's causing it. But, I'd like to hear from somebody who's encountered it first hand, and what they did to rid it. I'm still getting random lockups, no BSOD's thought since the first one. Assuming my lockups are atapi.sys related.

any suggestions??

thanks

 

[OdiN]

ATAPI is short for Advanced Technology Attachments Packet Interface, which is an extention of EIDE (Enhanced Integrated Drive Electronics).

Basically it is used for CDRom and tape drive devices. It's possible that a CD drive could be acting up...I've seen that cause this BSOD.

I believe that atapi.sys also deals with large hard drives.

Try running this command:

sfc /scannow

That will check your system files and see if any are damaged. You will need your XP media if it does want to replace them. Having a copy of XP on CD that has SP2 integrated is best if you hvae SP2, otherwise you will have to reload SP2 probably.

You can also try moving the atapi.sys file to a temp directory and reloading the service pack, then deleting the file in the temp directory after that.

Other than the standard troubleshooting of memory and scanning of hard drives (hard drive errors could cause this..run a checkdisk) - I can't suggest anything else.

It may help if you can provide the STOP 0x0 number.

 

[imported_BikeDude]

You've read http://msdn.microsoft.com/library/en-us...03-0e59-4ed3-bba5-13214dc906df.xml.asp already?

I'm tempted to blame your HD. I just don't trust SATA and EIDE drives these days. (but without knowing the error status code, it is of course just a wild guess)

 

[Nothinman]

An in-page error happens when there was a problem reading data from a medium into memory, I can't see how ATAPI.sys was would be at fault unless you were booting from a CDROM. The primary suspect is your hard drive since that's where 99% of paging activity is to or from.

 

[imported_BikeDude]

Originally posted by: Nothinman
I can't see how ATAPI.sys was would be at fault unless you were booting from a CDROM.

I thought atapi.sys was the standard EIDE device driver? (surely there isn't a seperate driver for CD-ROM devices hanging off the EIDE cable?)

OTOH I've been 100% SCSI for a decade now, so what do I know...

 

[Nothinman]

ATAPI is a packetized version of ATA, similar to SCSI. I think the only thing it was ever used for is CDROM, TAPE, FLOPPY and ZIP drives.

 

[imported_BikeDude]

I see. That explains why its description says "IDE/ATAPI Port Driver".

The controller remains the same, so I doubt it is even possible to have two different drivers to talk with it...

But this probably means the op never installed the chipset specific EIDE device driver. Perhaps it is worth a shot? (doubtful, but if it too crashes then IMO it counts as one more reason to suspect a hw-fault)

 

[Nocturnal]

I had this happen and it was the motherboard's IDE controller. It was going bad or was already bad. Try another hard drive along with CD-ROM or DVD-ROM drive and see if the problem persists. If it does, more than likely it's a mobo problem.

 

[dclive]

Originally posted by: QueBert
Fixed my XP (thought I did) it was locking up and I was having to manually reboot I got the BSOD in the topic once today, with atapi.sys listed as the file.

I did some Googling, and apparently this could be many things, I figured it was a memory/HD problem. But there doesn't seem to be any fixes, a few people said to delete atapi.sys and re-install SP2, but that doesn't seem like it would do anything if it's just replacing a file with the same file? reading all the tech documents on this helped me understand a bit better what's causing it. But, I'd like to hear from somebody who's encountered it first hand, and what they did to rid it. I'm still getting random lockups, no BSOD's thought since the first one. Assuming my lockups are atapi.sys related.

any suggestions??

thanks

Do you have disk errors in your event logs?

Lockups are typically hardware-related - the system can't throw up the bluescreen because it never gets a signal that something is wrong - the hardware simply locks. If you're getting consistent lockups, you have a hardware issue, not a software issue, IMHO.

 

[Nothinman]

The controller remains the same, so I doubt it is even possible to have two different drivers to talk with it...

Huh? If you couldn't have both drivers talking to the controller at once you wouldn't be able to have a CDROM and a hard disk on the same controller.

 

[imported_BikeDude]

Originally posted by: Nothinman
Huh? If you couldn't have both drivers talking to the controller at once you wouldn't be able to have a CDROM and a hard disk on the same controller.

If you look under "Primary IDE channel", you'll find atapi.sys and storprop.dll. The display name for atapi.sys is "Standard IDE/ESDI Hard Disk Controller". I don't see any reason why this driver is exclusively for non-HD devices.

 

[Nothinman]

AFAIK all disks speak straight ATA while the other mentioned devices use ATAPI, but I wouldn't say I was surprised if MS put both protocols in one driver and didn't lable it properly.

 

[QueBert]

I think it's a HD problem. Seagate's disc checking utility said the drive failed SMART test. I swapped out the CPU and I'm not getting the same errors, but some things are still not working. I bought Spinrite 6, I hope the new version is as good as the ooooooold Dos based ones. Anyone know of another HD util that's similar? if infact the drive does have bad sectors I'd like to try and get all the data I can xfered to the other HD.

When I run games, they all give me either a totally black, or totally blue (not BSOD, no message) screen, and either kick me back to my desktop or force me to reboot. ugh