ZBrushCentral

Unable to read virtual memory file

Hi

Every time I try and load my project I get “unable to read virtual memory file” then a bunch of other errors and then Zbrush crashes. All my quick saves and two alternative saves do the same for this project other projects load fine and this current problematic one has had no problems yesterday.

Any Thing I can do to get back my work?
File is around 6 GB

Pc Specs:

Gpu: RTX 2080 Ti
Cpu: i9-9900K
Ram: 64 GB
SSD: Samsung 970 EVO Plus 1 TB With over 400 GB free

Um, I’d view that as a quite large file. Are you saving with the UNDO History? Have you updated to the latest release?

I have files much bigger up to 20 GB no problem with those. I save without Undo History ZTL. I have ZBrush 2021.1.2 so I believe so.

I was working on it yesterday just fine everything saved normally and then today just won’t open.

I have some back ups from two days ago they work fine. Everything from yesterday tho is broken.

First time opening it today after all the other error messages it said something about having a problem with one ztool that I haven’t touched in weeks and that it will replace it with PolyMesh3D or something but then zbrush will just crash.

Hello @Helmut_Rabe

This would suggest one of your tools has become corrupt or problematic in some fashion. Without further information, I could only speculate about the possible causes. However, attempting to save a file that is too large for your system is one possible cause for this.

If the problem file is a ZPR (Project) file, you can attempt to extract the tools from it via the Tool> “Load Tools from Project” function. It is unlikely that you will be able to extract the corrupt tool from the file. If you are able to extract the tools, immediately save them out as individual ZTLs (tool> Save as).


This is just general information. I don’t have enough information to do anything other than speculate.

A 6gb file is going to be too large to reliably work with on some systems–I personally wouldn’t choose to let a file get this large on a system that only met the recommended system specs of 16gb of RAM. A 20GB file is large by any standard. I’m only speculating, but this is likely to be problematic for many systems.

I’m not saying this is the cause of your issue, however. Just a reminder that file discipline should be practiced regardless of hardware spec. You don’t want to work with a file that is larger than it has to be. The closer you get to your practical system limits, the greater the chances for instability and corruption. Eventually a file will fail to save altogether, or may refuse to open even if you get it saved.


It could also be an issue with the geometry of a subtool, or some other aspect that has rendered it problematic. It could be an issue with your installation-installations that have become damaged or improperly modified can result in file corruption.

When a file gets really large, it takes a long time to save. If auto-saving is enabled, this may increase the chance of trying to perform an operation at the same time a lengthy auto-save kicks in which could possibly result in a corrupted save. I would personally disable auto save if working on files of this size, and rely solely on manual saving.


Excellent! However also be sure to make a habit of aggressive manual saving under different file names, rather than saving to the same file.


If you find you can reproduce the issue that is causing the tool to become problematic, or if you’d like us to take a look at your installation, please contact Pixologic Support.

Good luck! :slightly_smiling_face:

Thank you for the advice.

I was told to run the Zbrush Diagnostic Utility. It has been running for the last 8 hours and it’s still busy is that normal? how long will it take?

That will depend upon several factors.
Errors will be found.

So I just let it run for the next two days and hopefully it will do something?

@Helmut_Rabe

No, this is not normal. It should not take that long to complete. There may be an issue with how it is installed, or the OS environment it has been installed to. Support will likely go over this with you.

Thanks!

2 Likes