19 replies
by mcsid
by josjea
A divide by zero is caused when a DIV instruction is executed and the divisor is 0. As you probably know, you cannot mathematically divide by 0. Memory corruption (or other hardware problems) or software failures can cause this.
NTVDM is the module that Windows NT uses to run 16-bit applications, so it is probably one of those pieces of software that is causing it. Open up the task manager and see which process is using the NTVDM.
by steved
If you've really stopped all your 16-bit apps, then NTVDM should unload also. Go into Task Manager and see what's listed directly under NTVDM, indented. Those are the 16-bit executables. You may recognize the names.
It is safe to use Task Managerto end the NTVDM process itself. That will also unload any 16-bit processes that are still running. It sounds as if one of them has a bug and doesn't remove itself entirely when you think you've stopped it.
by mcsid
by ann777
The fact that this tends to happen after a certain period of inactivity... leads me to believe that you may be experiencing problems/conflicts with a screen saver. Which screen saver do you have installed?
You might need to list all the apps that you have installed on this computer to try to narrow down what may be causing this.
Another thing you might try is seeing if you have anything running in task scheduler after a certain period of inactivity.
by mcsid
by mcsid
by steved
by mcsid
by vh_s
Well, I'm not really comfortable with SP6. Seems that I do have the same problem with NTVDM, that somehow it got executed and taking processor resources up to 100%.
What I would do is to unload SP6 and try to use the good old SP4 instead.
by mcsid
by mcsid
by mcsid
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending