Event ID 11 (disk) in Event Viewer - frontal USB ports acting weird


  1. Posts : 19
    Windows 10 21H2 (19044.1526)
       #1

    Event ID 11 (disk) in Event Viewer - frontal USB ports acting weird


    Hello,

    So, I was taking a look at Event Viewer today, and I found lots of events, the source being "disk", with ID 11, about a controller error. As my SSD works fine and everything seems to point to removable drives (since the SSD is 'HardDisk0' and all errors show 'HardDisk1'), I tested three different USB drives in two computers, my desktop PC and a Lenovo G51 laptop. Also it's important noting both frontal USB ports are acting weird - this is all detailed below. Devices are:

    • Kingston DataTraveler 3.0 (64 GB)
    • Kingston DataTraveler 100 G2 (16 GB)
    • TOSHIBA DTB310 External HDD (1TB)


    ==== KINGSTON DataTraveler 3.0 ====

    Not recognized at all in the front left port; it works very slowly in the front right and two rear ports: one that supports USB 3.0 and the other 2.0. File Explorer hangs frequently when browsing and data transfer rates are very slow and/or behave erratically.

    Ejecting the drive generates an event ID 11: "The driver detected a controller error in \ Device \ Harddisk1 \ DR4." This does not appear to occur if it is ejected from either of the two aforementioned rear ports.

    Works in all laptop's ports (two USB 3.0 and 2.0) - transfer rates behave in the same way, but events with ID 11 did NOT appear after ejecting the device.

    Note: HDTune Pro and CheckFlash both showed no bad sectors.

    ==== KINGSTON DataTraveler 100 G2 ====

    Works in both front ports and two rear USB 3.0 and 2.0 ports. In all cases transfer speeds are decent and fairly constant.

    When ejecting, ID 11 events showed up in all cases:

    - Front left: "The driver detected a controller error in \ Device \ Harddisk1 \ DR6."
    - Front right: "The driver detected a controller error in \ Device \ Harddisk1 \ DR7."
    - Rear USB 3.0: "The driver detected a controller error in \ Device \ Harddisk1 \ DR8." (Three in three seconds apart!)
    - Rear USB 2.0: "The driver detected a controller error in \ Device \ Harddisk1 \ DR9."

    On the Lenovo G51, it is recognized by all ports and transfer speeds behave the same. ID 11 events appeared when ejected from one of the USB 3.0 ports and on the only 2.0 port.

    Note: Quick Check with HDTune Pro does not show bad sectors. This flash drive it's quite old and even though it works fine, generated errors in both computers, but way more on the desktop PC. It could be a problem with the drive itself.

    ==== TOSHIBA DTB310 ====

    It does not work on either of the two front ports. In both cases when disconnecting it does not generate any event.

    It works correctly and as expected in the rear ports, both USB 2.0 and USB 3.0. When ejecting and disconnecting, no event is generated.

    It works correctly and as expected on all ports of the Lenovo G51, and no event is generated when ejecting.

    Note: S.M.A.R.T. attributes are all OK - checked with CrystalDiskInfo. Also, a quick scan with HDTune Pro and WD LifeGuard showed no errors.

    ===

    My desktop PC was built six and a half years ago, with many components being older or slightly older. This could just be wear and tear. However, I'd like to hear other thoughts, because you guys very likely know better than me. Should I be worried or just carry on?
    Last edited by marmalade22; 20 Dec 2020 at 20:53.
      My Computer


  2. Posts : 1
    Windows 10
       #2

    Error Event (ID 11) logged following 'Eject' of CF card.


    System details:-

    Akasa USB 3.0 SuperSpeed Memory Card Reader AK-ICR-14

    Edition Windows 10 Pro
    Version 21H1
    Installed on ‎29/‎05/‎2021
    OS build 19043.1165
    Experience Windows Feature Experience Pack 120.2212.3530.0

    Problem:-

    Each time I eject a CF card from the taskbar, I get three consecutive error messages reported in the Event Log:-
    ID: 11 The driver detected a controller error on \Device\Harddisk2\DRx.
    Each of the three events is separated in time by about 1 second.
    The drive name DRx increments each time a CF card is plugged in & ejected.
    The errors are reported even without physically unplugging the CF card.
    The errors happen even if the card is not in use (i.e. not being read).

    This happens with every CF card I have tried. Files on the cards can be read without problems.

    I am unsure if this problem only began to appear following a Windows 10 update.

    The problem does not happen when using a USB stick inserted in the USB 3.0 socket on the Akasa card reader.
    It only happens when using a CF card (formatted in a Nikon D810).

    According to Device Manager, I have Realtek USB 3.0 Card Reader driver version 10.0.17763.31247.
    Attempts to update the driver give a message telling me that Windows thinks it is up to date.
    However, searching the web, I have found a later version: 10.0.19042.31267 dated 2021 from softpedia.com.
    I could not find this driver on the Realtek website. They just have 10.0.370.188 dated 2018.
    I tried updating the driver but it made no difference to the errors.

    ====

    Log Name: System
    Source: disk
    Date: 26/08/2021 09:04:07
    Event ID: 11
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-383S470
    Description:
    The driver detected a controller error on \Device\Harddisk2\DR10.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="disk" />
    <EventID Qualifiers="49156">11</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-08-26T08:04:07.7058395Z" />
    <EventRecordID>13647</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="18172" />
    <Channel>System</Channel>
    <Computer>DESKTOP-383S470</Computer>
    <Security />
    </System>
    <EventData>
    <Data>\Device\Harddisk2\DR10</Data>
    <Binary>0E00800001000000000000000B0004C003010000000000000000000000082D00000000000000000068F09C020000 0000FFFFFFFF06000000580000000000000000000612080000100000000041000000000000000000000080AFEF0907CFFFFF 000000000000000010700E0407CFFFFF00000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000</Binary>
    </EventData>
    </Event>

    ====

    - - - Updated - - -

    I think I may have found the problem...

    I downloaded and installed the original driver for the Akasa AK-ICR-14 card reader from here:-
    Akasa Thermal Solution

    Now when I check the Realtek USB3.0 Card Reader Driver Version in Device Manager, I get:-
    Driver Date: 18/10/2017
    Driver Version: 10.0.16299.31239

    The Event ID 11 errors on ejecting the CF card have gone away.
    What's more, I now get a notification message telling me that it is safe to unplug the card.
    That message stopped working when I started getting the errors.

    When I first noticed the problem, the Realtek driver version was 10.0.17763.31247
    It looks like a Windows Update had replaced the driver with a later version that doesn't work correctly with the Akasa card reader.

    A later version of the Realtek driver (10.0.19042.31267) from softpedia.com gives the same problem.

    The solution is to stick to the original driver.
    No doubt a future Windows Update will update the driver and screw things up again.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:26.
Find Us




Windows 10 Forums