PDA

View Full Version : atapi.sys and pciide.sys not loading


Mrkvonic
September 18th, 2007, 02:01 AM
Hello,

I have a curious problem.

I have reinstalled Windows on a machine. I have just formatted the Windows partition, leaving others intact.

Following a successful install, everything works, BUT:

When I check the event log, I see that every time I reboot and boot into Windows, atapi.sys and pciide.sys are not loading. The hard drives are a pair of SATA.

Supposedly, this does not interfere in any way.

But sometimes during the boot, the Windows hangs. I must reboot and then it would start normally.

Does anyone have any ideas? I have followed several guides via google, suggesting extracting the drivers, merging registry keys etc, but these did not render anything. The two drivers are still not functioning.

So, has anyone ever encountered this?
Any ideas why - or how I could fix this?

Again, everything works, except the occasional boot hiccup.

If you need more sysinfo tell me, I'll provide.

Mrk

iceni60
September 18th, 2007, 07:53 AM
you can try searching at MSKB -
http://support.microsoft.com/search/?adv=1

i just looked through it and there are some problems caused by some chipsets, i don't know why. but maybe you could try adding the name of your chipset to the search ???

Mrkvonic
September 18th, 2007, 08:00 AM
Hello,
I didn't have this before reinstall.
Best and worst of all, everything works...
Mrk

iceni60
September 18th, 2007, 08:27 AM
{QUOTE-> Hello,
I didn't have this before reinstall.
Best and worst of all, everything works...
Mrk <-QUOTE}
i still think searching the MS KB is the best place to find an answer because the thing that's most likely to be different is an update from MS, sometimes they don't give the full reasons for an update, but will explain how to fix it in the KB.

stapp
September 18th, 2007, 10:54 AM
Have no idea really if this is of any use but it does mention SATA, atapi.sys and pciide.sys

http://www.911cd.net/forums//index.php?showtopic=19397&pid=135727&st=120&#entry135727

Mrkvonic
September 18th, 2007, 04:04 PM
Hello,

This is mainly bothering me cause I'm anal. Don't like unexplained things...

Solved the problem by reloading MS IDE controller rather than Nvidia one. No bloody difference. But now atapi and pciide load... No change in any functionality of any device.

BUT ...

Now, I notice that PartMgr is not functioning properly, in fact hasn't from the start. Again, supposedly without any ill effect save for the occasional windows hang during a random reboot.

MAYBE this somehow affects the boot sequence...

Could this have to do with bios channel controllers? Or something ...

I have a very old ATI image of this drive, same config. Do you think virtually mounting it and inspecting the insides could help?

Would I be able to examine the device management without actually physically mounting the drive?

Why do I always find the most twilight zone problems?

Mrk

Mrkvonic
September 18th, 2007, 04:09 PM
Hello,

Another update:

I have also Linux on this machine ...

So I checked another comp with Linux, and voila! This one has a little yellow sign near PartMgr driver! But here everything works perfectly and not a single hiccup during any reboot EVER.

Could this be Windows inability to handle STOLEN partitions - Linuxed ones?

Could the hang on reboot be a matter of voltages? But I haven't played with them ... bloody hell.

If anyone is smart enough to figure this one, he'll feature as the king of the month on dedoimedo...

Cheers all!
Mrk

lucas1985
September 20th, 2007, 03:54 PM
{QUOTE-> Solved the problem by reloading MS IDE controller rather than Nvidia one. <-QUOTE}
The NVIDIA IDE driver often does some weird things. I always try to avoid it.

Mrkvonic
September 20th, 2007, 06:01 PM
Hello,
Yes, I guess. I'm avoiding them too now.
The nforce4 chipset had some serious troubles. There was the nvidia firewall and the bsod issues ... well, no matter. Things look ok now.
But I wonder how I come up with these quirks?
Mrk

lucas1985
September 20th, 2007, 07:09 PM
{QUOTE-> The nforce4 chipset had some serious troubles. There was the nvidia firewall and the bsod issues. <-QUOTE}
It's a pity that the chipsets for AMD-based systems are more troublesome than an Intel chipset :(
{QUOTE-> But I wonder how I come up with these quirks? <-QUOTE}
Microsoft is hating you because of your superb Linux articles ;D