Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 0 Source: PNPMEM

Failed to add memory range starting at 0x40000000 for 0x40000000 bytes. This operation exceeded the maximum memory capacity of the operating system or the server is not configured to support dynamic memory operations.
You may experience this problem when you hot-add random access memory (RAM) to a Microsoft Windows Server 2003-based computer that has the Hot Add Memory feature enabled. The additional memory is unavailable to Windows. See ME922095 to find out how you can solve this problem.
Just insert the /PAE switch in the boot.ini file. See ME283037 for information on how to use Physical Address Extension (PAE) to take advantage of physical memory beyond 4 GB.
This event is raised when you hot-add memory to a server that fully supports hot-add memory functionality. This behavior occurs only if the /3GB switch is enabled in the Boot.ini file. If the /3GB switch is not present, hot-add memory (for example, RAM) is correctly added to the total physical memory pool that is available to Windows. See ME822842 to troubleshoot this problem.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.