Ntvdm.exe Encountered Hard Error
Contents |
your while on the topic of VMware, Microsoft Products, Snowboarding, Skating, Music or Golf. Home
Ntvdm Error Windows 7
Archives Profile Subscribe « Changing the SCSI controller on a (VMware ntvdm has encountered a system error windows 10 ESX) VM running Windows 2003 | Main | I'm back... » 02/24/2006 NTVDM.EXE has encountered a hard ntvdm has encountered a system error a device attached to the system is not functioning error You were either trying to install some software that ships with a 16bit installer (SQL2000, Exchange, etc), trying to run command.com, or at a command prompt and https://social.technet.microsoft.com/Forums/windows/en-US/aaede3d8-9372-4449-b20f-9adc05a9e6f7/ntvdm-encountered-a-hard-error?forum=winservergen tried running edit.exe and this not-so-descriptive message pops up. What now? You checked the event logs and nothing. What have you done to cause this? In my case I had imported a baseline security template from Microsoft...I spent a good 2 hours trying to figure out the root cause. I went through the security configuration, all local http://www.alexwho.com/blog/2006/02/ntvdmexe-has-encountered-a-hard-error.html gp settings, and finally broke out filemon.exe. After a short trace and investigating the logs I found the culprit of my problem...NTVDM.EXE was trying to read/write to a file in my %temp% environment variable (which it had wrong).Some background; the security template above makes a change to the registry disabling 8.3 filenames. This template was imported after the Administrator account was created, which explains why the admin account did not see the same problems my account did. Since my account was made after 8.3 filenames had been disabled %temp% for me equaled a path containing a space "...\Local Settings\...", this was "\Local~1\" for the local administrator account. As with all my other issues, and trust me there are plenty, below are some things to look for and some fixes for the issue above, some are directly from MS, link to the articles below.1. Check the following registry value:Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystemName: NtfsDisable8dot3NameCreationValue: 0 or 1 (0 disabled - default)Link to Microsoft2. Check Config.NT and Autoexec.NT in the %windir%\system32 directory for
Today I troubleshooted an old DOS application that needed to run on a 32 bit Citrix XenApp Server. The last time I saw an actual DOS application in a production environment must be years ago.When starting the application, the WOW subsystem (NTVDM) crashed with the message: "NTVM encountered a hard error.":After spending some time troubleshooting I remembered a similar issue from a few years ago where a DOS application worked fine from the Console but refused to work from an RDP or ICA session.And indeed the application works perfectly when run from the Console but not from a Console session. I noticed that the application switched to full screen mode after it was launched (even when I set it to Windowed mode) and presumably this is why ntvdm errors: full-screen mode is disallowed for DOS apps in RDP (and ICA) sessions as documented in Q192190.I looked for a way to force the application to run in windowed mode but I was unable to find such a solution. So I decided to test the application in DOSBox, an x86 PC emulator.And that worked perfectly, no changes were needed at all to make the application run.As an added bonus, DOSBox takes care of typical issues with DOS applications running on Citrix XenApp such as keyboard polling and 100% cpu usage.I was even more impressed that the application runs fine with DOSBox on my Windows 7 64 bit machine!There is one thing I didn't like though, DOSBox always shows a Splashscreen that fades in and out:This is typically something that is not desirable on a XenApp (or RDS) environment because it causes many unnecessary screen updates. This may be a non issue on a fast LAN but on a slower WAN or high latency connection it may matter. Do how do we get rid of it?There is no commandline argument or config setting that disables the splash so I figured that my only option would be to compile the DOSBox source and leave out the splash screen.So I downloaded the source files from the sourceforge project page and launched Visual Studio 2010.The Splashscreen is in sdlmain.cpp but I noticed this comment:C++ /* Please leave t