event id 11 the driver detected a controller error Campbell Hill Illinois

Address 1214 Walnut St, Murphysboro, IL 62966
Phone (618) 519-9300
Website Link http://www.kctechnologies.com
Hours

event id 11 the driver detected a controller error Campbell Hill, Illinois

Backups complete fine and verify fine. As an aside – DDR3 memory is Ridiculously Cheap. An example of English, please! The key word as you put it is "near" identical, how near, same mobo disk controller graphics?

the driver? Help! That should tell you. 1 Sonora OP derektom Feb 19, 2013 at 2:56 UTC Thanks for your reply. Thanks! 0 LVL 46 Overall: Level 46 Storage Hardware 30 Windows 7 16 Hardware 11 Message Active today Expert Comment by:noxcho2010-07-06 Thanks for points.

Thought it would be one last spot in the equation. Right-click the gray portion of the basic or dynamic disk whose disk number matches the "Harddisk#" in the error message. It shows that "disk" is the source of Event 11 and the details state: "The driver detected a controller error on \Device\Harddisk4\DR4" OR "The driver detected a controller error on \Device\Harddisk1\DR1" We have Volumes for C:\ D:\ and E:\ and then one that says *** NO MOUNT POINT *** Ocanada, the external hard drive(s) are not set as index locations. 0

Noxcho we will check that right away and post again. One of them I was able to find the cause by simply installing Dell OpenManager Server Administrator and taking a look at the storage.The firmware driver was out of date. they have a group of really really bright folks working on part of this whole disk drive management issue. Good news and this question is really worth of being added to EE knowledge base.

But eventually the disk wakes up and the backup is ok. YES, I swapped out the "Disk 2" drive (an external Seagate GoFlex) as indicated in the Disk Management console and the errors went away. Inserte un disco en la unidad /device/Harddisk5/DRS, ALGUNO DE UDS SABRIA DARME UNA ORIENTACION A KE SE DEBE Y COMO RESOLVERLO,? The Write Through Policy was a temporary solution till the new controller battery has arrived.

x 288 EventID.Net As per Microsoft: "This problem is typically caused by a failing cable that connects the drive to the computer". Ask ! I change it so each drive was on its own IDE physical connection, and put my CDROM on the second channel as slave. But in my experience this error is almost always logged for USB drives (and we see a lot of events since we do event log monitoring).

Disable sleep mode in power management? (this might not be very good for the drive to spin all the time). So, it confims that this is due to hardware error on the Cache board and HP is going to replace it for me. TechSpot is a registered trademark. Anyone have any input on the error?

It looks like the sleep setting was that cause also. Event ID 225: The application System with process id 4 stopped the removal or ejection for the device USB\VID_0BC2&PID_2101\2GE4ECS0. nobody grasps the big picture concept. Few days ago a fresh HDD became available (separate long story), so I tried replacing the “dying” HD.

Facebook Google+ Twitter YouTube Subscribe to TechSpot RSS Get our weekly newsletter Search TechSpot Trending Hardware The Web Culture Mobile Gaming Apple Microsoft Google Reviews Graphics Laptops Smartphones CPUs Storage Cases Edited Apr 16, 2014 at 10:23 UTC 0 Pimiento OP yolandahornus Apr 25, 2014 at 10:29 UTC 1st Post Hola, estoy leyendolos y a mi me aparece este Seems I have to use some low level access functions. The driver detected a controller error on \Device\Harddisk3\DR3.

See ME885352 if the problem appears when you cancel an I/O operation to a raw USB 2.0-attached hard disk drive in Windows 2000 Server SP4. luls. How can I determine what hard drive / storage device is "\Device\Harddisk2\DR2"? m 0 l Can't find your answer ?

It found HDD head-misalignment and after running for about an hour, it was able to repair it. Cheers, Derek Reply Subscribe RELATED TOPICS: Driver detected a controller error The driver detected a controller error on \Device\Harddisk1\DR1. It used to appear 2-5 times a minute and now I have not seen it once since last reboot. I'll try to disable this function for a few days, and let you know what happens...

Further investigation revealed Windows 2000 is generating (1E) Prevent/Allow Medium Removal commands to the boot device. One of the last few times the message was generated, we got the following events also. I think maybe this post can help explain how to map between the number and the Hard-disk (look at photos especially), but if you have only one (most common), then there And, of course, with computers sometimes "who knows"? !

Going to give it another 30 minutes or so and try again. The Technet article you linked to has some details our error does not mention. Here's a thought: I am getting the impression though I'm not yet certain of it, that "indexing" of drives is being put on each drive instead of all under C:\program files Try removing them to see if the events persist or stop.