Jump to content
is99

Problem with 5.0.200

Recommended Posts

We have version 5 instaled in our network and working more or less ok for a few months.

 

Recently I put the new 5.0.200 package in our administration server.

 

Since then I have a very big problem, I install a clean PC and just after the Install (before office or anything else) I install 5.0.200.

 

In most of the PCs after the first restart I get a blue screen in both normal and safe modes.

 

Even if I disable the kaspersky services from windows recovery mode I still have the problem, also if I reinstall windows over the old one I still have a problem.

 

The only thing that helps is fully reinstall the workstation.

 

Any Ideas what is the problem.

Share this post


Link to post
In most of the PCs after the first restart I get a blue screen in both normal and safe modes.

*Blue screen*

What OS? What does blue screen tell?

give more information.

Share this post


Link to post

Windows XP XP2 Fresh Install

 

I dont know what exactly it writes in the blue screen because it shows the blue screen and after a second restarts.

And I cant log on to windows to change the settings of the windows so that it wont restart after fatal error.

 

 

*Blue screen*

What OS? What does blue screen tell?

give more information.

Share this post


Link to post
I dont know what exactly it writes in the blue screen because it shows the blue screen and after a second restarts.

Then mount your fs and get crash report from c\winnt\bugcheck\ there should be files for every crash.

[Or try winxp last known good configuration or smth to get in normaly.]

Share this post


Link to post

We've had the same problem with our winxp sp2 workstations.

 

On one of your crashing workstations view the boot.ini file (located in the c:\ root). Open it using notepad, it should look something like this:

 

[boot loader]

timeout=0

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=Optin /fastdetect

 

Try and change /noexecute=Optin to /noexecute=AlwaysOff and see if that helps, if the problem isn't solved you can always start the client in the last known good configuration, but if it is the same problem that we had (memory dump when rebooting) it is possible that this fixes the situation...

Share this post


Link to post

The error I'm getting on the blue screen is:

 

stop: c000021 {Fatal system Error}

Share this post


Link to post

I tried to change it and it also desn't help

 

 

 

We've had the same problem with our winxp sp2 workstations.

 

On one of your crashing workstations view the boot.ini file (located in the c:\  root). Open it using notepad, it should look something like this:

 

[boot loader]

timeout=0

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=Optin /fastdetect

 

Try and change /noexecute=Optin to /noexecute=AlwaysOff and see if that helps, if the problem isn't solved you can always start the client in the last known good configuration, but if it is the same problem that we had (memory dump when rebooting) it is possible that this fixes the situation...

Share this post


Link to post
I tried to change it and it also desn't help

If you are l33t, you can debug c\winnt\bugcheck files, to see what exactly wrong.

Or, bugg your local KL support, because it seems that in this forum Moscow KL support

doesn't give a fcuk.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.