16-bit error

[Guest]

I'm in a small office with about 250 users. Of those users about 100 are on
Windows 2000 pro workstations, 50 are on Windows NT 4.0 and the rest are on
XP Pro. Recently (in the last week) some of the Windows 2000 pro users have
started to have a strange problem. Out of nowhere they will get a pop
stating that they : Can't run 16-bit Windows Program - Insufficient memory to
run this application. Quit one or more Windows applications and then try
again. This pop up then will respawn over and over again, at about the rate
of one per second until I manually close the NTVDM.EXE process. None of
these users are running any 16 bit processes that would start this. It's not
a virus (that is known) as I have run updated virus scans on all of these
computers (also ran spyware removal tools). I'm baffled and can find no
answers on this. Currently about 12 of my users have this problem. Its easy
to kill, but pops up about 3 or 4 times during the day for each user.

 

[IT Tech Guy]

I'm in a small office with about 250 users. Of those users about 100 are on
Windows 2000 pro workstations, 50 are on Windows NT 4.0 and the rest are on
XP Pro. Recently (in the last week) some of the Windows 2000 pro users have
started to have a strange problem. Out of nowhere they will get a pop
stating that they : Can't run 16-bit Windows Program - Insufficient memory to
run this application. Quit one or more Windows applications and then try
again. This pop up then will respawn over and over again, at about the rate
of one per second until I manually close the NTVDM.EXE process. None of
these users are running any 16 bit processes that would start this. It's not
a virus (that is known) as I have run updated virus scans on all of these
computers (also ran spyware removal tools). I'm baffled and can find no
answers on this. Currently about 12 of my users have this problem. Its easy
to kill, but pops up about 3 or 4 times during the day for each user.

We have had the same problem after running windows update last week.
It appears the problem comes from the updates KB841533 and KB840987.
Uninstalling these updates appear to solve the problem.

 

[Guest]

We have had the same problem after running windows update last week.
It appears the problem comes from the updates KB841533 and KB840987.
Uninstalling these updates appear to solve the problem.

Thanks! I actually found this before I got this response, but I'm grateful
that I received a response. I'm glad to see somebody else had the problem
besides us . . . (well not glad, just reassured more then anything) . . .
Wonder how many others are now experiencing this.

 

[Guest]

I have been having this exact problem on several PCs all running Win2000
seeming just after the users installed some of the Critical Updates. I have
been scouring the web for a couple of weeks and asking all my geek buddies
and so far no answer has shown itself. I'll try removing these patches and
see if it solves our problems as well. Thanks guys.