NTVDM.exe has stopped working

[ck1402]

Hello all,

I have recently upgraded three systems to windows 7 Pro 32-bit.
The company i work for uses a 16-bit application that the owner created ages ago.

The issue i am having is on one of the systems it is gettinga NTVDM.exe error when opening the application.
Heres the kicker
They are setup with roaming profiles, when that end user switches machines there is no problem.
When i log into a different profile and use the program no problem.

So i did virus scans on her profile, i checked it over on her system and i couldn't find anything.
I removed the profile from the system and it worked great for a few weeks.

Now it's back, so i am not sure what is causing this issue. I have not been able to look at it today to see if it is just their profile or if it is the system globally.

Has anyone run into this issue before?

 

[YeOldeStonecat]

I remember running into this issue frequently years ago (I haven't seen it in a while). But it was usually related to a leftover driver that Symantec/Norton (usually Corporate Edition) loaded in the registry...that caused the NT Virtual Dos Machine to crash. Wouldn't see the issue when Symantec was installed...but when you uninstalled it...as was frequent, there are still remnants left behind. I did a quick Google to try to find that registry entry...but can't find it yet. Was just a line in the registry we'd delete.

 

[ck1402]

That's what i thought it was as well.
When i installed Windows 7 it was coming from XP. So i did a full wipe of the hard drive. They used Symantec before i came on, but you would think with a fresh install it would take that out.

 

[YeOldeStonecat]

Hmm...that should've cleared it then. Perhaps they installed symantsuck again when you weren't looking?

 

[ck1402]

Ok so I found that it's not just that profile but the system itself. Odd how it changes. However I ran BD, SFC, And did the remaining windows updates. I ran CCleaner and cleared out the registry errors. There were a lot of net framework errors. Well SFC can back fine. BD came back clean. I did the windows updates (which happened to be for the update framework) restarted a few times and BAM! It works. Why? No clue really....

 

[JoeMcDonalds]

You can try using the System File Checker to find missing or corrupt files that may be causing this issue.


The System File Checker tool To determine whether the issue that you are experiencing is caused by one or more system files that are used by Windows Vista, run the System File Checker tool. The System File Checker tool scans system files and replaces incorrect versions of the system files by using the correct versions.

To run the System File Checker tool, follow these steps:

1. Click Start , and then type cmd in the Start Search box.
2. Right-click cmd in the Programs list, and then click Run as administrator .
   
   If you are prompted for an administrator password or confirmation, type your password or click Continue
3. At the command prompt, the following line, and then press ENTER:
   sfc /scannow

The System File Checker tool To determine whether the issue that you are experiencing is caused by one or more system files that are used by Windows Vista, run the System File Checker tool. The System File Checker tool scans system files and replaces incorrect versions of the system files by using the correct versions.

To run the System File Checker tool, follow these steps:

1. Click Start , and then type cmd in the Start Search box.
2. Right-click cmd in the Programs list, and then click Run as administrator .
   
   If you are prompted for an administrator password or confirmation, type your password or click Continue
3. At the command prompt, the following line, and then press ENTER:
   sfc /scannow

Regards,
Joe McDonalds

 

[ck1402]

You can try using the System File Checker to find missing or corrupt files that may be causing this issue.


The System File Checker tool To determine whether the issue that you are experiencing is caused by one or more system files that are used by Windows Vista, run the System File Checker tool. The System File Checker tool scans system files and replaces incorrect versions of the system files by using the correct versions.

To run the System File Checker tool, follow these steps:

1. Click Start , and then type cmd in the Start Search box.
2. Right-click cmd in the Programs list, and then click Run as administrator .
   
   If you are prompted for an administrator password or confirmation, type your password or click Continue
3. At the command prompt, the following line, and then press ENTER:
   sfc /scannow

The System File Checker tool To determine whether the issue that you are experiencing is caused by one or more system files that are used by Windows Vista, run the System File Checker tool. The System File Checker tool scans system files and replaces incorrect versions of the system files by using the correct versions.

To run the System File Checker tool, follow these steps:

1. Click Start , and then type cmd in the Start Search box.
2. Right-click cmd in the Programs list, and then click Run as administrator .
   
   If you are prompted for an administrator password or confirmation, type your password or click Continue
3. At the command prompt, the following line, and then press ENTER:
   sfc /scannow

Regards,
Joe McDonalds

Thank you!
That was one of the first things I did.

Once the system was fully updated the issue resolved it's self.