Error Unhandled Exception

[glorybound]

Been rendering all afternoon and nothing changed, however, I crash with this error now.

[tsvetan.geshev]

Hello Bobby,

We will need the scene and some more information how to reproduce the crash:
- V-Ray version
- 3DS Max version
- if you have any additional plugins

[3dcrgr]

Hello Bobby,

We will need the scene and some more information how to reproduce the crash:
- V-Ray version
- 3DS Max version
- if you have any additional plugins

I have a similar issue. I think it is caused by some memory leak with the VraySpawner2016 service.
Windows 10 Pro
3Ds Max 2016
VRay 3.20.02 (I had crashes with 3.20.03 so I downgraded because of VIZPARK XMAP plugin)

While the service is running there is a SYSTEM process that load the system until VRay crashes and remain loaded even after the crash.
As soon as I restart the spawner this process it is gone.

[tsvetan.geshev]

This process is Windows system process, I'm not a developer, but i think it it not related to the crash.

Just send us sample scene and give us more information, how can we reproduce the crash - screenshots, workflow ..?

[Morne]

I have a similar issue. I think it is caused by some memory leak with the VraySpawner2016 service.
Windows 10 Pro

Just remember that that none of the Autodesk products are officially supported yet on Windows 10, but they are working on getting this done asap

[3dcrgr]

This process is Windows system process, I'm not a developer, but i think it it not related to the crash.

Just send us sample scene and give us more information, how can we reproduce the crash - screenshots, workflow ..?

To reproduce the crash you need Windows 10 Pro and 3Ds Max 2016 + V-Ray 3.20.02
Open 3Ds Max, load a teapot and a vray light and hit render.
It might take a long while with such a simple scene, or open anything you created and made sure did not had any problems before. Observe how "system" process loads more and more memory each render.
After sometime 3Ds Max will crash or there will be a Windows pop-up suggesting to shutdown 3Ds Max because there is not enough memory.
If Max crashes Watch how the memory is still loaded in the "system" process.
Go to the "vrayspawner2016" process and restart it.
You will see the "system" process is now releasing memory until it hits 12MB.

I search a little and it is probably causes by a Windows 10 "feature" called "compression store"

http://lifehacker.com/why-is-windows...ram-1725076206

I will try disabling it somehow and report back if there any improvements.
Right after that

[Svetlozar Draganov]

We've run a couple of tests on Windows 10 with 3DSMax 2016 and V-Ray 3.20.02 following your instructions but we couldn't see any memory faults.
Here is a short video from our tests: http://ftp.chaosgroup.com/support/sc...crash_test.avi

Would it be possible to capture how what's going on into your environment and send it for investigation?
If possible please send us the scene that reproduce this issue even if the scene is very simple one.

We are looking forward to hearing from you.

[3dcrgr]

I found what is the problem and it is not related to V-Ray but to the way Windows 10 manages RAM.

So here is the solution:

http://superuser.com/questions/95214...amounts-of-ram

Disable prefetcher in regedit key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager\Memory Management\PrefetchParameters you probably have Enable Prefetcher at a value of 2 or 3 so change it to 0

Next you need to disable Superfetch in services

Search for services.msc

Find superfetch click properties then set it to disabled and stop the service as well.

I do these steps and when I am gaming and normally using PC and the system process uses only 28k

All Windows 10 users are supposed to stumble upon this and it is a very spread issue (aka "feature") according to Google search and other forums.
Sorry for misleading you with thinking its V-Ray. It also happens when just running Chrome browser, but the spawner was the one who dominated.

[Morbid Angel]

I found what is the problem and it is not related to V-Ray but to the way Windows 10 manages RAM.

So here is the solution:



All Windows 10 users are supposed to stumble upon this and it is a very spread issue (aka "feature") according to Google search and other forums.
Sorry for misleading you with thinking its V-Ray. It also happens when just running Chrome browser, but the spawner was the one who dominated.

Epic fail. Especially after microsoft is maliciously trying to push windows10 to every one without even their permission.

[Svetlozar Draganov]

I found what is the problem and it is not related to V-Ray but to the way Windows 10 manages RAM.

So here is the solution:



All Windows 10 users are supposed to stumble upon this and it is a very spread issue (aka "feature") according to Google search and other forums.
Sorry for misleading you with thinking its V-Ray. It also happens when just running Chrome browser, but the spawner was the one who dominated.

Glad to hear you figured it out and thank you very much for sharing the solution.