Multiple redundant csrss.exe processes cause crash

[Guest oscartheswede]

Hello!

 

Im trying to troubleshoot a problem on a Windows 64x 2003 Server running as

a Terminal Server... Over the course of about two weeks enough redundant

"ghost" csrss.exe processes from former logins remain, slowly building until

the RAM/VRAM runs out resulting in an inevitable IRQL error, which causes the

server to crash. As the csrss.exe is a system process I cannot terminate it

as-it-comes, instead I am forced to schedule continual and repeated reboots

to maintain the csrss.exe process buildup to a minimum...

 

Also...

 

Ive understood that running 32 bit applications on a 64 bit terminal server

is problematic at best, so I took the liberty of looking into the windows

registry and found that two keys were registered under the Wow6432Node:

Microsoft/SQLserver

Microsoft/Weaver/Loom

An "alternate" registry key for both is maintained together with the rest of

the 64 bit keys, and I am unsure of whether or not both the 32 bit keys are

integral for running the 64 bit application as a whole (as i have heard that

it is common for 64 bit applications to have small 32 bit processes

integrated into their architecture)... Does this have anything to do with the

redundant csrss.exe?

 

Any help would be gratefully accepted, at the moment Im feeling pretty lost

as too what to do :/... Im aware of the issues surrounding the use of

Terminal Servers but it is the only relevent solution for our business needs.

Ive done the works with chkdsk etc but havent been able to find the source of

the bothersome 'csrss.exe' processes.

[Guest Mike Douglas]

RE: Multiple redundant csrss.exe processes cause crash

 

Hi There. I run 3 Windows 2003 R2 X64 Enterprise Edition with Service Pack 2

servers. Never seen this issue you have. You fail to mention what service

pack level you are at?

 

Mike D

 

"oscartheswede" wrote:

> Hello!

>

> Im trying to troubleshoot a problem on a Windows 64x 2003 Server running as

> a Terminal Server... Over the course of about two weeks enough redundant

> "ghost" csrss.exe processes from former logins remain, slowly building until

> the RAM/VRAM runs out resulting in an inevitable IRQL error, which causes the

> server to crash. As the csrss.exe is a system process I cannot terminate it

> as-it-comes, instead I am forced to schedule continual and repeated reboots

> to maintain the csrss.exe process buildup to a minimum...

>

> Also...

>

> Ive understood that running 32 bit applications on a 64 bit terminal server

> is problematic at best, so I took the liberty of looking into the windows

> registry and found that two keys were registered under the Wow6432Node:

> Microsoft/SQLserver

> Microsoft/Weaver/Loom

> An "alternate" registry key for both is maintained together with the rest of

> the 64 bit keys, and I am unsure of whether or not both the 32 bit keys are

> integral for running the 64 bit application as a whole (as i have heard that

> it is common for 64 bit applications to have small 32 bit processes

> integrated into their architecture)... Does this have anything to do with the

> redundant csrss.exe?

>

> Any help would be gratefully accepted, at the moment Im feeling pretty lost

> as too what to do :/... Im aware of the issues surrounding the use of

> Terminal Servers but it is the only relevent solution for our business needs.

> Ive done the works with chkdsk etc but havent been able to find the source of

> the bothersome 'csrss.exe' processes.

[Guest Mike Douglas]

RE: Multiple redundant csrss.exe processes cause crash

 

I also forgot to mention I am running Terminal Services on these 3 Servers I

got along with Citrix PS 4.0 X64 Edition.

For every user logged into the server you are suppose to see an instance of

csrss.exe. THis is because the csrss.exe file is part of the log on process.

Now when a user logs off then this process will go away for that user. This

is by design.

Hence the reason why you do not see a lot of these instances of csrss.exe

when no one is logged into the server.

 

Mike D

 

"Mike Douglas" wrote:

> Hi There. I run 3 Windows 2003 R2 X64 Enterprise Edition with Service Pack 2

> servers. Never seen this issue you have. You fail to mention what service

> pack level you are at?

>

> Mike D

>

> "oscartheswede" wrote:

>

> > Hello!

> >

> > Im trying to troubleshoot a problem on a Windows 64x 2003 Server running as

> > a Terminal Server... Over the course of about two weeks enough redundant

> > "ghost" csrss.exe processes from former logins remain, slowly building until

> > the RAM/VRAM runs out resulting in an inevitable IRQL error, which causes the

> > server to crash. As the csrss.exe is a system process I cannot terminate it

> > as-it-comes, instead I am forced to schedule continual and repeated reboots

> > to maintain the csrss.exe process buildup to a minimum...

> >

> > Also...

> >

> > Ive understood that running 32 bit applications on a 64 bit terminal server

> > is problematic at best, so I took the liberty of looking into the windows

> > registry and found that two keys were registered under the Wow6432Node:

> > Microsoft/SQLserver

> > Microsoft/Weaver/Loom

> > An "alternate" registry key for both is maintained together with the rest of

> > the 64 bit keys, and I am unsure of whether or not both the 32 bit keys are

> > integral for running the 64 bit application as a whole (as i have heard that

> > it is common for 64 bit applications to have small 32 bit processes

> > integrated into their architecture)... Does this have anything to do with the

> > redundant csrss.exe?

> >

> > Any help would be gratefully accepted, at the moment Im feeling pretty lost

> > as too what to do :/... Im aware of the issues surrounding the use of

> > Terminal Servers but it is the only relevent solution for our business needs.

> > Ive done the works with chkdsk etc but havent been able to find the source of

> > the bothersome 'csrss.exe' processes.