So, it's not the infamous FPW "fast CPU" / divide-by-zero issue, right?

I believe the "FoxPro for Windows 2.x runtime stops running w/o error on
WinNT/W2k/XP" issue might be caused by the "NT Virtual DOS Machine"
NTVDM, respectivly wowexec.exe, on some PCs thinking the foxw*.esl runtime
is doing something illegal (most likely regarding memory managment).
Personally, I never saw the effect you described myself but got a customer's
report back in ~1996, and saw others every other year here in the NGs.
So I think it's an old one and that it seems to be very rare - even back then
only a very few people reported it.
http://groups-beta.google.com/groups?as_q=ntvdm%20group%3A*fox*&safe=images&lr=&hl=en

In three cases at least it did help to reinstall Windows on the same hardware.
My guess is that other 16bit runtimes might be affected as well, so maybe
you'll get some feedback in Windows newsgroups, too.
(the foxw2*.esl runtime was written in C using the Watcom compiler, AFAIK)
Will you post back if you find a solution?

hth
-Stefan