locked
System went into a Tamper State, Spsys.log Content decryption RRS feed

  • Question

  • hey guys, ( i know this is a windows7 board, but the guys over at the windows server2008 boards sent me in this direction

    So we had a server go into a tamper state wiyhout any identifiable cause, however we were able to restart the server and the tamper state cleared, we have ran the Microsoft Genuine Advantage Diagnostic (MGADIAG) tool and are wondering if anyone can decode the output of the spsys encrypted log contents for us so i can help get to root cause on why the file in questions was tampered

    thanks guys!

     

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-*****-*****-removedWindows Product Key Hash: RJPQ1Qy/mcqEApqF2y4kQAUYRJI=
    Windows Product ID: 55041-083-5406686-76971
    Windows Product ID Type: 6
    Windows License Type: Volume MAK
    Windows OS version: 6.0.6001.2.00030510.1.0.017
    ID: {8AC7FE5D-81AC-498A-A76A-064D0A031425}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows (R) Web Server 2008
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.100608-0458
    TTS Error: K:20110208065726981-M:20110207055824501-
    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: B4D0AA8B-543-80070002_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 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Disabled
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Disabled
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Disabled
    Script ActiveX controls marked as safe for scripting: Disabled

    File Scan Data-->
    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{8AC7FE5D-81AC-498A-A76A-064D0A031425}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00030510.1.0.017</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-083-5406686-76971</PID><PIDType>6</PIDType><SID>S-1-5-21-390953604-4046890811-3479441913</SID><SYSTEM><Manufacturer>HP</Manufacturer><Model>ProLiant DL160 G5</Model></SYSTEM><BIOS><Manufacturer>HP</Manufacturer><Version>O12</Version><SMBIOSVersion major="2" minor="5"/><Date>20080822000000.000000+000</Date></BIOS><HWID>53330500018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>1</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: U1BMRwEAAAAAAQAABAAAAFRjEgQAAAAAYWECAATAYoeJTU8Wz8bLARhy9171jCizkdIEkQaJZ64sWgYELK60hEgzzT3bahtBC+/2NH0RtEN4Q3RVcwANQlF0H9Oh+hJEw7XKSAShRbeO1Xm3ZiAqjIia8vVbNXKAdxIbWknBaowHIAW5hNfPOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxX3nN9kyIniwyWL8pSCxW3PHR7ulY5jvzSgmuh/M0ckwy1PxxBZmOO8CWsKMjj4ZTmUWrxbbo2lsCrH1k64ZcijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=+/2NH0RtEN4Q3RVcwANQlF0H9Oh+hJEw7XKSAShRbeO1Xm3ZiAqjIia8vVbNXKAdxIbWknBaowHIAW5hNfPOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxX3nN9kyIniwyWL8pSCxW3PHR7ulY5jvzSgmuh/M0ckwy1PxxBZmOO8CWsKMjj4ZTmUWrxbbo2lsCrH1k64ZcijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

    Friday, March 4, 2011 8:39 PM

Answers

  • "Brett James" wrote in message news:54179fa9-a079-44a1-916a-cbeceb0e8001...

    hey guys, ( i know this is a windows7 board, but the guys over at the windows server2008 boards sent me in this direction

    So we had a server go into a tamper state wiyhout any identifiable cause, however we were able to restart the server and the tamper state cleared, we have ran the Microsoft Genuine Advantage Diagnostic (MGADIAG) tool and are wondering if anyone can decode the output of the spsys encrypted log contents for us so i can help get to root cause on why the file in questions was tampered

    thanks guys!

     

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-*****-*****-removedWindows Product Key Hash: RJPQ1Qy/mcqEApqF2y4kQAUYRJI=
    Windows Product ID: 55041-083-5406686-76971
    Windows Product ID Type: 6
    Windows License Type: Volume MAK
    Windows OS version: 6.0.6001.2.00030510.1.0.017
    ID: {8AC7FE5D-81AC-498A-A76A-064D0A031425}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows (R) Web Server 2008
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.100608-0458
    TTS Error: K:20110208065726981-M:20110207055824501-
    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: B4D0AA8B-543-80070002_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 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Disabled
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Disabled
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Disabled
    Script ActiveX controls marked as safe for scripting: Disabled

    File Scan Data-->
    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{8AC7FE5D-81AC-498A-A76A-064D0A031425}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00030510.1.0.017</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-083-5406686-76971</PID><PIDType>6</PIDType><SID>S-1-5-21-390953604-4046890811-3479441913</SID><SYSTEM><Manufacturer>HP</Manufacturer><Model>ProLiant DL160 G5</Model></SYSTEM><BIOS><Manufacturer>HP</Manufacturer><Version>O12</Version><SMBIOSVersion major="2" minor="5"/><Date>20080822000000.000000+000</Date></BIOS><HWID>53330500018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>1</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: U1BMRwEAAAAAAQAABAAAAFRjEgQAAAAAYWECAATAYoeJTU8Wz8bLARhy9171jCizkdIEkQaJZ64sWgYELK60hEgzzT3bahtBC+/2NH0RtEN4Q3RVcwANQlF0H9Oh+hJEw7XKSAShRbeO1Xm3ZiAqjIia8vVbNXKAdxIbWknBaowHIAW5hNfPOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxX3nN9kyIniwyWL8pSCxW3PHR7ulY5jvzSgmuh/M0ckwy1PxxBZmOO8CWsKMjj4ZTmUWrxbbo2lsCrH1k64ZcijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=+/2NH0RtEN4Q3RVcwANQlF0H9Oh+hJEw7XKSAShRbeO1Xm3ZiAqjIia8vVbNXKAdxIbWknBaowHIAW5hNfPOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxX3nN9kyIniwyWL8pSCxW3PHR7ulY5jvzSgmuh/M0ckwy1PxxBZmOO8CWsKMjj4ZTmUWrxbbo2lsCrH1k64ZcijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=


    You actually have two types of tamper preset - a Kernel Mode tamper, and a Mod Auth tamper
     
    Here's the standard response.....
     
    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 a Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an On Disk Mod-Auth.
     
     
      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:20110207055824501- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2011      02        07                 0558               24501   -
     
     
     
    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 7th Feb 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 7th Feb 2011 "
     
    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 4-6 Feb  (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:
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, March 4, 2011 8:54 PM
    Moderator
  • "Brett James" wrote in message news:c8ef9025-8b4d-4826-8921-1d38aba9b00f...

    hey thanks Noel,

     

    So just to provide a bit of update

    - the server does not have any of the listed software installed that would be problematic from the list on the kb article

    - Checked the reliability monitor, there are no new programs installed on the server that are reported in that interface for two prior

    - there is nothing logged for server or file system instability when viewing through the event view logs.

    - the sever was fine and fully operational after it was restarted and hasnted reappered for the last month at least

    - i am running online virus and malware scans against the server at this time.

    What i am wondering is if a dignosis of the spsys.log file can be done as from what i have read that log should provide some insight as to what is going on with the server. Is there a certain path i need to take to submit that log file for analysys ?


    I don't know if Darin has the tools for this - he may do (he's MS's forum 'owner' for these WGA forums), but I've never seen any evidence of it if so.
    Your best bet is to contact WGA support (it should be free - make sure that you choose options for Activation/Validation/WGA in the dropdowns)
     
    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4
     
    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, March 5, 2011 6:03 AM
    Moderator

All replies

  • "Brett James" wrote in message news:54179fa9-a079-44a1-916a-cbeceb0e8001...

    hey guys, ( i know this is a windows7 board, but the guys over at the windows server2008 boards sent me in this direction

    So we had a server go into a tamper state wiyhout any identifiable cause, however we were able to restart the server and the tamper state cleared, we have ran the Microsoft Genuine Advantage Diagnostic (MGADIAG) tool and are wondering if anyone can decode the output of the spsys encrypted log contents for us so i can help get to root cause on why the file in questions was tampered

    thanks guys!

     

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-*****-*****-removedWindows Product Key Hash: RJPQ1Qy/mcqEApqF2y4kQAUYRJI=
    Windows Product ID: 55041-083-5406686-76971
    Windows Product ID Type: 6
    Windows License Type: Volume MAK
    Windows OS version: 6.0.6001.2.00030510.1.0.017
    ID: {8AC7FE5D-81AC-498A-A76A-064D0A031425}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows (R) Web Server 2008
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.100608-0458
    TTS Error: K:20110208065726981-M:20110207055824501-
    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: B4D0AA8B-543-80070002_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 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Disabled
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Disabled
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Disabled
    Script ActiveX controls marked as safe for scripting: Disabled

    File Scan Data-->
    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{8AC7FE5D-81AC-498A-A76A-064D0A031425}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00030510.1.0.017</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-083-5406686-76971</PID><PIDType>6</PIDType><SID>S-1-5-21-390953604-4046890811-3479441913</SID><SYSTEM><Manufacturer>HP</Manufacturer><Model>ProLiant DL160 G5</Model></SYSTEM><BIOS><Manufacturer>HP</Manufacturer><Version>O12</Version><SMBIOSVersion major="2" minor="5"/><Date>20080822000000.000000+000</Date></BIOS><HWID>53330500018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>1</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: U1BMRwEAAAAAAQAABAAAAFRjEgQAAAAAYWECAATAYoeJTU8Wz8bLARhy9171jCizkdIEkQaJZ64sWgYELK60hEgzzT3bahtBC+/2NH0RtEN4Q3RVcwANQlF0H9Oh+hJEw7XKSAShRbeO1Xm3ZiAqjIia8vVbNXKAdxIbWknBaowHIAW5hNfPOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxX3nN9kyIniwyWL8pSCxW3PHR7ulY5jvzSgmuh/M0ckwy1PxxBZmOO8CWsKMjj4ZTmUWrxbbo2lsCrH1k64ZcijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=+/2NH0RtEN4Q3RVcwANQlF0H9Oh+hJEw7XKSAShRbeO1Xm3ZiAqjIia8vVbNXKAdxIbWknBaowHIAW5hNfPOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxX3nN9kyIniwyWL8pSCxW3PHR7ulY5jvzSgmuh/M0ckwy1PxxBZmOO8CWsKMjj4ZTmUWrxbbo2lsCrH1k64ZcijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=


    You actually have two types of tamper preset - a Kernel Mode tamper, and a Mod Auth tamper
     
    Here's the standard response.....
     
    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 a Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an On Disk Mod-Auth.
     
     
      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:20110207055824501- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2011      02        07                 0558               24501   -
     
     
     
    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 7th Feb 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 7th Feb 2011 "
     
    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 4-6 Feb  (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:
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, March 4, 2011 8:54 PM
    Moderator
  • hey thanks Noel,

     

    So just to provide a bit of update

    - the server does not have any of the listed software installed that would be problematic from the list on the kb article

    - Checked the reliability monitor, there are no new programs installed on the server that are reported in that interface for two prior

    - there is nothing logged for server or file system instability when viewing through the event view logs.

    - the sever was fine and fully operational after it was restarted and hasnted reappered for the last month at least

    - i am running online virus and malware scans against the server at this time.

    What i am wondering is if a dignosis of the spsys.log file can be done as from what i have read that log should provide some insight as to what is going on with the server. Is there a certain path i need to take to submit that log file for analysys ?

    Friday, March 4, 2011 11:05 PM
  • "Brett James" wrote in message news:c8ef9025-8b4d-4826-8921-1d38aba9b00f...

    hey thanks Noel,

     

    So just to provide a bit of update

    - the server does not have any of the listed software installed that would be problematic from the list on the kb article

    - Checked the reliability monitor, there are no new programs installed on the server that are reported in that interface for two prior

    - there is nothing logged for server or file system instability when viewing through the event view logs.

    - the sever was fine and fully operational after it was restarted and hasnted reappered for the last month at least

    - i am running online virus and malware scans against the server at this time.

    What i am wondering is if a dignosis of the spsys.log file can be done as from what i have read that log should provide some insight as to what is going on with the server. Is there a certain path i need to take to submit that log file for analysys ?


    I don't know if Darin has the tools for this - he may do (he's MS's forum 'owner' for these WGA forums), but I've never seen any evidence of it if so.
    Your best bet is to contact WGA support (it should be free - make sure that you choose options for Activation/Validation/WGA in the dropdowns)
     
    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4
     
    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, March 5, 2011 6:03 AM
    Moderator
  • Thanks Noel, i appreciate it, i will follow up with WGA support, i did a full virus and malware scan and it came up clean on the results.
    Monday, March 7, 2011 11:03 PM