Last month, I happened to got free BMW E-Sys 3.27.1 link from a car diagnostic forum:
and have been using E-Sys 3.27.1 with my old ENET cable (Chinese knock-off) a lot recently and I noticed that it crashes a lot due to a myriad of issues. Something as simple as having the MSM Updated turned on could crash E-Sys. The good news is that MSM update is the last process in coding, so the crash does not pose big problem when coding. It’s just so annoying.
Memory, or the lack thereof, could also crash E-Sys. So, when running on default memory settings and trying to code complex ECUs, like NBT, could crash it.
I’ve never seen this happen to previous versions of E-Sys. It was pretty good at handling exceptions, but 3.27.1 seems different.
If you are forced to run E-Sys using default memory settings (512MB), you can help it by moving some PSdZData folders you never use. Some folders you can safely move, so long as you don’t own a series which uses them are the series folders inside kiswb. I have F30 so I moved the following folder:
C:\Data\psdzdata\kiswb\S15A (used by G-Series)
C:\Data\psdzdata\kiswb\K001 and C:\Data\psdzdata\kiswb\KE01 (used by BMW motorcycle?)
C:\Data\psdzdata\kiswb\RR01 (used by Rolls Royce)
C:\Data\psdzdata\kiswb\I001 (used by i-3, i-8)
C:\Data\psdzdata\kiswb\F056 (used by Mini)
Moving the above folders prevent E-Sys from reading database associated with these series. These databases are read on startup and kept in memory while E-Sys is running, using precious memory.
If you have plenty of RAM and can run at least using the medium settings, then moving the above folders are not required. Again, only do this if you are forced to run using default memory settings.