Paging error in Event Viewer

Anybody seen this one before? I don't get it since its my backup drive and there is no swap file on it?

Thanks
Rockit

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 1/14/2005
Time: 11:01:04 AM
User: N/A
Computer: COMPUTER
Description:
An error was detected on device \Device\Harddisk0\D during a paging operation.

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 33 00 04 80 ....3..€
0010: 2d 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: 1c 69 6b 00 00 00 00 00 .ik.....
0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ....
0038: 40 00 00 12 00 00 00 00 @.......
0040: 00 20 0a 12 40 03 20 40 . ..@. @
0048: 00 30 00 00 0a 00 00 00 .0......
0050: 00 00 00 00 68 95 77 82 ....h•w‚
0058: 00 00 00 00 38 93 77 82 ....8“w‚
0060: 02 00 00 00 59 e1 77 01 ....Yáw.
0068: 28 00 01 77 e1 59 00 00 (..wáY..
0070: 18 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 ........

 

Since it references hard disk 0, it is referring to your primary (1st) hard drive and not your backup drive. I'm assuming you are installed in the typical configuration with the OS booting from the primary drive.

Run chkdsk c: from a command prompt session but do not include any switches for the moment. Read the resultant report and see if any errors have been found. Post back the results.

Also tell us what kind of partitions you have on each drive. I assume you have two drives since you inferred that, but I may be wrong.

 

Surfer,

I have two hard drives. Hard drive 1 has 2 partitions (c:\ = 62 gb)(e:\ = 48gb)

Hard drive # 2 is Backup and D:\ = 6.4gb

If I run the chkdsk will the report be in the event viewer?

Thanks
Rockit

 

chkdsk with no switches (so read-only) does not report detail to the eventlogs if the run is fairly clean. I really don't know if major errors will generate an event. About all you will see will be the display to the DOS window with a quick summary of scan events. Again, maybe major errors will report there. I really don't remember.

Disk Paging is pretty much any memory <--> disk related I/O operation. Nothing specifically to do with your pagefile/swapfile although they can be involved in the I/O process.

A good summary of event 51 is Here with explanation and some troubleshooting tips.

note the altered title. I made it a little more specific to the problem

 

When I run with no page file I do not get this error?

This harddrive has been replaced by Western Digital because of getting this error before?

So it's a new hard drive that only gets this error when I have a swap file

Here's what I got in the dos window:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Rockit>chkdsk c:
The type of the file system is NTFS.
Volume label is Main.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Sorting index $I30 in file 8214.
Deleting index entry channel[1].css in index $I30 of file 1716.
Deleting index entry CHANNE~1.CSS in index $I30 of file 1716.
Deleting index entry gradient_panel[1].gif in index $I30 of file 1716.
Deleting index entry GRADIE~1.GIF in index $I30 of file 1716.
Deleting index entry hbx[1].js in index $I30 of file 1716.
Deleting index entry HBX_1_~1.JS in index $I30 of file 1716.
Deleting index entry quote[1].gif in index $I30 of file 1716.
Deleting index entry QUOTE_~1.GIF in index $I30 of file 1716.
Deleting index entry __utm[1].gif in index $I30 of file 1716.
Deleting index entry __UTM_~1.GIF in index $I30 of file 1716.
Deleting index entry newt-head[2].jpg in index $I30 of file 2547.
Deleting index entry NEWT-H~2.JPG in index $I30 of file 2547.
Deleting index entry rating_5[1].gif in index $I30 of file 2547.
Deleting index entry RATING~3.GIF in index $I30 of file 2547.
Deleting index entry favicon[1].ico in index $I30 of file 3227.
Deleting index entry FAVICO~1.ICO in index $I30 of file 3227.
Deleting index entry gradient_panelsurround[1].gif in index $I30 of file 3227.
Deleting index entry GRADIE~1.GIF in index $I30 of file 3227.
Deleting index entry rh5568[1].htm in index $I30 of file 3227.
Deleting index entry RH5568~1.HTM in index $I30 of file 3227.
Deleting index entry mail_yahoo_com_32005011318302700847.ico in index $I30 of fi
le 8214.
Deleting index entry www_grandtraverse_org_3aver011318325250768.ico in index $I3
0 of file 8214.
Deleting index entry WWW_G in index $I30 of file 8214.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

C:\Documents and Settings\Rockit>

 

That's exactly why I wanted you to run it without switches. You must now get your personal data backed up properly before running chkdsk /f or chkdsk /r since the data may get hosed with either of those switches. It's not a sure thing but the risk is great enough that protection is prudent.

 

My backup is a few weeks old but I went for it anyway.

I noticed that the files it lists as corrupt are in the browser cache?

Why does this keep happining? Is there a way to prevent it?

I ran the full chkdsk (5 steps) before I left for work this morning so I may have some work to do when I get home but I think it will be OK.

Thanks Allot
Rockit

 

I'll keep my fingers crossed and hope you don't get any big surprise when you get home.

As for the corruption in your TIF cache, that would be due to a corrupt index.dat file. You will need a special tool to fix that since deletion and recreation is the usual approach. I recommend CrapCleaner having recommended it for this same problem before with great results.

For the time being, limit its scope of work to the TIF's and the index.dat file only. Uncheck any other items that may be checked by default. You should have only those two boxes checked. Then run the program and reboot. You'll have a new index.dat file and hopefully your problem will have been disposed of.

 

No problems found? Also no found folder either. Everything seems to be working fine.

Could a browser crash cause this to happen?

Thanks
Rockit

 

Who knows? Could be I suppose but I rather think it was just a corrupt jpg or bmp in the cache.

Some very odd things can result from the index.dat cache getting corrupt. One recent one was here. Who would have thought?

 

Hmmm,
I left my computer on last night and when I checked the event viewer this morning the error was back? Ran Chkdsk and no error's found? So I got rid of the page file on the main hard drive and moved it to the other hard drive. We'll see what happens now.

P.S. I have been using **** Cleaner for quite some time now and I also run a script that deletes the index.dat file on shutdown. This error comes and goes but seems to be related to if and where I have the swap file?

Thanks
Rockit

 

It won't go away

There has to be something that's making this happen.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Rockit>chkdsk c:
The type of the file system is NTFS.
Volume label is Main.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
Deleting corrupt attribute record (160, $I30)
from file record segment 218.
Deleting corrupt attribute record (48, " ")
from file record segment 219.
Deleting corrupt file record segment 428.
Deleting corrupt attribute record (128, " ")
from file record segment 431.
Truncating badly linked attribute records
from file record segment 10489.
Deleting corrupt file record segment 10490.
Deleting corrupt file record segment 18914.
Truncating badly linked attribute records
from file record segment 18915.
Deleting corrupt attribute record (128, " ")
from file record segment 19085.
Deleting corrupt file record segment 19086.
Deleting corrupt file record segment 19087.
Deleting corrupt file record segment 19088.
Deleting corrupt file record segment 19092.
Deleting corrupt attribute record (48, " ")
from file record segment 19100.
Deleting corrupt file record segment 19101.
Deleting corrupt attribute record (16, " ")
from file record segment 19103.
Deleting corrupt file record segment 19103.
Deleting corrupt attribute record (48, " ")
from file record segment 19105.
Deleting corrupt file record segment 19109.
Deleting corrupt file record segment 19110.
Deleting corrupt file record segment 19111.
File verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

Anyway to troubleshoot this?

Thanks
Rockit

 

Perhaps it would pay to check the data cables, reseat them just to give them some frictional exercise. I don't know where else to look. I will say that I had a one week old computer that insisted on checking for and correcting errors on nearly every boot. The HD failed completely in the second week. I don't mean to alarm you unduly but in case you don't have good backups, now's the time.

I can't imagine this could be software - would be strange. Viral maybe..but most likely hardware. Memory is a possibility, substitution is the best test there, or pull each half and test.

 

Thanks for the reply Surfer

I have had this problem before and Western Digital sent me a new harddrive about two months ago after running a bunch of tests. It went away for awhile but now it's back. I'll try reseating the cables and checking the ram out.

Could this be because my system spec's are pretty low for doing the stuff I do on this computer? After all its a home built system with some parts in it from 1991

I rebuilt it in 2000 with a AMD 500 K62 and VIA chipset.

What about reverting to the original drivers for VIA?

The Nvidia and 4 in 1 VIA drivers are the only non Windows XP Pro SP2 drivers that I have updated.

Thanks Again
Rockit

 

At this point I think it comes down to a matter of personal preference.

For me, if a drive is gonna fail, I want to pick when it does so with all my personal stuff backed up, I'd boot to the XP CD and get into the recovery console then from there, run chkdsk /r on all the drives/partitions.

It could very well locate a bad spot on the drive, clean around it, mark it as bad, and you'd be back in business for ever. I've had that exact thing happen more than a few times. Or it could tear the thing up beyond any hope of repair. Had that one a couple of times too.

Usually if a complete chkdsk tears things up, your system wasn't long for this world anyway and you've saved yourself the worry of, 'will it start, will it run' every day.

I seriously doubt that 'low system specs' would contribute to this but then hardware is not my thing so I could easily be wrong.

 

Once NTFS starts going bad, for whatever reason, it usually just gets worse and worse till one day no-boot. It creeps like kudzu, and about as quick.

The original error message you posted indicates that something is wrong with the IO subsystem, probably at the hardware level. This phenomenon is only logged when it happens during paging, you could be getting hundreds of these a day, and the OS hides it from you, thanks to the miracle of NTFS journaling. This is the only reason you only get this error when you have a paging file there.

You've had an $index blown, and now a whole series of segments have gone aschew (notice the segments are sequential).

I agree with newt, i doubt its a low specs thing, but quite possibly a end of life issue. Hard drives come with a one year warrenty for a reason, because they start to fail after a year with enough frequency that its not profitable to provide replacements for longer. Money talks when it comes to that sort of thing. Since you've replaced the drive, its probably something else, I/O controller, on the motherboard perhaps, or standalone?

I also agree with surferdude, especially if this is old stuff, a little friction from a couple of reseats can knock the corrosion off the connectors.

 

I opened up the computer and reset the cables to and from the hard drives but the error keeps coming back .. No pattern .. just shows up once in awhile. I've got a couple other idea's but if anybody has any other suggestions I would greatly appreciate them.

Thanks Allot
Rockit