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. November 15th, 2011 at 19:04 | #1

    Unbelievable! I was running into this issue using Mac OS X 10.7.2 (Lion) when copying files from my mac to my windows 7 PC. Finder gave me Error 36 all the time when copying big files!
    Check this Thread for detailed info!
    https://discussions.apple.com/message/16660147
    Thank you a 100 times!

  2. Mark
    November 15th, 2011 at 21:27 | #2

    +1… thanks!

  3. XSeb74
    November 25th, 2011 at 04:16 | #3

    Great thanks !

  4. November 28th, 2011 at 05:53 | #4

    We (have to) use this fix with every new install.

    Thanks a million!

  5. Doug
    November 30th, 2011 at 11:56 | #5

    Thank you, thank you. This issue hit me when I upgraded my home network to gigabit. Silly MS.

  6. December 12th, 2011 at 09:28 | #6

    Thanks a lot for the solution. It gave me headaches.
    Regards,

  7. Michael
    January 3rd, 2012 at 13:09 | #7

    OMG….THANK YOU! totally worked for me…now OSX 10.6.8 and 10.7.2 both see SMB network shares from Vista64 machines. I thought SMB was not included with Lion, but EVERYTHING WORKS!!!

  8. January 5th, 2012 at 15:03 | #8

    Excellent! Just what I needed. Thanks!

  9. Tom
    January 13th, 2012 at 10:39 | #9

    You the man!!!! Thanks for the timely tip – saved me hours of heartburn….Tom

  10. astromb
    January 15th, 2012 at 09:47 | #10

    Thanks a lot ! It’s works now !

Comment pages
1 2 3 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