I've been getting a problem recently:
"NTVDM has encountered a hard error"
-Close- -Ignore-
If I choose either close or ignore the same thing happens: Nothing.
I've been having this problem with many of my programs, most of them older programs. I've never had this before though. Any ideas on what it is/how to fix it?
Full Version: NTVDM.exe
Here is what i got from googling the info. So no wonder it is happining with the holder programs cause it must be something with those 16 bit programs failing to execute or something on the 32 bit process?
Process File: ntvdm or ntvdm.exe
Process Name: Windows 16-bit Virtual Machine
Description: Application that provides an environment for a 16-bit process to execute on a 32-bit platform.
Company: Microsoft Corp.
System Process: Yes
Security Risk ( Virus/Trojan/Worm/Adware/Spyware ): No
Common Errors: N/A
Process File: ntvdm or ntvdm.exe
Process Name: Windows 16-bit Virtual Machine
Description: Application that provides an environment for a 16-bit process to execute on a 32-bit platform.
Company: Microsoft Corp.
System Process: Yes
Security Risk ( Virus/Trojan/Worm/Adware/Spyware ): No
Common Errors: N/A
Cool... thanks for the info... well, that tells me what it does... now I need a way to fix it...
I found a page listing a little info on the error, but i cant figure out what it means. http://msdn.microsoft.com/library/default....s__500-999_.asp
Just search for NTVDM or scroll down to number 593 for a description
Just search for NTVDM or scroll down to number 593 for a description
Maybe you could find a fresh copy somewhere and install it ? lol
Well ... I came across this while hunting for some other problems - may help you
http://support.microsoft.com/default.aspx?kbid=156687
http://support.microsoft.com/default.aspx?kbid=156687
The information there doesn't apply to XP or later (I'm running 2003)...
I guess I should've mentioned that...
Thanks though, as that did give me a few starters on where to look for the problem
I guess I should've mentioned that...
Thanks though, as that did give me a few starters on where to look for the problem
Some detailed information about ntvdm.exe
Hi
I seem to have the same problem. Did you found a solution to this problem?
I am also running win2k3. I am debugging a consoleapplication(C#). This app calls a program by using the Process.start(processinfoobject) method. When I do this call I receive this error. My code is as follows:
Anyone got a clue? I have successfully runned this code before. Can the ntvdm.exe be corrupted by any means? I started getting a popupbox with an error like:
ntvdm.exe
Error while setting up the application. Choose 'close' to terminate the application.
Then I tried to solve the problem by updating to SP1. Then I received this error:
NTVDM.EXE -System error
NTVDM.EXE encountered a hard error
close | ignore
I seem to have the same problem. Did you found a solution to this problem?
I am also running win2k3. I am debugging a consoleapplication(C#). This app calls a program by using the Process.start(processinfoobject) method. When I do this call I receive this error. My code is as follows:
CODE
ProcessStartInfo ps = new ProcessStartInfo( program, arguments );
ps.UseShellExecute = false;
ps.RedirectStandardOutput = true;
ps.CreateNoWindow = true;
Process p = Process.Start(ps);
p.WaitForExit();
ps.UseShellExecute = false;
ps.RedirectStandardOutput = true;
ps.CreateNoWindow = true;
Process p = Process.Start(ps);
p.WaitForExit();
Anyone got a clue? I have successfully runned this code before. Can the ntvdm.exe be corrupted by any means? I started getting a popupbox with an error like:
ntvdm.exe
Error while setting up the application. Choose 'close' to terminate the application.
Then I tried to solve the problem by updating to SP1. Then I received this error:
NTVDM.EXE -System error
NTVDM.EXE encountered a hard error
close | ignore
I too get the same error when i type 'command' in the run window. In windows xp, when i go to 'command' window in full screen mode and i exit, display goes black and i realised system is not hanging. so i blindly press the windows key and select shutdown and press enter(i just do it blindly coz the screen is full black.). in both OS, cmd is working fine. but i need to resolve this issue for 'command'. is this related to patching for unsigned themes and windows file protection? coz i did this for both OSs.
I am setting w2003server on a network running quite a few 16-bit applications, mainly DOS applications. I get the same hard error message when I drag a shortcut to from the EXEs of the 16bit programs.
My solution to came to mind when i realized i was working in a rdp client session, which of course can't go full-screen. So I try going windowed mode and everything works just fine. And when I have users log onto domain wihtout terminal session the program works fine too with or without fullscreen mode.
As for the cmdprompt going blank I had that error on some compaqs after updating gfx drivers from windows update, same thing, prompt was ok, but returning to windows just showed blackscreen but everything was working fine. I narrowed it down, in my case, to ONLY flatscreens and not CRT screens and only intel onboard graphics cards. Only suggestion I got is to rollback graphpics drivers, it worked for me. This was some time ago and a suggestion was made to download dirvers directly form intel website instead of hp so maybe a new driver is out there.
Hope that helps
My solution to came to mind when i realized i was working in a rdp client session, which of course can't go full-screen. So I try going windowed mode and everything works just fine. And when I have users log onto domain wihtout terminal session the program works fine too with or without fullscreen mode.
As for the cmdprompt going blank I had that error on some compaqs after updating gfx drivers from windows update, same thing, prompt was ok, but returning to windows just showed blackscreen but everything was working fine. I narrowed it down, in my case, to ONLY flatscreens and not CRT screens and only intel onboard graphics cards. Only suggestion I got is to rollback graphpics drivers, it worked for me. This was some time ago and a suggestion was made to download dirvers directly form intel website instead of hp so maybe a new driver is out there.
Hope that helps
First off, i found this forum by running a search on the said problem.
I get the same error when trying to run several older batch files such as BAT2EXEC.com and GETAKEY.com I also encounter this error when i type the "edit" command in the cmd prompt.
I am using Windows NT on my school's computer but windows xp at home. i have never encountered this error at home. could it be taht the school set it to where i can't run the edit command or files with certain attributes? How would i get around this?
I get the same error when trying to run several older batch files such as BAT2EXEC.com and GETAKEY.com I also encounter this error when i type the "edit" command in the cmd prompt.
I am using Windows NT on my school's computer but windows xp at home. i have never encountered this error at home. could it be taht the school set it to where i can't run the edit command or files with certain attributes? How would i get around this?
I my experience, most ntvdm errors can be fixed by modifying the TEMP and TMP environment settings to make them 8.3 namespace compatible.
The default path for the TEMP directories is %USERPROFILE%\Local Settings\Temp
Which will (typically) expand to something like:
C:\Documents and Settings\Administrator\Local Settings\Temp
16 bit applications can’t manage the spaces or long file names, and will generate ntvdm errors, even if they are not explicitly referencing the TEMP directory.
You can either use a common temp location (e.g. C:\Temp) or use the short version of the path. For the Administrator ID, the short filename path is C:\DOCUME~1\ADMINI~1\LOCALS~1\TEMP
Your can check these names by using ‘dir /x’
The variable settings can then be changed for each user by going into
My Computer -> Properties -> Advanced -> Environment Variables ->
Set TEMP and TMP to c:\temp or the short filename version
You should also consider the PATH environment variable, and any INI files that may be used. The short filename for the "c:\Program Files" directory is "c:\progra~1"
The default path for the TEMP directories is %USERPROFILE%\Local Settings\Temp
Which will (typically) expand to something like:
C:\Documents and Settings\Administrator\Local Settings\Temp
16 bit applications can’t manage the spaces or long file names, and will generate ntvdm errors, even if they are not explicitly referencing the TEMP directory.
You can either use a common temp location (e.g. C:\Temp) or use the short version of the path. For the Administrator ID, the short filename path is C:\DOCUME~1\ADMINI~1\LOCALS~1\TEMP
Your can check these names by using ‘dir /x’
The variable settings can then be changed for each user by going into
My Computer -> Properties -> Advanced -> Environment Variables ->
Set TEMP and TMP to c:\temp or the short filename version
You should also consider the PATH environment variable, and any INI files that may be used. The short filename for the "c:\Program Files" directory is "c:\progra~1"
QUOTE(Sparky @ Apr 9 2006, 05:17 PM) 
I my experience, most ntvdm errors can be fixed by modifying the TEMP and TMP environment settings to make them 8.3 namespace compatible.
The default path for the TEMP directories is %USERPROFILE%\Local Settings\Temp
Which will (typically) expand to something like:
C:\Documents and Settings\Administrator\Local Settings\Temp
16 bit applications can’t manage the spaces or long file names, and will generate ntvdm errors, even if they are not explicitly referencing the TEMP directory.
You can either use a common temp location (e.g. C:\Temp) or use the short version of the path. For the Administrator ID, the short filename path is C:\DOCUME~1\ADMINI~1\LOCALS~1\TEMP
Your can check these names by using ‘dir /x’
The variable settings can then be changed for each user by going into
My Computer -> Properties -> Advanced -> Environment Variables ->
Set TEMP and TMP to c:\temp or the short filename version
You should also consider the PATH environment variable, and any INI files that may be used. The short filename for the "c:\Program Files" directory is "c:\progra~1"
Thanks for your help Sparky. I also found out that there is a registry setting for turning off the 8 dot 3 requirements but it only takes effect from when you change it. You have to recopy directories to get them recognized in both formats. Here it is:
Problem - 16-bit applications encounter "hard error" during installation.
Many directories do not display 8.3 character names.
Environment - Windows Server 2003
Root Cause (if known) - The servers did have the 8.3 long file name system disabled to increase performance.
It has been disabled following the steps in http://support.microsoft.com/kb/121007/en-us
Resolution -
Reverse the steps in 121007 by setting the following registry value to 0.
HKLM\SYSTEM\ControlSet001\Control\FileSystem \NtfsDisable8dot3NameCreation
Hope this helps more people with this issue.
Mary-Ann
I had this problem today with the error (NTVDM encountered a hard error). This is a new server with a fresh install of Windows 2003 Server and Service Pack 1. I tried to install SQL Server 2000A and it gave me the error. I tried everything listed in this thread and every MS article I could find to no avail. I uninstalled SP1 and then tried installing SQL and it launched just fine. Don't know if this was a corrupted install of SP1 as most of the SQL servers I support already have SQL server installed when I updated them to SP1. Anyway, I'm going to install SQL Server, patch it and then try reinstalling SP1.
Thought this might be helpful if anyone else was running into something similar.
Thought this might be helpful if anyone else was running into something similar.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.