Pagefile.sys entry

[Guest]

At boot Windows checks the FAT32 file system on C: and reports that the
\pagefile.sys entry contains a nonvalid link, and that the size of the
\pagefile.sys entry is not valid. Further that \windows\dump9460.tmp is
crosslinked on allocation unit 2354418.

Thinking the pagefile.sys file might have been corrupted, e.g. by a bad
shutdown, I tried temporarily setting No Paging file under advanced system
setttings via the Control Panel, as in http://aumha.org/win5/a/xpvm.php (see
Problems). I then rebooted and searched in vain on all drives for a
pagefile.sys file to delete. The boot sequence continues to be interrupted
and stalled by the message. I bypass it with the h/w reset button.

My conclusion is that it is the Registry entry that has a problem. If so,
how do I fix it?

 

[Ayush]

Run chkdsk

1.Go to Start menu > Run
2. Type this :
chkdsk c: /f
3.Press y and then hit Enter
4.Now the next time you boot let it run.
--

Ayush [ Be ''?'' Happy ]

For any query, search > www.Google.com
Want to know about a term > http://en.wikipedia.org


| At boot Windows checks the FAT32 file system on C: and reports that the
| \pagefile.sys entry contains a nonvalid link, and that the size of the
| \pagefile.sys entry is not valid. Further that \windows\dump9460.tmp is
| crosslinked on allocation unit 2354418.
|
| Thinking the pagefile.sys file might have been corrupted, e.g. by a bad
| shutdown, I tried temporarily setting No Paging file under advanced system
| setttings via the Control Panel, as in http://aumha.org/win5/a/xpvm.php
(see
| Problems). I then rebooted and searched in vain on all drives for a
| pagefile.sys file to delete. The boot sequence continues to be interrupted
| and stalled by the message. I bypass it with the h/w reset button.
|
| My conclusion is that it is the Registry entry that has a problem. If so,
| how do I fix it?

 

[Guest]

I ran the checkdisk routine numerous times, in fact I cannot boot without
being invited to do so. The messages I report at the beginning of my post can
only be found when it has completed. On completion Windows fails to boot,
unless I bypass the stoppage with a hardware re-set. Your answer is of no
help.

Run chkdsk

1.Go to Start menu > Run
2. Type this :
chkdsk c: /f
3.Press y and then hit Enter
4.Now the next time you boot let it run.
--

Ayush [ Be ''?'' Happy ]

For any query, search > www.Google.com
Want to know about a term > http://en.wikipedia.org


| At boot Windows checks the FAT32 file system on C: and reports that the
| \pagefile.sys entry contains a nonvalid link, and that the size of the
| \pagefile.sys entry is not valid. Further that \windows\dump9460.tmp is
| crosslinked on allocation unit 2354418.
|
| Thinking the pagefile.sys file might have been corrupted, e.g. by a bad
| shutdown, I tried temporarily setting No Paging file under advanced system
| setttings via the Control Panel, as in http://aumha.org/win5/a/xpvm.php
(see
| Problems). I then rebooted and searched in vain on all drives for a
| pagefile.sys file to delete. The boot sequence continues to be interrupted
| and stalled by the message. I bypass it with the h/w reset button.
|
| My conclusion is that it is the Registry entry that has a problem. If so,
| how do I fix it?

 

[Robert Moir]

I ran the checkdisk routine numerous times, in fact I cannot boot
without being invited to do so. The messages I report at the
beginning of my post can only be found when it has completed. On
completion Windows fails to boot, unless I bypass the stoppage with a
hardware re-set. Your answer is of no help.

Hmmm. From your description of the problem I would list a disk fault as one
of the more reasonable outcomes, which makes suggesting running chkdsk
fairly reasonable, so you might consider being a little more patient with
someone who is trying to help you. I'd have a registry problem somewhere
towards the back of my list of likely problems, only slightly ahead of alien
intervention.

If you haven't already, you may need to change your explorer settings to
find the file. In explorer folder options / view, you will need to tick
"show hidden files and folders" (which you've probably already done) and
turn off "Hide Protected Operating System files" (which many people miss).

I'd also see about testing the disk with something a bit smarter than
chkdsk - I like Ontrack Data Advisor for this, myself.
http://www.ontrack.com/dataadvisor/

 

[Ayush]

What is the size of Pagefile, check it is below 4 gb.

AND run the chkdsk with f and r parameters.
chkdsk /f /r

--

Ayush [ Be ''?'' Happy ]

For any query, search > www.Google.com
Want to know about a term > http://en.wikipedia.org


|I ran the checkdisk routine numerous times, in fact I cannot boot without
| being invited to do so. The messages I report at the beginning of my post
can
| only be found when it has completed. On completion Windows fails to boot,
| unless I bypass the stoppage with a hardware re-set. Your answer is of no
| help.
|
| "Ayush" wrote:
|
| > Run chkdsk
| >
| > 1.Go to Start menu > Run
| > 2. Type this :
| > chkdsk c: /f
| > 3.Press y and then hit Enter
| > 4.Now the next time you boot let it run.
| > --
| > > Ayush [ Be ''?'' Happy ]
| >
| > For any query, search > www.Google.com
| > Want to know about a term > http://en.wikipedia.org
| >
| >
| > | > | At boot Windows checks the FAT32 file system on C: and reports that
the
| > | \pagefile.sys entry contains a nonvalid link, and that the size of the
| > | \pagefile.sys entry is not valid. Further that \windows\dump9460.tmp
is
| > | crosslinked on allocation unit 2354418.
| > |
| > | Thinking the pagefile.sys file might have been corrupted, e.g. by a
bad
| > | shutdown, I tried temporarily setting No Paging file under advanced
system
| > | setttings via the Control Panel, as in
http://aumha.org/win5/a/xpvm.php
| > (see
| > | Problems). I then rebooted and searched in vain on all drives for a
| > | pagefile.sys file to delete. The boot sequence continues to be
interrupted
| > | and stalled by the message. I bypass it with the h/w reset button.
| > |
| > | My conclusion is that it is the Registry entry that has a problem. If
so,
| > | how do I fix it?
| >
| >
| >

 

[Guest]

The log from PowerMax, like HD Tune, confirmed the problems were with the
files, as reported by Windows. But your remark about something alien seems to
have been correct. (BTW we were looking for causes, not outcomes at this
stage.)

I uninstalled Tencent's QQ program, an interactive messaging suite popular
in China. Not understanding Chinese, I was getting no value from it, only
mystification, and some aggro.

It was then possible to run CheckDisk, this time fixing about 50 lost
clusters and resolving by copying the crosslink on dump9460.tmp.

Windows now boots without the error message inviting me to run CheckDisk.
Continuing to clean up, I ran ran SpyBot Search and Destroy. It found
nothing, but Lavasoft Ad-Aware Personal Edn found and fixed 30 problems. Disk
Cleanup and a 6-hour Defrag (which used to stall and now completes) finished
the job.

The Defrag report however says that I have 1,083 fragments in a 1.5GB file,
\FOUND.001\FILE0000.CHK. I presume it's a system file and cannot be deleted?

The pagefile setting for C: is now Min 2MB Max 50, with the two other
internal harddrives handling the requirement using Windows management. Total
size is 3,070.

 

[Alec S.]

At boot Windows checks the FAT32 file system on C: and reports that the
\pagefile.sys entry contains a nonvalid link, and that the size of the
\pagefile.sys entry is not valid. Further that \windows\dump9460.tmp is
crosslinked on allocation unit 2354418.

Thinking the pagefile.sys file might have been corrupted, e.g. by a bad
shutdown, I tried temporarily setting No Paging file under advanced system
setttings via the Control Panel, as in http://aumha.org/win5/a/xpvm.php (see
Problems). I then rebooted and searched in vain on all drives for a
pagefile.sys file to delete. The boot sequence continues to be interrupted
and stalled by the message. I bypass it with the h/w reset button.

My conclusion is that it is the Registry entry that has a problem. If so,
how do I fix it?

Does it do this on every boot?

Just delete the pagefile. Boot into safe mode and delete \pagefile.sys. It is scrap paper; delete it, check the disk for errors,
then boot into normal mode and see if it still does it.

 

[Guest]

The problem is fixed, as described in my post a few hours ago. Yes, it was
occurring on every boot. Thanks.