Question about Microsoft Windows XP Home Edition
Everytime i start computer i get this dialog box:
the ntvdm cpu has encountered an illegal instruction.
cs:0000ip0077 op:fu 37 05 oc 02
choose close to terminate application
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.
Posted on Dec 27, 2008
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
Posted on Jan 02, 2017
Tips for a great answer:
8,346 people viewed this question
Usually answered in minutes!
Step 2: Please assign your manual to a product: