Are you running any special .MBX utilities?
In particular, older MBXs that provide their own DLLs?
The symptoms that you describe sound very much like a bug that has
been identified and should be fixed in the maintenance release, later
this year. Basically, MBXs can call DLLs -- they have always been
able to do that, that is nothing new. But, DLLs can do some low-level
operations, some of which are not compatible with .Net. What is new
is that MI Pro 10 is using more .Net than previous releases, in
particular in the layer control. Some background information, from
Microsoft:
http://support.microsoft.com/kb/326219
So, basically, if a third-party library manipulates the FPU in regards
to floating point exceptions, and if that library doesn't properly
return the FPU to its correct state, then that library will not be
compatible with an application that uses .Net... such as MapInfo.
But, again, I do not know if this is exactly the same problem you are
experiencing. Do you use any MBX utilities? If not, then you might
try adjusting the settings on your video driver -- someone on this
list reported that they eliminated a crash by adjusting the video
driver settings. I don't remember the details -- perhaps they turned
off hardware acceleration? Something like that.