The amount of physical RAM is not the issue.
It is the memory allocation, as managed by the OS for whatever programs are running (in the background, etc.).
Any modern PC with about 4G+ would normally be ok.
Potentially the paging file size may need increasing, as well as setting more CPU and RAM resources.
You can potentially also prioritize the ColourSpace Application via Task Manager.
As well as stopping other programs opening on start-up, etc.

But VMs tend to provide much smaller allocations, and tend to run way slower.

Steve

Update: I was able to get my M1 Mac to generate 256^3 LUTs using VMware by increasing the VM's allocated resources.

Steve

I don't really understand the suggestion to test this on a madVR HTPC when an Envy is in use.
In my Parallels VM I've now allocated 6 CPU cores and 24 GB of RAM. Generating the 256³ LUT now takes 45 minutes just to crash at the very end, and the upload to the Envy still doesn't work.

I also don't see any real benefit in the generation of the 256^3 LUT. It would be much more sensible—especially for users who aren't running monster-spec systems or a VM—to be able to choose directly in the UI whether to upload a 65³ or a 256³ LUT. Having to rely on environment variables for this is anything but user-friendly.

And to be clear: this isn't user error. The bottleneck here is the extremely high hardware demand on the ColourSpace side for such high LUT sizes.

The suggestion to test madVTR HTPC (actually just madTPG, as that is all that's needed to test LUT Upload) is because we know that works, so would help isolate any issue with Envy.

But, up to you if you don't want to bother.

However, with your PC (VM) not being able to generate 256^3 LUTs it is not a relevant test anyway, as you would not be able to upload the LUT due to the PC (VM) resources issues you have.

As said above, setting decent VM resource allocations On my M1 Mac using VMware enables 256^3 LUT generation.

Steve

Another update.
I can generate 256^3 LUTs on my Surface Laptop 3.
And that is not a monster spec PC at all.
And the LUT generation takes approx. 10 minutes.

Mind you, it's borderline as sometimes it will crash so I guess it does depend on any other BG processes running.
(Edit: yes, with decent Paging File size set, and no other programs running, 256^3 LUT generation works every time.)

The M1 Mac doesn't crash.

Steve

Christian will test that as well I send him my profile and maybe we can see some others as well.

I won't buy a Windows laptop to use 256^3 LUT size which has no visual benefits.

As my M1 Mac now has no issues maybe you just need to talk to Parallels support to get better resource settings suggestions?

But, if you are happy with 65^3 LUTs just stick with that.

The madVR upload is an Env. Variable as it is a set once option. If your PC can't do 256^3 LUTs you would never change it from 65, unless the PC hardware was changed.

Steve

Fabio profile crashed CS on my 16Gb RAM laptop. It was on battery, only app running.
Although 16gb should be more than enough I guess.

As said, the physical RAM is not the issue.
I've added more info HERE.

Steve