Author Topic: Windows 10, Max 2015, Corona 1.4 (trial) Crashing  (Read 18116 times)

2016-06-10, 19:37:15

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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!

2016-06-10, 19:45:10
Reply #1

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5556
    • View Profile
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?
Tom Grimes | chaos-corona.com
Product Manager | contact us

2016-06-10, 19:45:46
Reply #2

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8898
  • Let's move this topic, shall we?
    • View Profile
    • My Models
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
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2016-06-10, 20:07:44
Reply #3

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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.

2016-06-10, 21:55:00
Reply #4

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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?

2016-06-10, 21:58:50
Reply #5

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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.

2016-06-11, 03:44:00
Reply #6

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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 :(

2016-06-11, 06:40:08
Reply #7

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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?

2016-06-11, 09:28:51
Reply #8

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8898
  • Let's move this topic, shall we?
    • View Profile
    • My Models
Don't forget to attach minidumps - the more the merrier.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2016-06-11, 09:58:28
Reply #9

LUKEC3D

  • Active Users
  • **
  • Posts: 20
    • View Profile
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.

2016-06-11, 11:33:32
Reply #10

FrostKiwi

  • Active Users
  • **
  • Posts: 686
    • View Profile
    • YouTube
Also FX 8350 here.

If your machine reboots and / or crashes it is neither Max's, Windows', nor Corona's fault.
Run Prime95'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'm 🐥 not 🥝, pls don't eat me ( ;  ;   )

2016-06-11, 14:24:02
Reply #11

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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

2016-06-11, 14:27:49
Reply #12

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
Don't forget to attach minidumps - the more the merrier.

Is it helpful to post them here, or just keep sending them via ticket?

2016-06-11, 14:31:02
Reply #13

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
it is best to keep everything in single place - so post it directly here
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2016-06-11, 15:46:52
Reply #14

3dm.matthews

  • Active Users
  • **
  • Posts: 27
    • View Profile
    • Behance Profile
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:

Code: [Select]
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.