Welcome to the land of wild speculation ...
With the long lists of programs running in the background on most systems, the miracle isn't that they don't seize more often, it's that they manage to run at all.
My guess is that a program has a firm grip on a resource, but needs another to continue. Another program has an equally firm grip on the resource desired by the first program, but before it will release it, it needs the resource allocated to the first program, so they sit and wait for conditions that will never happen. Windows 9? and beyond have improved their ability to break these types of log-jams, but they're not perfect, as you can see.
I do not know if more memory will help. Certainly, if some memory shortage or constraint is the root cause of the problem, additional memory is the solution, but if the problem stems from a different source, adding memory will be like filling the car's tyres with air when the problem is an empty gas tank.
Cheers, PW.
P.S. In Windows, 32-bit stuff seems more reliable than 16-bit counterparts. Try editing SYSTEM.INI and WIN.INI to re-arrange some entries. Perhaps loading one driver or program before another will make a difference. Don't forget to make copies of the original first. |
