3.3.3r7: Frequent client BAD_POOL_CALLER blue-screens in Win2k.

[gl]

Plus I forgot (possibly) the most important info - the client that's
blue-screening is a multi-processor machine (Abit BP6 with two Celerons).  I
strongly suspect that SMP is the cause of the problems.
--
gl

----- Original Message -----
From: "gl" <gl "at" ntlworld.com>
To: <vnc-list "at" uk.research.att.com>
Sent: Sunday, June 11, 2000 1:40 AM
Subject: Re: 3.3.3r7: Frequent client BAD_POOL_CALLER blue-screens in Win2k.


> I should have mentioned that both machines are on a local LAN.
> --
> gl
>
> ----- Original Message -----
> From: "gl" <gl "at" ntlworld.com>
> To: <vnc-list "at" uk.research.att.com>
> Sent: Sunday, June 11, 2000 1:37 AM
> Subject: 3.3.3r7: Frequent client BAD_POOL_CALLER blue-screens in Win2k.
>
>
> >
> > I'm running VNC to control a Win2kPro installation from another.  With
> both
> > r2 and r7, I get frequent BAD_POOL_CALLER bluescreens on the machine
> running
> > the client.  Usually the client works fine for a short time, but sooner
or
> > later (usually during mouse or keyboard input), the client will
> blue-screen
> > unexpectedly, with no clear cause.
> >
> > Running the client from Win98 works perfectly... any ideas?
> >
> > Client system: Win2kPro, GeForce (5.22 ref drivers, crashes under other
> > versions too), 1152x864 @ 32bit.
> > Server: Win2kPro, TNT, 800x600 @ 16bit.
> > --
> > gl
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to majordomo "at" uk.research.att.com
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------