Tags Tags

NTVDM has encountered a system error c0h

May 11th, 2012 - 08:53 am ET by Robin Vowels | Report spam
Help Create a new topic
Hi,
On Windows XP, this error began occurring from the DOS prompt.
All programs such as EDIT, PKZIP, and other old-style programs
that used to run in DOS on XP suddenly will not run.

Has anyone else experienced this error, and if so,
how did you fix the problem?

Thanks.
email Follow the discussionReplies 6 repliesReplies Make a reply

Similar topics

Display all similar topics

Replies

#1 philo
May 14th, 2012 - 08:59 pm ET | Report spam
On 05/11/2012 07:53 AM, Robin Vowels wrote:
Hi,
On Windows XP, this error began occurring from the DOS prompt.
All programs such as EDIT, PKZIP, and other old-style programs
that used to run in DOS on XP suddenly will not run.

Has anyone else experienced this error, and if so,
how did you fix the problem?

Thanks.





http://support.microsoft.com/kb/314106





https://www.createspace.com/3707686
Replies Reply to this message
#2 Robin Vowels
May 15th, 2012 - 10:32 am ET | Report spam
On Tuesday, 15 May 2012 10:59:01 UTC+10, philo wrote:
On 05/11/2012 07:53 AM, Robin Vowels wrote:

> On Windows XP, this error began occurring from the DOS prompt.
> All programs such as EDIT, PKZIP, and other old-style programs
> that used to run in DOS on XP suddenly will not run.
>
> Has anyone else experienced this error, and if so,
> how did you fix the problem?

http://support.microsoft.com/kb/314106



Thanks for your suggestion.
I have followed the steps, and checked the files,
including config.nt and autoexec.nt .
However, nothing out of place.
Replies Reply to this message
#3 philo
May 15th, 2012 - 04:42 pm ET | Report spam
On 05/15/2012 09:32 AM, Robin Vowels wrote:
On Tuesday, 15 May 2012 10:59:01 UTC+10, philo wrote:
On 05/11/2012 07:53 AM, Robin Vowels wrote:



On Windows XP, this error began occurring from the DOS prompt.
All programs such as EDIT, PKZIP, and other old-style programs
that used to run in DOS on XP suddenly will not run.

Has anyone else experienced this error, and if so,
how did you fix the problem?



http://support.microsoft.com/kb/314106



Thanks for your suggestion.
I have followed the steps, and checked the files,
including config.nt and autoexec.nt .
However, nothing out of place.






I am stumped too

All I can think of is to run System Restore back to a point prior to the
problem

https://www.createspace.com/3707686
Replies Reply to this message
#4 Robin Vowels
May 15th, 2012 - 10:29 pm ET | Report spam
On Wednesday, 16 May 2012 06:42:25 UTC+10, philo wrote:
On 05/15/2012 09:32 AM, Robin Vowels wrote:
> On Tuesday, 15 May 2012 10:59:01 UTC+10, philo wrote:
>> On 05/11/2012 07:53 AM, Robin Vowels wrote:
>
>>> On Windows XP, this error began occurring from the DOS prompt.
>>> All programs such as EDIT, PKZIP, and other old-style programs
>>> that used to run in DOS on XP suddenly will not run.
>>>
>>> Has anyone else experienced this error, and if so,
>>> how did you fix the problem?
>>
>> http://support.microsoft.com/kb/314106
>
> Thanks for your suggestion.
> I have followed the steps, and checked the files,
> including config.nt and autoexec.nt .
> However, nothing out of place.

I am stumped too

All I can think of is to run System Restore back to a point prior to the
problem



I had already done that twice. No change.
Replies Reply to this message
#5 philo
May 17th, 2012 - 07:36 pm ET | Report spam
On 05/15/2012 09:29 PM, Robin Vowels wrote:
On Wednesday, 16 May 2012 06:42:25 UTC+10, philo wrote:
On 05/15/2012 09:32 AM, Robin Vowels wrote:
On Tuesday, 15 May 2012 10:59:01 UTC+10, philo wrote:
On 05/11/2012 07:53 AM, Robin Vowels wrote:



On Windows XP, this error began occurring from the DOS prompt.
All programs such as EDIT, PKZIP, and other old-style programs
that used to run in DOS on XP suddenly will not run.

Has anyone else experienced this error, and if so,
how did you fix the problem?



http://support.microsoft.com/kb/314106



Thanks for your suggestion.
I have followed the steps, and checked the files,
including config.nt and autoexec.nt .
However, nothing out of place.



I am stumped too

All I can think of is to run System Restore back to a point prior to the
problem



I had already done that twice. No change.





Hmmm...
does the machine have any other problems???

If so , try running a RAM test

https://www.createspace.com/3707686
Replies Reply to this message
Help Create a new topicNext page Replies Make a reply
Search Make your own search