Event ID 51, USB 2.0 HDD not responding properly (internal WD 160 GB in a CompUSA enclosure)

Event ID: 51

Event Type: Warning

Event Source: Disk

Description: An Error was detected on device \Device\Harddisk3\D during a
paging operation.

Q244780

My results below (and differ slightly from Q244780):

0000: 04 00 68 00 01 00 b6 00

0008: 00 00 00 00 33 00 04 80

(IO_WARNING PAGING FAILURE)



0010: 2d 01 00 00 00 00 00 00

(STATUS_SUCCESS, request will be retried)



0018: 00 00 00 00 00 00 00 00

0020: 00 00 00 00 00 00 00 00

0028: c2 4e 00 00 00 00 00 00

(PATH ID= 0x????????; TARGET ID = 0x????????)



0030: ff ff ff ff 03 00 00 00 (LUN = 0x????????)



0038: 40 00 00 0e 00 00 00 00

(ScsiStatus = 0x40; SrbStatus =0x00)

(ScsiStatus = 0x40 means what?)

(SrbStatus of 0x00 = SRB_Status pending)



0040: 00 20 0a 12 80 03 20 40

0048: 00 00 01 00 0a 00 00 00

0050: 00 00 00 00 a8 bf 9b 81

0058: 00 00 00 00 38 ea b2 fb

0060: 00 00 00 00 08 81 c0 07

0068: 2a 00 07 c0 81 08 00 00

0070: 80 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

Those nos mean absolutly zero to 99% of all pc users.However,click on the
event/warning in event viewer,click on the url in it,this opens kb
help/support
in xp usually with a fix or solution to it.Event 51 is a hardware issue i
believe.

"Cymbal Man Freq." wrote:

> Event ID: 51
>
> Event Type: Warning
>
> Event Source: Disk
>
> Description: An Error was detected on device \Device\Harddisk3\D during a
> paging operation.
>
> Q244780
>
> My results below (and differ slightly from Q244780):
>
> 0000: 04 00 68 00 01 00 b6 00
>
> 0008: 00 00 00 00 33 00 04 80
>
> (IO_WARNING PAGING FAILURE)
>
>
>
> 0010: 2d 01 00 00 00 00 00 00
>
> (STATUS_SUCCESS, request will be retried)
>
>
>
> 0018: 00 00 00 00 00 00 00 00
>
> 0020: 00 00 00 00 00 00 00 00
>
> 0028: c2 4e 00 00 00 00 00 00
>
> (PATH ID= 0x????????; TARGET ID = 0x????????)
>
>
>
> 0030: ff ff ff ff 03 00 00 00 (LUN = 0x????????)
>
>
>
> 0038: 40 00 00 0e 00 00 00 00
>
> (ScsiStatus = 0x40; SrbStatus =0x00)
>
> (ScsiStatus = 0x40 means what?)
>
> (SrbStatus of 0x00 = SRB_Status pending)
>
>
>
> 0040: 00 20 0a 12 80 03 20 40
>
> 0048: 00 00 01 00 0a 00 00 00
>
> 0050: 00 00 00 00 a8 bf 9b 81
>
> 0058: 00 00 00 00 38 ea b2 fb
>
> 0060: 00 00 00 00 08 81 c0 07
>
> 0068: 2a 00 07 c0 81 08 00 00
>
> 0070: 80 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
>
>
>

As you already can guess yourself, there was an i/o error on the usb-attached
disk.
Close all apps that can access it and reconnect the disk.
Run chkdsk /F on it to fix possible errors.
If you see these errors often, replace the USB cable. Get the highest
quality cable (in a thick rigid metallic mesh coating. not el cheapo, thin
black plastic coating)

Regards,
--PA

"Cymbal Man Freq." wrote:
> Event ID: 51
>
> Event Type: Warning
>
> Event Source: Disk
>
> Description: An Error was detected on device \Device\Harddisk3\D during a
> paging operation.
>
> Q244780
>
> My results below (and differ slightly from Q244780):
>
> 0000: 04 00 68 00 01 00 b6 00
>
> 0008: 00 00 00 00 33 00 04 80
>
> (IO_WARNING PAGING FAILURE)
>
>
>
> 0010: 2d 01 00 00 00 00 00 00
>
> (STATUS_SUCCESS, request will be retried)
>
>
>
> 0018: 00 00 00 00 00 00 00 00
>
> 0020: 00 00 00 00 00 00 00 00
>
> 0028: c2 4e 00 00 00 00 00 00
>
> (PATH ID= 0x????????; TARGET ID = 0x????????)
>
>
>
> 0030: ff ff ff ff 03 00 00 00 (LUN = 0x????????)
>
>
>
> 0038: 40 00 00 0e 00 00 00 00
>
> (ScsiStatus = 0x40; SrbStatus =0x00)
>
> (ScsiStatus = 0x40 means what?)
>
> (SrbStatus of 0x00 = SRB_Status pending)
>
>
>
> 0040: 00 20 0a 12 80 03 20 40
>
> 0048: 00 00 01 00 0a 00 00 00
>
> 0050: 00 00 00 00 a8 bf 9b 81
>
> 0058: 00 00 00 00 38 ea b2 fb
>
> 0060: 00 00 00 00 08 81 c0 07
>
> 0068: 2a 00 07 c0 81 08 00 00
>
> 0070: 80 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
>
>
>

"Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
news:282E0D0B-BFB0-4840-A777-B3569AF14442@microsoft.com...
> As you already can guess yourself, there was an i/o error on the usb-attached
> disk.
> Close all apps that can access it and reconnect the disk.
> Run chkdsk /F on it to fix possible errors.
> If you see these errors often, replace the USB cable. Get the highest
> quality cable (in a thick rigid metallic mesh coating. not el cheapo, thin
> black plastic coating)
>
> Regards,
> --PA

Would I likely get this kind of error when using Win XP Home?
http://support.microsoft.com/?kbid=885352
System event ID 11 is logged when you cancel an I/O operation to a raw USB
2.0-attached hard disk drive in Windows 2000 Server SP4

"CAUSE
The System log error occurs because, when an I/O request packet (IRP) is
correctly canceled, the Usbstor.sys driver cannot translate the cancel operation
to a SCSI error, and therefore the operation is marked as an error. The error is
not valid, because no data destined for the hard disk drive is lost, and there
is no device error.
RESOLUTION
No action is required. The System log error is informational only and can be
safely ignored.
The third-party products that this article discusses are manufactured by
companies that are independent of Microsoft. Microsoft makes no warranty,
implied or otherwise, regarding the performance or reliability of these
products."



I'll try a powered USB 2.0 hub plugged into a USB 2.0/Firewire PCI card and use
a different USB cable between the HDD and the hub.
The HDD is currently in RAW form since formatting cannot be completed in either
FAT32 or NTFS, and the last partition couldn't be completed either.

I'm wondering now if I can format the USB 2.0 drive on a Windows 98 SE machine
without a PCI controller card, but with a USB 2.0 PCI card? I'll still be stuck
for the last partition not being any good at all (the last 47 GB of a 160 GB
HDD). Maybe I could repartition, so I lose less space on the last partition? How
much space should I have left in the unallocated space of the last partition? At
least in Windows 98 SE I could format to something bigger than 32GB per FAT32
partition!? I would guess that all would work on a WinXP machine if I could do
it.

"Cymbal Man Freq." wrote:
> Would I likely get this kind of error when using Win XP Home?

Yes. XP Pro and Home share the same kernel and drivers.
The Home version does it's best to be easier on clueless users, but in case
of hardware errors it falls short

> http://support.microsoft.com/?kbid=885352
> System event ID 11 is logged when you cancel an I/O operation to a raw USB
> 2.0-attached hard disk drive in Windows 2000 Server SP4

Wait a moment... it was event id 51, how it become 11?
Or this question is not related to your previous one?

--PA

Well, I switched out the USB cable for a different one, and brought in a USB
2.0 powered HUB. Then I could partition and format once again, so the hard
drive ISN"T shot! Then I got to copy three 2 GB image files. The first two
copied in 4 minutes flat, each. The third one took 20 minutes, so I figure
the machine ramped down to USB 1.1 speed (100 MB per minute as a salesman at
the store told me once). I still have many more GB to copy. Why the sudden
slowdown in the copy rate? Nothing changed with the machine in that time,
AFAIK yet.

There were HUNDREDS of Event 51 errors during the time that the copying was
done for all 3 large files. So why were the files copied successfully?


"Cymbal Man Freq." <Don't Bother@ForgedPostsAnonymous.unorg> wrote in
message news:5LzFf.5777$mF2.3217@trndny09...
> Well, I switched out the USB cable for a different one, and brought in a
> USB 2.0 powered HUB. Then I could partition and format once again, so the
> hard drive ISN"T shot! Then I got to copy three 2 GB image files. The
> first two copied in 4 minutes flat, each. The third one took 20 minutes,
> so I figure the machine ramped down to USB 1.1 speed (100 MB per minute as
> a salesman at the store told me once). I still have many more GB to copy.
> Why the sudden slowdown in the copy rate? Nothing changed with the machine
> in that time, AFAIK yet.
>

error 51 usually means trouble reading the drive, thats why it slowed down. Windows will drop the
speed if it has trouble doing a read. Just because you can partition and format doesn't mean they
isn't anything wrong with drive. Download diagnostics from har drive manufacturer to be sure.
--
Dave Vair
CNE, CNA, MCP, A+, N+

"Cymbal Man Freq." <Don't Bother@ForgedPostsAnonymous.unorg> wrote in message
news:fPzFf.19204$ZS3.2145@trndny05...
> There were HUNDREDS of Event 51 errors during the time that the copying was done for all 3 large
> files. So why were the files copied successfully?
>
>
> "Cymbal Man Freq." <Don't Bother@ForgedPostsAnonymous.unorg> wrote in message
> news:5LzFf.5777$mF2.3217@trndny09...
>> Well, I switched out the USB cable for a different one, and brought in a USB 2.0 powered HUB.
>> Then I could partition and format once again, so the hard drive ISN"T shot! Then I got to copy
>> three 2 GB image files. The first two copied in 4 minutes flat, each. The third one took 20
>> minutes, so I figure the machine ramped down to USB 1.1 speed (100 MB per minute as a salesman at
>> the store told me once). I still have many more GB to copy. Why the sudden slowdown in the copy
>> rate? Nothing changed with the machine in that time, AFAIK yet.
>>
>
>

Here's an excerpt by someone who thinks they've figured out some fix for Event
51 errors....but many people at this link have vastly different answers and
temporary answers. What works for awhile, quickly doesn't work much longer. A
lot of blame on M$ for this kind of problem. I am using a Promise ATA 100
Controller PCI card for the two internal hard drives. Everybody at this link
swears by Promise Controller cards for fixing problems like this. Maybe mine is
a little too old? It hasn't been used but for the last 4 months.

http://www.hardwareanalysis.com/con...ic/12946/?o=120

Yeah, I'm using Windows XP Pro with SP2 installed. I've never installed or used
Norton on my machine but I am using McAfee VirusScan 9.0. I did try adjusting my
pagefile but it had no effect. I set it to 500MB, then 1500MB, then disabled it
altogether, but I still kept gettings those errors. I know it sounds silly but
setting my memory preference to Programs instead of System Cache really does
solve my \Device\Harddisk0\D problems. People can give it a try by going to
their control panel and clicking on the system icon/app, click on the "Advanced"
tab, click on the "Settings" button under Performance to bring up the
Performance Options menu, click on "Advanced" tab, and then you can set your
memory usage to Programs instead of System Cache. I've also set my Processor
scheduling to Programs but that doesn't seem to affect the \Device\Harddisk0\D
errors. It seems like such a small insignificant setting but I swear it is the
cause and cure of my \Device\Harddisk0\D problems. I too was also prepared to
take everyone's advice and buy a Promise RAID controller but I stumbled onto my
cure. I hope everyone here finds a way to solve their problems because I know
how frustrating it is to spend your hard-earned money on "quality" parts only to
have your computer running less than perfectly. And I have tons of respect for
all you guys out there that actually contact your system/software vendors and
demand answers for these annoying problems that we all experience. To all the
people who actually have the time and energy to contact Microsoft: You guys are
heroes! I would never have the patience to do that.

Should I set the swapfile to 2.5 GB if I want to copy 2.0 GB image files?