What causes ATAPI Timout Errors in System Log?

Anyone have a clue as to why I would receive these errors in my system log every once in a while??? The driver detected a controller error on \Device\Ide\IdePort0. The device, \Device\Ide\IdePort0, did not respond within the timeout period.

Windows Hardware 9627 This topic was started by ,


data/avatar/default/avatar08.webp

17 Posts
Location -
Joined 2002-01-07
Anyone have a clue as to why I would receive these errors in my system log every once in a while???
 
"The driver detected a controller error on \Device\Ide\IdePort0."
 
"The device, \Device\Ide\IdePort0, did not respond within the timeout period."
 
Both appearing concurrently, and usually after a cold boot, or when system files are changed. It causes my Primary chain devices to go from DMA to PIO modes, though uninstalling the Primary IDE device and rebooting seems to fix it, and return the devices to DMA modes.
 
Any clue kids??
 
Cheers

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar12.webp

1915 Posts
Location -
Joined 2000-03-30
HAd same problem with plextor cdrw
 
 
Have no clue
 
I'd like to know as well

data/avatar/default/avatar08.webp

17 Posts
Location -
Joined 2002-01-07
OP
Hey kids --
I seem to have fixed my problem, by hard-setting the DMA mode of the HDD. I have a Fujitsu MPG3204AT-E - which supports UDMA5, though my MoBo (Abit VA6) only supports UDMA4 at the max. So I checked the Fujitsu Canada website, and downloaded the DMA Mode program, and set the drive to UDMA4. No more timeouts.
 
Cheers -- hopefully this helps someone else, too... )