The NTVDM CPU has encountered an illegal instruction

[BigDough]

This computer at work running NT 4 sp3, is crashing anytime someone runs any applications.

16 Bit MS-DOS Subsystem
C:\WINNT\Profiles\Scottm\Desktop\(traderapp.lnk)

The NTVDM CPU has encountered an illegal instruction.
CS: 04fa IP:0120 OP:c728 c001 d0

**I first tried rebooting this user's pc, but this did not work. I then went to Microsoft's Support site and found the following:
SYMPTOMS
When you attempt to run a 16-bit program on a computer running Microsoft Windows NT 4.0 Service Pack 3, the program may quit immediately, or you may receive the following error message:

Hidden Console of WOW VDM
The NTVDM CPU has encountered an illegal instruction.
CS: 04c3 IP:3937 OP:c71c 9d 37 00
Choose Close to terminate the application.
When you click Close, you may receive several similar error messages.

CAUSE
This behavior can occur if you use an incorrect version of the Command.com file. For example, this issue is known to occur if you use a Command.com file included in Microsoft Windows 95, dated 7/11/95.

RESOLUTION
To resolve this issue, replace the Command.com file in the Winnt\System32 folder with the same file from another computer that is running Windows NT Workstation 4.0 or Windows NT Server 4.0, and then make sure that there are no Command.com files dated 7/11/95 on the computer. You can also replace the Command.com file on the computer with the same file on the Windows NT installation CD-ROM.

Additional query words: NT simulate emulate 95

*This did not fix the problem. I also tried running Service Pack 5. This did not work either. Anyone got any ideas?

 

[bunker]

I had the exact same problem here at work. The culprit was a dos based program that I needed for my job. The program had been recently updated and now caused that error. The only solution the techs here could come up with was to install W2K on my machine.

 

[Saltin]

Yeah, that's the NT Virtual Dos Machine. It makes 16 bit apps think they are running in a 16 bit environment.
I know this works in 2k, dunno about NT.
Make a shortcut to the program and ensure the "run in seperate memory space" box is checked. Often, when several 16 bit apps are running within the NTVDM, if one crashes it causes the others to hang. Running them in thier own NTVDM's can fix this probelm. This may not be related to what is happening to you. Just thought I'd put it out there.