Error Atapi Event 9
Contents |
360 games PC games
Atapi Error In Event Viewer
Windows games Windows phone games Entertainment All Entertainment atapi error event 11 Movies & TV Music Business & Education Business Students & educators atapi incompatible error Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Atapi Error 11 Device Ide Ideport0
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Atapi Error Windows 7
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Gaming Smartphones Tablets Windows 8 PSUs Android Your question Get the answer Tom's Hardware>Forum>Storage>ATAPI Errors> Solved ATAPI Errors Tags: Hard Drives Storage Last response: 25 February 2016 event id 11 atapi 06:04 in Storage Share xxx666yyy777 28 July 2011 03:21:43 Hello there -
Event Id 11 Disk
i just recently encountered ATAPI errors in my Win 7 event viewer. The errors say "The driver detected event id 15 disk not ready for access a controller error on \Device\Ide\IdePort2.". At the same time, transfer rates to the hdd in question became very slow. I ran chkdsk /f /r - no issues reported. I also https://support.microsoft.com/en-us/kb/154690 ran the SeaTools for Windows tool - no SMART errors, short tests show also no issues. Currently running the check from EASUS Partition Manager - so far everything green, however, at the same time, the errors in the even viewer keep showing up (while EASUS is running surface check and reporting everything as green...) Any ideas, what the problem could http://www.tomshardware.com/forum/271734-32-atapi-errors be? Thx. More about : atapi errors Best solution John_VanKirk a c 106 G Storage 29 July 2011 00:57:51 Hi there, Couple things to check: Double click on the Event Viewer error (is this a red exclamation point error?) and it will bring up a an event properties box. That has an online help link which may give you more specific information about the error. Also, could there be another HDD or Device on this IDePort2 that is not being checked, since you mention transfer rates from another device. Check the BIOS to see what is on Port 2. A very good testing program is HD Tune (free edition) or HD Tune Pro, which gives you Disk Health Info, S.M.A.R.T. parameters, and you can test the file data transfer rates across the disk. Here's the link www.hdtune.com And if there is any concern about the controller chip on the MB, rather than the HDD itself, consider downloading the latest chipset drivers from the MB website. Share xxx666yyy777 1 August 2011 10:00:28 Thanks - HDTune did indeed help me
Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 9 (Error) Source: atapi How important https://community.spiceworks.com/windows_event/show/546-atapi-9 is this event? (4 votes) 1 2 3 4 5 not important very important Description The device, \Ide\IdePort , did not respond within the timeout period. The device, \Ide\IdePort , did not respond http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ within the timeout period. Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript atapi error Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages The device, \Device\Ide\IdePort3, did not respond within the timeout period.
Jun 23, 2009 The device, \Device\Ide\IdePort0, did not respond within the timeout period. Aug 10, 2009 The device, \Device\Ide\IdePort1, did not respond within the timeout period. Aug 10, 2009 Das Gerät \Device\Ide\IdePort0 hat innerhalb der event id 11 Fehlerwartezeit nicht geantwortet. Jun 06, 2011 message string data: \Device\Ide\IdePort0 Mar 20, 2012 message string data: \Device\Ide\IdePort2 Nov 13, 2012 Comments Thai Pepper May 27, 2011 Steve M. Other, 101-250 Employees How to troubleshoot error messages about Event ID 9 and Event ID 11 http://support.microsoft.com/kb/314093 In almost all cases, these messages are posted because of hardware problems. The source may be the controller or (more probably) a device that is attached to the controller. The hardware problem can be poor cabling, incorrect termination or transfer rate settings, slow device relinquishment of the SCSI bus, a faulty device, or in rare cases, a poorly written device driver. Pure Capsaicin Jun 30, 2011 peter Non Profit, 101-250 Employees thanks for info Pimiento Aug 31, 2011 James51G Manufacturing, 1-50 Employees Some old Pentium 4 chipsets have a hardware bug that causes several of these errors every day. The hard disk is simply timing out due to lack of a return interrupt and will normally retry the operation and correct itself. I have never found documentation from Microsoft or Intel on this but have noticed it for a long time on our old server. It also caused major headaches on systemsordeal with this Event 11 that Windows quietly generates. It took us few weeks to fully work out why Windows suddenly started hanging, misbehaving or even crashing with blue screen. Now that I feel it is fully resolved, I thought I’d share my conclusion (and the process) – hopefully it will help few others out there who are struggling with this. Ridiculously, many people are likely affected by this issue, but unless they open Event Viewer and search for this event id 11, they will not realize that hanging is not “normal” behavior, even for Windows! OS seems to silently recover from this problem 10 to 60 seconds later, which is really strange in my book – considering that user isn’t even alerted to this serious atapi error. For impatient souls among us, here are my conclusions: First thing – check the SATA/EIDE and power cable connection between your hard-drive and the motherboard. If possible, try another SATA outlet on motherboard or another SATA cable if available. If it still happens, the bad news is that this is likely a disk controller error, which is especially problematic since nowadays disk controllers are built into the Motherboard. If you are in a budget crunch, one potential workaround is to slow down your HD to use different PIO. This may avoid hangs, but will slow overall performance, so no fun solution… Proper solution appears to be to replace motherboard, hence replacing disk controller. There are many motherboards starting at just $50 and in most cases it will improve overall performance and stability for you, even if you keep the same CPU and other components. I am pretty confident that this is the right diagnosis, as we went through a lot of trial and error investigative work, in a space of few weeks, after it started abruptly. At first, I was pretty much convinced that HD is dying. The system had two hard-drives, and the older hard-drive was seemingly working just fine, even with the same SATA cable and connected to the same slot on the Motherboard. Turns out it was using slower PIO by virtue of it being older HDD. During the troubleshooting process I reinstalled fresh Windows 7 64 Bit multiple times, on various HD drives, only to see the issue start happening almost instantly after clean install. Few days ago a fresh HDD became available (separate long story), so I tried replacing the “dying” HD. Guess what, it being newer HD, it was instantly affected by the same issue, even thoug