KB2694911

When working in Windows, you may revive the following error

Windows Explorer has stopped working. Windows is restarting

Additionally, you may notice the screen flicker just before or after the error message appears.

KB2673371

Consider the following scenario:

  • You enable the following Group Policy settings on a computer that is running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 SP2:

    Computer Configuration\Administrative Templates\Windows Components\Event Log Service\Security\Backup log automatically when full
    Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Audit: Shut down system immediately if unable to log

  • You enable the Archive the log when full, do not overwrite events option in the Security log.
  • The Security log reaches its maximum log size.

In this scenario, the computer crashes. Additionally, you receive the following Stop error message:

0xc0000244 – {Audit Failed}
An attempt to generate a security audit failed.

Note: The expected behavior is that the computer backs up the Security log when the log reaches its maximum size, and the computer does not crash.

KB2675625

A hotfix is available for the following two issues.

Issue 1
Assume Assume that you try to use a Universal Naming Convention (UNC) path to access a network file system (NFS) share from a computer that is running one of the following operating systems:

  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2

The NFS share is hosted on a UNIX-based NFS server. In this situation, you cannot access the NFS share. Additionally, you receive the following error message:

Network error

Issue 2
Assume that you use a UNC path to access an NFS share from a computer that is running one of the following operating systems:

  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2.

The NFS share is hosted on a UNIX-based NFS server. However, when you try to save some files to the NFS share by using an application such as Notepad or Wordpad, you receive the following error message:

Filename not valid

KB2674065

After you install the latest Windows Updates and reboot your computer, you may get the the error below. To fix this, follow the steps in the Resolution section below.

Error: Windows failed to start. A recent hardware or software change might have caused the issue after you install Windows Updates

KB2639793

Consider the following scenario:

  • You join a computer to a network. The computer is running one of the following operating systems:
    • Windows Vista
    • Windows Server 2008
    • Windows 7
    • Windows Server 2008 R2
  • The network is configured to use Internet Protocol security (IPsec) network address translation traversal (NAT-T) security.
  • You use IPsec to communicate with another computer in the network.

In this scenario, you randomly receive a Stop error message that resembles the following, and then the computer restarts:

STOP 0x000000C2 (parameter1, parameter2, parameter3, parameter4)

Notes:

  • This Stop error describes a BAD_POOL_CALLER issue.
  • The four parameters in this error message vary, depending on the configuration of the computer.
  • Not all “0x000000C2” Stop errors are caused by this issue.

KB2592339

When you connect to a computer that is running Windows Server 2008 R2, Windows 7, Windows Vista or Windows Server 2008 by using the RDP protocol, the computer stops responding or you receive the following Stop error message:

STOP: 0x0000007F (0x0000008, parameter2, parameter3, parameter4)

Notes:

  • The parameters in this Stop error message may vary, depending on the configuration of the computer. However, the first parameter is always 0x0000008.
  • Not all “0x0000007F” Stop errors are caused by this issue.

For example, you have deployed a Microsoft Virtual Desktop Infrastructure (VDI) environment in a network. You log on to a virtual machine that is running Windows Server 2008 R2, Windows 7, Windows Vista or Windows Server 2008 in the VDI environment. In this situation, the virtual machine stops responding or you receive the Stop error message.

KB2654668

Consider the following scenario:

  • You install Microsoft Message Queuing (also known as MSMQ) 4.0 on a computer that is running Windows Vista or Windows Server 2008.
  • You create a transactional Message Queuing queue on the computer.
  • You run a client application that performs a transactional remote receive on the queue by using the exclusive access mode.

In this scenario, the client application intermittently receives an error message that resembles the following:

Access denied

Note: This issue occurs even after you restart the application.

KB2655104

A computer that is running an x64-based version of Windows Vista Service Pack 2 (SP2) or of Windows Server 2008 SP2 crashes when you do one of the following:

  • Restart the computer
  • Restart the computer and then access the computer immediately by using Remote Desktop Protocol (RDP)

When this issue occurs, you receive the following Stop error message:

STOP: 0x0000001E : (ffffffffc0000005, fffff8000253254e, 0, ffffffffffffffff)
KMODE_EXCEPTION_NOT_HANDLED

KB2639793

Consider the following scenario:

  • You join a computer that is running Windows Server 2008 or Windows Vista to a network.
  • The network is configured to use Internet Protocol security (IPsec) network address translation traversal (NAT-T) security.
  • You use IPsec to communicate with another computer in the network.

In this scenario, you randomly receive a Stop error message that resembles the following, and then the computer restarts:

STOP 0x000000C2 (parameter1, parameter2, parameter3, parameter4)

Notes:

  • This Stop error describes a BAD_POOL_CALLER issue.
  • The four parameters in this error message vary, depending on the configuration of the computer.
  • Not all “0x000000C2” Stop errors are caused by this issue.