Hi Michael,
File version/date for moi_lib.dll for the Sep-1 v3 are exactly as you state: 09/01/2012 04:12 PM 5,273,088 moi_lib.dll - here's the screengrab of my v3 SEP 01 install directory, if that's of any further interest:
https://www.dropbox.com/s/u5ccn9fmyojgfre/MoI%203.0%20beta%202012-09-01_cmd_screengrab.jpg
The only change I've made within the v3 install directory is adding the CustomDistance.js /.htm script (dated 6/13/2008) to the commands folder.
>when you check Task Manager, is moi.exe still running or not?
moi.exe is no longer present after any crashes.
>And just to confirm, if you only simply launch MoI and do nothing else at all (no loading of files, etc...), you get a crash after a while just having left the program totally undisturbed?
Correct. And for further clarification, it makes no difference whether other programs, (whether started automatically at system startup or manually) are running in the background or not. However, the average period between starting MoI and it crashing seems to have increased (from 5 - 10 mins to 10 - 20 mins) since I changed the video drivers and had a good clean out my installed programs; this might be coincidence.
BTW, it makes no difference if my AV is active or temporarily disabled.
I'll do a memory test tonight using Memtest86+ and let you know how it goes.
Any other ideas for stress testing?
Also, is there any point in seeing if MoI will 'crash-while-idle' in safe-mode? Perhaps this might eliminate or implicate the display driver? I noticed when I tried running MoI in safemode I received the error "Unable to create Direct3D9 device", identical, except for the (higher) display resolution, to the one when the latest video driver wouldn't install properly as shown here:
https://www.dropbox.com/s/ylxawznl7zzs410/moi_screen_dump_640_480.JPG
Thanks,
hamish