Serious problem with virtual memory

[Qu0ll]

Vista Ultimate x64, 4GB RAM.

I am unable to process some image files of less than 512MB in size in
various image manipulation applications as they complain that there is not
enough memory. The virtual memory is setup as 512MB on the system volume
(C and 4-8GB on D: but it appears that only the 512MB is being used. So I
go into it to set it to be system managed or to increase the amount of VM on
the C: drive and it gives me a BSOD. The BSOD has 0x0000001E as the first
data value and mentions something about checking for insufficient disk space
before the machine reboots (this may be on all BSODs, I don't know). I have
experimented with various values of VM and it is clear that ANY change to
the settings will result in a BSOD. There is about 15GB free on C: (which
is 50GB in total) and about 300GB free on D:. I have defragmented C: and
there seems to be plenty of space for a contiguous swap file of the size
that I am trying to set.

How do I resolve this issue? I am severely hampered by not being able to
use more than about 512MB of RAM or so it would seem.

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[DP]

How much RAM do you have (excluding virtual memory)?

 

[Lee]

How much RAM do you have (excluding virtual memory)?

Read the first line of his post.

 

[Lee]

Vista Ultimate x64, 4GB RAM.

I am unable to process some image files of less than 512MB in size in
various image manipulation applications as they complain that there is not
enough memory. The virtual memory is setup as 512MB on the system volume
(C and 4-8GB on D: but it appears that only the 512MB is being used. So
I go into it to set it to be system managed or to increase the amount of
VM on the C: drive and it gives me a BSOD. The BSOD has 0x0000001E as the
first data value and mentions something about checking for insufficient
disk space before the machine reboots (this may be on all BSODs, I don't
know). I have experimented with various values of VM and it is clear that
ANY change to the settings will result in a BSOD. There is about 15GB
free on C: (which is 50GB in total) and about 300GB free on D:. I have
defragmented C: and there seems to be plenty of space for a contiguous
swap file of the size that I am trying to set.

How do I resolve this issue? I am severely hampered by not being able to
use more than about 512MB of RAM or so it would seem.

You could probably change the settings via the registry if you had another
machine to import them from.

I am running Ultimate 32 bit so I don't know if mine would apply, but they
look like below, all system managed. It probably would not be wise to import
these settings without more information.

There's a bunch XP pagefule info here
http://www.petri.co.il/pagefile_optimization.htm


Here's something that looks somewhat promising
http://www.downloadjunction.com/product/store/31201/index.html

Lee
-----------------------------------------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management]
"WriteWatch"=dword:00000001
"ClearPageFileAtShutdown"=dword:00000000
"DisablePagingExecutive"=dword:00000000
"LargeSystemCache"=dword:00000000
"NonPagedPoolQuota"=dword:00000000
"NonPagedPoolSize"=dword:00000000
"PagedPoolQuota"=dword:00000000
"PagedPoolSize"=dword:00000000
"PhysicalAddressExtension"=dword:00000000
"SecondLevelDataCache"=dword:00000000
"SessionPoolSize"=dword:00000004
"SessionViewSize"=dword:00000030
"SystemPages"=dword:000c3000
"PagingFiles"=hex(7):3f,00,3a,00,5c,00,70,00,61,00,67,00,65,00,66,00,69,00,6c,\
00,65,00,2e,00,73,00,79,00,73,00,00,00,00,00
"ExistingPageFiles"=hex(7):5c,00,3f,00,3f,00,5c,00,43,00,3a,00,5c,00,70,00,61,\
00,67,00,65,00,66,00,69,00,6c,00,65,00,2e,00,73,00,79,00,73,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\PrefetchParameters]
"BootId"=dword:0000008d
"BaseTime"=dword:0bc3b9e4
"VideoInitTime"=dword:0000008c
"EnableSuperfetch"=dword:00000003
"EnablePrefetcher"=dword:00000003
"EnableBootTrace"=dword:00000000

----------------------------------------------------------

 

[Qu0ll]

You could probably change the settings via the registry if you had another
machine to import them from.

I am running Ultimate 32 bit so I don't know if mine would apply, but they
look like below, all system managed. It probably would not be wise to
import these settings without more information.

There's a bunch XP pagefule info here
http://www.petri.co.il/pagefile_optimization.htm


Here's something that looks somewhat promising
http://www.downloadjunction.com/product/store/31201/index.html

I have managed to changed the VM settings by using TweakVI but I am not
convinced that they actually work. Is there some way to test if the VM is
working properly? I have two different image manipulation applications and
both complain that there's not enough memory when working with files of
about 300MB or greater. Surely they should be able to cope with bigger
files than that given that I now have 8GB of virtual memory and 4GB physical
memory.

I ran the memory diagnostic tool on the Vista DVD and it reported no
problems and I also ran a startup repair (as someone else suggested) and it
reported that nothing needed to be done. I really need some way to
determine if all 8GB of VM is usable by applications. I think it unlikely
that 2 totally different applications from different vendors would both have
a limitation inbuilt in regard to file sizes in memory so I am doubting that
Vista's VM management strategies and algorithms are working.

Any ideas?

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[Dana Cline - MVP]

Just an off the wall question here - are you using 64 bit versions of these
graphic apps? Have you talked to their support people?

Dana Cline - MCE MVP

 

[Qu0ll]

Just an off the wall question here - are you using 64 bit versions of
these graphic apps? Have you talked to their support people?

Well no, not exactly but they are supposed to be compatible with Vista x64.
I spoke to one support rep who said that the problem is solved by increasing
the virtual memory. Clearly, that hasn't worked.

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[Larry Maturo]

This is a wild and crazy idea, but if you have 4 Gigs or physical
RAM, why don't you just turn off virtual memory? Then you
surely will not have applications complaining about you not
having enough of it.

-- Larry Maturo

 

[Dana Cline - MVP]

Which programs are these? A fellow MVP, Barb Bowman, uses only x64 Vista and
she does a lot of image processing on her DSLR Raw files - she might know of
any incompatibilities or tweaks...

Dana Cline - MCE MVP

 

[Qu0ll]

Which programs are these? A fellow MVP, Barb Bowman, uses only x64 Vista
and she does a lot of image processing on her DSLR Raw files - she might
know of any incompatibilities or tweaks...

The main problem is with Paint Shop Pro Photo XI and also with the Control
Center that comes with the Brother scanner I am using. PSP Photo XI fails
when I try to do noise reduction or other fairly simple image manipulations
and the Brother Control Center fails when I try to scan images at greater
than resolutions of 2400 x 2400 dpi (even though it declares that the
resulting file is only about 350MB).

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[Qu0ll]

This is a wild and crazy idea, but if you have 4 Gigs or physical
RAM, why don't you just turn off virtual memory? Then you
surely will not have applications complaining about you not
having enough of it.

Umm, I would turn it off if I didn't encounter a nasty BSOD whenever I make
ANY change to the settings.

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[Richard Urban]

When I run into unexplainable errors I always suspect one of two things. The
first, and easiest to work with is logical disk corruption.

1. Open an elevated command prompt window
A. Click the Start Orb
B. Type cmd in the search box
C. Right click on the cmd entry that appears in the top pane.
Choose "run as administrator"

2. Type chkdsk c: /f as a command to be run

3. Press the enter key

4. You will be told that the command can not be run because the drive
can not be locked. You will be asked if you want to run this command
upon your next boot into Vista. Type Y and then press enter.

5. Exit the command prompt window

6. Reboot your computer

See if the icons are now correct for the program associated with them.

Note: The command above (chkdsk c: /f) is assuming that you have Vista
installed to drive C:

If you have installed Vista to another drive you will have to change C: to
whatever drive you have installed the operating system to.

Let us know the outcome!

The second thing I suspect is RAM that is not working properly with Vista.
Just because it is fine in Windows XP (before a person upgrades) does not
necessarily mean that it is optimal for Vista. I have solved for many
seemingly impossible problems by changing out the RAM to a "premium" RAM
from either Corsair or Crucial. And, until you (or anyone) has actually made
the switch I/you/he/they are not qualified to say that the RAM is fine.
Substitution is the best check. Testing RAM doesn't find it all.

A good technician will have dozens of various sticks of spare RAM of a known
quality, just for such testing purposes.


--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Dana Cline - MVP]

I'm betting Barb's answer in this case is to use a more professional image
program like PhotoShop. Personally I use PSP also, but would never attempt
to do anything with an image that large. I don't know much about the Brother
other than my wife has had odd issues with her Brother all-in-one. You might
be better served with a Canon or HP scanner...

More curiosity - what kind of images are you trying to scan at such a high
resolution?

Dana Cline - MCE MVP

 

[Richard Urban]

I would agree that Photoshop is better able to work with the larger image
files. But in this case, the fact that the O/P can not alter his pagefile
without his O/S crashing indicates a severe system problem.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Larry Maturo]

I didn't realize you got a BSOD on any change, I thougth it was onlly
when you ran certain programs. In this case I whole heartedly agree with
Richard. This is definitely some sort of system problem.

-- Larry Maturo

 

[Drew Boillot]

I'd suggest going to safe mode, and tring to put the page file on 1 and only
1 drive (start w/ the C: drive and make it about 4gb min to 6.5gb max) if
your problems still occure, try it on the D:\ drive.

other things to check, make sure you have the latest mobo drivers installed,
as they may have updated IDE/sATA drivers

running chkdsk on both drives like suggested earlier isn't a bad idea at
all.

HTH

 

[Qu0ll]

When I run into unexplainable errors I always suspect one of two things.
The first, and easiest to work with is logical disk corruption.

1. Open an elevated command prompt window
A. Click the Start Orb
B. Type cmd in the search box
C. Right click on the cmd entry that appears in the top pane.
Choose "run as administrator"

2. Type chkdsk c: /f as a command to be run

3. Press the enter key

4. You will be told that the command can not be run because the drive
can not be locked. You will be asked if you want to run this
command
upon your next boot into Vista. Type Y and then press enter.

5. Exit the command prompt window

6. Reboot your computer

See if the icons are now correct for the program associated with them.

Note: The command above (chkdsk c: /f) is assuming that you have Vista
installed to drive C:

If you have installed Vista to another drive you will have to change C: to
whatever drive you have installed the operating system to.

Let us know the outcome!

The second thing I suspect is RAM that is not working properly with Vista.
Just because it is fine in Windows XP (before a person upgrades) does not
necessarily mean that it is optimal for Vista. I have solved for many
seemingly impossible problems by changing out the RAM to a "premium" RAM
from either Corsair or Crucial. And, until you (or anyone) has actually
made the switch I/you/he/they are not qualified to say that the RAM is
fine. Substitution is the best check. Testing RAM doesn't find it all.

A good technician will have dozens of various sticks of spare RAM of a
known quality, just for such testing purposes.

I ran chkdsk as suggested and it reported only a couple of unindexed files
but no other actual errors or problems (and it still BSODs). I guess that
faulty RAM is still a possibility but it's very expensive FB-DIMM memory
from Kingston so replacing it isn't really an option at this point. Also,
there are absolutely no other symptoms of memory problems in all other
aspects of the way Vista is running. It just purrs like a kitten - all
other software (a considerable collection) works as expected.

Any ideas?

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[Qu0ll]

I'd suggest going to safe mode, and tring to put the page file on 1 and
only 1 drive (start w/ the C: drive and make it about 4gb min to 6.5gb
max) if your problems still occure, try it on the D:\ drive.

When I use TweakVI to put the page file entirely on the C: drive the same
problem happens. When I place it totally on the D: drive it doesn't even
BSOD when I go to adjust the settings - it just reboots spontaneously. I'll
try Safe Mode next.

other things to check, make sure you have the latest mobo drivers
installed, as they may have updated IDE/sATA drivers

All the latest drivers and firmware are installed.

running chkdsk on both drives like suggested earlier isn't a bad idea at
all.

Done, see other post.

Hmm, any further ideas? This is driving me nuts.

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[Drew Boillot]

Your memory should have a Limited Lifetime warranty if its from Kingston..
Check in to that.
If you are running in Dual Channel mode, (and if you have a free slot), move
the 2nd chip to another slot, and try it again.