Fatal Internal Error 0x6D0FD433 : "undo.cpp", line 5038

[popo971]

Hello everyone,

I am using LabVIEW 2023 Q3 . I get posted error.
Fatal Internal Error 0x6D0FD433 : "undo.cpp", line 5038

Please help me how to resolve this error.

Any insights or suggestions would be greatly appreciated. Thank you!

[billko]

I think I read somewhere that you should set the LabVIEW undo limit to 15 or so because of crashes like this.  Unfortunately, I think you're going to have to let LabVIEW crash and lose your work this time around.

[Kyle97330]

How many times has this happened?

If this was just one time?  Sorry, but you just have to recreate any lost work, if it wasn't caught by the auto-save.

Does this happen often but not in a way that's something you can re-create on demand?  If so, it could be that there's a VI or a NI file that's corrupt that you're working with.  You could try a repair or reinstall of LabVIEW.

Or does it happen every time you do a specific sequence of actions on a file?  Post the file and a set of instructions to replicate the problem so we can try it out and see if it is repeatable.

[Darren]

Add the following to your LabVIEW.ini file:

debugging=True

LVdebugKeys=True

DPrintfLogging=True

The next time the crash happens, check one of these log files:

%temp%\LabVIEW_[bitness]_[version]_[user]_cur.txt

%temp%\LabVIEW_[bitness]_[version]_[user]_log.txt

Hopefully the last entry in the log will point to whatever VI is causing the crash. You might have a VI with some insane objects or other corruptions that you'll need to address... and if the VI isn't loadable, you may need to restore it from a backup or recreate it.

> I think I read somewhere that you should set the LabVIEW undo limit to 15 or so because of crashes like this.

I don't think the undo limit has anything to do with this crash, and I don't recommend changing it. You shouldn't have any problems with the default value of '99'.

[billko]

Looks like what I was thinking of got fixed in LV2017.  Here is the topic I was thinking of.  And of course, I was the one who put suggested it was the undo level (it was never really revealed what the root cause was), which is why I remember reading it.

[popo971]

Hello billko,

Understood. Thank you for your response!

[popo971]

Hello Kyle97330,

This error has only happened once so far. If it occurs again, I will try the approach you suggested and share the details with everyone. Thank you for your reply!

[popo971]

Hello Darren,

I will try adding the settings you mentioned, and I will keep the undo limit at its default. If this error occurs again, I will share the information with everyone. Thank you for your reply!