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


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
The driver detected a controller error on \Device\Ide\IdePort3.
Event Xml:
<Event xmlns="">
    <Provider Name="atapi" />
    <EventID Qualifiers="49156">11</EventID>
    <TimeCreated SystemTime="2011-12-31T03:49:02.830078100Z" />
    <Security />
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Most likely a problem with your driver 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.
noxchoGlobal Support CoordinatorCommented:
Did your set the drive to AHCI before Windows installation? Or was it done after initial system installation?
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bridgegaelAuthor Commented:
Poor quality cable was the problem.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.