Controller Errors in Event Log

[Agent_C]

This error pops up in the Administrative Tools / Event Log several
times a day. If I didn't examine the long, I'd have no idea there was
a problem, as it doesn't seem to be impacting performance.

Any idea how to troubleshoot this?

Thanks,

A_C


---- Event Log entry ---
Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 6/25/2006
Time: 2:41:50 PM
User: N/A
Computer: c9887-NY
Description:

The driver detected a controller error on \Device\Harddisk2\D.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 0b 00 04 c0 .......À
0010: 03 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 13 c4 00 00 00 00 00 00 .Ä......
0030: ff ff ff ff 06 00 00 00 ÿÿÿÿ....
0038: 40 00 00 00 00 00 00 00 @.......
0040: ff 20 06 12 08 01 30 10 ÿ ....0.
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 60 ae 60 86 ....`®`?
0058: 00 00 00 00 70 ee 4a 86 ....pîJ?
0060: 00 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........
- END

My system:

Abit AW8 Motherboard
Intel 3.4 GHZ Dual Core CPU
1 GB Kingston Ram
XP Home SP2
Adaptec 19160 controller card
Fujitsu (MAS3735NP) 15K rpm 73 GB SCSI drive

 

[Dave Patrick]

This article may help. I'd download and run a disk diagnostic utility from
the drive manufacturer's web site.

http://support.microsoft.com/kb/159865/

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| This error pops up in the Administrative Tools / Event Log several
| times a day. If I didn't examine the long, I'd have no idea there was
| a problem, as it doesn't seem to be impacting performance.
|
| Any idea how to troubleshoot this?
|
| Thanks,
|
| A_C
|
|
| ---- Event Log entry ---
| Event Type: Error
| Event Source: Disk
| Event Category: None
| Event ID: 11
| Date: 6/25/2006
| Time: 2:41:50 PM
| User: N/A
| Computer: c9887-NY
| Description:
|
| The driver detected a controller error on \Device\Harddisk2\D.
|
| For more information, see Help and Support Center at
| http://go.microsoft.com/fwlink/events.asp.
| Data:
| 0000: 0f 00 68 00 01 00 b6 00 ..h...¶.
| 0008: 00 00 00 00 0b 00 04 c0 .......À
| 0010: 03 01 00 00 00 00 00 00 ........
| 0018: 00 00 00 00 00 00 00 00 ........
| 0020: 00 00 00 00 00 00 00 00 ........
| 0028: 13 c4 00 00 00 00 00 00 .Ä......
| 0030: ff ff ff ff 06 00 00 00 ÿÿÿÿ....
| 0038: 40 00 00 00 00 00 00 00 @.......
| 0040: ff 20 06 12 08 01 30 10 ÿ ....0.
| 0048: 00 00 00 00 14 00 00 00 ........
| 0050: 00 00 00 00 60 ae 60 86 ....`®`?
| 0058: 00 00 00 00 70 ee 4a 86 ....pîJ?
| 0060: 00 00 00 00 00 00 00 00 ........
| 0068: 00 00 00 00 00 00 00 00 ........
| 0070: 00 00 00 00 00 00 00 00 ........
| 0078: 00 00 00 00 00 00 00 00 ........
| 0080: 00 00 00 00 00 00 00 00 ........
| 0088: 00 00 00 00 00 00 00 00 ........
| - END
|
| My system:
|
| Abit AW8 Motherboard
| Intel 3.4 GHZ Dual Core CPU
| 1 GB Kingston Ram
| XP Home SP2
| Adaptec 19160 controller card
| Fujitsu (MAS3735NP) 15K rpm 73 GB SCSI drive
|
|
|
|

 

[daytripper]

This error pops up in the Administrative Tools / Event Log several
times a day. If I didn't examine the long, I'd have no idea there was
a problem, as it doesn't seem to be impacting performance.

Any idea how to troubleshoot this?

Thanks,

A_C


---- Event Log entry ---
Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 6/25/2006
Time: 2:41:50 PM
User: N/A
Computer: c9887-NY
Description:

The driver detected a controller error on \Device\Harddisk2\D.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 0b 00 04 c0 .......À
0010: 03 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 13 c4 00 00 00 00 00 00 .Ä......
0030: ff ff ff ff 06 00 00 00 ÿÿÿÿ....
0038: 40 00 00 00 00 00 00 00 @.......
0040: ff 20 06 12 08 01 30 10 ÿ ....0.
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 60 ae 60 86 ....`®`?
0058: 00 00 00 00 70 ee 4a 86 ....pîJ?
0060: 00 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........
- END

My system:

Abit AW8 Motherboard
Intel 3.4 GHZ Dual Core CPU
1 GB Kingston Ram
XP Home SP2
Adaptec 19160 controller card
Fujitsu (MAS3735NP) 15K rpm 73 GB SCSI drive

You only listed the one hard drive, yet the message is pointing to the third
hard drive. But note that memory card readers are also listed as "harddrives"
in the system event recorder and Disk Management applet, and it wouldn't
surprise me if USB flash "disks" would show up as "harddrives" as well.

If you really only have a single hard drive on this system, it's likely these
messages are pointing at some other device...

/daytripper

 

[Agent_C]

If you really only have a single hard drive on this system, it's likely these
messages are pointing at some other device.

Thanks, you were entirely correct. These messages were emanating from
a front panel card reader, defined as drives 1 & 2 in Device Manager.

Drive 0 = SCSI hard drive
Drive 1, 2 assigned to a 9in1 USB card reader connected directly to
the MB.

A_C

 

[daytripper]

Thanks, you were entirely correct. These messages were emanating from
a front panel card reader, defined as drives 1 & 2 in Device Manager.

Drive 0 = SCSI hard drive
Drive 1, 2 assigned to a 9in1 USB card reader connected directly to
the MB.

A_C

Indeed, I was going to ask if you had one of those readers.

fwiw, I occasionally see a similar error fingering my USB-connected memory
card reader when my system wakes from Standby mode and fails to (logically)
reconnect the (empty) reader. Unplugging and replugging the reader brings it
back to life, and the problem hasn't been onerous enough to do much more than
that...

Cheers

/daytripper