Windows Server 2003 error

[Simcfc73]

Morning people.

I feel like crap today so I wasn't happy when my server crashed over the weekend and I had to drag myself out of bed to reboot the bloody thing.

Has anyone had this error before.

Event ID 2019

The server was unable to allocate from the system non paged poolbecause the pool was empty.

It killed my server on Sunday morning which is the second time its done it.

I know its something to do with memory not being released by something or other but wondered if I could save a bit of time and see if anyone else has got it.

Only thins that changed on my server is the new version of Sophos EM (I always blame this) and putting on R2.

Thanks

[mrforgetful]

www.eventid.net will explain it more clearly, you need to know the Source as the event id will be reported by a few meaning different things.

[webman]

We've just had this error, too and half our users can't access network services on said server.

ID 2019, Source Srv.

[mrforgetful]

What else do the servers have running?

Looking at eventid.net it seems it could be related to printer drivers, antivirus or any number of other things.

By the way, if you go look on that site and want to follow the links, the M912376 numbers are just Microsoft Knowledgebase articles that you can paste onto the end of a URL after removing the M.

[Geoff]

Memory leak, in a driver or system service.

[Simcfc73]

We break up for summer on Wednesday so I am rebuilding the server. Its had a fair bit of cr@p on it including a failed exchange install so I thik it could do with one.

There were no other errors in the log when it happens and poolmon shows nothing out of the ordinary. It happened at 9am on Saturday so I was stuck.

I'll keep monitoring it till I rebuild but I can't see it happening again.

[PiqueABoo]

I'm got one of those..... 2K3 DC.. no SP, but most MS security hotfixes...

eventid.net didn't help.

Taskman shows three times normal system usage for Kernel Memory(K) -> Paged Pool... seems to be like this fairly soon after a reboot... one of the reskit memory utils suggests the memory has been consumed by some GDI land driver thingy whose Tag is gh05.. and that's as far as I've got...

..my next step is to binary chop all non-essential services.. turn 'em off... restart .. see what happens... it it's ok turn half back on... etc.