Discussion Locked

NTVDM.EXE is continually failing

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The error is:
Initialization of dynamic link library c:\winnt\system32\kernel32.dll failed. The process is terminating abnormally.

The only resolution I have been made aware of in the past was to reinstall NT. Is this really the only resolutionto this error? Any better solutions? I've seen this happen on 3 of the 50 NT workstations here. BTW, they are running NT4sp6a, on custom made machines with AMD 600 - AMD 800 mhz processors.

7 replies

by timthetoolman

Hi,

Do the machines automatically start any 16 bit applications?

If they do, then I would think its more likely to be a problem with the 16bit app causing the NTVDM to crash than the NTVDM subsystem.

If you can boot the machine without having it crash, then try re-installing the 16bit app first...

If you're not running any 16 bit applications, then I suggest you create ERDs for all machines and use them to recover with.

Why dont you upgrade to Win2K?

Cheers,
Tim.

by curlergirl

I agree with TimTTM - check any 16-bit apps - could be an app that appears to be 32-bit but has some 16-bit code, too. I've seen older versions of Norton Antivirus cause some similar behavior, for example. Also, you might try just reinstalling SP6a first to see if that might fix it. Hope this helps!

by chipw

Well, a couple hours ago, I removed the 3com diagnostics from the start-up. That was the only thing loading on start-up. The error box has not popped up since, and it was appearing several times per hour previously. I will let you know how it goes later, hopefully that will fix the problem. :-)

by chipw

Well, been about a day-and-a-half without error boxes popping up. Maybe the problem was the 3com diagnostics? The same thing is running on 40-some-odd computers here, but only the one has the problem. Must just be a corrupt file. We'll see...

This discussion is closed to new replies.