Halt! Exception time! suspiciously often

[iLEZ]

I have a machine with 48 gb memory. My Corona .02 crashes with the "Bad allocation" and "Halt! Exception time!" a little too often.
It seems like I hit a total memory roof around 31 Gb and then the render crashes. 3ds max uses only about 22 gb when I get back to see the crash. Maybe it peaks before that? I haven't been able to babysit the Task Manager to see if it fills my entire memory.
The render is 6667px * 4000px. I know I have rendered a LOT larger renders on That Other Renderer. Is Corona more memory intensive? The scene is a simple gaming keyboard with very few polygons, around 300k before subdivision. I do use the OpenSubdiv modifier on some things though, can that be a problem? I have noticed that OpenSubdiv lags incredibly in 3ds max 2015.
Incredibly compressed pic attached.

[maru]

Hi, are you using displacement in this scene?

[iLEZ]

Hi, are you using displacement in this scene?

Yes! The bumps on the handrest!

[maru]

So this is probably the cause of memory problems. You are rendering in a huge resolution. What are your displacement settings? Try lowering them (higher screen size or at least less max subdivs per poly). See: https://coronarenderer.freshdesk.com/support/solutions/articles/5000513437

[iLEZ]

So this is probably the cause of memory problems. You are rendering in a huge resolution. What are your displacement settings? Try lowering them (higher screen size or at least less max subdivs per poly). See: https://coronarenderer.freshdesk.com/support/solutions/articles/5000513437

Thanks for the quick reply! You guys are really helpful and patient. I sure don't regret switching to Corona this early. =)

Displacement is:
Max subdivs per poly: 100
Screen size (px): 1,0 (this is probably the culprit then?)

My filter settings are the default.

[maru]

Displacement is:
Max subdivs per poly: 100
Screen size (px): 1,0 (this is probably the culprit then?)

I would suggest increasing screen size to 2. Just let's hope it won't look much worse. If so, then I would try slightly decreasing it to the point where memory errors start. And you can also try decreasing max subdiv per poly (especially if the mesh is dense).

[iLEZ]

Displacement is:
Max subdivs per poly: 100
Screen size (px): 1,0 (this is probably the culprit then?)

I would suggest increasing screen size to 2. Just let's hope it won't look much worse. If so, then I would try slightly decreasing it to the point where memory errors start. And you can also try decreasing max subdiv per poly (especially if the mesh is dense).

Thanks, I'll do that! I'll get back here if it doesn't solve the problem.