search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.22k stars 2.08k forks source link

Cura Fails to slice consistently with any model #15378

Open Symtrips opened 1 year ago

Symtrips commented 1 year ago

Application Version

5.2.1

Platform

Windows 11

Printer

FLSun V400

Reproduction steps

Load any file (in version 5.2.1, 5.3.0, 5.3.1) Select any profile Click Slice

Actual results

Hangs - then Fails Unknown Error

Occurs 80+% of time, sometimes changing a speed or layer setting will slice successfully once, but not twice.

As noted this occurs in all three installed versions of Cura (freshly installed 5.3.1). The new install sliced once then fails repeatedly. Have tried multiple models with multiple profiles. Problem started after turning computer off and then back on the next morning. No changes have been made. PC runs cleanly through memtest, CPU and GPU stress tests.

Expected results

The model should slice as it has been previously.

Checklist of files to include

Additional information & file uploads

cura.log FV_3DBenchy15.zip

GregValiant commented 1 year ago

Thanks for the report and the files. There a couple of these lines in your log. "Backend exited abnormally with return code 3221225477!" From what I've read that is a memory fault. I'm running Win11 and I can't reproduce that as I never get that fault but some systems do. It may be the way that Cura is discussing things with your particular hardware. What processor do you have, what video system, and how many monitors are you using? Somebody from the Cura team will take a look.

Symtrips commented 1 year ago

Not sure what to say, just finished a 4 hour memtest86 run with zero faults. Same hardware I have been using for a few months without issue, turned on this morning and complete blep with any Cura version. Thinking maybe a corrupt runtime, but no clue where to start with that.

I9-13900KS Strix Z790-A 32gb DDR 7200 Strix RTX 4080 OC Single monitor

*Edit: After resetting bios to defaults Cura functions. Still functions with XMP profile enabled. Functions with AI Overclocking enabled. Fails with custom overclocking configuration. Going to dig through any ancillary bios settings to see if I can narrow down the culprit. Still feel there is an issue in Cura as no other (much more memory intensive) programs have issue. Cinebench 30min no sweat, Memtest86 no errors, 3D Mark Time Spy extreme torture test flying colors.