Sign in
 
HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums

none
Event Id 2017 The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

 > 

    General discussion

  • Discussion
    Sign in to vote
    25
    Sign in to vote
    Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly.  Set the following registry key to ‘1′:

    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

    and set the following registry key to ‘3′:

    HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

    After making these changes and restarting, I haven’t seen this issue arise again

     

    Sunday, February 07, 2010 10:09 PM
    |

All replies

  • Discussion
    Sign in to vote
    1
    Sign in to vote

    Hi,

     

    Thank you for your sharing. I hope this information will benefit some other users who meet the similar issues.

    Nicholas Li - MSFT
    Friday, February 12, 2010 2:51 AM
    |
    Moderator
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    Thanks krbaugh, I was so frustrated with this and hopefully I will not get disconnected on the network again. I have mapped a drive on my XP machine and the software is running on Windows 7 Pro. My XP was accessing all other computers but not the Windows 7. I will post if that error comes back or I get disconnected to access that mapped drive. 
    Friday, March 08, 2013 9:38 PM
    |
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    krbaugh, thank you so much! I had a Windows 7 system that just kept crashing with this event log error. I followed your instructions and it is working great! You are a life saver!

    Lyle Epstein
    Kortek Solutions
    http://www.korteksolutions.com

    Sunday, June 16, 2013 5:16 AM
    |
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    Thank you, thank you, thank you. I had the problem with XP machines being locked out of a Windows 7 pseudo file server that would only resolve with a reboot of the win 7 machine.  A Microsoft engineer advised that I needed to run the 'file server' in safe mode or clean boot mode to try and find what software program was causing the issue.  Luckily I decided instead to just look through the event viewer, and I found this very Event ID at times that I knew the xp machines had been kicked out of the server.  I've just done the registry edit, and fingers crossed, we'll have no further issues with the network.
    Tuesday, August 06, 2013 11:05 PM
    |
  • Discussion
    Sign in to vote
    2
    Sign in to vote
    thank you, excelent....helpful and concise! :)
    Thursday, August 08, 2013 5:50 PM
    |
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    Thanks for taking the time to post this useful information
    Sunday, January 26, 2014 9:08 PM
    |
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    THANK YOUUUUUUU
    Tuesday, January 28, 2014 1:22 PM
    |
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    Funcionou aqui também, muito obrigado.
    Wednesday, July 30, 2014 9:43 PM
    |
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    You are a legend - great solution!
    Thursday, November 12, 2015 7:10 AM
    |
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I wanted to reply to say this post has saved me lots of time. Thank you for posting this five years ago.
    Thursday, January 14, 2016 2:09 PM
    |
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    I knew this needed to be done from prior experience but forgot to note the specifics.  Thanks for the concise, helpful post that Google turned up easily with the search string:

    nonpaged pool allocation limit windows 7

    -Noel

    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options

    Thursday, January 28, 2016 2:36 PM
    |
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Thank you.

    Bonnie Whalon

    Monday, February 22, 2016 11:40 PM
    |
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Thank you so much, it's very helpful.
    Monday, July 25, 2016 6:12 PM
    |
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Thank you krbaugh for your contribution.

    I would just like to add that on a "client" machine this error seams to appear if one has at least one "Maped Network Drive" that dose no longer exist. This is not to be mistaken for a disconnected drive! The client is desperately attempting to reach the drive, which it believes to still be their. I am not sure if the Registry edits you proposed help the client to stop looking for drive(s) that no longer exist. 

    Friday, September 16, 2016 6:00 PM
    |