16bit MS-Dos Subsystem

[Guest]

I've been getting an error message saying that the NTVDM CPU has encountered
an ilegal instruction.
I've been reading the advice to others who have had the same problem but i
cant follow the instructions to fix it- I've been a a complete technophobe
up til now, but willing to learn! This is a computer that has had a virus but
is now up to date with all the spyware protection and windows updates.
Does this error message mean that it still has problems? If so what can I do
to get rid of the problem? Can someone talk me through step by step (in
simple language!!) what i need to do to stop the error message. Thanks for
your help in advance

 

[DatabaseBen]

hmm? Does your pc have a video board installed in it? It sounds like the
message is in regards to an older 16 bit video board by NTV.... If you are
not sure you can try running msinfo32.exe from the run command via start
"or" download and initiate BeLarc Advisor which will describe your system in
"detail" and you should also be able to see a question mark in the device
control panel somewhere on or near the video or monitor .....

 

[Guest]

Thanks so much for replying, I dont think it has a video board. I tried to do
what you suggested and didnt see a questiion mark. I did print put the info
on the computer though- will this lend any light on the subject. TX again

 

[DatabaseBen]

well, there isn't too much to worry about if your system seems to be
functioning fine. Since windows prevented the file from loading up because
it is "illegal instruction", then what ever it pertained to was prevented by
windows.

The key is to find out what caused that ntvdm to suddenly appear as an error
for you. It could be a failed driver or maybe you recently installed
something and it tried to load an old 16 bit file that is incompatiable.....

You could see if you can fix the problem. But first create a restore point
then

You can try to go to start then click run then type msconfig and hit enter.
At the dialog go to the startup tab and look down the listing and see any
line item that resembles the error file name. If there is, simply disable
it and reboot.... (If by chance your system becomes unfunctional, the
restore point you made, can bring you back. But its my guess that you will
not have any problems...)