Not enough resources to complete this operation

An old issue but I couldn't find anything that seemed like a solution.

Windows 10 22H2 - 19045 32 bit, 4Gb memory

Ran Chkdsk, DISM and Scannow - all come up clean
Increased page file size, increased non-paged pool and services\null
increased IRP stack size
resource monitor shows good memory resources

Restart usually temporarily solves it. This makes me think there is a buffer somewhere
I'm not aware of, but what could it be? It gets flushed at restart apparently.

One prog that usually fails is Image For Windows backup, especially when doing
a differential backup, which is resource intensive. Terabyte has no answer.

Can't upgrade this to 64 bit right now due to downtime and inconvenience, but
it doesn't seem to be regular RAM that is the issue, so additional RAM may not
make a difference

Appreciate any hints/insights, etc.

Mario

spunk said:

You cannot upgrade to more the 4GB of RAM on your system running Windows 10 32 bit, adding more RAM will not be read in a 32 bit OS.
Resources indicates not Enough RAM. If you are doing a System Image of your computer, consider using a 3rd party app like Macrium Reflect or your favorite Imaging software. Inside that app, create a USB Flash Drive Rescue Windows PE of the app. Boot the computer with the Flash drive and backup a system image Outside of Windows so there won't be using as many resources.

The bottom line is, you need to backup your files and do a Clean Install of Windows 10 64 bit to eliminate any resource conflicts.

Thanks for the reply. I understand the 32 bit limit of 4Gb, however watching the Resource Monitor does not show RAM insufficiency.
Normally anything exceeding available ram would go to swap, which it does. The non-paged pool was increased because that
won't go to swap. I suspect a driver issue with Nvidia being #1. Their drivers have been buggy in the past and for the later
cards the 64 bit version is updated all the time but the 32 bit is from 2018.

What possible "buffer" could be getting exceeded but get cleared upon restart? It's unpredictable with no problems for a while, then issues recur. All of the usual resources have been increased with no effect. I'd like to move to 64 bit but that's not an option at this time. If RAM doesn't show excessive load and swapping, then even 64 bit with lots of RAM might give problems. It's not just the BU program. If enough usage occurs between restarts by routine programs, then it can happen. This constant restarting is reminding me of Win98. I'm missing something.

Hi Mario,

Yes, I will fix your computer!

Not enough resources to complete this operation error indicates that the process is running out of virtual memory. In 32 bit Windows the limit for process virtual memory is 2GB, but you may see errors starting at 1.8GB+ because of memory fragmentation.
The above recommendation is right. The system needs to be updated to 64 bit. There is one other thing to try but no guarantees that it will help and may, in fact makes things worse.
Change the process virtual memory to 3GB, lowering the kernel memory to 1GB by using the /3gb switch. There is an AutoDesk post that goes over how to do this. https://www.autodesk.com/support/tec...the%20computer.

AARC said:

Restart usually temporarily solves it. This makes me think there is a buffer somewhere
I'm not aware of, but what could it be? It gets flushed at restart apparently.

Could be USER or GDI resources that your device is running out of. It's difficult to tell without knowing what apps you run, how often you open and close them and how long you run your device before rebooting.

Have a look at Mark Russinovich's blogs about the subject:
Pushing the Limits of Windows: USER and GDI Objects – Part 1
Pushing the Limits of Windows: USER and GDI Objects – Part 2

Hope this helps...

Many thanks to all for the concise input. I'll work through all of the suggestions and see
if I can turn up the problem and will post back any solution.

It may or may not be related to 32 vs 64 bit but at this time going to 64 bit is not
possible. The only doubt about the 32 vs 64 would be that all will go well for
a while, i.e. it's not reproducible on command. From what I've checked it seems that
whatever goes on is not easily seen, so maybe some of the deeper info will
reveal the culprit.

Mario