Driver Detected Controller Error Device Ide Ideport0 Windows 7
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related
The Driver Detected A Controller Error On Device Ide Ideport0 Laptop Windows 7
threads Remove From My Forums Answered by: System EventID the driver detected a controller error on device ide ideport0 atapi 11 atapi controller error on \Device\Ide\IdePort0 ==> what KB-No. from Windows Update causes this atapi error 11 bad performance issue for several times??? Windows 7 IT Pro > Windows 7 Hardware Compatibility Question 0 Sign in to vote -
The Driver Detected A Controller Error On Device Ide Ideport0 Windows 10
System - Provider [ Name] atapi - EventID 11 [ Qualifiers] 49156 Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2011-10-05T03:29:02.442524200Z EventRecordID 11139 Channel System Computer Haribo-LenovoNB Security - EventData \Device\Ide\IdePort0 0000100001000000000000000B0004C002000000850100C00000000000000000000000000000000000000000000000000000000004100000 Binary data: In Words 0000: 00100000 00000001 00000000 C004000B 0008:
Atapi Error 9
00000002 C0000185 00000000 00000000 0010: 00000000 00000000 00000000 00000000 0018: 00000000 00001004 In Bytes 0000: 00 00 10 00 01 00 00 00 ........ 0008: 00 00 00 00 0B 00 04 C0 .......À 0010: 02 00 00 00 85 01 00 C0 ....…..À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 00 00 00 00 00 00 00 00 ........ 0030: 00 00 00 00 04 10 00 00 ........ Wednesday, October 05, 2011 3:38 AM Reply | Quote Answers 1 Sign in to vote Hi, 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 terminat
ordeal with this Event 11 that Windows quietly generates. It took us few weeks to fully work out why Windows suddenly started hanging, misbehaving or the driver detected a controller error on \device\harddisk even crashing with blue screen. Now that I feel it is fully resolved,
\device\ide\ideport2
I thought I’d share my conclusion (and the process) – hopefully it will help few others out there who are event id 11 disk the driver detected a controller error 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 https://social.technet.microsoft.com/Forums/windows/en-US/9abb65e1-3020-4409-b83b-276c253b934a/system-eventid-11-atapi-controller-error-on-deviceideideport0-what-kbno-from-windows?forum=w7itprohardware 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 http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ 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
List Welcome Guide More BleepingComputer.com → Microsoft Windows Support → Windows Vista Javascript Disabled Detected http://www.bleepingcomputer.com/forums/t/397872/the-driver-detected-a-controller-error-on-deviceideideport0/ You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Register a free account to unlock additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. driver detected Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics the driver detected and forums, creating a blog, and having no ads shown anywhere on the site. Click here to Register a free account now! or read our Welcome Guide to learn how to use this site. The driver detected a controller error on \Device\Ide\IdePort0. Started by ermat_46 , May 17 2011 08:47 AM Please log in to reply 5 replies to this topic #1 ermat_46 ermat_46 Members 27 posts OFFLINE Local time:10:12 PM Posted 17 May 2011 - 08:47 AM I checked the Event Viewer log and I saw 4 instances of this error. These 4 instances happened today: "The driver detected a controller error on \Device\Ide\IdePort0." I never had this kind of error once. This is the XML view: -