Large File Import GPU Memory Call Invalid Request from Orca #910

Open
opened 2026-04-05 16:34:53 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @VinceS2 on 2/2/2026

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.3.2-dev Build f27605e

Operating System (OS)

Windows

OS Version

Win 11 Pro, Build 26100.ge_release.240331-1435

Additional system information

MSI MEG Z890 ACE Socket 1851 mobo;
Intel Core Ultra 9 24 Core LGA 1851 285K 5.70GHz cpu;
256GB Crucial DDR5 RAM; Crucial T705 4TB NVMe PCIe 5.0 ssd + 2@ 4TB Samsung 990 Pro PCIe 4.0’s for overflow;
Quadro RTX A6000 48GB Video Card

The latest Nvidia RTX Enterprise driver, 591.59, is installed

Printer

Sovol SV08 Max

How to reproduce

(refer initiating / discovery report here

  1. Start Orca as Admin, with Lasso running to keep it on performance cores and high priority.
  2. New project, save it, import 1.4Gb .STP file generated with Solidworks 2026, of a 27m long mining machine we want to make a 3D demo prototype of. This file has been optimised by unticking materials etc and it opens perfectly in Autocad 2022, in about 10 mins. Smaller files (parts of the main file) open and slice fine.
  3. At around 30 hours get popup prompt for scale, select autoscale
  4. Get popup to say application to be closed due to call to unavailable RAM, with this explanation.

Actual results

Image

This is the Event Viewer log:
Event ID: 1000
Faulting application name: orca-slicer.exe, version: 1.0.0.0, time stamp: 0x697d00a1
Faulting module name: nvoglv64.dll, version: 32.0.15.9159, time stamp: 0x693a80fc
Exception code: 0xc0000409
Fault offset: 0x00000000010907dd
Faulting process id: 0xB774
Faulting application start time: 0x1DC929146FB41B0
Faulting application path: C:\Program Files\OrcaSlicer\orca-slicer.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_e9abceceea3b5a0e\nvoglv64.dll
Report Id: f5b6d540-2616-4496-b44a-d38f119de900
Faulting package full name:
Faulting package-relative application ID:

Expected results

The file should open, then I can scale it at 1.7% and see if it slices OK!

Here is a pic of the 3D print prep'd model that I am trying to import, mostly elements have been thickened to allow 3D printing - there may be some 'fails' where post-processing is needed. I need to have a crack at it to see what works and what doesn't, but cannot get the thing to load to even find out:

Image

Typically, 'dumb solids' have been extruded over details that can vanish under the now-external surface. Undoubtedly these unneeded details contribute to size of the model, but it is a big deal to get rid of them, although many have been deleted where practical. Just to do the thickening was a solid 10 day exercise, but trying to get it in to slice it has taken longer!

Project file & Debug log uploads

debug_Mon_Feb_02_08_38_59_49496.log.0.zip

The following project file is basically blank as it has never been able to be saved as importing the model crashes the app.

Project-01-Tracked_DMU_Machine.zip

Checklist of files to include

  • Log file
  • Project file

Anything else?

As a final check, I am in the process of running it in a non-elevated condition and will report back to see if any difference to elev condition. Given it has failed many times previously, I am not expecting a different outcome on this (now latest nightly bar one) version.

*Originally created by @VinceS2 on 2/2/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2-dev Build f27605e ### Operating System (OS) Windows ### OS Version Win 11 Pro, Build 26100.ge_release.240331-1435 ### Additional system information MSI MEG Z890 ACE Socket 1851 mobo; Intel Core Ultra 9 24 Core LGA 1851 285K 5.70GHz cpu; 256GB Crucial DDR5 RAM; Crucial T705 4TB NVMe PCIe 5.0 ssd + 2@ 4TB Samsung 990 Pro PCIe 4.0’s for overflow; Quadro RTX A6000 48GB Video Card The latest Nvidia RTX Enterprise driver, 591.59, is installed ### Printer Sovol SV08 Max ### How to reproduce (refer initiating / discovery report [here](https://github.com/OrcaSlicer/OrcaSlicer/discussions/12104) 1) Start Orca as Admin, with Lasso running to keep it on performance cores and high priority. 2) New project, save it, import 1.4Gb .STP file generated with Solidworks 2026, of a 27m long mining machine we want to make a 3D demo prototype of. This file has been optimised by unticking materials etc and it opens perfectly in Autocad 2022, in about 10 mins. Smaller files (parts of the main file) open and slice fine. 3) At around 30 hours get popup prompt for scale, select autoscale 4) Get popup to say application to be closed due to call to unavailable RAM, with [this ](https://nvidia.custhelp.com/app/answers/detail/a_id/3553)explanation. ### Actual results ![Image](https://github.com/user-attachments/assets/4d525897-b2bf-4b83-9ae3-d700ad44f310) This is the Event Viewer log: Event ID: 1000 Faulting application name: orca-slicer.exe, version: 1.0.0.0, time stamp: 0x697d00a1 Faulting module name: nvoglv64.dll, version: 32.0.15.9159, time stamp: 0x693a80fc Exception code: 0xc0000409 Fault offset: 0x00000000010907dd Faulting process id: 0xB774 Faulting application start time: 0x1DC929146FB41B0 Faulting application path: C:\Program Files\OrcaSlicer\orca-slicer.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_e9abceceea3b5a0e\nvoglv64.dll Report Id: f5b6d540-2616-4496-b44a-d38f119de900 Faulting package full name: Faulting package-relative application ID: ### Expected results The file should open, then I can scale it at 1.7% and see if it slices OK! Here is a pic of the 3D print prep'd model that I am trying to import, mostly elements have been thickened to allow 3D printing - there may be some 'fails' where post-processing is needed. I need to have a crack at it to see what works and what doesn't, but cannot get the thing to load to even find out: ![Image](https://github.com/user-attachments/assets/8fc628e1-368b-4ed7-8e3e-476a5979aa36) Typically, 'dumb solids' have been extruded over details that can vanish under the now-external surface. Undoubtedly these unneeded details contribute to size of the model, but it is a big deal to get rid of them, although many have been deleted where practical. Just to do the thickening was a solid 10 day exercise, but trying to get it in to slice it has taken longer! ### Project file & Debug log uploads [debug_Mon_Feb_02_08_38_59_49496.log.0.zip](https://github.com/user-attachments/files/24998495/debug_Mon_Feb_02_08_38_59_49496.log.0.zip) The following project file is basically blank as it has never been able to be saved as importing the model crashes the app. [Project-01-Tracked_DMU_Machine.zip](https://github.com/user-attachments/files/24996787/Project-01-Tracked_DMU_Machine.zip) ### Checklist of files to include - [x] Log file - [x] Project file ### Anything else? As a final check, I am in the process of running it in a non-elevated condition and will report back to see if any difference to elev condition. Given it has failed many times previously, I am not expecting a different outcome on this (now latest nightly bar one) version.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OrcaSlicer#910