event id 11 disk controller error usb drive Burden Kansas

Address 1221 Main St, Winfield, KS 67156
Phone (620) 229-8316
Website Link http://www.kpmwinfield.com
Hours

event id 11 disk controller error usb drive Burden, Kansas

http://support.microsoft.com/kb/159865 NOTE: Disk Management is enhanced in Windows 2000 and later operating systems. I do not know yet if the problem is with the Noontec hub or the Shintaro drive dock. Thanks... After troubleshooting the disk and possible bad IDE cable, it turned out that the enclosure was bad.

I myself and 3 of my friends have this problem, and it is the cables… sebastian Aug 13, 2012 @ 14:20:17 Suscribed hekomi Oct 15, 2012 @ 14:57:22 Solved!! Inserte un disco en la unidad /device/Harddisk5/DRS, ALGUNO DE UDS SABRIA DARME UNA ORIENTACION A KE SE DEBE Y COMO RESOLVERLO,? The Properties will contain "Device Type" information that will tell you if the disk is IDE or SCSI, and it will also display the "Hardware Vendor" name of the physical device Join & Ask a Question Need Help in Real-Time?

Is 99.999% and lossless good enough? Wow the identical machine does not do it eh. I checked and saw that it has Western-Digital Hard-drive, and went to their support site to download free utility. Still, as mentioned earlier - for most folks motherboard is fine and the culprit will be hard-drive that is getting old and about to fail.

I mean what if my car speedometer gave me my speed in furlongs per fortnight then converted that to a secret guid so my speedometer reads your speed is ...  {000f-2343-aff1-0034......}? Ended up saying they have no further ideas and were willing to ship a new MOBO if we want. might be finally solving it. Really sucks.

Today we connected this afternoon to test this again. Cause for concern? PS: As a bonus tip – while I was troubleshooting, I had to reinstall Windows 7 couple of times on various HD drives. Privacy statement  © 2016 Microsoft.

Kitts und Nevis St. I'll swap out that drive and see if the error goes away. 0 Jalapeno OP ToledoTown May 7, 2013 at 7:08 UTC Any update on this? I was able to pick up 8 GB of Gamer grade memory for $25 (after rebate), so that is another bonus with upgrade. Checked and this drive is not being imaged by system restore points.

But on removable media it seems that the Harddisk number I get seems so correspond with the PhysicalDrive. At first, I thought it was just a hardware problem with the system I got, but it's replacement suffered from the same thing. or it could be a mobo hd controller and/or driver issue, OR VERY LIKELY usb driver / traffic jam / communications handshake retries related, perhaps significant, or perhaps insignificant "ok to I have run both short and full diagnostics on this drive using both WD Utilities and PC-Doctor, and also Chkdsk, and every test completes successfully, indicating that there are no recognizables

Disabling the card reader through Device Manager seems to have stopped the intermittent error messages. The fatal error details are as follows: logical blockaddress 171f3f8, block count 128, command 30, drive bus 1 and drive bay 1. Even some graphics "share" memory with the the mobo and if said memory were swapped by virtual memory management (ever see a graphics card painting the screen reallly slowly, then speeds Doubtful but maybe.

Tried killing the BESR service, seemed to work eventually but in the end got the error removing with it stopped. 0 LVL 46 Overall: Level 46 Storage Hardware 30 Interestingly, it looks like others have used the sleep mode setting to fix those event Id 57 errors that we spent a while chasing on Windows XP. According to Microsoft Enterprise Support, the Hard disk number and the DR number should match. 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

Specifically we don't get the "IO_ERR_CONTROLLER_ERROR" part of the message or the 1% at the end of the controller message. I was under the impression that "DR" stands for "disk removable", but I honestly wasn't able to find any references to that so I could be wrong. You can use Disk Management to view this information without using Registry Editor. To "truly" solve this, you'd likely have to install the debugging version of windows and put windows into step-by-step debugging mode and might have to have the debugging code of the

Brad Jun 08, 2012 @ 01:58:50 I hate to say this but we have a radio station and our broadcast machine just got this error. At first, I was pretty much convinced that HD is dying. Hope this helps. EDIT: could this be in reference to the floppy ( A: ) drive that the system sees but that doesn't exist?

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. Really, what's needed is for Microsoft and Seagate engineer to ensure that in fact that error results in a retry and is LOSSLESS, that would be key, or else the sleep/wakeup maintenance efforts suffer while troops in the field try to decipher this hodgepodge of disparately presented information about the same subject. the driver?

Zoomed to 200% in Word it should be easy to read. At last I resolved it successfully. Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended Anyone have any input on the error?

Although it doesn't happen everytime, we found two additional messages that might help. system Error   1 2 Next ► 28 Replies Cayenne OP murpheous Feb 19, 2013 at 2:42 UTC click start, right click computer and select manage. by derektom on Feb 19, 2013 at 2:39 UTC | Windows Server 0Spice Down Next: Azure Server for my client or on Premise? It didn't get us very far though.

Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking Oddly enough, Windows allows you to click safely remove, and it then says "the device can now be safely removed" but it still throws this error at the exact same time. From a newsgroup post: "I had event 11 errors and it was a bug in my IBM ServeRaid firmware. I tried multiple cables and hard drives.