Unable to open Windows Live Mail or IE. My system is Windows XP. At reboot I get a notice that NTVDM has encountered a system error.Also two .dll files are missing: luyehedu.dll and yetanehe.dll.

Receiving a bad image checksum error message when upgrading a computer to Windows XP means that a Windows system file such as user32.dll is damaged. This error occurs when any damaged system file is encountered that isn't overwritten during Setup. The repair process for this error involves voiding the damaged dynamic link library file from the DOS command line prompt and replacing it with a new copy from the Windows XP disk.

Insert a clean Microsoft Windows Millennium Edition (ME) or Microsoft Windows 98 Edition startup disk into the computer, and hold the reset button on the front of the computer until the system commences rebooting. Navigate the Windows startup menu with the keyboard's directional keys and select 'Start Computer with CD-ROM Support'. Hit "Enter" to continue. Write down your CD-ROM's drive letter on a piece of paper. At the command prompt, type "Drive:" without quotes (Drive should be replaced with the drive letter on which Windows is installed), and press "Enter." Type "cd windows\system32" without quotes, and press "Enter." Type "ren user32.dll user32.old" without quotes and again press "Enter." This renames your damaged user32.dll file so it is not recognized by the system, but still physically exists as a backup if needed in the future. Eject the Windows ME or 98 disk, and insert the Windows XP disk. At the command prompt, type "extract CDROMDrive:\i386\user32.dl_ Drive:\windows\system32\user32.dll" without quotes, replacing CDROMDrive with the CD-ROM's drive letter that you made a note of earlier, and replacing Drive with the system's drive letter on which Windows is installed. Hit "Enter" to execute the command. This process extracts a new copy of the user32.dll file to your hard disk, from the Windows XP CD. The new file will be found in the Windows/System32 directory. Restart the system by holding the reset button on the front of the tower until reboot commences.

Try to find "ie.inf" file on your computer than right click on that file and click on the option "Install". You should restart the computer after completing the installation process.

Here is how it should be done.

Start>Search (type in ie.inf then hit enter)>After it comes up in the search results window right click the ie.inf file>Install>Wait till done>Reboot computer. Done!!

If I am reading this right your issue is not the application but where you obtained the application. Maya 2010 is a modern design application and comes in 32 & 64 bit versions. It is not a 16 bit application.

When Windows encounters a legacy application it calls the NTVDM for the legacy application to run in.

The fact that the application is calling the NTVDM is highly suspicious. NTVDM is the NT Virtual Dos Machine, a way for legacy applications to run in NT environments.

NT environments are Windows NT 3.5, NT 4.0, Windows 2000 Professional, Windows XP (Home, Pro & Media Center Ed), Vista (all versions) and Windows 7.

Old (legacy) applications written for 16 bit date back to Windows 3.1 and include Windows 95, 98 and Millennium Edition.

I would obtain a copy of Maya 2010 from a reputable outlet instead of Bit Torrent as "warez" frequently contain malicious items that will infect and ruin your machine.

- Double click on the clock in the taskbar and make sure the system clock is set correctly.
- Disable Zone Alarm
- Register softpub.dll using the regsvr32.exe tool.Click Start, and then click Run.
- In the Open box, type regsvr32 softpub.dll and then click OK.
- Do the same for the following regsvr32 wintrust.dll, regsvr32 initpki.dll, regsvr32 MSXML3.dll.
- Restart Windows Live Messenger.

If you are still unable to fix Windows Live Messenger your computer might be infected, I recommend you Download registry cleaner to fix your errors and speed up your computer.

Try reinstalling IE 7 but make sure to scan your computer for viruses first

Boot into Safe Mode and see if the computer will let you uninstall Windows Live. If it does, reboot the computer into normal mode and Re-Download the installation files for Windows live. Are there any details or technical information provided when the error message shows up? Also, outdated drivers have been known to cause similar issues.

I took this from another web site:
Michael Chiew said:
What did you do before this happened? What were your last deeds on the machine before the pop-up appeared?

I think what you're referring to is NTVDM CPU, not NTDVM CPU. Am I correct?

What do you know about 16-bit and 32-bit applications? Well, 16-bit applications are those that must work within the DOS (Disk Operating System) environment, a real-mode arena. NTVDM stands for NT Virtual Dos Machine.

In Windows XP, as in Windows 2000, or Windows 98, there are 16-bit and 32-bit environments (real mode and protected mode respectively).

Windows XP can only operate in 32-bit mode. All 16-bit applications must work within its own theatre of operation, typically, the first MB of physical memory (ram). Conversely, 32-bit applications must function above the first MB memory line. If either of these applications happens to slip into "alien" territory, you get an error message like "something" has encounter an illegal instruction. In other words, the wayward application is trying to slip by the immigration checkpoint.

In your case, updatemgr.exe (I suspect updatemgr.exe is a 32-bit application) has in all likelihood wondered into the 16-bit arena. Hence, NTVDM CPU issues that warning. 

Why do you continue to get the message. It's because updatemgr.exe incessantly misbehaves itself on start-up, always trying to load itself into a particular memory address where it is not welcome. Why the persistence? Updatemgr.exe has gone bonkers. It is either corrupted or damaged.

On the other hand, one cannot discount the possibility that NTVDM (NTVDM.EXE) is corrupted or damaged. So your problem lies with either updatemgr.exe or NTVDM.EXE, or both.

There are 2 things you could do.

First, establish who owns updatemgr.exe, Microsoft or some third-party owner. Second, rename updatemgr.exe and see whether the message goes away.

To establish ownership (and the function of updatemgr.exe), do a search for the file. 

Click START, select FIND. In the FIND dialog box, type: updatemgr.exe. See the directory in which the file has lodged. In Windows Explorer, get to the file, right-click on it, select PROPERTIES. Who owns it? Is there an indication of its function.

Next, rename the file. Right-click it, select RENAME and rename it to, say, updatemgr.old. RESTART your computer. Do you still get the error message. Not likely.

To clean things up a bit, perhaps it is a good idea for you to replace the current NTVDM.EXE with a new copy. Find out where NTVDM.EXE is. Then, click START, select RUN. Type in the RUN dialog box SFC to run the System File Checker. Insert your OS CD, follow the prompts, extract a copy of NTVDM.EXE and send it to its place of residence. Of course, you should also replace a copy of updatemgr.exe.

That should eliminate your problem for good.

The link below is a step-by-step troubleshooter from the Microsoft website. You'll just need to follow all the instructions on the site and you should be able to fix it all by yourself. This seems to be a common error with windows.

Troubleshooting NTVDM and WOW Startup Errors

HERE IS THE SOLUTION :
click on the link given below and find oc25.dll....if you are unable to find press keyboard key cntrl + f .A dialog box will appear now type oc25.dll and hit find key and you will find the oc25.dll .click on that file to download it to your computer.

http://www.dlldump.com/dll-files/O_2.html

Once you have downloaded the file you are looking for you still need to make sure Windows or the program causing the error can find it. Follow these steps:

1. If you are encountering an error with Windows...
The file you downloaded needs to be placed into the Windows System directory. On most machines this is one of the following locations:
C:\Windows\System (Windows 95/98/Me),
C:\WINNT\System32 (Windows NT/2000), or
C:\Windows\System32 (Windows XP).

If you are encountering an error with a particular program...
The file most likely needs to be in this program's directory. This directory is where the program is installed (i.e. c:\Program Files\ThisProgram).

If this step solves the problem, you do not need to complete step 2.

2. You may to register this file with Windows. Click on the Start Menu and then on 'Run'. If you are replacing a Windows system file, type the following command:
regsvr32 \windows\system\file.dll (Windows 95/98/ME),
regsvr32 \WINNT\system32\file.dll (Windows NT/2000), or
regsvr32 \windows\system32\file.dll (Windows XP).

For example, 'regsvr32 \windows\system\apphelp.dll'

If you are replacing a file for another program, change the directory where appropriate. For example, 'regsvr32 \program files\Norton\xyz.dll'

If the file is registered correctly, you will receive a positive confirmation message.
-------------------------------------------
Please let me know your feed-back.

Thanks
dilipbagdi
Technical Associate

Try pressing F8 before while booting and run Last Known Good Configuration. Also try to boot into safe mode and uninstalled IE 7.

Let me know what happens.