Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows Vista / General Topics / April 2007

Tip: Looking for answers? Try searching our database.

Killing CSRSS.exe kills vista!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
theinvisibleGhost - 15 Apr 2007 15:34 GMT
This morning I was having issues with Internet Explorer,
and in Taskmanager requested to be taken to the process
causing the problem.  I know that should be Iexplore.exe but for
some reason it instead went to CSRSS.exe.

Out of frustration I clicked End Process.
I was then shocked to see Vista Blue Screen.

I restarted the machine, and tried the same thing... and it done it
again.
I went up to my XP box and tried on that machine, no can do
CSRSS.exe is a critical process fair enough!
This system's fully up to date with patches as far as I know.
Richard Urban - 15 Apr 2007 15:46 GMT
Thanks for the information. I now know better and will not kill that
process..

Signature

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

> This morning I was having issues with Internet Explorer,
> and in Taskmanager requested to be taken to the process
[quoted text clipped - 9 lines]
> CSRSS.exe is a critical process fair enough!
> This system's fully up to date with patches as far as I know.
Dale M. White - 15 Apr 2007 17:50 GMT
Back in the NT4 days,we we're looking for a way to cause a BSOD because we
wanted to test certain recovery features and such in a cluster environment.
One of the guys found that Killing the CSRSS was a great way to create a
BSOD.

I think it also worked in Win2000, but MS protected it in XP and Win2003.
Nice to see it's back to crashing in Vista.

In short, I would say this is expected behavior.

> This morning I was having issues with Internet Explorer,
> and in Taskmanager requested to be taken to the process
[quoted text clipped - 9 lines]
> CSRSS.exe is a critical process fair enough!
> This system's fully up to date with patches as far as I know.
Dave Horne - 27 Apr 2007 11:36 GMT
So how did you manage to get back into Vista after this?

> This morning I was having issues with Internet Explorer,
> and in Taskmanager requested to be taken to the process
[quoted text clipped - 9 lines]
> CSRSS.exe is a critical process fair enough!
> This system's fully up to date with patches as far as I know.
Dale White - 27 Apr 2007 13:46 GMT
Killing it, just causes a BSOD, system reboots and you are back to runnning

> So how did you manage to get back into Vista after this?
>
[quoted text clipped - 11 lines]
>> CSRSS.exe is a critical process fair enough!
>> This system's fully up to date with patches as far as I know.
Dave Horne - 27 Apr 2007 14:50 GMT
Dale, thanks.  I realized that when I went back and reread the initial post.
(I access this forum from a newsreader and couldn't go back and delete my
post once I realized that.)

> Killing it, just causes a BSOD, system reboots and you are back to
> runnning
[quoted text clipped - 14 lines]
>>> CSRSS.exe is a critical process fair enough!
>>> This system's fully up to date with patches as far as I know.
Dave Wood [MS] - 27 Apr 2007 22:49 GMT
Yes, you can now kill any process with Task Manager, even the ones that will
bring down your machine. At one point Task Manager prevented you from
killing processes like this, but then spyware started giving their processes
the same names to make themselves harder to kill ...

Dave

> Dale, thanks.  I realized that when I went back and reread the initial
> post. (I access this forum from a newsreader and couldn't go back and
[quoted text clipped - 18 lines]
>>>> CSRSS.exe is a critical process fair enough!
>>>> This system's fully up to date with patches as far as I know.
Dale White - 29 Apr 2007 17:50 GMT
And I think that was something that should have always been there or make
the "Kill" command work that way.

I understand protecting the user from the user, but at some point has an
Admin, I should get absolute power over killing a process.

So glad it's back

> Yes, you can now kill any process with Task Manager, even the ones that
> will bring down your machine. At one point Task Manager prevented you from
[quoted text clipped - 25 lines]
>>>>> CSRSS.exe is a critical process fair enough!
>>>>> This system's fully up to date with patches as far as I know.
Dave Wood [MS] - 30 Apr 2007 19:26 GMT
Yes, you can now kill any process with Task Manager, even the ones that will
bring down your machine. At one point Task Manager prevented you from
killing processes like this, but then spyware started giving their processes
the same names to make themselves harder to kill ...

Dave

> Dale, thanks.  I realized that when I went back and reread the initial
> post. (I access this forum from a newsreader and couldn't go back and
[quoted text clipped - 18 lines]
>>>> CSRSS.exe is a critical process fair enough!
>>>> This system's fully up to date with patches as far as I know.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.