The kernel memory dump file includes contents of memory allocated to the Executive, Kernel, Hardware Abstraction Layer (HAL), and file system cache, in addition to nonpaged pool memory allocated to kernel-mode drivers and other kernel-mode routines. The kernel memory dump file records only kernel memory contents and its size varies (several megabytes) but it is always less than the size of the system memory. Also, it takes longer to create than a small dump file and this increases the downtime associated with a system failure.
The Windows registry editor allows you to access certain configuration settings that may be unavailable from the GUI. Some knowledgeable users enjoy tweaking the registry for the fun of it but others do it to troubleshoot various problems. However, I must remind you that the registry contains low-level operating system components that if incorrectly set or accidentally deleted can result in your computer not starting properly! However, you can restore the registry using the Last Known Good Configuration option found in the boot up process.
Windows Management Instrumentation (WMI) allows you to write scripts and expose information about a Windows 7 resource or service. As we have seen in the previous post – Windows Management Instrumentation (WMI), WMI allows you to access system management information from the command-line interface! WMI can become handy when you need to retrieve specific information which may be not available from the GUI. Mastering the WMI command line utility may turn you into command line freak never wanting to leave the command line.
Windows Management Instrumentation (WMI) allows you to write scripts that configure performance settings and resolve performance issues. System performance is dependant on many factors and settings, and the amount of resources every service or process consumes. With WMI, you can write scripts that manage event logs, file systems, printers, processes, registry settings, scheduled tasks, security, services, shared folders, etc. WMI scripts can monitor and respond to entries in the event log, modifications to the file system or the registry, and other real-time operating system changes.
A memory dump during a crash of Windows 7 will fail if your system drive (%SystemRoot%) has less than 25GB of free space! Memory dumps help you diagnose crash issues and it is always recommended to allow enough free space on your system drive for debugging information to be logged and for better overall performance. You can set the dump file to be stored on a different local drive with ample storage space or disable this feature, but in cases where this is not possible and regardless of free space, you can force Windows 7 to create a dump file using the following new registry entry:
Do you know which tool to use when applications and services running on Windows 7 encounter problems? The tools provided by Windows 7 can help you monitor resources, establish baselines and logs, and determine where problems might occur. Sometimes, you may need to further configure these tools or create basic scripts to address your particular problem. In this post you will find a brief overview of the various monitoring and performance tools available with your Windows 7 operating system.
You can configure several Windows Update settings using the Local Group Policy Editor that you cannot configure using the Windows Update control panel. For instance, you can configure your computer to wake if it is in hibernation when the assigned automatic update period occurs or allow updates to install automatically if they do not require a restart as shown in the following steps: