The driver detected a controller error on \Device\Ide\IdePort3 and BSOD

Hi,

I'm getting the event log message "The driver detected a controller error on \Device\Ide\IdePort3"  several times a day on a Windows 7 x64 PC followed by BSOD.  I have only started having these problems since I installed a OCZ Vertex 60GB SSD and put a clean windows install on this drive.  In the BIOS I have set the storage mode to AHCPI.  All drives are connected via SATA.  I have ran CHKDSK against the SSD and no problems are resolved.  I have moved the SSD to a different SATA port and the problem follows it.  I have tried updating the drivers for drives and controllers in device manager using its update facility but all drivers are up to date.  Maybe I need to go to manufacturers websites?  I have updated the firmare on the SSD but to no joy.  Any ideas?  Thanks in advance.
-----------------------------------------------------------------------
Log Name:      System
Source:        atapi
Date:          31/12/2011 03:49:02
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mediacenter
Description:
The driver detected a controller error on \Device\Ide\IdePort3.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="atapi" />
    <EventID Qualifiers="49156">11</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-12-31T03:49:02.830078100Z" />
    <EventRecordID>10024</EventRecordID>
    <Channel>System</Channel>
    <Computer>mediacenter</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\Ide\IdePort3</Data>
    <Binary>0000100001000000000000000B0004C002000000850100C00000000000000000000000000000000003000000000000000000000004100000</Binary>
  </EventData>
</Event>
bridgegaelAsked:
Who is Participating?
 
bridgegaelAuthor Commented:
Found the problem.  I used a different SATA cable and the problem has gone.  I think the original cable was a poor quality one.
0
 
PenguinNCommented:
Most likely a problem with your driver http://support.microsoft.com/kb/314093 It could also be hardware but this error has been around some time with various configurations (check google). I would update all drivers to the latest version, also upgrade all firmware, BIOS and chipset drivers and see what happens.
0
 
noxchoGlobal Support CoordinatorCommented:
Did your set the drive to AHCI before Windows installation? Or was it done after initial system installation?
0
 
bridgegaelAuthor Commented:
Poor quality cable was the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.