When you install the 2007 Office system on a Windows Vista based computer, the following event is logged in the Application log:

Log Name: Application
Source: VSS
Date: DateTime
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ComputerName
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {51ff0833-99d7-4f35-b8f9-0495ceff2a24}

Additionally, the same event may be logged when you uninstall the 2007 Office system.

When you use the Binary protocol or the Tagged Binary Core Protocol (TBCP) to print from a PostScript printer on a Windows Vista-based computer, the Printer Spooler service stops responding. Or, the print application closes with an error message. Additionally, the following event is logged in the Application log:

Source: Application Error
Event ID: 1000
Information: Faulting application printdrvstress.exe, version 6.0.6000.16386, time stamp 0×454a010d, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0×4549bdc9, exception code 0×80000003, fault offset 0×00042ea8, process id 0×36c, application start time 0×01c74c0a5dea560b.

After you install Windows Vista Service Pack 1 (SP1), the following WMI error is logged in the Application log:

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 1/18/2008 2:37:27 PM
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
Description: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
    <EventID Qualifiers="49152">10</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-18T22:37:27.000Z" />
    <EventRecordID>187</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>adsd-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>//./root/CIMV2</Data>
    <Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage &gt; 99</Data>
    <Data>0x80041003</Data>
  </EventData>
</Event>

Consider the following scenario:

• You are using a Trusted Platform Module (TPM) chip on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 (SP1).
• You put the computer to sleep, and then you resume it from sleep.

In this scenario, the following errors may be logged in the System log every 40 minutes:

Event ID: 13
Event Source: TPM
Event Type: Error
Event Description: The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer.

Event ID: 516
Event Source: TBS
Event Type: Error
Event Description: An error occurred while communicating with the TPM. The driver returned 0×8007045d.

The TPM driver and the TPM Base Services (TBS) log these errors when they try to obtain a random number from the TPM chip for the Windows operating system. The operating system uses this random number as an additional source of entropy when the operating system’s cryptographic methods generate random numbers.

Additionally, if the TBS sends other commands to the TPM chip after the computer resumes from sleep and if the operating system receives a “TPM_NEEDS_SELFTEST” response from the TPM, the operating system may be unable to use the TPM chip to generate random numbers for additional entropy.