not enough virtual memory or paging file quota after repair instal

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I installed the SP2 from an automatic update and after the reboot it wanted
to do it was busy doing stuff and got a blue screen of death. I had no option
other than to reboot. It never started again. It said it was canceling the
installation and reverting back to the previous state but rebooted itself and
never completed. It was basically stuck in an install cycle and was failing
to cancel it.

I was left with only one option - a repair install. I did this and now it
starts up but after the Windows screen appears it flashes up (for all of
1/10th of a second) a popup that says the following text before it
immediately reboots again.

"Not enough virtual memory or paging file quota to complete the specified
operation"

This happens in safe mode or VGA mode also. I have no way of getting into
windows other than via a command prompt (emergency repair console).

I doubt another repair installation will help.

Are there any files I can delete that could help this? I looked for
pagefile.sys but didn't see it. I did see a hiberfil.sys and tried renaming
it but after the next reboot it was back with the same size.

I desperately need a solution as I'm leaving the country (and the people
who's computer it is) tomorrow and if I can't solve it for them then they'll
be at the mercy of some computer store who'll charge them hundreds of $$
probably.
 
d d said:
Hi,

I installed the SP2 from an automatic update and after the reboot it wanted
to do it was busy doing stuff and got a blue screen of death. I had no option
other than to reboot. It never started again. It said it was canceling the
installation and reverting back to the previous state but rebooted itself and
never completed. It was basically stuck in an install cycle and was failing
to cancel it.

I was left with only one option - a repair install. I did this and now it
starts up but after the Windows screen appears it flashes up (for all of
1/10th of a second) a popup that says the following text before it
immediately reboots again.

"Not enough virtual memory or paging file quota to complete the specified
operation"

This happens in safe mode or VGA mode also. I have no way of getting into
windows other than via a command prompt (emergency repair console).

I doubt another repair installation will help.

Are there any files I can delete that could help this? I looked for
pagefile.sys but didn't see it. I did see a hiberfil.sys and tried renaming
it but after the next reboot it was back with the same size.

I desperately need a solution as I'm leaving the country (and the people
who's computer it is) tomorrow and if I can't solve it for them then they'll
be at the mercy of some computer store who'll charge them hundreds of $$
probably.
Click to expand...

The setting for your paging file in the registry is probably incorrect.
Edit the registry via a networked machine to restore the registry file
pointer to the correct drive. It is kept here:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
 
Try booting to xp cd,recovery,press enter for password,then in cmd screen
type:CHKDSK C: /R When its thru,type:EXIT Let xp try to start.If problems
still exist,you might try to repair xp again,also if the registry is
corrupt,or
pagefile in the registry corrupt (i dought) but the fix for that is:307545
#307973 Both deal in repair.
 
Hi,

I'll try these options. Thanks.



Andrew E. said:
Try booting to xp cd,recovery,press enter for password,then in cmd screen
type:CHKDSK C: /R When its thru,type:EXIT Let xp try to start.If problems
still exist,you might try to repair xp again,also if the registry is
corrupt,or
pagefile in the registry corrupt (i dought) but the fix for that is:307545
#307973 Both deal in repair.
Click to expand...
 
Thanks but I have no network access to the machine. I really need
to know how to change the registry from the recovery console, or
to restore it to a previous point. Looks like I won't be able to fix it
for them in time.
 
You cannot edit the registry from the Recovery Console.

If you had plenty of time, knowledge and a good deal of
patience then you could boot the machine with a boot
disk from here:
http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html

It gives you the option to edit the registry off-line and
examine/modify the location of the paging file:

3. Boot from the boot disk.
4. Accept the suggested NT partition.
5. Accept the full path to the registry directory.
6. Type system
7. Type 9 (for Registry Editor)
8. Type ? (to see the available commands)
9. Type ls (to see the current keys)
10. Type cd ControlSet003 (or ControlSet002 if you have no 003) (it's
case-sensitive!)
11. Type cd Control
12. Type cd Session Manager
13. Type cd Memory Manager
14. Type type PagingFiles
You can now see where the system expects your paging file to be.
15. Type ed PagingFiles
16. Type C:\pagefile.sys 192 385
(or whatever is appropriate for you)
17. Type --n
18. Type type PagingFile
You should see your changes.
19. Type q
You will be prompted to save or discard your changes.
 
You are the MAAAANN !!!!!!

I tried the deleting of the config files (the hive) from the
windows\system32\config folder and replaced them with
the ones from windows\system32\repair (or was it just
windows\repair) and that did the trick. That tip was in the
307545 KB article you suggested. One reboot later and everything
was all still in place.

And all that with 3 hours to spare :) Thanks sooooo much.
 
I'll be saving this for another time, I'm sure it will come in
useful. For this occasion I was lucky that restoring the hive
did the trick. Never again will I visit someone and think "I'm
gonna do all your windows updates for you to ensure you're
up to date and secure". Leave well alone :)

Thanks guys . . . .
 
d said:
*You are the MAAAANN !!!!!!

I tried the deleting of the config files (the hive) from the
windows\system32\config folder and replaced them with
the ones from windows\system32\repair (or was it just
windows\repair) and that did the trick. That tip was in the
307545 KB article you suggested. One reboot later and everything
was all still in place.

And all that with 3 hours to spare :) Thanks sooooo much.


:
[vbcol=seagreen]
Try booting to xp cd,recovery,press enter for password,then in cmd screen
type:CHKDSK C: /R When its thru,type:EXIT Let xp try to start.If problems
still exist,you might try to repair xp again,also if the registry is
corrupt,or
pagefile in the registry corrupt (i dought) but the fix for that is:307545
#307973 Both deal in repair.

:
*
Click to expand...
Click to expand...
 
d said:
*You are the MAAAANN !!!!!!

I tried the deleting of the config files (the hive) from the
windows\system32\config folder and replaced them with
the ones from windows\system32\repair (or was it just
windows\repair) and that did the trick. That tip was in the
307545 KB article you suggested. One reboot later and everything
was all still in place.

And all that with 3 hours to spare :) Thanks sooooo much.


:
[vbcol=seagreen]
Try booting to xp cd,recovery,press enter for password,then in cmd screen
type:CHKDSK C: /R When its thru,type:EXIT Let xp try to start.If problems
still exist,you might try to repair xp again,also if the registry is
corrupt,or
pagefile in the registry corrupt (i dought) but the fix for that is:307545
#307973 Both deal in repair.

:
*
Click to expand...
Click to expand...


This also worked great for me. I wish I had found this sooner. I
spent most of a day trying different tools to hack registry, SAM etc.,
with no luck. Then this!!! I used ERD to do it. wow!! I never even
had to try twice :)
 
Back
Top