Increased RAM has messed up my system

  • Thread starter Thread starter Alexis
  • Start date Start date
A

Alexis

I have recently incresed the RAM on my machine from 128 to
384 MB. Since the change, all the programs that i run (so
far office and explorer) crash soon after they get
started. I also had a few automatic shutdown problems
(although these have ceased) with the error message
reading approx: "winnt\system32.exe not executable at 128
RAM" Or similar (the .exe file is correct, as is the 128
part),

I figure that the the programs and system have not
recognized that i now have 384 MB of RAM. How do I get it
to do this?

Any thoughts are greatly appreciated.

Alexis
 
Hi Alexis,

You have the wrong RAM, it's installed in the wrong order, or uninstall the
programs and reinstall them.


--
good computing,
don
--------

I have recently incresed the RAM on my machine from 128 to
384 MB. Since the change, all the programs that i run (so
far office and explorer) crash soon after they get
started. I also had a few automatic shutdown problems
(although these have ceased) with the error message
reading approx: "winnt\system32.exe not executable at 128
RAM" Or similar (the .exe file is correct, as is the 128
part),

I figure that the the programs and system have not
recognized that i now have 384 MB of RAM. How do I get it
to do this?

Any thoughts are greatly appreciated.

Alexis
 
....or it could be flaky ram. Try pulling the old ram out and replace
it with the new, if you still have problems them you know it's bad.

Rick
 
Greetings --

It's absolutely essential that any new RAM module(s) be fully
compatible with both the motherboard _and_ any other RAM module(s)
already in the system. Additionally, there are sometimes jumper
switches on older motherboards that need to be reset for the new RAM
configuration. Consult your PC/motherboard's manual for specific RAM
types that are acceptable, and any configuration requirements.


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Good thought Rick, and the possibility of it not being completely seated, I've
seen where folks didn't do this day in and day out.

--
good computing,
don
--------

....or it could be flaky ram. Try pulling the old ram out and replace
it with the new, if you still have problems them you know it's bad.

Rick
 
Possibly you are still running on your old
pagefile, which, as it was set up when
you had 128M, is now too small.

Right click My Computer>>Properties>>Advanced
Performance Options>>Virtual Memory>>Change

Make sure your page file is set to at least 384M

Costs nothing to try...
 
Vance Green said:
Possibly you are still running on your old
pagefile, which, as it was set up when
you had 128M, is now too small.

Right click My Computer>>Properties>>Advanced
Performance Options>>Virtual Memory>>Change

Make sure your page file is set to at least 384M
Click to expand...

Actually there's no specific requirement between the two. In fact
the more physical memory one has, the smaller pagefile is usually
required. One of my current systems has 768MB physical ram
with a 64MB pagefile. Runs great.

Rick
 
Microsoft has defined the min. and max. size of pagefile.sys as:

Minimum - RAM+32 megs ( anything less may cause the file to become corrupt)
Maximum- 4095 meg (there is a registry hack workaround to set multiple fils
containing 4095 meg each)

--
good computing,
don
--------


Good thought Rick, and the possibility of it not being completely seated, I've
seen where folks didn't do this day in and day out.

--
good computing,
don
--------

....or it could be flaky ram. Try pulling the old ram out and replace
it with the new, if you still have problems them you know it's bad.

Rick
 
dcdon said:
Microsoft has defined the min. and max. size of pagefile.sys as:

Minimum - RAM+32 megs ( anything less may cause the file to become corrupt)
Click to expand...

Don, this is the first time I've heard this. Can you provide a
reference? Assuming one is not doing suspend-to-ram, I don't
see why the pagefile has to be a minimum of RAM+32MB.

Thanks,
Rick
 
Hi rick,

The KB for max work around is
http://support.microsoft.com/?id=237740

I'm still looking for the minimum
I have so many files, it may take a little while.

--
:o)
don
---------



dcdon said:
Microsoft has defined the min. and max. size of pagefile.sys as:

Minimum - RAM+32 megs ( anything less may cause the file to become corrupt)
Click to expand...

Don, this is the first time I've heard this. Can you provide a
reference? Assuming one is not doing suspend-to-ram, I don't
see why the pagefile has to be a minimum of RAM+32MB.

Thanks,
Rick
 
Hi Rick,

There has been some issues with Virtual Memory. I don't know if it is UpDate
related or possibly infection. There is one KB on resetting the pagefile.sys.

Here it is: http://support.microsoft.com/?kbid=257758

This is more likely for rebuilding after the system has created temppf.sys. You
can do a search, but you have to be able to see system files. To do that look in
Folder Options in Control Panel. It's under general[tab].

There is another work around, if there is no temppf.sys created. The reason, you
can not delete the pagefile.sys. You will have to do that from the Restoration
Console by overwriting the file with say the boot.ini.

But I have another idea first. You can try resetting the virtual Memory size to
below the minimum MS recommends, like 31 MB for both and reboot. Then search for
temppf.sys then. If it shows, you are free to nuke pagefile.sys, so try 257758.

If you can't get it from there here is a KB for clearing pagefile.sys.
http://support.microsoft.com/?kbid=314834

If you have trouble, I am going to give you the instructions to rebuild
pagefile.sys.

--
good computing,
don
--------

Hi rick,

The KB for max work around is
http://support.microsoft.com/?id=237740

I'm still looking for the minimum
I have so many files, it may take a little while.

--
:o)
don
---------



dcdon said:
Microsoft has defined the min. and max. size of pagefile.sys as:

Minimum - RAM+32 megs ( anything less may cause the file to become corrupt)
Click to expand...

Don, this is the first time I've heard this. Can you provide a
reference? Assuming one is not doing suspend-to-ram, I don't
see why the pagefile has to be a minimum of RAM+32MB.

Thanks,
Rick
 
That's interesting...
I have 2gb RAM, and several times tried to reduce size of page-file,
but windows keeps resetting it to the previous value...
exact size cant remember offhand...
hmmm...

Chris
 
Back
Top