Home > Tech, Windows > Windows 7 Nonpaged Pool Srv Error 2017

Windows 7 Nonpaged Pool Srv Error 2017

I’m using my Windows 7 machine as a file server in addition to it being my Media Center. I’m mounting a Samba (smb) share using CIFS from my Linux server so I can synchronize files using rsync.  However, I ran into a problem after using the mounted share for a small amount of time.  I found a simple solution after a bit of research.

After running rsync for a short amount of time, I discovered that I was getting memory allocation errors related to the Windows share.  After unmounting, I attempted to remount the share and received the error:

mount error(12): Cannot allocate memory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

After checking the Event Viewer System log, I found the following error:

Source: srv
Event ID: 2017
Level: Error
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

Some research led me to find this Google Groups discussion about the problem and this Microsoft Technet article discussing the solution (look at the bottom of the page).  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.  Fixed!

Update (2011/9/16): I had no idea this fix would end up being so popular when I wrote it up.  It is easily the most visited page on this site.  The original Technet article seems to be gone now, but a commenter has pointed me to a text file that contains the same content.  Here is the link: http://www.decuslib.com/decus/vmslt99a/nt/tips.txt

  1. Random user
    March 28th, 2014 at 07:54 | #1

    Note!
    Works without changing value to LargeSystemCache.
    Also IF YOU CHANGE IT, it makes network drives considerably slower.

    Took a good amount of time to troubleshoot this issue. And i had only about 8GB in my net drives. I would not want to try with drives over 100GB.

  2. Barton
    June 2nd, 2014 at 01:39 | #2

    Thank you! “Random user” is due much thanks as well. Great tips, both of you.

  3. Dave
    September 6th, 2014 at 16:15 | #3

    Thanks so much for this post!!! You have posted the solution to something that has been impacting me for so long.
    You would think MS should default to LargeSystemCache=3, otherwise this is a bug.

Comment pages
1 3 4 5 444
  1. July 21st, 2010 at 13:24 | #1
  2. August 3rd, 2010 at 03:46 | #2
  3. August 5th, 2010 at 17:33 | #3
  4. October 16th, 2010 at 14:21 | #4
  5. November 13th, 2010 at 12:39 | #5
  6. December 13th, 2010 at 06:46 | #6
  7. January 12th, 2011 at 10:38 | #7
  8. January 14th, 2011 at 06:41 | #8
  9. January 27th, 2011 at 02:16 | #9
  10. January 27th, 2011 at 19:40 | #10
  11. February 6th, 2011 at 08:50 | #11
  12. March 3rd, 2011 at 07:11 | #12
  13. April 10th, 2011 at 11:22 | #13
  14. April 20th, 2011 at 05:34 | #14
  15. July 10th, 2011 at 17:13 | #15
  16. October 2nd, 2011 at 08:21 | #16
  17. November 7th, 2011 at 14:30 | #17
  18. January 21st, 2012 at 09:02 | #18
  19. February 15th, 2012 at 09:31 | #19
  20. February 26th, 2012 at 08:34 | #20
  21. March 20th, 2012 at 05:45 | #21
  22. June 27th, 2012 at 09:58 | #22
  23. July 7th, 2012 at 23:53 | #23
  24. July 23rd, 2012 at 07:22 | #24
  25. October 27th, 2012 at 10:54 | #25
  26. November 23rd, 2012 at 01:40 | #26
  27. February 12th, 2013 at 23:07 | #27
  28. March 9th, 2013 at 04:56 | #28
  29. April 21st, 2013 at 09:45 | #29
  30. June 14th, 2013 at 09:04 | #30
  31. July 14th, 2013 at 13:35 | #31
  32. September 6th, 2013 at 07:52 | #32
  33. September 6th, 2013 at 09:13 | #33
  34. October 28th, 2013 at 04:36 | #34
  35. January 16th, 2014 at 20:13 | #35
  36. February 19th, 2014 at 13:35 | #36
  37. February 21st, 2014 at 11:10 | #37
  38. September 9th, 2014 at 02:16 | #38
  39. September 20th, 2014 at 09:40 | #39