An error was detected on device \Device\Harddisk0\D during a pagin

  • Thread starter Thread starter sriesch
  • Start date Start date
S

sriesch

While attempting to determine the cause of an intermittent slowdown in
Windows XP Pro boot times (extra seconds to extra minutes, or no slowdown at
all), I ran across a set of warnings in the Event Viewer that seem to happen
whenever the slowdown happens. Source: Disk, Event ID 51, "An error was
detected on device \Device\Harddisk0\D during a paging operation."
Question 1: Any idea what is causing this? I would rather avoid the
expense of randomly replacing my newest hard drive on the off chance that
this fixes the error unless there is a way to know for sure it's about to die.
Question 2: what is the 'D' referring to? I thought it was supposed to
refer to the partition, but I have not created a partition D on that disk;
the entire drive is the boot partition (unless that's the default name given
to the boot partition? can't find that mentioned anywhere though.)

If I follow the supplied link, I get: "Explanation: An input/output (I/O)
request to a memory-mapped file failed and the operation was retried." and
"User Action: If these events are logged regularly on a primary system
drive, replace the device. Otherwise, no user action is required."

Other clues: I ran Seagate's "DiskWizard for Windows", and it thinks the
disk is perfectly healthy. The disc has in fact been functional since I got
it a few short years ago with no obvious problems, however I did just today
have an error during a file copy operation, which I'm hoping will turn out to
be the same problem. I was not monitoring the log up until recently, and
I'm uncertain exactly when the slowdown started as I often walk away during
bootup since it's so slow normally anyway. Looking back through the log, I
also see (although only in one area) Source atapi, Event ID 5, "A parity
error was detected on \Device\Ide\IdePort1." and Source disk, event ID 11,
"The driver detected a controller error on \Device\Harddisk1\D.". These
errors along with the failed copy were somewhere in the middle of a bunch of
attempts to completely reload the PC from scratch and thus may have been
between driver installations and updates. The disk is a Seagate ST3300822AS
300GB hard drive, although Windows only reports 232 GB of free space. It has
only a single partition.

Thanks in advance for any solutions/clues.
 
Harddisk0 Usually refers to C: drive with the OS on it.Try going to run,type:
cmd In cmd type:DiskPart In DiskPart,type:list disk Type:list volume
You'll see the partitions installed,type:HELP For all cmds If only one
hd is
installed,you must have multiple partitions on it,& the OS must be on D:,it
should be on C: +,the OS is using the "other" partition on the same hd as a
paging file,somthing it should not ever do...
 
Andrew E. said:
Harddisk0 Usually refers to C: drive with the OS on it.Try going to run,type:
cmd In cmd type:DiskPart In DiskPart,type:list disk Type:list volume
You'll see the partitions installed,type:HELP For all cmds If only one
hd is
installed,you must have multiple partitions on it,& the OS must be on D:,it
should be on C: +,the OS is using the "other" partition on the same hd as a
paging file,somthing it should not ever do...
Click to expand...

It appears that the hard drive does not have an extra D partition. I
deleted all partitions and then created the boot partition from the
unpartitioned space and stopped there.

DISKPART > list volume gives me the following info:
Volume ### Ltr Label Fs Type Size Status Info
--------------- --- --------- ---- --------- ------- --------
 
The disk is a Seagate ST3300822AS
300GB hard drive, although Windows only reports 232 GB of free space.
Click to expand...
Whoops, correction, it is a 250GB disk. I was looking at the wrong
receipt, so that's not actually a clue after all.

I have also completely disconnected my DVD-ROM drive which was D: just for
kicks and that does not prevent the paging operation warnings from happening.
 
I also tried moving the SATA cable from one socket to another, which moved
the drive from channel 3 to channel 6, but that doesn't stop the error 51
from happening.
 
I think the error 51 may be unrelated to the other errors I saw. After
completely reloading my system from scratch (also updating some firmware and
doing some disk maintenance while I was at it) I haven't seen the error 51
yet. Admittedly it hasn't been very long, but previously I would have
encountered it by now. Hopefully it is gone for good and not just hiding.
The other two errors remain, and seem to be tied to the motherboard as I
can move the disks to another PC (although I had to reload the OS and drivers
for the other PC which could have an effect) and not see the exact same
errors in the log. Unsure if it's hardware or driver related. I guess I'll
just try to live with it until it's time to either get a new motherboard or a
new secondary drive (which will probably be SATA instead of IDE.)
 
Back
Top