Diadem crash error

[Lukas_Doubek]

Hello,

i got massive script in diadem which i cant send. when i run the script, it proceeds to the end based on logs i got and when its done, error message displays with OK only button, when i close it, diadem closes as well. when i open diadem again and go to script, in logfile i got following message with no info about line of file on which it crashed, just some non informative error for me.

can you point me please where to search what can cause this?

1 22.05.2025 13:47:04 Error:
Error while executing "("C:\LOCAL\CrashEvalTool\CrashEvalTool.VBS")" command
Error type: ACCESS VIOLATION
Error address: 00005351
Module name:vbscript.dll
2 22.05.2025 13:47:04 Error:
Error while executing "("C:\LOCAL\CrashEvalTool\CrashEvalTool.VBS")" command
Error type: ACCESS VIOLATION
Error address: 00005351
Module name:vbscript.dll

AMD EPYC 7543 32-Core Processor

64bit Windows 10 Enterprise 22H2

Diadem 2020

[rebecca65bell · Accepted solution]

---

@Lukas_Doubek cattranslatorapp wrote:

Hello,

i got massive script in diadem which i cant send. when i run the script, it proceeds to the end based on logs i got and when its done, error message displays with OK only button, when i close it, diadem closes as well. when i open diadem again and go to script, in logfile i got following message with no info about line of file on which it crashed, just some non informative error for me.

can you point me please where to search what can cause this?

1 22.05.2025 13:47:04 Error:
Error while executing "("C:\LOCAL\CrashEvalTool\CrashEvalTool.VBS")" command
Error type: ACCESS VIOLATION
Error address: 00005351
Module name:vbscript.dll
2 22.05.2025 13:47:04 Error:
Error while executing "("C:\LOCAL\CrashEvalTool\CrashEvalTool.VBS")" command
Error type: ACCESS VIOLATION
Error address: 00005351
Module name:vbscript.dll

AMD EPYC 7543 32-Core Processor

64bit Windows 10 Enterprise 22H2

Diadem 2020

---

That "ACCESS VIOLATION" error from vbscript.dll means your DIAdem script, CrashEvalTool.VBS, tried to access restricted memory, likely due to faulty interaction with an external object, file I/O, or possibly corrupted data. Since you can't send the script, your best bet is to debug it systematically: add MsgBox or LogFileWrite statements to pinpoint the last successful execution point, then use DIAdem's built-in debugger to step through the code line by line, especially around any interactions with external COM objects, files, or large data operations. If it's not a script error, consider repairing your DIAdem installation or checking for system file corruption with sfc /scannow.

[Lukas_Doubek]

ok, i got and error in the script, thats why it was crashing. but in that situation, diadem didnt returned me classic error pointing on file and line which causes it and triggered different error about ACCESS VIOLATION.

i had to do exactlu what you suggested with logfilewrite and fixed the bug, but this happens to me sometimes that it just crash and dont tell me where it crashed, so i decided to write it here to have more info about it.

so basically when it will happen again, i will have to debug it like i did every time.

thanks 

[albertoj200]

Totally get what you mean. I’ve run into the same issue before where DIAdem crashes without any clear trace. Logging definitely helps, but it would be great if it threw a more specific error instead of just ACCESS VIOLATION. Hopefully future updates improve that part.

[Lukas_Doubek]

yes they should program the exception to tell just on which line and file it crashed. just this and we are "friends" 🙂

[Lukas_Doubek]

today is another one with new error address, diadem just crashed with the session with data i got. start new diadem, prepare everything again like it was before crash. i mean data. i got workspaces defined. Its just so annoying that i take time to write it here, even i know it will not help me.

1 05.06.2025 9:40:19 Error:
Error while executing "("C:\LOCAL\CrashEvalTool\app\Jonas_Base.vbs")" command
Error type: UNKNOWN
Error address: 0005F1DC
Module name:KERNELBASE.dll
2 05.06.2025 9:40:19 Error:
Error in <CrashEvalTool.VBS> (Line: 11, Column: 1):
The VBS script has been aborted.
3 05.06.2025 9:40:19 Error:
Error in <CrashEvalTool.VBS> (Line: 11, Column: 1):
The VBS script has been aborted.

[Lukas_Doubek]

another error and diadem crashes...

[Lukas_Doubek]

i found out that it crashed only because variable was not defined. i checked diff of my changes and checked the new variables. but diadem kept crashing and didnt write nothing in logfile, just the same errors like on top. but please do something with this dll, this is really bad if it crashes like this because some variable is not defined. it should tell me that variable is not defined, but not crash like this, its hilarious.

[Lukas_Doubek]

i think its because i got lot of scripts included in my app, i believe on single file it wont crash like this. but including is ment to be used i think..