The server was unable to allocate from the system paged pool

[russdev]

ok having following problem

 

http://support.microsoft.com/?kbid=822219&SD=tech

 

it then basicly causes network to run to stop

 

in kb article it talks about "To disable opportunistic locking on the server, set the following registry value to 0:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\EnableOplocks"

 

is that is ok to do will it have any other adverse effects at moment want to keep system running then will look at why it is doing it.

 

any advice

 

cheers

 

Russ

[Geoff]

There's a driver or service leaking kernel memory. You need to run poolmon.exe to find hte culprit. (poolmon.exe is in the w2k3 support tools).

 

http://support.microsoft.com/kb/q177415/

 

Usually its either a dodgy hardware driver, antivirus software or backup software in my experience.

[russdev]

but question is how do you work out what is causing it using poolmon

 

russ

[Geoff]

Did you enable pool tagging like the KB article said?

[russdev]

yer did that ran poolmon but is specific what i am looking for probabaly missing obvious

 

russ

[Geoff]

your looking for a tag that's eating all your pool memory.

[russdev]

ok here is log file from poolmon anyideas

 

Russ

mem2.txt

[Geoff]

Looks ok to me.

[russdev]

ok did this just after i restarted server after it crashed going to have to go back to drawing board and work through event logs again.

 

Russ

[russdev]

thought you would be interested to know we think it is...

 

was really obvious running out of room on c drive where page file was....

 

so we have moved page file to g drive

 

 

Russ

[RobC]

Thought it was always good practise to have the server's Paging File on a different physical drive anyway...

 

Certainly what I do on my servers (the ones that Fujitsu don't own, at least).