locked
Fails to validate, but it worked before reformating! RRS feed

  • Question

  • I reformated a few days back, reinstalled all my previous software, and now, 2 days later, this happenes. I am using the same software/hardware I have been using before the reformat, nothing is new what-so-ever. Please help me!

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-VJ2YQ-7C8TG-2BR4P
    Windows Product Key Hash: c9aA2y+cXA6K7dZxBnEfpyikIbM=
    Windows Product ID: 89587-495-4099213-71930
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {6763757D-79F9-448D-B0C3-7CE8189F35D3}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.longhorn_rtm.080118-1840
    TTS Error: M:20100614133924322-
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{6763757D-79F9-448D-B0C3-7CE8189F35D3}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-2BR4P</PKey><PID>89587-495-4099213-71930</PID><PIDType>5</PIDType><SID>S-1-5-21-1820867902-1934256352-3086010841</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1101   </Version><SMBIOSVersion major="2" minor="5"/><Date>20091127000000.000000+000</Date></BIOS><HWID>25313507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>US Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAFAHAAAAAAAAYWECAAAAAACojwIt/wvLARhy9171jCizkdIEkQaJZ64nIzDspYs4HecP4mZu2pNrI4ZXBWFQpTbiu7U48E3jPyd7IPmIgITKmLNv1wD2WLawyLFpRCmbTRTTU5T/uLxm4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeu/tYKJAZL6EXxPRo6NeATf0ibt6ycMmdRfpIMSzK6j3YneyD5iICEypizb9cA9li2sMixaUQpm00U01OU/7i8ZuA5JAndldPsNKjMPTVtZSSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1634, 5) (null): 0xC004D401

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAEAAQABAAAAAgABAAEAln1OzdjEuFQA11YQlpIUr9Zm8vQazfQmrFaOLg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   112709  APIC1514
      FACP   112709  FACP1514
      HPET   112709  OEMHPET0
      MCFG   112709  OEMMCFG
      OEMB   112709  OEMB1514
      INFO   112709  AMDINFO
      NVHD   112709  NVHDCP
      SSDT   A M I   POWERNOW

     

    Monday, June 14, 2010 8:55 PM

Answers

  • "Link_Dead" wrote in message news:292dfdf0-c4b8-44ef-836e-669e56e3ccc4...

    I reformated a few days back, reinstalled all my previous software, and now, 2 days later, this happenes. I am using the same software/hardware I have been using before the reformat, nothing is new what-so-ever. Please help me!

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-VJ2YQ-7C8TG-2BR4P
    Windows Product Key Hash: c9aA2y+cXA6K7dZxBnEfpyikIbM=
    Windows Product ID: 89587-495-4099213-71930
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {6763757D-79F9-448D-B0C3-7CE8189F35D3}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.longhorn_rtm.080118-1840
    TTS Error: M:20100614133924322-
    Validation Diagnostic:
    Resolution Status: N/A

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1634, 5) (null): 0xC004D401

     


    Do you have an Office 2010 install there? - if so, it's either non-legal, TechNet/MSDN, or Beta. The tools haven't yet been updated for O2010.
    You appear to have a Mod Auth Tamper
     
    <quote Darin - forum owner>
    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.
     
    1)    A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occur.
     
     
     
    2)    A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way and is caused by a running program that is incompatible with Vista.
     
     
     
      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.
     
    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).
     
     
     
      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.
     
     
     
       Below I have provided a number of steps to help you identify the program that is causing the tamper:
     
      First, go to http://support.microsoft..com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
     
      Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010     06        07         1630                57984-
     
     
     
    Now that you know the time of the tamper, you can now try to connect that time with a program.
     
    1)    Login to Vista and select the option that launches an Internet Browser
     
    2)    Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter
     
    3)    When asked if you want to Open or Save this file, select Open
     
    4)     In the left hand panel, click Reliability Monitor
     
    5)    Click on the “System Stability Chart” above the date 06/07
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 06/07/2010 "
     
    7)    Look for any program that shows "Application Install" in the 'Activity' column.
     
    8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 06/06, 06/05 and 06/04 (or around the date the issue first occurred)
     
      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
     
     
     
    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
     
    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.
     
    PC Safety:
     
     
     
    </quote>
     
    HTH
    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, June 15, 2010 8:54 AM
    Moderator

All replies

  • "Link_Dead" wrote in message news:292dfdf0-c4b8-44ef-836e-669e56e3ccc4...

    I reformated a few days back, reinstalled all my previous software, and now, 2 days later, this happenes. I am using the same software/hardware I have been using before the reformat, nothing is new what-so-ever. Please help me!

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-VJ2YQ-7C8TG-2BR4P
    Windows Product Key Hash: c9aA2y+cXA6K7dZxBnEfpyikIbM=
    Windows Product ID: 89587-495-4099213-71930
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {6763757D-79F9-448D-B0C3-7CE8189F35D3}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.longhorn_rtm.080118-1840
    TTS Error: M:20100614133924322-
    Validation Diagnostic:
    Resolution Status: N/A

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1634, 5) (null): 0xC004D401

     


    Do you have an Office 2010 install there? - if so, it's either non-legal, TechNet/MSDN, or Beta. The tools haven't yet been updated for O2010.
    You appear to have a Mod Auth Tamper
     
    <quote Darin - forum owner>
    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.
     
    1)    A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occur.
     
     
     
    2)    A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way and is caused by a running program that is incompatible with Vista.
     
     
     
      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.
     
    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).
     
     
     
      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.
     
     
     
       Below I have provided a number of steps to help you identify the program that is causing the tamper:
     
      First, go to http://support.microsoft..com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
     
      Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010     06        07         1630                57984-
     
     
     
    Now that you know the time of the tamper, you can now try to connect that time with a program.
     
    1)    Login to Vista and select the option that launches an Internet Browser
     
    2)    Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter
     
    3)    When asked if you want to Open or Save this file, select Open
     
    4)     In the left hand panel, click Reliability Monitor
     
    5)    Click on the “System Stability Chart” above the date 06/07
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 06/07/2010 "
     
    7)    Look for any program that shows "Application Install" in the 'Activity' column.
     
    8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 06/06, 06/05 and 06/04 (or around the date the issue first occurred)
     
      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
     
     
     
    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
     
    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.
     
    PC Safety:
     
     
     
    </quote>
     
    HTH
    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, June 15, 2010 8:54 AM
    Moderator
  • Hi Noel,

    Please Note that when you post the In Memory Mod-Auth resolution steps, you need to modify the steps to the specific user's Diag.

    Specifically the line:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010     06        07         1630                57984-
     

    For this customer it should read:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010     06        14         1339               24322-

    Here is why:

    TTS Error: M:20100614133924322-

    TTS Error: M:2010 06 14 1339 24322-

    Lastly, any dates listed in the Resolution steps should reflect the date shown in the TTS Error line
    .

    Hope that makes sense,


    Darin MS
    Tuesday, June 15, 2010 9:24 PM
  • "Darin Smith MS" wrote in message news:f29f1681-d841-4b38-94e6-4d253a3a117f...

    Hi Noel,

    Please Note that when you post the In Memory Mod-Auth resolution steps, you need to modify the steps to the specific user's Diag.

    Specifically the line:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010     06        07         1630                57984-
     

    For this customer it should read:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010     06        14         1339               24322-

    Here is why:

    TTS Error: M:20100614133924322-

    TTS Error: M:2010 06 14 1339 24322-

    Lastly, any dates listed in the Resolution steps should reflect the date shown in the TTS Error line

    Hope that makes sense,


    Darin MS

    It does indeed - thanks Darin.
    I missed in copy/pasting that you'd tailored it - I'll see if I can create a generic that isn't too complex.
     

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, June 16, 2010 7:38 AM
    Moderator
  • Hi Noel,

    Here is the template I use (note: Anything in black is meant to be copies/pasted into a post to the customer, anything in blue or orange, is not.  This is also Vista only):

     

    V102 – Mod-Auth: In Memory (aka AppCompat)

     

    Symptoms:

    * From Diagnostic Report: Will show “0xC004C401” after line “Validation Code:” (i.e. Validation Code: C004C401)

    * From Diagnostic Report: Has text after the line “Spsys.log Contents:” (other than 0x80070002)

    * From Diagnostic Report: Shows a timestamp (starting with the letter “M”) after the line “TTS Error:” (i.e.  TTS Error: M:20080226114924778- )

    * From Diagnostic Report: May (or may not) also shows another timestamp, starting with the letter “K”

    * From Diagnostic Report: Does NOT have any files listed under the “File Scan Data-->” line

    * From User: May mention the error “An unauthorized change was made to windows.”

     

    Resolution Steps:

    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.

    1)    A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occur.

     

    2)    A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way and is caused by a running program that is incompatible with Vista.

     

      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.

     

       Below I have provided a number of steps to help you identify the program that is causing the tamper:
     
      First, go to
    http://support.microsoft.com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
     
      Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:
    xxxx          xx        xx           xxxx                     xxxxx[C1] -

     

    Note: I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Kernel Mode tamper may be resolved as well. But a Kernel Mode Tamper can sometime indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm)[v2] 


    Now that you know the time of the tamper, you can now try to connect that time with a program.

    1)    Login to Vista and select the option that launches an Internet Browser

    2)    Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter

    3)    When asked if you want to Open or Save this file, select Open

    4)     In the left hand panel, click Reliability Monitor

    5)    Click on the “System Stability Chart” above the date mm/dd[C3] 

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for mm/dd/yyyy[C4] "

    7)    Look for any program that shows "Application Install" in the 'Activity' column.

    8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates mm/dd, mm/dd and mm/ddC5]  (or around the date the issue first occurred)

      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.

     

    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029

    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

    http://www.microsoft.com/protect/support/default.mspx

    http://onecare.live.com/site/en-us/center/whatsnew.htm

     

     


     [C1]Replace with Customer’s TTS Error Timestamp break down

     [v2]Only include if the customer also has a “K” type TTS  (example:  TTS Error: K:20080226120633039-)

     [C3]Replace with your Customer’s TTS date

     [C4]Replace with your Customer’s TTS date

     [C5]Replace with the 3 dates prior to Customer’s TTS date


    Darin MS
    Wednesday, June 16, 2010 8:53 PM
  • "Darin Smith MS" wrote in message news:d135c2e5-a26e-4691-8fa5-7aff5106225c...

    Hi Noel,

    Here is the template I use (note: Anything in black is meant to be copies/pasted into a post to the customer, anything in blue or orange, is not.  This is also Vista only):

    Many thanks, Darin
    If there's any more you'd like to communicate to me, rather than to the forum, please feel free to use the following email addie

    (I find their spam-filters more efficient than hotmail's <g>)
     
     

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Edited by Darin Smith MS Thursday, June 17, 2010 8:58 PM I have the email address now, so I have deleted it from the post
    Thursday, June 17, 2010 6:21 AM
    Moderator