Discussion:
Blank Blue Screen Lockups
(too old to reply)
Blank Blue Screen Lockups
2005-07-01 18:45:03 UTC
Permalink
Hello,
Recently some of our clients at our compnay have recently experienced Blank
Blue Screens when Alt Tabbing or closing an active terminal service window.
We have about 50 clients that use a Terminal Service based program. They all
run in "Full Screen" Mode, so they often Alt Tab to change between prorams.
Randomly though, a few clients a day (around 3-5) will experience a blank
blue screen when alt tabbing between the windows or even when trying to
closet he active session. It appears their session is locking up as you can
still navitage around the other programs or use the rest of the PC without
issue. But the terminal service window itself freezes.

We have contacted the tech support for the program itself but they are
stumped fully. I don't know if this is a Terminal Service bug. I'm actually
not too familiar with it.
We run Windows 2000 Terminal Services on a Server Running Windows 2000
Advanced Server.

Has anyone experienced a situation like this? Where they can't back out of a
terminal service window, or had random clients that couldn't backout, without
the window freezing up?
Marvin P. Winterbottom
2005-07-05 21:12:03 UTC
Permalink
I used to get it all the time, it was the virus scanner, we finally had to
just remove it. With virus scanning on the mail server, and no internet
access on the TS, it hasn't been a problem.
Patrick
2005-07-05 21:32:02 UTC
Permalink
Interesting...
We Run Symantec Antivirus Corp Edition 9.0, were you perhaps running the
same anti virus? I'll have to take that into a possibility as maybe a cause.
I didn't think of that before.
Post by Marvin P. Winterbottom
I used to get it all the time, it was the virus scanner, we finally had to
just remove it. With virus scanning on the mail server, and no internet
access on the TS, it hasn't been a problem.
Marvin P. Winterbottom
2005-07-06 15:04:10 UTC
Permalink
We had McAfee. Also tried AVG freebee, but it tended to crash the server
when updating itself.
Sung Duc
2005-07-07 03:27:02 UTC
Permalink
Hi All,

We run Symantec Antivirus Client edition 9.0 and don't seem to have any
issues.

Also, our users frequently would Alt Tab to change between different
applications.

Hope you find a fix.

Regards,
Sung
Post by Marvin P. Winterbottom
We had McAfee. Also tried AVG freebee, but it tended to crash the server
when updating itself.
Marvin P. Winterbottom
2005-07-07 13:43:10 UTC
Permalink
Of course, people run antivirus on TS all the time, with no problem, but in
some cases, on some clients, it causes this blue screen hang, I just wish
someone could figure out why, it seems to only happen with win2k server, but
now the world has moved on, so we will never know.
Post by Sung Duc
Hi All,
We run Symantec Antivirus Client edition 9.0 and don't seem to have any
issues.
Also, our users frequently would Alt Tab to change between different
applications.
Hope you find a fix.
Regards,
Sung
Post by Marvin P. Winterbottom
We had McAfee. Also tried AVG freebee, but it tended to crash the server
when updating itself.
unknown
2005-07-19 14:12:52 UTC
Permalink
I had the same problem. I looked high and low for a solution, it took
while but here are my results.: Registry keys under CLSID that thos
sepcific users did not have access rights. In my case, it was a
ACCPAC upgrade I did (tax table) which messed up the users which wer
not part of the ACCPAC group (because they did not use accpac) althoug
ACCPAC was on that server. I had to add them to the ACCPAC group unti
I figure out exactly which keys need be remove from the 3 user
registry that are not required.

I hope this helps.



--
shltechPosted from http://www.pcreview.co.uk/ newsgroup acces
Gilbert
2005-08-04 00:55:02 UTC
Permalink
I have the same problem (blue screen happens only sometimes), I'm running win
2003 server and I was running Symantec antivirus on it... I'll have to try to
remove it and see if it fixes it.
I had the same problem. I looked high and low for a solution, it took a
while but here are my results.: Registry keys under CLSID that those
sepcific users did not have access rights. In my case, it was an
ACCPAC upgrade I did (tax table) which messed up the users which were
not part of the ACCPAC group (because they did not use accpac) although
ACCPAC was on that server. I had to add them to the ACCPAC group until
I figure out exactly which keys need be remove from the 3 users
registry that are not required.
I hope this helps.
J
--
shltechPosted from http://www.pcreview.co.uk/ newsgroup access
Loading...