Microsoft Windows XP Professional, SP3 (all updates and fixes current from Microsoft) - all legit software
File conversion type:
Does not apply, no file loaded
Error reproduction (details)
I had several crashes, supposedly caused by MSVCRT.DLL, but I noticed that the conversion process continued behind the error screen - This gives us a clue that the crash is UI (User interface) related. I left the error screen in place and did nothing but let it set there, and the batch conversion continued in the background through all 93 files (FLV to AVI).
So, I restarted the software and did nothing but let it set there; I did not move the mouse, click on anything, type anything or allow QMC to loose focus, etc. after exactly 5 minutes and 10 seconds it crashed; I repeated this exact test 3 times, and it crashed on time every time (every 5m 10s).
File name: MSVCRT.DLL
Version: 7.0.260.5512 (xpsp.080413-2111)*1
Type: Protected operating system file*2
1: (xpsp.080413-2111) identifies this file as an update to the operating system, to Service Pack 3
2: This file is a "Known DLL" meaning that only Microsoft and or the Operating System can change, update, replace, or restore the file - see: http://wiki.codeblocks.org/index.php?ti ... use_it_.3F
The msvcrt.dll is now a "known DLL," meaning that it is a system component owned and built by Windows. It is intended for future use only by system-level components.
http://msdn.microsoft.com/en-us/library ... 80%29.aspx
One of your links about (the) "DLL Hell" that happened on Windows operating systems prior to XP is what caused this change; now that file cannot be tampered with in any way - Ok, yes it can but not by the "normal user" it can be force replaced by logging into the Recovery Console and forcing its replacement by expanding its original source MSVCRT.DL_ (but I don't see many users doing that (successfully))
In any case every operating system since Windows 2000 has flagged this DLL as a protected OS file, and the errors about the previous problems in that DLL is outdated; as the DLL is now unified and you simply call any of the other MSVCxx.DLL files for extended functions that are not included in that dll (MSVC80.DLL for instance), or you build your own and include it with your install.
Because this is a Protected Operating System File any attempt to change it would cause windows to throw an error popup about the file being changed - also SFC /SCANNOW (system file checker) shows that this file is correct, and uncorrupted from ServicePack 3.
Code Calls to DLL:
It seems that this DLL is used for function calls; it does not matter if you are using C++, Viso, Python, or whatever: some function that your software is calling is not present in that DLL.
It almost seems that: http://msdn.microsoft.com/en-us/library ... 85%29.aspx could give insight as to how, where, why this is occurring and or a way to redirect the calls through your own version of a known working DLL to stop the crash <> but, I'm no programmer and 'that' is just a guess.