locked
error 0xC004D401 RRS feed

  • Question

  • hi im having what seems to be a common problem, how do i get the diagnostics to work? I keep being told this copy of windows is not valid, furthermore i have read the responses to other users problems and it seems that its either a program i have or an update, and to find out when the problem occurred i need to run the diagnostic, but am unable can u help..... will removing the software /  update fix the problem if not what can be done?
    Monday, October 6, 2008 9:46 PM

Answers

  •  Hello Harrymore,


    Thank you for running the MGA Diagnostic test. As you may have noticed I merged your threads together. Please stay in the same thread as it will help us understand what you are experiencing and so we won't miss a possible post.


    Windows 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, and was modified in some way. This can be caused by a malicious program (malware) 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 usually caused by a running program that is incompatible with Windows Vista.

     Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, 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 Windows Vista does not allow which by definition means it is incompatible with Windows Vista.

     In addition to why a Tamper occurs, it's also important to understand how Windows Vista detects the Tamper event. There is a Service that runs in Windows 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, Windows Vista (most likely) would not immediately enter a Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Windows Vista detects the Tamper, you know that the program that caused the tamper, is currently running.

     Below I have provided a number of steps to help you identify the program that is causing the tamper:

     The following Knowledge Base (KB) article may help you confirm that you do not have any of the programs known to cause this type of issue.

     KB931699 - Error message when you use Windows Vista: "An unauthorized change was made to your license"

     http://support.microsoft.com/kb/931699/

     
    Second, in your Microsoft Genuine Diagnostic Tool (MGADT) 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:2008       10               06                2211                               26291-

    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.

    (Year)       (Month)        (Day)        (Time in 24format)         (Millisecond)

    K:2008        10               06                2008                              59683-


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

     

    1) Login to Windows Vista and select the option which 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) Then click System Stability Chart above the date 10/06.   

    6) Below the chart, in the System Stability Report section look at the report titled "Software (Un) Installs for 10/06//2008.

    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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 10/05//2008, 10/04//2008 and 10/063/2008 

    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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state) till 10/06//2008, 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 as well since it may fall outside of the 3 day time frame described above.

    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 the following link below:

    http://go.microsoft.com/fwlink/?linkid=52029

    Thank you for visiting the Genuine Advantage forum.



    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    • Marked as answer by Stephen Holm Tuesday, October 7, 2008 5:49 PM
    Tuesday, October 7, 2008 5:47 PM

All replies

  • Diagnostic Report (1.7.0095.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-JQMWD-2QJRJ-RJ34F
    Windows Product Key Hash: R8gPTEFMoOygFewoq/uOoWMpz68=
    Windows Product ID: 89578-OEM-7332157-00237
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {BD173B4A-AD85-4153-8EBE-709ADD2AF625}(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.080425-1930
    TTS Error: K:20081006200859683-M:20081006221126291-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: 114 Blocked VLK 2
    Microsoft Office XP Professional with FrontPage - 114 Blocked VLK 2
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-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>{BD173B4A-AD85-4153-8EBE-709ADD2AF625}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RJ34F</PKey><PID>89578-OEM-7332157-00237</PID><PIDType>2</PIDType><SID>S-1-5-21-3243587282-764416343-1273663159</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>EQUIUM A200</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>1.60    </Version><SMBIOSVersion major="2" minor="4"/><Date>20071005000000.000000+000</Date></BIOS><HWID>56313507018400FA</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>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90280409-6000-11D3-8CFE-0050048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office XP Professional with FrontPage</Name><Ver>10</Ver><Val>39476F84C4B4004</Val><Hash>4iCnywwNW1w4s9ukTIwGMGxyGic=</Hash><Pid>54185-640-0000025-17604</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="10" Result="114"/><App Id="16" Version="10" Result="114"/><App Id="17" Version="10" Result="114"/><App Id="18" Version="10" Result="114"/><App Id="1A" Version="10" Result="114"/><App Id="1B" Version="10" Result="114"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAANoAmwAAAAAAYWECAAQgwocQbqjb4ybJAW4aG1/FHasdtBRBPRnxqCJqjNxaXpkAA56fRKda6qx1ccD3NXHh33Lt1ASyckQUS/ZoN8yKbr1eYK7Yw+wy3nn2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agijYHmBwkyq/solUo1O9CF5Fl+l7EjHbwSgIbcf4vRsrOqFF+BuupxHz9jdR/LlcbR9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM




    this means nothing to me.... also i haven't installed any software for a while.

    I am using a pre-installed copy of vista home premium i hope this is all the information i need to provide

    • Moved by RickImAPC Monday, October 6, 2008 10:56 PM Vista Diagnostic Report (Moved from Windows XP Genuine Advantage Validation Issues (Windows XP) to Windows Vista Validation Issues (Windows Vista))
    • Merged by Stephen Holm Tuesday, October 7, 2008 5:34 PM Merging
    Monday, October 6, 2008 10:02 PM
  • Hello Harrymore,

    Why can you not run the MGA Diagnostic Tool? Please sare with us what is preventing you from running the tool.  Is your computer from a major manufacturer or was it built by a local business?


    Thank you,


    Stephen Holm, MS
    WGA Forum Manager
    Stephen Holm
    Tuesday, October 7, 2008 4:03 PM
  •  Hello Harrymore,


    Thank you for running the MGA Diagnostic test. As you may have noticed I merged your threads together. Please stay in the same thread as it will help us understand what you are experiencing and so we won't miss a possible post.


    Windows 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, and was modified in some way. This can be caused by a malicious program (malware) 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 usually caused by a running program that is incompatible with Windows Vista.

     Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, 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 Windows Vista does not allow which by definition means it is incompatible with Windows Vista.

     In addition to why a Tamper occurs, it's also important to understand how Windows Vista detects the Tamper event. There is a Service that runs in Windows 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, Windows Vista (most likely) would not immediately enter a Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Windows Vista detects the Tamper, you know that the program that caused the tamper, is currently running.

     Below I have provided a number of steps to help you identify the program that is causing the tamper:

     The following Knowledge Base (KB) article may help you confirm that you do not have any of the programs known to cause this type of issue.

     KB931699 - Error message when you use Windows Vista: "An unauthorized change was made to your license"

     http://support.microsoft.com/kb/931699/

     
    Second, in your Microsoft Genuine Diagnostic Tool (MGADT) 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:2008       10               06                2211                               26291-

    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.

    (Year)       (Month)        (Day)        (Time in 24format)         (Millisecond)

    K:2008        10               06                2008                              59683-


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

     

    1) Login to Windows Vista and select the option which 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) Then click System Stability Chart above the date 10/06.   

    6) Below the chart, in the System Stability Report section look at the report titled "Software (Un) Installs for 10/06//2008.

    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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 10/05//2008, 10/04//2008 and 10/063/2008 

    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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state) till 10/06//2008, 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 as well since it may fall outside of the 3 day time frame described above.

    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 the following link below:

    http://go.microsoft.com/fwlink/?linkid=52029

    Thank you for visiting the Genuine Advantage forum.



    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    • Marked as answer by Stephen Holm Tuesday, October 7, 2008 5:49 PM
    Tuesday, October 7, 2008 5:47 PM