locked
"Error: 0xC004D401" Says "An unauthorized change was made to Windows....The security processor reported a system file mismatch error." RRS feed

  • Question

  • I recently thought I had laptop problems, so the first thing I did was remove my hard drive and plug into my desktop to "recover" my data.  The laptop is running Vista Business and my desktop is XP Pro.  After jumping through many hoops, I managed to recover my data and copy to another hard drive on my desktop.  I then replaced the laptop drive back and started the system.  As if by magic, all the errors I had seemed to have dissappeared with the exception of my internal wireless NIC stopped functioning.  My laptop HD is 160 gig but the "D" partition seems to have dissappeared.  Then I started getting the error messages and was told that my copy of Vista was not legal.  here are the results of the test I performed after spending countless hours researching my troubles:

    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50

    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-R7X4H-6F2XJ-VVMP9
    Windows Product Key Hash: UqxyryRKzOt7kYPGi0qReynjiPg=
    Windows Product ID: 89576-OEM-7332141-00216
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010100.0.0.006
    ID: {CB21F664-A86D-40AA-AAEE-20B1DE93E0D2}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Business
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.091208-0542
    TTS Error: K:20100402074754620-M:20100401110258691-
    Validation Diagnostic:
    Resolution Status: N/A

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

    WGA 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-604-645_B4D0AA8B-604-645_B4D0AA8B-604-645_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: 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>{CB21F664-A86D-40AA-AAEE-20B1DE93E0D2}

    </UGUID><Version>1.9.0019.0</Version><OS>6.0.6000.2.00010100.0.0.006</OS><Architecture>x32</Architecture><PKey>*****-

    *****-*****-*****-VVMP9</PKey><PID>89576-OEM-7332141-00216</PID><PIDType>2</PIDType><SID>S-1-5-21-3174999860-

    2027271585-1959557450</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc. </Manufacturer><Model>A8JS               

    </Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>A8JsvAS.213

    </Version><SMBIOSVersion major="2"

    minor="3"/><Date>20070302000000.000000+000</Date></BIOS><HWID>69323507018400FA</HWID><UserLCID>0409</UserLCID

    ><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)

    </TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>_

    ASUS_</OEMID><OEMTableID>Notebook</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109

    </Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content:

    U1BMRwEAAAAAAQAABAAAAIpJAAAAAAAAYWECADAgAAC53WB3eM/KARhDs/4hWdo7Xkl9D+HKpnjcc3ahBU0H4tK09osCsq+pFy

    waDVMXFuFqYAd3G0Tz6OfDvX0zCybmDilyQLttVIyNh70lYQ6qfw+J5b0kd5dEsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaT

    BgAm18BkdJTE0EGACwl7dV9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j

    0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQU

    QT0Z8agiLrXa3AJ/Jdo3jJaZmuzHEwPR1zCMFR3s9Q2NVqJZDSgGFbLRYyF4kXUOtDeDOhV0f2QVaQQPYN5MZx6vU/ApvDOQ1ifb1s

    tzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ

    9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwz

    kNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIi612twCfyXaN4yWmZrsxxO00frALCVLNACw3Rs8hLWFBhWy0WMheJF1DrQ3gzo

    VdH9kFWkED2DeTGcer1PwKbwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfs

    N1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stz

    rqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCIutdrcAn8l2jeMlpma7McTtNH6wCwl

    SzQAsN0bPIS1hQYVstFjIXiRdQ60N4M6FXR/ZBVpBA9g3kxnHq9T8Cm8M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkN

    Yn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1o

    DDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0

    Z8agiLrXa3AJ/Jdo3jJaZmuzHE7TR+sAsJUs0ALDdGzyEtYUGFbLRYyF4kXUOtDeDOhV0f2QVaQQPYN5MZx6vU/ApvDOQ1ifb1stzrqx+

    w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy

    3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn

    29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIi612twCfyXaN4yWmZrsxxO00frALCVLNACw3Rs8hLWFBhWy0WMheJF1DrQ3gzoVdH9

    kFWkED2DeTGcer1PwKbwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jW

    gMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w

    3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCIutdrcAn8l2jeMlpma7McTtNH6wCwlSzQAs

    N0bPIS1hQYVstFjIXiRdQ60N4M6FXR/ZBVpBA9g3kxnHq9T8Cm8M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29b

    Lc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ

    1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiLr

    Xa3AJ/Jdo3jJaZmuzHE7TR+sAsJUs0ALDdGzyEtYUGFbLRYyF4kXUOtDeDOhV0f2QVaQQPYN5MZx6vU/ApvDOQ1ifb1stzrqx+w3WNa

    AwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7

    DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc6

    6sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeGQWgC+FIV9vM6i293OblhwBYiSCOehmbHX362KZybJFUXQf06H6EkTDtcpIBKFFtzpC4DcJoT2

    SO2v742lFn4fWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXFlyAkTu8DL2SS7xOUXjklamxsmKxy8

    BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn

    29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhDs/4hWdo7Xkl9D+HKpngEyO3/7ElIe7jEslMrowPUwHQ3VrGdfBGmfd9/VDAE4VF0

    H9Oh+hJEw7XKSAShRbe29MS7FN0RVWqZLwWofYgW1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAH

    nVxZcgJE7vAy9kku8TlF45JWpsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3

    WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agidL8RJzUfoLHUm

    DZmO1r5KTuKiyg6Ylu922WSnMv8aOHuAOWVzSada/b8tYXhaAfKf2QVaQQPYN5MZx6vU/ApvDOQ1ifb1stzrqx+w3WNaAwzkNYn29bL

    c66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1i

    fb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbho

    bX8Udqx20FEE9GfGoInS/ESc1H6Cx1Jg2Zjta+SleJrE9bcnJJbbxd8xR1LaP7gDllc0mnWv2/LWF4WgHyn9kFWkED2DeTGcer1PwKbwzk

    NYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1

    oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN

    1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCJ0vxEnNR+gsdSYNmY7WvkpXiaxPW3JySW28XfMUdS2j+4A5ZXNJp1

    r9vy1heFoB8p/ZBVpBA9g3kxnHq9T8Cm8M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9

    vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzk

    NYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agidL8RJzUfoLHUmDZmO1r5

    KV4msT1tyckltvF3zFHUto/uAOWVzSada/b8tYXhaAfKf2QVaQQPYN5MZx6vU/ApvDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWg

    MM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3

    WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20F

    EE9GfGoInS/ESc1H6Cx1Jg2Zjta+SleJrE9bcnJJbbxd8xR1LaP7gDllc0mnWv2/LWF4WgHyn9kFWkED2DeTGcer1PwKbwzkNYn29bLc66

    sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1

    stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DW

    J9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCJ0vxEnNR+gsdSYNmY7WvkpXiaxPW3JySW28XfMUdS2j+4A5ZXNJp1r9vy1heFoB8

    p/ZBVpBA9g3kxnHq9T8Cm8M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7

    DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc6

    6sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agidL8RJzUfoLHUmDZmO1r5KV4msT1ty

    ckltvF3zFHUto/uAOWVzSada/b8tYXhaAfKf2QVaQQPYN5MZx6vU/ApvDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9v

    Wy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzk

    NYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqme

    Pi4hweKo9kY9IqYIxX1J/v16RCVA170eFxhAN3wa1CgUXQf06H6EkTDtcpIBKFFt+x2ML67lRBWBLW85WBti4DWaOSPNeFyr3ibjxx4mo

    Y4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXFlyAkTu8DL2SS7xOUXjklamxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjd

    a9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3Our

    H7DdY1oDA==

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

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: OAAAAAEABQABAAIAAQABAAAAAgABAAEAJJQa9KpYZA+iCTKHWs/qTqwV2oLOcPL0Fgna16xWKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20000
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   AMI     OEMAPIC
      FACP   AMI     OEMFACP
      HPET   AMI     OEMHPET
      BOOT   AMI     OEMBOOT
      MCFG   AMI     OEMMCFG
      SLIC   _ASUS_  Notebook
      OEMB   AMI     AMI_OEM


    Please, whatever I can do so I don't have to re-install the OS from the recovery cd that came with the laptop.  I have so much info on this system that I MUST have, I also need to resolve my "D"drive issue.  If I go to admin tools, dick mangment, it sees the partition as 54.6 gig of "free space", which used to be my "D" partition.  I have backups of the data so thats not a concern, I just wanted explorer or my computer to recognize and be able to access the space on the drive.  Thanks for your help and suggestions!

    Regards,

    Fred Nolte

    Friday, April 2, 2010 2:13 PM

Answers

  • Hello Fred,

    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      04       01           1102              58691-

    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)


    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 04/01

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 04/01/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 03/31/2010, 03/30/2010 and 03/29/2010  (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

    Thank you,


    Darin MS
    Friday, April 2, 2010 8:48 PM

All replies

  • Hello Fred,

    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      04       01           1102              58691-

    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)


    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 04/01

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 04/01/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 03/31/2010, 03/30/2010 and 03/29/2010  (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

    Thank you,


    Darin MS
    Friday, April 2, 2010 8:48 PM
  • Hello Daren

    I'm having the same problem that Fred has , but after 2 hours surfing the net I figured out that the cause of the problem could be simple as installing new software that is not compaitable with Vista. All I did to solve the problem is logging in the Safe Mode (Restart the computer and press F8) and uninstall this Software.

    T.Max

    Thursday, March 17, 2011 5:50 AM