Question Locked

Windows XP Event ID 2017

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
All of the PCs in my peer-to-peer network have lately been getting event id 2017, which indicates nonpaged memory is no longer available for allocation. This problem seems to have begun after I installed XP fix KBB929338 and manifests itself as a "server memory not available" message. Has anyone experienced this problem? Thanks.

12 replies

by rob miners

that you have installed a fix? KBB929338 dosn't show on the M$ site.

by puzz623

Hi,

I noticed a typo: you presumably meant KB929338. The corresponding MS article is not very forthcoming on your error however....

Paul Robertson

by puzz623

Hi again,

Looking at the MS site, my reading of it is that Event ID 2017 corresponds to Message Queuing issues. There is a lot of synchronised timing involved in MSMQ and I have had some wierd stuff in the past when machine clocks on a network have got out of sync with each other. In the States you guys have just shifted the change to daylight saving and I wondered if it isn't just coincidence that you installed fix 929338 at round about the same time. Do you use MSMQ, and are the clocks tidy?

Paul Robertson

by sissue

Yes we are all experiencing this problem since that update fix from MS. Hmmmm...what's going on....? I know it is MS related...

by robertlbradley

Sorry about the extra "B" in the fix. Thanks for correcting that. No, we are not running MSMQ; I also noticed that issue on the MS site. Event ID 2021 seems to be paired with event ID 2017, but it doesn't add much information. ID 2017 refers to nonpaged memory, which is used by programs that cannot tolerate a page fault. KB929338 made a change to NTOSKRNL to address a memory issue, which is why I suspect it as the cause. Unfortunately, I don't have a restore point before it was installed and removing the fix creates an extremely unstable PC.
Thanks to all who replied.

by puzz623

This is beginning to look like a problem that MS should be solving. What puzzles me is why it not more widespread. Here, update 929338 went in on 2007-03-17 without generating a hitch, but note, this is on the French version of XP Pro. The actual update seems to have been available since 2006-12-20. Have you tried upping the amount of physical memory in a machine in order to see if that alleviates the situation? It's not a solution, but as a diagnostic move it would confirm that you are on the right track. You could set the pagefile size to zero on a test machine.

Other thoughts. Have you successfully installed all subsequent updates? I ask because there may be a hidden correction for your problem in an update that ostensibly addresses another issue. The famous DST one came along after, for example.

Paul Robertson

by robertlbradley

We are running 16 XP machines in a peer-to-peer network. The 929338 fix was applied as part of automatic updates around March 18 on all of them. On every PC that I have checked the 2017 event id starts appearing after that date. The fact that there is an interim of a few days casts some doubt on my theory of the cause. The PC with the least amount of memory is having the most problems. I have installed all available succeeding updates, which only address security issues.
I, too, am curious why this problem may not be more reported. It could be that there is some software, e.g, Avast, that we are already running on all PCs that was impacted by the fix, and the combination is causing the problem. Your suggested test scenario is a good idea. I also plan to run poolmon.exe to monitor the nonpaged pool to determine what is causing the memory links. That should indicate what process or application is creating the problem. I'll keep you posted.
Thanks for your help.

by puzz623

Interesting. I am running Avast on some W2000 machines and that all works real smooth. My XP units have Symantec Corp Ed 9.0 (nope - not the latest) but you could try uninstalling Avast from one machine (and not risking importing a virus obviously). That might point an accusing finger.

Are there any machines into which you could shoehorn 4Gig of memory? Assuming you are 32-bit here, that eliminates any recourse to a page file.

Anyway, the weekend has started here in France. Time to hit the bar. (Sorry.) If I have any further thoughts I'll send them.

The thing that intrigues me the most is the delay of a few days you mention. Might need to look for another event on a subsequent date. For example, was there not a new version of Avast issued not so long ago? Or how about an MS Office update? I have IE7 going in in February but that was by choice. You might have delayed longer....

Paul Robertson

by robertlbradley

I found what is causing this problem. I had recently updated the network backup program to a new release, and everything was running fine. Then I added file filtering to reduce the number of files that I back up. Taking file filtering off permitted the backup to run normally again, which it had not done sine the inception of the problem. Since I was getting event ID 2021, as well as 2017, MS article 317249 addresses the issue. It states that the cause of a 2021 is that "the Server service cannot keep up with the demand for network work items that are queued by the network layer of the I/O stream." I don't why filtering created this problem, but it gives me an avenue to research.

This discussion is closed to new replies.