Event id 333 is generally caused because of one of the following reasons -
• There is memory pressure either Physical (Physical ram, virtual memory, Working Set trimming, pagefile, and etc) or Kernel (low paged/nonpaged pool/system Page Table Entries).
• The disk hosting on the system partition is not keeping up with the load (high disk queue lengths).
• A filter driver is keeping the registry from being flushed.
• A User account granted the “Lock system pages in memory” user right.
Please check for any other event ids on the server like 2019,2020,2012,2021,2022 in the system event logs.
They might not be viible since the events are already being flooded.
Please tweak the paged pool memory by making the following registry changes - Microsoft KB312362
http://support.microsoft.com/default.aspx?scid=kb;EN-US;312362
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management
PoolUsageMaximum = 40
PagedPoolSize = FFFFFFFF
Also disable the TCP Chimney Feature by the following command -- Netsh int ip set chimney DISABLED
Made sure we have the following registry keys created -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
"EnableTCPA"=dword:00000000
"EnableRSS"=dword:00000000
"DisableTaskOffload"=dword:00000001
Reboot the server after making these changes and then test. You may want to clear the eventlogs.