C++ Runtime

[glorybound]

I was fussing over on the Autodesk Forum, about MAX, and I was told several causes of my MAX crashes are caused my V-Ray. I was given a suggestion to reinstall my C++ Runtime, which I did, and now it seems that my V-Ray is mucked up. My Progressive render will not go past pass 0, even after waiting for 45 minutes. It gets past the light cache, but the Rendering image goes nowhere. I tried bucket and the same thing, the buckets don't budge. Below is a list of the reasons they gave me why I am crashing 2-3X's a day. Notice, V-Ray is on there twice. Actually all the plug-ins I have and Windows itself I am being told is causes of my crashes.

• 3 issues which were fixed in 2018 but exist in 2017
• vrender2017
• QTgui-Itoo_4
• Coronalib_release
• ucrtbase (Shows errors with your visual C++ runtimes)
• graphicsdriver (Again, errors with Visual C++ runtimes)
• ntdll (Error with msvcr110... Visual C++ runtimes)
• vray2017
• railclonepro
• rayfx (This is an old school Blur raytracer... shouldn't be in use in any scene but must be. Materials from vraymaterials.de maybe?)

Any ideas? Do I need to reinstall V-Ray? MAX has been playing good since I reinstalled C++, so it sounds like if you want MAX not to crash, don't use plugins, or Windows, or NVIDIA

[glorybound]

Actually, MAX just crashed while rendering.

[glorybound]

Anybody? I have a deadline and this is a mess.

[glorybound]

Dam you Autograss! Oh, this update will make things so fast they said.