Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

A disk read error occurred. Press ctrl+alt+del to restart.

3 views
Skip to first unread message

Mac

unread,
Jun 25, 2003, 1:59:45 PM6/25/03
to
I'm having a problem with a computer. It has Windows XP Professional
(spanish edition) installed.

The problem is that windows does not boot. This computer has been
working for a year. Bios recognizes harddisk. The boot process goes
well, the bios tests memory, detects disks and cdroms and then windows
should start but instead of that, a message is show that reads "error
de lectura de disco. Presione ctrl+alt+supr para reiniciar".

I've found ppl with a similar problem and seems that the exact text of
the english versión of XP is "a disk read error occurred. Press
ctrl+alt+del to restart"

If tried to boot admin console with XP CD, but unfortunately this PC
has not an administrator user so I'm unable to log in. Anyway, XP CD
recognizes windows and knows that windows is installed on c:\windows
so it seems that the disk works.

Harddisk, spins correctly and does not make any unusual noise. It's a
one year old 40GB Western Digital Caviar. So it's still in warranty.

I've seen postings of people with the same problem but I've been
unable to find a solution.

My question is: is it a SOFTWARE or a HARDWARE error? Maybe
reinstalling windows the problem get's fixed but that computer is not
mine and I don´t want to have the same problem again in a few weeks.

R. McCarty

unread,
Jun 25, 2003, 2:12:40 PM6/25/03
to
From your description, I would say it is a data corruption problem
that effects part of the XP boot code. I would suggest you boot to
the Windows XP CD, take the Recovery Console. Once you get
a prompt type Chkdsk C: \R
This should locate and repair any un-readable clusters. If this works
you should immediately image the machine. I would download the
WDC diagnostics tool and verify the drive is not defective.


"Mac" <m...@theoffice.net> wrote in message
news:bd81d16b.03062...@posting.google.com...

Jonathan

unread,
Jul 9, 2003, 11:49:10 PM7/9/03
to
I had this very error tonight. I booted from the XP cd and ran the
recovery console. I ran the command FIXBOOT and it worked. The very
odd thing I can't seem to pinpoint is, each of the instances of this
error I have found online are from WD drives. Mine was also a WD
drive.

Best of Luck

"R. McCarty" <RMcC_...@mindspring.com> wrote in message news:<uo7BgV0O...@TK2MSFTNGP11.phx.gbl>...

Mac

unread,
Jul 11, 2003, 11:21:13 AM7/11/03
to
rid...@hotmail.com (Jonathan) wrote in message news:<75e94888.03070...@posting.google.com>...

> I had this very error tonight. I booted from the XP cd and ran the
> recovery console. I ran the command FIXBOOT and it worked. The very
> odd thing I can't seem to pinpoint is, each of the instances of this
> error I have found online are from WD drives. Mine was also a WD
> drive.

Mine was finally a physical hard disk fail. The first 10GB out of
30 had errors. Now it愀 working with the same disk repartitioned to
use only those last 30GB that seem to be fine. Don愒 know if it will
go on deteriorating or will stay stable. If it fails in a short period
of time I will post it in this thread.

I did not realize what you say about always being WD disks owners
who report this problem. Anyway, it seems much more related to faulty
boot files that could appear with any disk of any brand. But, who
knows, I bought about six PCs at the same time with the same
configuration, all them with seagate disks but one that carried a WD
unit. This is the one that have failed.

0 new messages