locked
Vista suddenly saying invalid RRS feed

  • Question

  • Got this before so did fresh install now getting it again
    Error: 0xC004D401

    Now saying vista invlaid & running in reduced functionality mode.
    If I restart all seems well until the erroe comes up again.
    Ran WGA & got this:

    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: *****-*****-4P9QR-HRPXQ-343K8
    Windows Product Key Hash: N+qUWuTBmSmG/WgiLYNRXOvWLEg=
    Windows Product ID: 89578-OEM-7304124-07581
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {855BCACC-F87C-4FFD-9346-63C49EB0EC81}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.080917-1612
    TTS Error: K:20090318213200475-M:20090318204001274-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: 100 Genuine
    Microsoft Office Enterprise 2007 - 100 Genuine
    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\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>{855BCACC-F87C-4FFD-9346-63C49EB0EC81}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-343K8</PKey><PID>89578-OEM-7304124-07581</PID><PIDType>3</PIDType><SID>S-1-5-21-2337160784-3691590503-1836864491</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1004   </Version><SMBIOSVersion major="2" minor="4"/><Date>20070122000000.000000+000</Date></BIOS><HWID>2C313507018400FA</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>MSTEST</OEMID><OEMTableID>TESTONLY</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>72ED6A5F1BD4ECE</Val><Hash>WW+4gAhSbPveYNC8rWB1k1idNM0=</Hash><Pid>81599-871-7892306-65020</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAJe6AAAAAAAAYWECAASgEYfURmGIBajJARhy9171jCizkdIEkQaJZ67vTO0Seo+WdxQ0T1nZ5KCktTXNQRHSpCo3qSY4BSNICFF0H9Oh+hJEw7XKSAShRbcWwRXJhXdhgsArwA6tiGLf1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuuqU6lgjYeCI9oPuXGSNKHF9lwAYsE5KQRzARaRAgDwcUI3Tw8A4p035EFwEhEbHhGqmCdHLdFhuLqf/v+RAVt5P6AP0nxF+qLf25zZoCwNb7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctgV+5kNkO9/d8+V0OdFV7/ZoayoauFCIvj8LRkH4zhiIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

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

    HWID Data-->
    HWID Hash Current: PAAAAAEABgABAAEAAQABAAAABAABAAEAJJReHKIkpgyA+JJF7Ngu9wiFKLV6vPL0YhsKnWKjrFZfMSqF

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   MSTEST  OEMAPIC
      FACP   MSTEST  OEMFACP
      HPET   MSTEST  OEMHPET
      MCFG   MSTEST  OEMMCFG
      SLIC   MSTEST  TESTONLY
      OEMB   MSTEST  AMI_OEM


    I am tearing my hair out.
    Any help gratefully received.
    John

    Wednesday, March 18, 2009 9:59 PM

Answers

  • Hello John,

    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.

     

      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       03         18            2040                     01274-

     

    Note, I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. This is a minor tamper and is most likely directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well.


    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 03/18
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/18/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 03/17/2009, 03/16/2009 and 03/15/2009

      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 few 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, that provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ <Removed by Moderator: Phone number and/or site link no longer in use>before contacting PC Safety.

    <Removed by Moderator: Phone number and/or site link no longer in use>


    Thank you,
    Darin MS


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. 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.
    • Marked as answer by Darin Smith MS Wednesday, March 18, 2009 10:46 PM
    • Edited by Darin Smith MS Tuesday, April 10, 2012 7:11 PM <Removed by Moderator: Phone number and/or site link no longer in use>
    Wednesday, March 18, 2009 10:45 PM
  • Hello Jess01,

      I strongly recommend that you contact PC Safety. They are a group at Microsoft that provides free assistance with Malware infection.

    PC Safety: 1-866-PCSafety or 1-866-727-2338

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

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

    Thank you,
    Darin MS


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful" button for that post. This will help us showcase the threads that best help our customers.
    Monday, April 6, 2009 8:30 PM

All replies

  • Hello John,

    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.

     

      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       03         18            2040                     01274-

     

    Note, I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. This is a minor tamper and is most likely directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well.


    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 03/18
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/18/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 03/17/2009, 03/16/2009 and 03/15/2009

      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 few 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, that provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ <Removed by Moderator: Phone number and/or site link no longer in use>before contacting PC Safety.

    <Removed by Moderator: Phone number and/or site link no longer in use>


    Thank you,
    Darin MS


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. 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.
    • Marked as answer by Darin Smith MS Wednesday, March 18, 2009 10:46 PM
    • Edited by Darin Smith MS Tuesday, April 10, 2012 7:11 PM <Removed by Moderator: Phone number and/or site link no longer in use>
    Wednesday, March 18, 2009 10:45 PM
  • Is it possible that a windows update has caused this state?
    The reason I ask this is that prior to reformatting a few days ago I was running without problems for over 18 months.
    I then performed a windows update which installed several updates then rebooted.
    When I rebooted I got the error message.

    Unable to fix it I reformatted, & then updated through windows update (stupidly) & installed all available updates.
    Since reformatting I have only installed software that i had previously used for ages, & cannot fathom this one out.

    Also is there a PC safety contact number available in the UK?

    Grateful for advice,
    john
    Thursday, March 19, 2009 9:21 AM
  • Hi John,

      "Is it possible that a windows update has caused this state?"

    No, 'In Memory Mod-Auth tampers' are only caused by an Incompatible Program. The program has to be running for the issue to occure and it causes the issue by Hooking into or Shimming (Tampering with) a protected system file that is resident in system memory.

    A Windows Update usually only runs once and usually, all it's doing is adding or updating part of Vista. It would be Very unusual for Vista to be able to 'Tamper' itself (I'm unsure if that's even possible) 

    If you only installed the same programs as you have used in the past without any issue, my feeling would be they are not causing the problem. In which case, the next thing I would look for is a possible Malware infection.

    The PC Safety UK web page is http://www.microsoft.com/uk/protect/support/default.mspx and their contact number is 0870 60 10 100

    Cheers,
    Darin MS
    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. 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.
    Thursday, March 19, 2009 8:30 PM
  • Darin,

    I ran the live one care online scanner which picked up Trojan:Win32/Killav.gen!A in ....Netgear/WN111/unload.tmp


    Since your advice & finding this I reformatted & reinstalled vista, installed nothing but AVG AV 8.5 pro + firewall & my netgear drivers.

    No other software has been installed as yet..
    AVG doesn't pick up this trojan. I also ran malaware bytes anti-malware scan which didn't find anything either. Could the online scan be a false postive?
    I have not yet had any message about vista licence yet but feel it is only a matter of time.
    I am tearing my hair out as to why immediately after a reinstall i have this.

    Can you help at all?
    Thanks,
    John
    Saturday, March 21, 2009 7:42 AM
  • Hi John,

      I don't know much about viruses (other then know there are some that appear to be incompatible with Vista...or at least do the same type of things as a incompatible program does) so any question on Malware false positive would need to be directed to the PC Safety people.  But, I did do a web search for 'Trojan:Win32/Killav.gen!A' and got 10 pages of results, so that trojan does seem to be well documented.

      As for why it happened, right after reinstall, I do not know. If you have already used, without any problem, all the programs you installed right after the Vista reinstall, then it's unlikely they are the cause. So, if it's not something you installed, it would be something that installed itself. Which suggests malware.

      As to how Malware infected the computer right after windows reinstall, I don't know either. I have, however, read studies where  researchers  would leave a newly built computer connected directly to the internet without protection (i.e. no firewall, no anti-virus) and it took less then 3 min. for the computer to get infected.   Now, if you are using DSL or Cable, you have a router (that your computer connectes thru) to get to the internet and all routers (that I know of) have a firewall, so you had protection. But during reinstall, window's firewall isn't up and you have no anti-virus program running. Some people may call me paranoid, but I always ensure my computer is not connected to the internet while I am reinstalling Windows and if my Vista install disk didn't come with Service Pack 1, I would have downloaded it before hand and installed it before reconnecting to the internet...but that's just me and, as I said, some people think I'm overcautious. 

      All I can suggest is:

    a) Contact PC Safety and see if they have any answers to your Malware related questions.
    b) Before you install any programs, doublecheck they are specificly noted as being compatible with Vista, and, once they are installed, update them to their most recent version. 

    Sorry I couldn't tell you exactly what software was causing the issue, but I am glad you are back up and running.

    If you ever have any additional Validation or Activatiuon question or issue, please don't hesitate to contact me again,
    Darin MS
      
    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. 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.
    Monday, March 23, 2009 8:12 PM
  • Hi Darin,  I am finding it strange that I am having the EXACT same problem.  I was doing some work in the internet and all of a sudden my screen went black and took me to "my computer".  It then showed all my drives with and in red writing how many trojans I had in each of my drives.  There was then a pop-up saying I had 3 different viruses and or trojans and asked me if I wanted to delete them.  Having been warned about scareware, I tried to exit out and it would not let me, so I shut down my entire system.  I ran a systems scan through my Windows Defender and then also Maleware bytes just like you.  Neither of which caught this.  I then did a scan through Windows One Live and got the same thing you did and that it was in my Netgear.  I also have since done a scan through Spybot and reran the others saying I am okay.  Windows One Live first told me in the results it could not remove it, but then after going through some steps, it did claim it had been removed.  I have rebooted and rescanned from above mentioned sources and have gotten nothing.  I did start having problems with my Netgear remote last fall and have not used it since.  I was all of a sudden not able to get online.  My internal network card is faulty on my computer since I bought it and I was forced to either be without it for a couple months or buy an external network card and chose a Netgear remote adapter.  I find it interesting that we are having the exact same problem at the same time.  Jess01
    Monday, April 6, 2009 4:13 AM
  • Hello Jess01,

      I strongly recommend that you contact PC Safety. They are a group at Microsoft that provides free assistance with Malware infection.

    PC Safety: 1-866-PCSafety or 1-866-727-2338

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

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

    Thank you,
    Darin MS


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful" button for that post. This will help us showcase the threads that best help our customers.
    Monday, April 6, 2009 8:30 PM