For some reason, blender seems to crash extremely often as soon as I render (occurring when rendering directly after making some change). It does not happen 100% of the time, but when it does, the program instantly closes without any hanging.
Additionally, the crash log itself seems to reference whatever thing I just changed. I am not good at reading these logs, but an older version of the same crash log referenced subdivision levels, right after changing the subdivision of an object and then crashing on render. The crash log below seems to mention ColorRamps, which I did modify in a material before getting the crash.
Welcome ,
i don’t think that the color ramp change leads to a crash… it may be more useful to investigate the subdiv levels of your models (too high??) or giving some more information about you actual scene…
(And you should be able to post images after successfully completing the tutorial… see discobot in your messages or spending some more time here… it’s some kind of spam prevention.)
Thank you!
I’m not entirely sure it’d be subdiv levels- It’s was only set to 2 when I got those crashes, and is currently completely disabled, yet rendering still crashes pretty often. The grand total polygon count of the entire scene is just 4.2k faces/4.6k verts, and the crashes were essentially occurring from the moment I started working in the file.
Okay… but again: it would be more helpfull if you give some more info about the scene maybe also about your setup (OS, RAM, GPU)… there was someone complaing about blender 2.8/9 not running on Win7… (so there will be no guessing )
Right, here’s some more info:
Essentially the scene is just a few textured planes/blocks with an orthographic camera from above, rendering 128x128 images. There is a compositor setup to decrease the color depth of the final render. I am using it to render out texture sheets in a specific style for use in another game engine. I am using Blender 3.1.2 for this.
And some system info:
OS: Microsoft Windows 10 Home
GPU: NVIDIA GeForce RTX 2060 SUPER
CPU: Intel Core i7-10700KF
RAM: 32GB total
I hope this is enough info to help, and that I did not leave out anything you were looking for.
Okay no you are given us a riddle … why does it crash ?? Shouldn’t be a problem at all … (The only thing i can think of is: Is this already those new kind of different core CPU which isn’t supported in win10 ???) Even some depth fighting would crash blender…
According to your crash logs, the problem is occurring at blender::deg::DepsgraphRelationBuilder::build_object_data_geometry. In other words, as Blender is building the dependency graph, it’s failing to build the geometry of an object data correctly. The exact error at this point is EXCEPTION_ACCESS_VIOLATION. It seems like this EXCEPTION_ACCESS_VIOLATION is related to a missing .DLL file… so I’m thinking you should try re-installing Blender and get a fresh set of DLL files.
Alright yeah, the issue seems to no longer be present after running the repair option on the blender installer. In hindsight I probably should have figured out that my install was probably messed up, but thanks either way!
Is it a bad idea to update my own solved thread if it turns out the solution wasn’t actually found…?
because while it seemed the issue had disappeared, it’s now even worse than ever. The same things from before are seeming to crash Blender, but now it’s extended to more. If I had ever entered the material preview mode AT ALL during that session, rendering will crash the program. Sometimes it just happens randomly when I render. It’s VERY consistent, except for when it decides not to be.
Hmm… you’re still getting an EXCEPTION_ACCESS_VIOLATION, which means you’re still having DLL problems. This might sounds extreme, but have you tried re-installing your OS?
No I haven’t, and that does sound a little extreme. Really i’d like to try exhausting other options before resorting to that.
To me it seems unlikely it’d be OS related, since I’ve never had this issue before, and it seems to only be happening within this single file. I’ve never experienced blender crashes like this on this computer, until I started working on this specific project.
One more thing I’d like to mention, the crash on render after entering material preview actually stopped when I hid a bunch of area lights in a hidden collection, when they weren’t being used in the current render. Those crashes don’t even leave a crash log, so they may be unrelated, yet it’s still weird.
This is just plain and flat out wrong, EXCEPTION_ACCESS_VIOLATION does not mean “dll problems” it means it tried to read or write or execute from memory it should not have been touching. Many bugs inside blender itself will also give this error. Judging from the stack trace it seems to originate out of the despgraph code (which uses no external libraries)
If this problem can be reproduced on the latest 3.3 daily build please report it on the bug tracker. You can use Help->Report a bug from within blender to prefill the form with the important bits required. If you could attach a .blend showing the problem that would be ideal.
,
in your messages or spending some more time here… it’s some kind of spam prevention.)
)
… why does it crash ?? Shouldn’t be a problem at all 
… (The only thing i can think of is: Is this already those new kind of different core CPU which isn’t supported in win10 ???) Even some depth fighting would crash blender…