none
Conficker virus. RRS feed

  • Question

  • Hi all. I just wanted to let you know that i believe (this is only a suspicion though) that i have received the conficker worm, or something similar directly from updating my vista system. last night i clicked on the "install updates and shut down your computer" tab on the start menu. i noticed that 2 updates were being installed at the time, however when my system restarted AVG free told my that i was infected with "Trojan Horse PSW.Agent.AABR" located in C:\Windows\System32\ispcsx.dll and now i keep getting the invalid license notification and also one telling me that i may be a victim of software piracy. i am currently running AVG, One Care Safety Scanner and Microsoft windows malicious software removal tool to try and locate the problem.
    I suspect conficker as certain aspects of windows (updates/control panel/programs and features etc) will not open, and i cannot log on to avg website from time to time. looking back at the updates on add or remove programs (in safe mode) it appears that only 1 official update was installed. im afraid i uninstalled it so i cant tell you which one. anyways... here is my mgadiag

    Diagnostic Report (1.9.0006.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-BGJ9B-24PMW-RYQMV
    Windows Product Key Hash: WLjrwBCxBnHS1kYTKs6dZ9LMPcE=
    Windows Product ID: 89580-OEM-7332132-00026
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {D9827F67-73B2-4462-AB76-105DEFCB386E}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.090302-1506
    TTS Error: K:20090513222040723-M:20090514111806420-
    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
    WGATray.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\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>{D9827F67-73B2-4462-AB76-105DEFCB386E}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6001.2.00010100.1.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RYQMV</PKey><PID>89580-OEM-7332132-00026</PID><PIDType>2</PIDType><SID>S-1-5-21-1900069112-206742364-3269106260</SID><SYSTEM><Manufacturer>DIXONSXP</Manufacturer><Model>Calistoga &amp; ICH7M Chipset</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>D3C72                         </Version><SMBIOSVersion major="2" minor="4"/><Date>20061222000000.000000+000</Date></BIOS><HWID>1D303507018400EA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DSGLTD</OEMID><OEMTableID>DSGVISTA</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAPQwAgAAAAAAYWECAASgqo/ugFcJ89PJAW4aG1/FHasdtBRBPRnxqCJwcTs0RwWlfH24skuXXpYgKt1X/BPJj6sVf1UJB58kO8JB+NSRv2hxTSBqKp9pnZ/2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiYmyfuJYma7lep4I6ONfkhDeYdADoB9ouKWKo88BLbEeNSHtUkDt3U2owx+MzxJ899lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIoCiSEyInhyEBqlejq3T39G3JEAjeJ3+uzR/IbeT5apgFpQWn+2SqggECh54r+hvcfZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCK54r99/tp+pG7Kozmx46i5x2/Y5cQlXwbrmMqo4ApNEpyvINNOGKAy8+MQWnmOxMr2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiMMgIJAW+KKo85kaMnixhqV5gf8vhLNhm/NYONLx8pQLrRjJ/48GpkuDUQbGGrbq+9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIm4Az//6dou0+TFgXjbvu3KjgTzI/9dds/pnoSEtmYZHZUPiU8OviL/RbCadb0P6S/ZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCJhuxUY0u3roXuaBHBFLCQ1xcTZdRzq5usN0bY8nnw/l2VD4lPDr4i/0WwmnW9D+kv2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agixDLj9FPF38v0yvoKkFfmfRXp14baHjo+lOvmenNHv1YliB7kgZwCEaHiMTnbSXS79lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIjek+O4ENZABI71FkJR2RPesNjIkb7NAEde9Wic10EG2/22T7aGrbL97wOL7au41GPZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

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

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

    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            DSGLTD        DSGVISTA
      FACP            DSGLTD        DSGVISTA
      HPET            DSGLTD        DSGVISTA
      BOOT            DSGLTD        DSGVISTA
      MCFG            DSGLTD        DSGVISTA
      APIC            DSGLTD        DSGVISTA
      SLIC            DSGLTD        DSGVISTA
      SSDT            PmRef        CpuPm

    As there is no FileScan Data -> this has to be an in memory situation, and i have uninstalled every possible program that could be conflicting with vista.
    I also ran a registry check recently, (registry first aid unsure what version as i uninstalled it) but im now thinking that i should have payed closer attention to what it was 'fixing' for me, as i dont know if this couldve been the cause.

    At any rate i still cant revalidate my vista, and i would really appreciate any specific help that anyone could offer to me. Thanks in advance
    Jack

    Thursday, May 14, 2009 11:57 AM

Answers

  • Jackzor,

    Thank you for visiting the Vista Forum today. The best resolution is back up all data and reformat your harddrive and reinstall Vista. I say this because you mentioned being infested with a virus. Should we try and resolve the existing problem you are having could manifest into other complications because you aren't sure if the virus has been completely purged. 


    Thank you Jackzor,


    Stephen
    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own which will help minimize confusion. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers. Thank you, Stephen Holm
    • Marked as answer by Stephen Holm Thursday, May 14, 2009 5:45 PM
    Thursday, May 14, 2009 5:45 PM
  • Jackzor,

    To my knowledge there doesn't appear to be a surge. The Online Validation Code: 0xc004d401 which you received does occur. Let me provide you with an explanation. Please keep in mind though Jackzor as the reason why I didn't provide you with potential fix steps was you had a virus and you weren't sure if it had successfully been removed.  



    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, and 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:2009         05          14           1118                      06420-
     

    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)



    (year)      (month)     (day)     (time in 24format)     (millisecond) 

    K:2009     05           13          2220                      40723-



    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 05/14

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un) Installs for 05/14/2009

    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 05/13/2009, 05/12/2009, and 05/11/2009  (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 these 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,

     

    Stephen

     


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own which will help minimize confusion. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers. Thank you, Stephen Holm
    • Marked as answer by Stephen Holm Tuesday, May 19, 2009 8:14 PM
    Tuesday, May 19, 2009 8:14 PM

All replies

  • sorry about the highly annoying long code strings in the above post!
    Thursday, May 14, 2009 11:58 AM
  • One other thing that i should probably mention is that all my system restore points have been removed since installing those updates, and trying to restore to before i installed the updates is unsuccessful each time. Jack
    Thursday, May 14, 2009 1:57 PM
  • Jackzor,

    Thank you for visiting the Vista Forum today. The best resolution is back up all data and reformat your harddrive and reinstall Vista. I say this because you mentioned being infested with a virus. Should we try and resolve the existing problem you are having could manifest into other complications because you aren't sure if the virus has been completely purged. 


    Thank you Jackzor,


    Stephen
    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own which will help minimize confusion. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers. Thank you, Stephen Holm
    • Marked as answer by Stephen Holm Thursday, May 14, 2009 5:45 PM
    Thursday, May 14, 2009 5:45 PM
  • Ok thanks for your input Stephen. i figured this would probably be the case. be nice to have a new feel to my computer anyways! thanks for all your tireless efforts on this forum as well, it seems you have a lot on your hands! if you dont mind me asking, do you have any ideas about the cause of what seems to be the recent surge in validation issues? are they all separate from one another. or is there a correlation?

    Thanks again.

    Jack
    Thursday, May 14, 2009 7:04 PM
  • Jackzor,

    To my knowledge there doesn't appear to be a surge. The Online Validation Code: 0xc004d401 which you received does occur. Let me provide you with an explanation. Please keep in mind though Jackzor as the reason why I didn't provide you with potential fix steps was you had a virus and you weren't sure if it had successfully been removed.  



    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, and 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:2009         05          14           1118                      06420-
     

    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)



    (year)      (month)     (day)     (time in 24format)     (millisecond) 

    K:2009     05           13          2220                      40723-



    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 05/14

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un) Installs for 05/14/2009

    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 05/13/2009, 05/12/2009, and 05/11/2009  (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 these 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,

     

    Stephen

     


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own which will help minimize confusion. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers. Thank you, Stephen Holm
    • Marked as answer by Stephen Holm Tuesday, May 19, 2009 8:14 PM
    Tuesday, May 19, 2009 8:14 PM
  • Hey Stephen. Thanks for clearing that up for me. ive actually solved my problem with the help of onecare scanner. a virus using the program.exe file SDRA64 was the cause. if anyone else is experiencing similar issues, i would advise them to check task manager/processes for SDRA64. end this process and then use onecare scanner to remove the threats files from your system. Thanks again for all you help.
    Jackzor
    Wednesday, May 20, 2009 7:43 AM
  • Hey Jackzor,

    No problem :-). I am glad to have been able to help. As a recommendation I would back up all of your files. Should you ever have a future problem maybe the only fix action may require a hard drive reformat then re-installation of Windows. What I have done in the past is purge files that are no longer needed then create one top level folder. Next create some sub-folders within and move all data into the sub-folders. Next I just grab the one folder "containing sub-folders" and move them to an external hard drive. How often one would do this would be determined how often you work and turn within the folders :-). 


    Take care and if you need further WGA Assistance please stop on by :-). Here is another forum which you may find useful as well.

    http://answers.microsoft.com/en-us/windows/default.aspx


    Take care,


    Stephen


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own which will help minimize confusion. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers. Thank you, Stephen Holm
    Wednesday, May 20, 2009 6:33 PM