After getting another round of errors, I downgraded to the NVidia 4.19x drivers - no issues since then.
One thing that’s puzzling to me: I’ve run 90+ files through the UI and haven’t run into an issues using the same configuration and drivers. Why would using the UI not express the memory issue, while the command line / script invocation does?
Do you have the link to the drivers so I can put it in the sticky?
Did you change the running mode of the engine? The only time you may see a difference is if the engine is running as a service vs as a command line engine. This is because of the way windows starts ffmpeg. In kernel context the graphics drivers behave differently vs in user context. This is a limitation of the windows/driver architecture.
Graphics Hardware API are typically designed for User context (eg games or design applications which run from user context). Most kernel apps don’t use graphics hardware acceleration APIs (because they don’t have native UI’s) so until Windows 8 the kernel didn’t offer those graphics API’s to apps and even after windows 8 and most graphics vendors don’t bother testing them properly in kernel space.