Updated (New Hotfixes):
-kb976883: http://support.microsoft.com/default...b;en-us;976883
-If, via msconfig, you have disabled some start-up programs, and then subsequently you decide to re-enable them; and inspite of re-enabling them again, you find that they do not start up at boot time, then this may interest you:
http://support.microsoft.com/kb/982591/en-us
---------------------------------------------
-kb981214:
Consider the following scenario.
- You have a computer that is running Windows Vista, Windows Server 2008, Windows Server 2008 R2 or Windows 7.
- You connect a full-speed USB 2.0 audio device to a high-speed hub, and then connect this hub to the root hub on the computer.
- You start an audio playback or recording program, such as Sound Recorder. This program opens the USB audio device.
In this scenario, you notice that there is high CPU usage approximately every 15 seconds on the computer. Additionally, you may experience skipping in audio playback from the audio device when overall CPU usage reaches 100%.
Cause:
This problem occurs because of an issue in the usbport.sys
driver.
http://support.microsoft.com/kb/981214/en-us
---------------------------------------------
-kb951418:
On a computer that is running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2, you receive the following Stop error message:
STOP 0x00000050 (parameter1, parameter2, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA
Notes - The parameters in this error message vary, depending on the configuration of the computer.
- Not all "Stop 0x00000050" errors are caused by this problem. This issue occurs when the Server service handles some SMB requests from some remote computers.
Cause:
This issue occurs because of a timing issue in the Server service
driver. This timing issue involves the operation that adds a new SMB session to the global session table and the operation that closes an SMB session. In this timing issue, the Server service
driver synchronizes these operations incorrectly. When this behavior occurs, an SMB session is added to the global session table after the session is deleted. Therefore, an entry in the global session table references freed memory. When the freed memory is accessed, you receive the Stop error message that is mentioned in the "Symptoms" section.
http://support.microsoft.com/kb/951418/en-us
---------------------------------------------
-kb977589
Consider the following scenario:
- An application or a service queries the HKEY_PERFORMANCE_DATA registry key for the value name GLOBAL on a computer that is running Windows Server 2008, Windows Vista, Windows Server 2008 R2, or Windows 7.
- The application or service enumerates the returned performance objects that are provided by the WmiApRpl.dll module. The number of performance objects that are to be accessed is determined by using the value of the NumObjectTypes variable in the returned PERF_DATA_BLOCK data.
In this scenario, the value of the NumObjectTypes variable may become larger than the actual number of performance objects in the buffer. When this occurs, the application or the service tries to read past the end of the buffer. This behavior causes an access violation exception, and then the application or the service crashes.
Cause:
This issue occurs because of an issue in the Windows Management Instrumentation (WMI) implementation. The issue causes the functions that are in Wmiaprpl.dll module to return an incorrect performance object number. Therefore, an access violation exception occurs, and the application or the service crashes.
http://support.microsoft.com/kb/977589/en-us
---------------------------------------------
-kb981096
You use the following performance counters to monitor the C-states of a processor on a computer that is running Windows Server 2008 R2 or Windows 7.
- Processor\%C1 Time
- Processor\%C2 Time
- Processor\%C3 Time
However, the collected data does not contain correct information for the current C-state of the processor.
For example, consider the following scenario:
- You have a computer that is running Windows Server 2008 R2 or Windows 7. This computer has an Intel Core i7 Nehalem processor.
- The collected data indicates that the processor is in the C2 state.
In this scenario, the current C-state data is incorrect, and the correct C-state is the
C3 state or the
C1 state.
Cause:
This issue occurs because the operating system uses the index of the C-state table instead of the state type variable when it collects the performance counter data for C-states. Therefore, the second entry in the C-state table is assumed to contain the data for the
C2 state. However, the second entry in the C-state table is the
C3 state on some processors such as Intel Core i7 Nehalem processors. Therefore, the C-state data is collected incorrectly.
http://support.microsoft.com/kb/981096/en-us