Entrar
 
HomeBibliotecaWikiAprenderGaleriaDownloadsSuporte ComunidadeFóruns
Recursos para Profissionais de TI >
> 
> 
Ntoskrnl.exe Consuming System Resources on Windows Server 2008 R2

建议的答复 Ntoskrnl.exe Consuming System Resources on Windows Server 2008 R2

  • domingo, 15 de abril de 2012 02:29
     
     
    Entrar para Votar
    0
    The past two days, we experienced very slow responding Windows Server 2008 R2 systems. They each have the ntoskrnl.exe consuming all of the system resources. If I restart the server then let it run for a few hours, the systems seem to return to normal. All of the articles found on the web predate SP1. Can someone give me some suggestions on this issue? Nothing has changed on these systems for several months.

    Jason

     

Todas as Respostas

  • domingo, 15 de abril de 2012 05:51
     
     Resposta Proposta
    Entrar para Votar
    0

    To narrow down the problem and to know whats causing NTOSKRNL.EXE is consuming system resources you may try using using the process explorer 

    http://technet.microsoft.com/en-us/sysinternals/bb896653

    In addition to the above suggestion I strongly advice to stop the Av and give a clean boot.

    http://www.windowsmaven.com/How_to_Clean_Boot_with_msconfig.htm

    http://www.arabitpro.com

     
  • domingo, 15 de abril de 2012 20:05
     
     Resposta Proposta
    Entrar para Votar
    0

    Hello,

    Process Monitor is the option to go for monitoring processes like Syed already mentioned.

    Please proceed like that:

    • Update all possible drivers
    • Uninstall all unused programs
    • Perform a clean boot: http://support.microsoft.com/kb/929135
    • Run chkdsk /r /f and sfc /scannow
    • Disable temporary all security softwares you have
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

     
  • segunda-feira, 16 de abril de 2012 06:36
    Moderador
     
     
    Entrar para Votar
    0

    Hi,

     

    I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help.

    Regards,

    Arthur Li

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Arthur Li

    TechNet Community Support

     
  • segunda-feira, 16 de abril de 2012 16:04
     
     
    Entrar para Votar
    0
    Thanks for all of the replys. I am still investigating this issue and hope to reproduce by restarting one of the DR servers.

    Jason

     
  • terça-feira, 24 de abril de 2012 15:24
     
     
    Entrar para Votar
    0
    Thanks for all of the updates but I have been unable to reproduce the issue at this time even after a restart of the server. I will continue to monitor.

    Jason

     
  • segunda-feira, 14 de maio de 2012 15:33
     
     
    Entrar para Votar
    0
    One thing I have noticed that every server where I have seen this issue are VMs on VMware. Will this make a difference?

    Jason

     
  • segunda-feira, 14 de maio de 2012 17:36
     
     
    Entrar para Votar
    0

    The Process Mon didn't do much good this morning but I did find this link which looks interesting. If anyone is still monitoring this thread, it appears Microsoft is aware of this issue. This is a link I found below and MS recently released a patch for this issue back in April.

    http://aidinit.com/2012/04/ntoskrnl-exe-pre-service-pack-3-revision-history-for-windows-server-2008-sp2-and-windows-small-business-server-2008-sbs-2008/

    Jason