It is currently Mon Feb 13, 2012 8:35 pm




 Page 1 of 1 [ 4 posts ] 
Author Message
 Post subject: NTVDM CPU has encounted an illegal instruction
PostPosted: Thu Jun 03, 2010 10:00 am 
Newbie
Newbie

Joined: Fri May 07, 2010 8:29 am
Posts: 3
At work we are usin SBS 2008 and all workstations run winXP. Once a week we get the message c:windows\system32\cmd.exe - the NTVDM CPU has encounted an illegal instruction with the option to close or ignore. It comes up on every workstation at the same time each week. Has anyone seen this and know why it does it?


Offline
 Profile  
 
 Post subject: Re: NTVDM CPU has encounted an illegal instruction
PostPosted: Fri Jun 04, 2010 3:01 pm 
Windows 2008 Enthusiast
Windows 2008 Enthusiast
User avatar

Joined: Wed Mar 04, 2009 6:48 pm
Posts: 58
Location: Birmingham
Is there anything in the event log that corresponds with the same time the error occurs?


Offline
 Profile  
 
 Post subject: Re: NTVDM CPU has encounted an illegal instruction
PostPosted: Sat Jun 05, 2010 12:07 pm 
Site Admin
Site Admin
User avatar

Joined: Mon Feb 09, 2009 1:31 pm
Posts: 193
Location: Newport, South Wales
This is the NT Virtual DOS Machine and simulates a 16-bit environment in Windows. Do you have any older 16-bit apps running that could be causing this? Also, if it's once a week, is something scheduled to run at the time the errors occur?



_________________
Dave Webb
Windows 2008 Forums
Offline
 Profile  
 
 Post subject: Re: NTVDM CPU has encounted an illegal instruction
PostPosted: Mon Jun 14, 2010 5:44 am 
Windows 2008 Enthusiast
Windows 2008 Enthusiast

Joined: Tue Apr 27, 2010 12:29 pm
Posts: 51
Location: New Jersey
The NTVDM attempted to create an isolated environment within the architecture of Windows NT, above the Executive Layer. It enabled 16bit (DOS) applications to run within a 32bit environment, it still does in fact. The theory was that if the DOS application crashed, as they were likely to do, it wouldn't take any other applications or the operating system down with it. The application would crash within the NTVDM and the NTVDM would contain that event within the Win32 subsystem, and not allow it to access the hardware (Microkernel). This didn't always work as it should, and usually resulted in the infamous BSOD. Fortunately things are becoming a little more stable on the Windows front, and we see less BSODs than we use to.



_________________
SharePoint Consulting || SharePoint Staffing
Offline
 Profile  
 
Display posts from previous:  Sort by  
 Page 1 of 1 [ 4 posts ] 


Who is online

Users browsing this forum: No registered users and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

cron