Crash on start

[stemper42]

Hi , i have a lot of crashes when i start madrix on my thinkpad t530.
I think problem in graphic card (nvs5400) driver.
What cdn you say about?

[Wissmann]

hi, maybe the optimus which comes with the nv5400 cause the issue.
If possible try to run without optimus.

[stemper42]

If i try to run madrix with intel graphic it shows 15-16 fps, crashes start after last madrix update.

[Wissmann]

yes the performance of the intel is maybe bad, but what about crashes during using the intel graphic?

[stemper42]

With intel all work's great, but with low fps:)

[Wissmann]

This is good and bad
.
This means MADRIX have issues with the nvidea and/or optimus driver.
.
Please be so kind and send us a MADRIX logfile to info[at]madrix[dot]com
.
For the moment i have unfortunately no better solution for you.
We already work on this issue but can not promise if there is a solution from our side or if this issue only could be solved by a new driver.
I guess you are running 3D previews?
If so you could try to run 2D Previews instead to improve the performance.

[stemper42]

unfortunately it shows 16 fps in 2D preview mode.

[Wissmann]

i am sorry to hear this, this sounds bad, we keep searching a solution for this issue.

[stemper42]

Сигнатура проблемы:
Имя события проблемы: APPCRASH
Имя приложения: MADRIX.exe
Версия приложения: 3.1.0.1
Отметка времени приложения: 5283c0d0
Имя модуля с ошибкой: nvoglv32.DLL
Версия модуля с ошибкой: 9.18.13.1269
Отметка времени модуля с ошибкой: 526ed945
Код исключения: c0000005
Смещение исключения: 00876de1
Версия ОС: 6.1.7601.2.1.0.256.48
Код языка: 1049
Дополнительные сведения 1: 0a9e
Дополнительные сведения 2: 0a9e372d3b4ad19135b953a78882e789
Дополнительные сведения 3: 0a9e
Дополнительные сведения 4: 0a9e372d3b4ad19135b953a78882e789



Sorry for Russian in log;)
As you see problem in nvoglv32.DLL and it means what Madrix try to write something in dedicated memory of graphic card, main strange thing is what it start crashes through time to time.

[Wissmann]

Hi stemper42,

thank you very much for this hint, also we have seen this and investigate already in this direction. So far we did not think we cause this error by programming so we currently think it is about the driver.

As far as we have a solution we will inform our customer on this website or release a new version.