Latest NTLite crashes during ESD compression

June8

New Member
Messages
10
Reaction score
1
Latest version crashes around 47% while optimizing image file structure. Tried both Widows 11 dev 26300.7965 and beta 26220.7961 builds on NTlite v2026.03.10873
But everything works fine on 2026.1.10761.
 

Attachments

Hi,

do you have a %temp%\ntlite.dmp file?

Thank you.
 
I just noticed you use ESD compression, that is very resource heavy, if you PC is in any way unstable it will show.

Try rebooting and without running anything else, try again please, from a fresh ISO.
Make sure to track your memory, it fills fast, do not start other programs while it's doing it.
And if you have that DMP file, please upload.
 
I just noticed you use ESD compression, that is very resource heavy, if you PC is in any way unstable it will show.

Try rebooting and without running anything else, try again please, from a fresh ISO.
Make sure to track your memory, it fills fast, do not start other programs while it's doing it.
And if you have that DMP file, please upload.
Hi Nuhi,

Thank you for your quick reply. My PC has 12700 CPU and 32 GB 6400mhz ram and I am working on separate SSD disk. I tried last night again with previous version and NTLite successfully finished without an error. Thats why I am surprised and thought something must have been changed in the new version. And I always use fresh .iso.

Anyway, In light of your suggestion I will try again and let you know how it will goes.

Please find the .dmp and .log files attached.

Thank you
 

Attachments

Thank you.
Crash is in libwim-15.dll (wimlib), it was updated though, please try the older working version NTLite\Tools\wimlib\x64\libwim-15.dll

If replacing it from the older version into the new makes the new not crash, I'll revert, don't have control over it other than that and changelog wasn't substantial between those two wimlibs.
 
Hello,

Thank you for your message.

When I used the newer version 2026.3.10876 I saw that crash has gone and finished without problem.

However, I saw the new version today (2026.03.10884), I download and used it. Unfortunately crashes return again when optimizing image file structure.

Thank you.
 

Attachments

The other crashes are also in libwim-15.dll
Please read both of my last messages above. My bet is on the PC instability as it sometimes works - it also could be a wimlib bug, but not sure how we catch that - I could build a debug version and send you that, then a DMP file might reveal more.

Second message has how to replace the wimlib if you want to go a few versions back, code around calling it is not important nor it changed, as the library is in control during optimization.
 
I already did replace libwim-15.dll from previous version - as it was working fine - but when i finished and clicked create it gives me error syaing wrong syntax or maybe wrong command (I am not remember exactly what was.

Sorry.

Let me try that again
 
Got another mail about the crash with this newer version of wimlib.
Shipped a new version using old one, and reserved one more thread for your 20 core situation (10% reserved now instead of 1 core), should reduce the load a bit.

Let me know how the new tool version goes, without changing libwim it comes with.
 
Got another mail about the crash with this newer version of wimlib.
Shipped a new version using old one, and reserved one more thread for your 20 core situation (10% reserved now instead of 1 core), should reduce the load a bit.

Let me know how the new tool version goes, without changing libwim it comes with.
Thank you.

FYI: I used the version 10885 and it works fine.

I will try the the new one you've mentioned and let you kow.

Thanks
 
Hello,

The crashes returned in the new version v2026.03.10909 while optimizing the image. The previous version - 2026.03.10889 - works perfectly fine.
Please find the .log and the .dmp file.

Thanks

Win 11 dev. 26300.9142
Solidigm D5-P5340 SSD
I7-12700k
32 Gb ram
 

Attachments

Crash is still in libwim, it wasn't changed nor anything around it, then it is most likely your machine. I'll return latest wimlib.

Somehow it either runs out of memory or overheats or lacks voltage, can be anything when it comes to so high utilization.

New idea:
edit NTLite shortcut, and add space then
/threadmax=4

So it is at the end like ...\NTLite.exe /threadmax=4

That will limit CPU to 4 threads max, keep increasing while you have stability, let me know when it starts crashing.
 
Hello,

Thank you for your quick reply. I'm really confused about why this didn't happen most of the time. Normally it works very well many times.
I already test my whole system stability with OCC both ram CPU tests which comes out well.


I will try your new idea and let you know
 
Hi again,

Hope you are well.

I would like to report that I tried your idea with /threadmax=6 instead of 4 (you've suggested), then /threadmax=10. it worked once but ctrashed on second.
Lastly set on /threadmax=8 which seems working fine now.
 
Back
Top