We still have STOP 0x000000AB on W2K3 Server with Terminal Services

Hello everybody,

I read http://www.windowsbbs.com/showthread.php?t=44491 (closed) and we do still have the same problem.

Can somebody advice me what we can do to solve this issue ?

Does the last bugfix (privat build) from MS help to avoid the problem ?
Does this bugfix lead to a working hotfix (what is the number of this hotfix) ?

Any help is be greatly appreciated.

 

Hello Arie,

thank you for your reply.

My question was - is there a solution (i.e. from MS) that really works.

Has anybody installed a bugfix that solved this problem and what is
the name/number of this fix ?

Note: We have already installed KB907242 and KB910362 - without an improvement.

 

No news here...

Howdie, olivf.
I have the same problem on four different servers (the same 0xAB error message and the server restarts). Two of them are old Intel servers and two are brand new HP DL360 G4.
A friend once said it is an issue of Symantec antivirus ( I am running Corporate Edition 10) and gave me a key registry to edit, but it did not solved the problem. BTW, I am getting a lot of warnings in the Event Viewer from Symantec Antivirus about not being able to scan all the files, because of lack of memory (the servers have 2GB ...).
More than that, I once gave the dump file to a support guy, and he didn't find anything rellevant in it.
I think I will escalate it to Microsoft.