Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] I need help! => Topic started by: 3dm.matthews on 2016-06-10, 19:37:15
-
I'm brand new to Corona, so far I am extremely thrilled with it. I am absolutely looking forward to using it professionally, as long as I can get this crashing issue figured out.
Machine basics: (maybe one or more of these are the issue)
- Windows 10 64-bit
- Max 2015
- Corona 1.4 trial
- Asus MB
- AMD 8350 8-core
- 16GB RAM
- SSD Drive
- Zotac GT640 2GB (cheap until upgrade)
I'm trying to render an exterior scene. That is only 2 smaller residential houses, with Hair/Fur modifier for grass. I was able to render using Corona Alpha-6, but needed some of the options with 1.4. Now it crashes 90% of the time. It will even reboot my machine! I'm guessing it's a hardware issue, or OS/Max issue. Any ideas, steps to try?
Thanks in advance!
-
Sounds like a minidump would be useful! (https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006-how-to-report-issues-)
At least, for those times when the whole machine doesn't reboot :)
Other thoughts - have you tried painting the whole scene with one simple CoronaMtl and rendering to see if a material is the cause? Or rendering sets of objects to see if a particular object is the cause? Any plugins in use for the scene? Any elements from another render engine left over, if it was a scene converted from another one? Can you share the scene itself (can do that privately if it can't be shared publicly - https://corona-renderer.com/upload/ )
Thanks!
Tom
EDIT - other thoughts: what SP of Max 2105, and do the crashes happen with other scenes or just this one?
-
Make sure that:
- Windows has installed all updates available
- Max has installed all service packs available
- your scene doesn't consume more RAM that your machine can offer
-
Mini-dump sending/sent
I tried an override material, still crashed.
I used to have displacement used in the scene, but I removed that completely (hoping that was the issue). Glad that it's still crashing, as once I figure it out, I can hopefully get the displacement back in.
Removed the grass (hair/fur) still crashed, but after a little bit longer. (RAM issue?)
I am running Max as administrator.
-
Just found the SSE41 Obsolete CPU test program on the forum, ran that and came up SUPPORTED. So I guess that rules out the CPU at least?
-
Tried applying a plain Corona material to every object directly, immediate crash.
Tried deleting the hair/fur modifier for grass (with above), immediate crash.
Tried new scene merging in all above, immediate crash.
Tried rendering with VFB turned off, immediate crash.
...I can't get it to render at all now...
---
I was hoping it was my weak GPU, but I read Corona is 100% CPU so I'm guessing not.
-
So, I just tried opening up the Studio template in Max. Switched to Corona, a ton of errors and an immediate crash.
Then, I reopened, applied a standard material to the whole scene. Corona processed the UDH, then crashed as soon as it tried to render.
It's not looking good :(
-
Well, it's either the mix of OS-Max-Corona, or it's my machine.
I just built a leaf under 100 poly's, and immediately crashed upon rendering :/
Is anyone else using Win10, Max2015, and Corona 1.4? Is it working?
-
Don't forget to attach minidumps - the more the merrier.
-
I use I7 with 32 Gb Ram, Windows 10, Max 2015 and corona 1.4, and everytime crashed with different scene, little, big, simple and hard, in different situation : real time preview, render, editor material
This is my test machine and all is updated.
With Max 2014 and corona 1.3 all work good and fine with hundreds scene.
We continue using corona 1.3 in our studio.
-
Also FX 8350 here.
If your machine reboots and / or crashes it is neither Max's, Windows', nor Corona's fault.
Run Prime95 (http://www.mersenne.org/download/)'s blend test for 4 minutes and see if your system says goodbye there.
I don't know when you bought that Mobo, but there are two thinks, that make my Mobo's VRM go to 100°C Corona and Prime95.
Fx 8350s are notorious for all sorts of Power related issues.
-
I use I7 with 32 Gb Ram, Windows 10, Max 2015 and corona 1.4, and everytime crashed with different scene, little, big, simple and hard, in different situation : real time preview, render, editor material
This is my test machine and all is updated.
With Max 2014 and corona 1.3 all work good and fine with hundreds scene.
We continue using corona 1.3 in our studio.
Thx Luke, I'll have to see if I can test that. I jumped straight from Alpha-6 to 1.4
-
Don't forget to attach minidumps - the more the merrier.
Is it helpful to post them here, or just keep sending them via ticket?
-
it is best to keep everything in single place - so post it directly here
-
Tried something new. Replaced every material with a standard material, set back to default scanline, started rendering. It went for about 5 minutes, 97% cpu, 19% RAM, no heat issues (Asus Monitor)... crashed...
Looked into Autodesk and Windows 10. Apparently, not one single Autodesk product is cleared with Windows 10... awesome :/
Short version of the MiniDump:
Exception Code 0xC0000005
Exception Info The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
-
I think that we are Intensive Corona Render users ; we render a year thousands of images from 10 to 100 hours each, scenes of hundreds of millions of polygons.
We have 16 computers I7 3930 K with 32 GB of RAM and 10 Dual Xeon super micro with 64 gb of ram which are replacing I7.
The combination 3dsmax 2014 Windows 7 and corona 1.3 never gave problems stability 'or crash.
We have a test comp where we install the new versions of the programs, and we noticed that we can not finish a render with max 2015 corona 1.4 and Windows 10.
I've already tested Gimps without problem
-
thx again Luke for the heads up.
Autodesk claims it's a Windows 10 .NET 4.6 issue causing the problem (installing Max after Win10 is installed) Looks like I'm going to have to try a bunch of different steps to debug it.
-
I have a similar issue with 1.4, minidump stating an exception c0000005 Access Violation (first/second chance not available) ntdll!NtGetContextThread+0x14
I'm still trying to figure out what causes it, but it is consistent when I'm saving the file after having used the Corona proxy converter on a file that originated in Vray with Forest Pack pro. If I don't save it will crash sooner or later.
Have any of you come any further?
-
I have a similar issue with 1.4, minidump stating an exception c0000005 Access Violation (first/second chance not available) ntdll!NtGetContextThread+0x14
I'm still trying to figure out what causes it, but it is consistent when I'm saving the file after having used the Corona proxy converter on a file that originated in Vray with Forest Pack pro. If I don't save it will crash sooner or later.
Have any of you come any further?
That's the exact error I get! But I am not using any proxies, or VRay.
Corona Support has rendered the file with no issues. I do not know if they are using a 'new' install of Win10 or an 'upgrade'.
Are you on a 'new' install of Win10 or an 'upgrade'? And, if an 'upgrade', did you install Max before you upgraded, or after?
-
Ops. Another case. Of Crashes. I am experiencing a lot of crashes on my last 2 projects too. I can´t say it´s corona´s fault or sundenly my machine has a problem. I will follow the sugestions here to test everything...
The config is :
I7 2700k - 32Gb - Windows 10 (too) - Corona 1.4 - Max 2016 Sp3
Sometimes the render goes ok, sometimes it start the parsing, and when building Acc structure, i got 30%-60% of the Ram used and Receive a windows Alert saying "Memory Low". Sometimes i don´t even receive the Alert, the screen Goes Black, and the machine Locks. And sometime, it Locks and... Boot itself... :(
I will try the Prime95 suggestion.
-
Windows 10 is an upgrade.
3DsMax is installed after 2/3 month about.
But until now i used "old" 1.3 corona scene to test, soon i test new scene, with new material, light, and so on...
-
I have a similar issue with 1.4, minidump stating an exception c0000005 Access Violation (first/second chance not available) ntdll!NtGetContextThread+0x14
I'm still trying to figure out what causes it, but it is consistent when I'm saving the file after having used the Corona proxy converter on a file that originated in Vray with Forest Pack pro. If I don't save it will crash sooner or later.
Have any of you come any further?
That's the exact error I get! But I am not using any proxies, or VRay.
Corona Support has rendered the file with no issues. I do not know if they are using a 'new' install of Win10 or an 'upgrade'.
Are you on a 'new' install of Win10 or an 'upgrade'? And, if an 'upgrade', did you install Max before you upgraded, or after?
I have such short memory for stuff like this, but I'm pretty sure it was a fresh install. There was some reason why I didn't qualify for that free Win 10 upgrade if I'm not entirely mistaken.
Interesting you have the exact same error but no Forest Pack and no Vray. I'm no programmer but I assume that means that error code is very general.
All I can say for sure is that the scene seems fine and that I can save it normally, if I convert it with the Vray converter it saves normally, but after I've run the proxy conversion part of the script Max crashes on save. Deadclown explained in another scene that if Max crashes it can't be the script, it has to be Corona. Again, not a programmer, but it certainly seems as if that script creates some sort of condition that offends Corona but it won't notice it until it is saving the file. Perhaps you create a similar condition somehow.
My machine does not crash, only Max.
-
Hi guys,
i try to start with empty scene, and all works good.
Very Simple, Simple and medium scene , and i've no problem.
1000 pass, denoise, real time render, normal shaders, standard camera.
In next days i open old ( 1.3 ) scene and retry..
-
I am starting to that my problem hasn´t relation to Corona 1.4... OR it´s some deadly combination from hell...
I got the same project i can´t render a single frame here without having memory problems and it renders totally ok on Rebus Farm... I´ve sent it to a friend and it rendered ok too...
I don´t know what to test more.... Tried the windows file testing...Files seems ok...
I even reinstalled Max 2016 and reinstaled it with Sp3 and Ext1... Same problem. Maybe my Windows10 is doomed. I will start to uninstall other programs and start a try and error test.. ;)
-
We have win 10 and 1in 7 machines at the office, corona 1.3 and 1.4 projects, no issue here on max 2016 last service pack.
-
I noticed I had some waiting Windows service updates that needed to be installed, will try the same thing shortly. Apparently one of them updates .NET something which I feel often seems to be the culprit.
EDIT: Happy to say that after the Windows 10 update I no longer seems to have the problem so make sure you are using the latest Windows update.
-
I noticed I had some waiting Windows service updates that needed to be installed, will try the same thing shortly. Apparently one of them updates .NET something which I feel often seems to be the culprit.
EDIT: Happy to say that after the Windows 10 update I no longer seems to have the problem so make sure you are using the latest Windows update.
I have my Win set to auto-update, which KB# is the one regarding .NET I'm not showing one.
Thanks for all the help and feedback guys, it's greatly appreciated!
EDIT: I just tried my scene again, crashed in under a minute. :(
-
May have figured out my problem!
It may be tied to my video card after all. After reading many internet posts regarding Win10 and Max, I switched away from DirectX and tried the Legacy OpenGL. It rendered for 5 min with no crashing. My CPU did warm up quite a bit, so I'm going to put some new heatsink compound on it (it's been a few years).
I'll keep you up-to-date on progress.
EDIT: Yup, just rendered a 4000x4000 image with displacement for 30 minutes. 100% of 16GB RAM used, still working. Guess it's a new video card time, and more RAM ;)
-
UPDATE:
Unfortunately all my errors are still occurring, just not as quick. However, I now have a new error that does specify a .NET issue.
My theory is Win10 and Max (installed onto 10, no upgraded)
-
The most recent update from Microsoft for Win10 had some effect on my crashing. Corona seems to now be the portion crashing/failing, as I'm no longer receiving a Max dump. I get two errors: one related to a missing drive which is weird, because I've never had any other drives, and the files I'm using are original creations with only items from my own computer; the second is a .NET error of some kind (which I'm not surprised about with Win10 4.6 .NET)
But what happens is, I get the errors (repeatedly, about 16 times) then that's all. I can still use Max, save my files etc. I can not however save the rendered image through the Corona VB, I can transfer it to the Max VB and save it from there.
Either way, I see this as progress.
-
Can you also post the pictures of the errors here? Maybe they will be familiar to some users?
-
Can you also post the pictures of the errors here? Maybe they will be familiar to some users?
I am working with Marcin with a ticket, but I'll post them here as well in case others have similar issues.
-
UPDATE: I'm getting my computer to freeze, just by having an active 3D app open! This may be a dang video card issue after all. I have two extra of the same video cards laying around, going to try swapping out, see if this one is shot. Then, it's waiting for a new video card to get shipped.