Discussion Locked

Divide by Zero error, ntvdm.exe

0 helpful
19 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Running NT4.0 SP5 on a DELL box. A Dr. Watson error from the ntvdm.exe with a divide by zero error appears after 45min to an 1hr of inactivity. No error occurs during hours of use but only after idle time. Have reloaded the service pack, loaded SP6, stopped any 16bit services that are running. This is happening on several machines in a staged network running an X windows application to connect with a VMS server and application. How can I capture the program or application that is causing this error?

19 replies

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

Answers 1 & 2, I appreciate your quick response but this is not new information to me. I already know that this NTVirtualDosMachine executable allows for 16bit apps to run, that is why I stopped those processes. Using the Task Manager, I have enabled Show 16 Bit but nothing comes up under the drwtn.exe process that displays in the list and thus my delemma. If this comment is more informative I will appretiate your solution.

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

I din't like the "Unacceptable" choince. You are an the right track. 1 of 11 machines reacted to the screensaver preview with the drwtn32.exe error. Re-ran SP5 and no reaction to test. The saver selected was "blank.svr". The other 10 machines were OK with the preview test so that may have been machine specific. Will obtain a list of apps. Stay with me, I think we'll lick this thing yet.

by mcsid

I didn't like "Unacceptable" as the only choice. You are on the right track. 1 of 11 machines reacted to the screensaver preview with the drwtn32.exe error. Re-ran SP5 and no reaction to test. The saver selected was "blank.svr". The other 10 machines were OK with the preview test so that may have been machine specific. Will obtain a list of apps. Stay with me, I think we'll lick this thing yet.

by steved

Hmm. I don't really have anything more to contribute. I'm now inclined to agree with Anna777 that a screen saver is somehow involved. It reminded me that some time ago we were running a 16-bit app whose vendor actually said in the docs: If you're running this on NT 4.0, you must turn off screen savers or it will crash.

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

Anna777 was right. It was caused by a conflict with the black16.scr screen saver. In the list of choices the "blank" choice was this black16.scr. Changing it to Default solved the problem. Bottom Line: Delete black16.scr-- no more problem. Thank you Anna777, you get the brass ring.

This discussion is closed to new replies.