Event viewer entries...

[Steve]

Hi, I'm running XP pro SP2 with all patches applied.

I've recently started getting multiple event log entries (see example
below). They seem to come in blocks of 20 entries, with each entry time
stamped about 20 seconds apart. They occur even when I am not logged on or
using the PC.

A hard drive scan reveals no problem and I am not having any obvious
operational problems. I cannot think of anything obvious that I have done to
prompt their appearance. Any ideas would be appreciated.

Thanks, Steve

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 7
Date: 10/30/2005
Time: 2:03:05 PM
User: N/A
Computer: MAIN
Description:
The device, \Device\Harddisk0\D, has a bad block.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 07 00 04 c0 .......À
0010: 00 01 00 00 9c 00 00 c0 ....?..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 38 0e e1 05 00 00 00 .8.á....
0028: 62 d5 f7 01 00 00 00 00 bÕ÷.....
0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ....
0038: 40 00 00 84 02 00 00 00 @..?....
0040: 00 20 0a 12 40 03 20 40 . ..@. @
0048: 00 00 00 00 0a 00 00 00 ........
0050: 00 b0 32 86 c8 1a db 84 .°2?È.Û?
0058: 00 00 00 00 48 6e b1 85 ....Hn±?
0060: 02 00 00 00 1c 87 f0 02 .....?ð.
0068: 28 00 02 f0 87 1c 00 00 (..ð?...
0070: 30 00 00 00 00 00 00 00 0.......
0078: f0 00 03 00 00 00 00 0b ð.......
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

 

[Steve]

Looking at the timing of the last set of events, it seems that my problem
may have something to do with my machine going into "sleep" mode.

Steve

 

[Sharon F]

Looking at the timing of the last set of events, it seems that my problem
may have something to do with my machine going into "sleep" mode.

Steve

Possible explanations:
-Driver for drive controller is not fully compatible with standby mode. If
an update is available, give it a try to see if it works any better. There
may also be other updates available from the system manufacturer (or system
board manufacturer) that will give better standby results.

-Drive health is fine but drive is slow to spin up when returning from
standby. In this case, the "error" in Event Viewer could be misleading -
The operating system probes the drive on its return from standby and can't
get a good initial read because it's not operating full tilt yet. When the
drive is fully "up" again, Event Viewer doesn't balance the picture because
it does not inform you that a read was finally successful. Not much you can
do about this one. It's the normal "state" of the current hardware.

You could test this by changing Power Options for the drives - do not allow
them to go into standby. There should be no further error messages
regarding the one drive when the rest of the system is returning from
standby. If the drive is slow to spin up at startup, there may still be a
lingering error in that time frame.

- The drive does have a problem that the Windows disk tools aren't
catching. For peace of mind, you could download utilities from the drive
manufacturer and test the drive again.