event id 11 driver detected controller error Camden Wyoming Delaware

Address 2423 Kenton Rd, Dover, DE 19904
Phone (302) 734-8862
Website Link http://compatibleinkjet.com

event id 11 driver detected controller error Camden Wyoming, Delaware

like C:, D:, etc and which is the harddrives and dvd/cd, floppy, etc. However, we get random numbers at the end. x 286 EventID.Net As per Adaptec: "Our testing indicates the event is generated on several models of hard disks used to boot to Windows 2000. We shall see if its the final answer or not.

Doubtful but maybe. Seculla Aug 09, 2012 @ 17:44:05 It's the stupid SATA cables. When a physical sector of the disk is read by an application (e.g. Nox Go to Solution 58 Comments LVL 2 Overall: Level 2 Message Expert Comment by:rupeshsaini2010-06-30 In almost all cases, the event id 11 message is being posted due to hardware

Will this help? Anyone have any input on how to fairly divide the points? Any advice? Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber?

The "Harddisk5" should refer to "Disk 5" in Disk Management however. I change it so each drive was on its own IDE physical connection, and put my CDROM on the second channel as slave. I found the cause to be a USB Compact Flash card reader. Thank God, chasing that "crown for wild goose chases" was getting old Ocanada!

Resolution: Remove or replace the faulty hard drive. And I guess SG support is making double assurance that you have no errors in file systems of these drives via this reformat. 0 Message Author Comment by:Jsmply2010-07-03 Thanks. This will be demonstrated using Windows Live Photo Gallery on Windows 7 operating system. This is especially true if Roxio EZCD Creator is installed.

TECHNOLOGY IN THIS DISCUSSION Microsoft 492074 Followers Follow Microsoft Windows Server Microsoft Windows Server 2012 Join the Community! Every disk will have a device controlling the Raw Physical drive (DR identifier) and a device per each partition, controlling the partition (DP instance) For example: Harddisk1\DR2 and Harddisk1\DP3 Unlike in the case And this error literally came out of no where. This error seems to be happening almost every time the drive is removed.

Further investigation revealed Windows 2000 is generating (1E) Prevent/Allow Medium Removal commands to the boot device. Boot-up returned to normal speed and errors went away after disconnecting the card reader. for my IDE drive the problem has not appeared anymore. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up

Already have an account? You and noxcho are already considering that evidently. Seems to be OK for just now but I'm not holding my breath, very strange fault, can easily be mis-diagnosed however I do agree with yourself on the controller as being Once in a while, the drive has trouble waking up and generate this controller error.

I reviewed all connections, they seemed fine. Wishing to have a printer usable at a moment's notice, I got un-lazy and updated my printer driver, so the printer connects to my router, instead. Good news and this question is really worth of being added to EE knowledge base. Please folow below link..

Heat can cause HDD to fail early, which is likely what you are seeing. The first part of the .txt output should hopefully contain a list of currently detected storage /Device strings and their associated drive letters. It looks like this question solved the mystery behind the event id 57 paging errors in Windows XP also. Not a member?

Thanks, in advance. I had windows search for an updated driver (in Device Manager) for the USB ports, but Windows claims that the driver is up to date. The utilities I tried from the Shareware/Free space are Ashampoo HDD Control 2 (Free to try, but can be a bit ‘spammy' - http://download.cnet.com/Ashampoo-HDD-Control/3000-2086_4-10929035.html) and HDD Scan (free - http://hddscan.com/). It is troubling that there is also the same event code for harddisk 1.

x 131 Anonymous This error is more likely to have been caused if Intel ATA Mass Storage device driver is installed or if it is an incorrect version. Ocanada any idea where to check what you suggested in Windows 7? The D: drive was not accessible. Maybe it's a combination of windows and drivers and hardware sort of timing-out that all just happen to coincide.

If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. I have HP RAID management software but it didn't really help either since I have so many other hard drives (USB, iSCSI) that are not on the internal RAID. During that period Windows is fully functional and we had used it like that for over a week while troubleshooting. 11/11/11 And Our Binary Future The Adventures of the Me-2 Ship I am just worried about losing data.

I have just switched the SATA cable to Port1 as all errors seem to happen on Port0. 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. 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. The system itself is a brand new install of Windows 7, and the diagnostics have been run on the system and it seems to be running flawlessly and with the latest

Ask ! So i'm curious.. It found HDD head-misalignment and after running for about an hour, it was able to repair it. Prior to finding out about this bug, I temporarily resolved the problem by defragging my hard drive to reduce disk I/O".

New computers are added to the network with the understanding that they will be taken care of by the admins. Join our community for more solutions or to ask questions. I've seen some give themselves points, if ever it was deserved this would be one. After restarting the machine a few times, I thought to check the event log.

Look at lower pane. Specifically we don't get the "IO_ERR_CONTROLLER_ERROR" part of the message or the 1% at the end of the controller message. They both have a qlogic 1040b scsi adapter, directly connected to digital ba356 scsi storage box. As soon as we clicked on the little green icon to safely remove hardware, it threw the error event before telling it to remove.