First, please consider making the data values in the bottom-screen display have a fixed number of places so the display does not jitter back and forth a character or two as the simulation runs.
My project runs successfully on 24.0.12 and is clean enough to run with the Normal Solver.
The same project always causes 24.1.9 to lockup at some random time usually between 20ms to 80ms into the sim.
For example:
LTspice 24.1.9 for Windows
Start Time: Mon Jun 9 18:30:10 2025
Options: gminsteps=0 noopiter NoMarch PlotWinSize=0 trtol=7 abstol=1e-7 vntol=1e-3 chgtol=1e-8 debugtran
solver = Normal
Maximum thread count: 16
tnom = 27
temp = 25
method = modified trap
abstol = 1e-07
chgtol = 1e-08
trtol = 7
volttol = 0.001
noOpIter = true
Direct Newton iteration for .op point skipped.
Gmin stepping method for .op point skipped.
Starting source stepping with srcstepmethod=0
Source Step = 3.0303%
Source Step = 33.3333%
Source Step = 63.6364%
Source Step = 93.9394%Source stepping succeeded in finding the operating point.
The first Warning: Simulation tolerance relaxed to achieve convergence from 7.3743666701653693e-02 to 7.3743666701653790e-02 seconds.
The 229,640th Warning: Simulation tolerance relaxed to achieve convergence from 7.3743666723961862e-02 to 7.3743666723961959e-02 seconds.
The entire time that the 229,640 warnings were being written to the log, the "Simulation Speed" display was absent from the screen.
The display stopped at "Simulation Time" 73.7437ms.
While the 229,640 warnings were being written to the log, only 22.308266ps of simulation time elapsed.
22ps was not enough elapsed time to cause the "Simulation Time" 73.7437ms data to advance 100ns to 73.7438ms.
Therefore I cannot determine if the entire bottom-screen display was locked up, or just had no new data to display.
The "Simulation Speed" display was not locked up, it was absent from the display.
I'm sorry but I cannot share my project. It is proprietary.
I will try my project on other versions with all settings unchanged from above.
LTspice 24.0.12 for Windows
Source stepping succeeded in finding the operating point.
Total elapsed time: 961.454 seconds.
LTspice 24.1.1 for Windows
Won't run. Aborts due to syntax errors.
LTspice 24.1.2 for Windows
Source stepping succeeded in finding the operating point.
Total elapsed time: 2469.579 seconds.
LTspice 24.1.4 for Windows
Source stepping succeeded in finding the operating point.
Total elapsed time: 1959.656 seconds.
LTspice 24.1.5 for Windows
Source stepping succeeded in finding the operating point.
Total elapsed time: 1822.458 seconds.
LTspice 24.1.6 for Windows
Source stepping succeeded in finding the operating point.
Total elapsed time: 917.384 seconds.
LTspice 24.1.7 for Windows
Source stepping succeeded in finding the operating point.
Warning: Simulation tolerance relaxed to achieve convergence from 6.7770050541269333e-02 to 6.7770050541269430e-02 seconds.
...
Warning: Simulation tolerance relaxed to achieve convergence from 6.7770050541874641e-02 to 6.7770050541874641e-02 seconds.
Simulation stopped by user.
Total elapsed time: 415.293 seconds.
LTspice 24.1.8 for Windows
Source stepping succeeded in finding the operating point.
Warning: Simulation tolerance relaxed to achieve convergence from 6.7252842460874707e-02 to 6.7252842460874804e-02 seconds.
...
Warning: Simulation tolerance relaxed to achieve convergence from 6.7252842461048887e-02 to 6.7252842461048887e-02 seconds.
Simulation stopped by user.
Total elapsed time: 316.645 seconds.
LTspice 24.1.9 for Windows
Source stepping succeeded in finding the operating point.
Warning: Simulation tolerance relaxed to achieve convergence from 6.7252842460874707e-02 to 6.7252842460874804e-02 seconds.
...
Warning: Simulation tolerance relaxed to achieve convergence from 6.7252842460986326e-02 to 6.7252842460986326e-02 seconds.
Simulation stopped by user.
Total elapsed time: 298.007 seconds.
I see now that the issue appeared with the release of 24.1.7.
In each case 24.1.7, 24.1.8 and 24.1.9, the "Simulation Speed" display disappears when the lockup starts.
I have closely analyzed the goings-on during the 60ms to 80ms period using 24.0.12 and nothing interesting is happening.
At 67ms power supplies are coming up to regulation and that's it. No other operation.
At around 91ms, power is good, the 2.5V logic is released and the device goes into full operation.
24.1.9 does not make it that far into the simulation.
All for now
