3ds Max 2017 crashes while exporting X files (Windows 10)

[alpha2echo]

Hi,

I have istalled 3DS Max version 2017 after having used 2015 without any problems. I need the objects exported as *.X files.
So I installed the latest P3D SDK to use the latest gamepack in 3DS Max.

Here's my issue:
I cannot export my existing project to x-files (which has worked well in V 2015), althought the setup seems to work generally as long as I use simple materials on simple objects out of a newly created scene.
The export window for selecting conditions appears as usual, but during the export process a warning window pops up to tell me that an error has occoured- and 3DS Max finally crashes.

Shortly, I have tested the scene on a collegue's system which is comparable to mine. He also recently installed 3DS Max 2017 and the same gamepack (4.5.11.29713). There the exporting process works fine. So finally, I assume it must have something to do with my system or 3DS Max setup, not necessarily the scene itself.

I have istalled the three servicepacks for 3ds, but anyway- The crashing problem remained.
Today I installed the SDK Hotfix (4.5.12.30293): still the same problem.

The event display said the following:

Name der fehlerhaften Anwendung: 3dsmax.exe, Version: 19.3.533.0, Zeitstempel: 0x57cf64b2
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.17134.677, Zeitstempel: 0x9f346d3f
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000000000006e14e
ID des fehlerhaften Prozesses: 0x10284
Startzeit der fehlerhaften Anwendung: 0x01d5193d1899c7bb
Pfad der fehlerhaften Anwendung: C:\Program Files\Autodesk\3ds Max 2017\3dsmax.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll
Berichtskennung: db9f785a-7fb5-4eea-8fcb-96fde2a40889
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

I asked google and found that a corrupted c++ maybe the reason for that error message so I repaired C++. And still: the same problem.

I'm getting desperate because I have nearly finished the project and now, so close to the end, such a thing....

Any help highly appreciated!!!

[alpha2echo]

Any ideas?

[Clifton Crane]

Hi alpha2echo,

Could there be a system memory limitation that you are hitting during export? Could you try doing an "Export Selected" with half of the scene selected to see if it successfully exports? You could also monitor memory usage using Windows Task Manager.

Thanks.

[alpha2echo]

Hi Clifton,

thanks for your reply!
Indeed, the last several times I have tried to export out of that scene I've chosen just one single polygon.
But I will try again while monitoring the memory usage and then let you know what happens there.

Best,

Arne