simtk.org

I was running into multiple issues with getting the simulations to run on my system after updating to the newest build (1703 via the Creator's Update). The simulation would get stuck at 0% and not start. I tried the last three builds of SimVascular mixed with the last 2 versions of SvSolver (all combinations) without any luck. I tried with leaving the solver paths blank and filled in, as well as changing everything within the simulation (including full reinstalls and deleting all pertaining files). The simulation was simple enough to take a few minutes, but would not run. A classmate ran the exact same files (copied over) without issue (not yet on Windows 1703). I rolled back Windows to before the update, and everything ran without a hitch, pretty much confirming the update breaks the simulation.

In the error file when closing, I would get (at the bottom of the report):
Image PC Routine Line Source
svsolver-nompi-bi 00007FF64BADC17C Unknown Unknown Unknown
svsolver-nompi-bi 00007FF64B98783B Unknown Unknown Unknown
svsolver-nompi-bi 00007FF64BBBA06A Unknown Unknown Unknown
svsolver-nompi-bi 00007FF64C010C43 Unknown Unknown Unknown
KERNEL32.DLL 00007FF9934E2774 Unknown Unknown Unknown
ntdll.dll 00007FF9935F0D61 Unknown Unknown Unknown
forrtl: severe (47): write to READONLY file, unit 15, file


I can do more runtesting if needed, and have copies/screenshots of most of the error reports, etc.

Thanks!

Did you reinstall svSolver after Windows update? You are using Windows 10? SimVascular installer was created in one of our Windows machine. Your update may cause some significant changes in the system.

SimVascular Development Team

I tried to run it after the update (without any changes to SimVascular or the solver), but without luck. After that, I fully uninstalled and removed all files before reinstalling. That didn't work, so I tried full uninstalls and file deletes with reinstalls of each combination without luck.

I am currently on the Creator's update to Windows 10 (the latest update that went live ~2 weeks ago).

As soon as I rolled back to 1702, SimVascular ran without issue, which pretty much points to it being caused by the Windows update.

Hello !

I got the similar issue on my Windows 10.
But I could run the solver by changing the property of SV Icon.
Please refer the attached scene.