Windows 10: Some applications keep saying that I have used up all of my memory.

Hi, When I enter things like my browser and Minecraft, they both crash and say out of memory. When I check task manager the memory is not even half full. I did a memory diagnostic and nothing came broken. I don't know why they keep saying out of memory but I have 16 GB of memory which is more than enough to run Minecraft and my browser.

:)

 

Overclocking / Undervolting guide for Vega 56 or 64?

Here's a quick laundry list:

List of software to use for overclocking and testing
Examples:
Wattman (and how to find and use it, like an overview, including profiles)
Unigine Valley or Heaven (use this for quick testing while changing settings in Wattman and checking for stability / artifacts) ...just suggesting this
How to monitor cores / mem speeds and temps during testing (I've seen screen overlays, and others using GPUz)

Step-by step overclocking in Wattman
Fan speeds
Power limit
Temp limit
Voltages
Core speeds
Memory speeds

 

Adobe Applications saying there isn't enough memory

@GracieAllen,

That seems golden.

From your "test" description, your two main application are still competing for memory when you switch back an forth from one to another. this is the main problem that causes the exhaustion at some point.

When you're ready, I still suggest to upgrade to 64Gb ram to mitigate that phenomenon as much as possible.

 

Adobe Applications saying there isn't enough memory

It’s not FIXED, but it IS different…
Today I created a small HDR/PANO – 18 D850 shots, 6 sets of 3-each HDR images.

Sent the first 6 pano images from Lightroom to Photoshop. Set reposition and content-aware fill.
Panorama worked fine, CA fill FAILED with out of memory.
Cleared all cache, PS memory usage dropped about 1.5GB, fill still failed. Memory usage around 16GB at this point.
Flattened the image, fill still failed.
Cleared cache again, fill still failed.
It APPEARS that once this error appears, it NEVER goes away…

During processing I captured a little info. This is during processing the first 6 images.







Sent the SECOND set of 6 images, same settings.
Panorama worked, CA FILL failed with out of memory.









I missed the period where memory got to 31.9 but it did, and it sat there for several seconds before dropping back slightly.

Sent the THIRD set of 6 pano images, same settings. Same thing... It went between 31.4 and 31.9 GB of memory
Pano worked, CA fill failed.

I SAVED all three panoramas and told PS to do the HDR blend of the 3 panorama images.
It worked fine.










In the shot of the Task manager - I have no idea how to make it show you the image larger - you can see that the only things using a significant amount of energy are Adobe. With all the processing done, and the HDR output sitting there, Photoshop hung onto around 21.5 GB of memory. It also continued to show almost all the Scratch in use…
Went back to Lightroom, took the three panorama outputs and told Lightroom to do a Photo Merge HDR.







Lightroom sucked up a bunch of memory – I captured an image where PS was about 14.4GB and Lightroom was over 13.5 GB, but it’s missing at the moment…

Anyhow, eventually Lightroom failed on the HDR – again, it’s never successfully created anything NEAR this size, and memory dropped back to “normal”…

BUT, it seems like once Photoshop displays that “out of memory” popup, it never goes away no matter how much memory I give it back. Clearing cache doesn’t help, deleting all the images and reloading them doesn’t help. Only thing that works is shutting down Photoshop and restarting it…

My OTHER question is why does Photoshop show 23.4GB for scratch space when the scratch drive has more than 1.2 TB of free space. There were about 25GB of photoshop temp files on the scratch disk, but there’s a HUGE amount of free space if needed. What would have happened if the 23.4 PS thinks is there had gotten exhausted?

And BTW, even when it showed 31.9 in use of 31.9 GB, Efficiency NEVER dropped below 100%.

And LAST BUT NOT LEAST, a shot of the screen showing HALF the memory on the system is available and Photoshop STILL won't do the content-aware fill...