Viking Supporters Co-operative

Viking Chat => Off Topic => Topic started by: Donnywolf on August 08, 2011, 08:21:54 pm

Title: NTVDM.exe Who can I trust ?
Post by: Donnywolf on August 08, 2011, 08:21:54 pm
I have JUST found a program on PC that now wont run. The dialog box says the above file has a fault and quotes the above reference

Looking on Google there are many fixes some very complicated - some looking simple enough for me to do. Some are free and some are £20 or more

I would like to get the missing prog to run again but can I trust any of the \"patch\" suppliers or better still anyone used any of them successfully or with no joy

Cheers DW
Title: Re: NTVDM.exe Who can I trust ?
Post by: RobTheRover on August 08, 2011, 09:10:59 pm
John

Found this on the net....


What is Ntvdm.exe?

The ntvdm.exe process belongs to the Windows 16-bit Virtual Machine, and it is especially relevant machines that are using Windows NT operating system. As a design feature of the Windows NT operating system, ntvdm.exe will help to run a 16-bit program. After you close this program, ntvdm.exe will remain in memory.

It is not hard to see that ntvdm.exe is crucial to the stability of your system. Since it is a process that could be ended, you should run a quick exe errors scan to make sure your system is running securely.

How to Fix Ntvdm.exe Errors?

First, you may to check whether the ntvdm.exe is running properly.

    Click Start, Run
    Type command.com in the open box, click OK

If a Command Prompt window opens, the ntvdm.exe is working properly. If not, you should take a look at the following tips to see how you can fix ntvdm.exe related problems.

The best way to solve this problem is to modify the TEMP and TMP environment settings.

    Check the location of ntvdm.exe, which will be looked like C:\\Documents and Settings\\Administrator\\Local Settings\\Temp
    Go to My Computer->Properties->Advanced->Environment Variables->Set TEMP and TMP
    Change the settings to C:\\temp or the short filename version


Also, download malwarebytes and run a full system scan.
Title: Re: NTVDM.exe Who can I trust ?
Post by: herouk87 on August 09, 2011, 08:22:24 am
Quote from: \"RobTheRover\" post=173796


Also, download malwarebytes and run a full system scan.


Good place to start but it doesn't necessarily find all malware. I've just had to reinstall windows on my PC because of a trojan
Title: Re: NTVDM.exe Who can I trust ?
Post by: Donnywolf on August 14, 2011, 05:48:48 am
Quote from: \"RobTheRover\" post=173796
John

Found this on the net....


What is Ntvdm.exe?

The ntvdm.exe process belongs to the Windows 16-bit Virtual Machine, and it is especially relevant machines that are using Windows NT operating system. As a design feature of the Windows NT operating system, ntvdm.exe will help to run a 16-bit program. After you close this program, ntvdm.exe will remain in memory.

It is not hard to see that ntvdm.exe is crucial to the stability of your system. Since it is a process that could be ended, you should run a quick exe errors scan to make sure your system is running securely.

How to Fix Ntvdm.exe Errors?

First, you may to check whether the ntvdm.exe is running properly.

    Click Start, Run
    Type command.com in the open box, click OK

If a Command Prompt window opens, the ntvdm.exe is working properly. If not, you should take a look at the following tips to see how you can fix ntvdm.exe related problems.

The best way to solve this problem is to modify the TEMP and TMP environment settings.

    Check the location of ntvdm.exe, which will be looked like C:\\Documents and Settings\\Administrator\\Local Settings\\Temp
    Go to My Computer->Properties->Advanced->Environment Variables->Set TEMP and TMP
    Change the settings to C:\\temp or the short filename version


Also, download malwarebytes and run a full system scan.


Thanks for that Rob ... but after trying the Command prompt check showed it was working I had to go out. When I shut down there were Windows updates available

I updated when home and after playing up for a week or so the fault (which affected just one program it seemed) was thankfully fixed during the updates or by some magic that would have fooled Penn and Teller !