Hi Michael,
I think the drive is failing, so I'll replace it. It's not software,
I suspect, but hardware. There are no page files on the primary IDE
physical, in any case. I have two SCSI drives that each have about a
gig and a half page files.
Seagate utility this morning okayed the quick test on the drive, but
flagged something about the file system. I give up. It seems people
who have this and can't get rid of it easily (without running
low-level utilities that seem to be a temporary fix at best)
experience drive failure in relatively short order.
I can afford a drive. ^^_^^
Thanks,
Yuki
P.S. Pagefiles can be moved, or defragged, but not while online. You
have to use a utility that will do it offline (not from within
Windows). Generally, there is little need of this however. If the
page file is a problem, it can simply be deleted offline, and Windows
will create a new one on the next boot.
Wednesday, August 2, 2006, 8:23:55 AM, you wrote:
MSG> Yuki,
MSG> Looking around, It appears to be some write cache problem. But
no solid
MSG> fixes for it.
MSG> Is most threads discussing this error many people are reporting
HD
MSG> failure soon after.
MSG> So to be sure, Backup your data.
MSG> Also, I don't think defraging will help. I believe the page
file is
MSG> "unmoveable". And it's
MSG> the page file that appears to have the problem.
MSG> MSG
MSG> Yuki Taga wrote:
>>
>> This is the rather infamous disk error during a paging operation.
>>
>> Event Type: Warning
>> Event Source: Disk
>> Event Category: None
>> Event ID: 51
>> Date: 8/1/2006
>> Time: 7:31:43 PM
>> User: N/A
>>
>> Description: An error was detected on device \Device\Harddisk2\D
>> during a paging operation.
>>
>> I get this once every, oh, six months or so. Usually the same drive
>> as indicated above, which is a logical partition on the primary IDE
>> drive (drives 0 and 1 are SCSI). Running chkdsk /F between boots has
>> always made this error message go away in the past.
>>
>> But today, it popped up again on a reboot, and I cannot make it go
>> away. It's in the system log of course, 12 or 13 times every time,
>> and apparently very early in the boot process, as in immediately
>> after the network adapter is detected. So far, it does not reappear
>> at all after the boot sequence, which leads me to believe it may be a
>> false positive.
>>
>> I've run chkdsk /F on the entire physical drive, which is actually
>> three logical partitions. Chkdsk says clean. System log says
>> problem after the subsequent boot. I've run off-line defrag runs
>> using Perfect Disk. If there was a genuine file system problem on
>> the volume, PD would require it be fixed before defrag could take
>> place. I'm backed up of course, but I cannot find any apparent
>> *real* problem ... except for the sys log warning.
>>
>> This logical drive is where AB lives.
>>
>> A lot of Googling on this serves up a lot of unsatisfactory
>> resolutions for other people. It seems this particular error can be
>> real, or a real wild goose chase.
>>
>> Anyone?
>>
>> Yuki
Please note that this group is for discussion between users only.
To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com
For other support material please check also:
http://www.amibroker.com/support.html
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/amibroker/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
