none
Error: 0xC004D401, The security processor reported a system file mismatch error RRS feed

  • Question

  • Hey everyone, I have been looking at the questions in this forum a little bit, and I know that there are other questions about this, but this is starting to seem even worse than I had feared. This is my diagnostics:

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89583-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {8F1C3287-C001-44F6-BF0D-ED902767900B}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.101014-0432
    TTS Error: M:20110419132632191-
    Validation Diagnostic:
    Resolution Status: N/A

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

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Home and Student 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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-8009_E2AD56EA-766-2ee7_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\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>{8F1C3287-C001-44F6-BF0D-ED902767900B}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89583-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-1502892438-1668698235-3231128645</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv5 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.13</Version><SMBIOSVersion major="2" minor="4"/><Date>20080923000000.000000+000</Date></BIOS><HWID>5C303507018400F6</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>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>8D624513106EDB2</Val><Hash>kw82hwiZ6NmryM6u86sS4HzLeFk=</Hash><Pid>81602-OEM-6872946-85992</Pid><PidType>4</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAJoIAAAAAAAAYWECAAAAAADcO46eP+rLARhy9171jCizkdIEkQaJZ678tJ4Ny3HOp9S4syJX0WpJhIsxtetu1e4OPzZ5tsjTLCd7IPmIgITKmLNv1wD2WLZyRNYm//fHipHGX7yIbsQPqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOntaE+R2pndVdwiQf9u1zaeZn0+XwJIK7QecSF/kJ+BROU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuMgpiwIcH5H15HpTc49O3gy9Qi9/rc2mEe/h6Qu1xp6cneyD5iICEypizb9cA9li2zHXbw0XAe4OdD/6i9p6lVamjnBHePB2LDp7apxATyFCKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDp7WhPkdqZ3VXcIkH/btc2nmZ9Pl8CSCu0HnEhf5CfgUTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrss/vbgim5d3ULOYXFG1yFj9VgDud4dL5HiwHuXOXh9cJ3sg+YiAhMqYs2/XAPZYtnE2dFsZAq+7WB/DvBdM7hapo5wR3jwdiw6e2qcQE8hQipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6e1oT5Hamd1V3CJB/27XNp5mfT5fAkgrtB5xIX+Qn4FE5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ654ro7QVp/qbVgTCOzFJ2v+Rr9fdp2ppuax3g4deFswjid7IPmIgITKmLNv1wD2WLZtwgElwMh/tT50FmgBOqMGqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOntaE+R2pndVdwiQf9u1zaeZn0+XwJIK7QecSF/kJ+BROU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuF0nxoCRfq2jM9+sFBDV5MDN5sOg4LDDQLPVYfBQFNnEneyD5iICEypizb9cA9li2QWC06Ojaf838VqfEZICMwqmjnBHePB2LDp7apxATyFCKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDp7WhPkdqZ3VXcIkH/btc2nmZ9Pl8CSCu0HnEhf5CfgUTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrhObhSg04w852igEwyUDb4JLP6Msj5E1huF8bNnr/FKtJ3sg+YiAhMqYs2/XAPZYtvRLpsM/bh25LVPxqmKlZ0Wpo5wR3jwdiw6e2qcQE8hQipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6e1oT5Hamd1V3CJB/27XNp5mfT5fAkgrtB5xIX+Qn4FE5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ67kybb9hO7yITXkdtudnWMY+h0FNMCPWIiKLA0lqn/wXCd7IPmIgITKmLNv1wD2WLaoUjX4dMgQ0CWvgumSU9FrqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOntaE+R2pndVdwiQf9u1zaeZn0+XwJIK7QecSF/kJ+BROU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

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

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: OAAAAAEAAgABAAEAAwACAAAAAwABAAEA6GFE5VKiPq0QMyyD+OHCoPL04I8a7LywmgvKP6xWfig=

    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            HP            3600   
      FACP            HP            3600   
      HPET            HP            3600   
      BOOT            HP            3600   
      MCFG            HP            3600   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           PowerNow

     

    I should also mention that at this time i CANNOT open control panel. I click on it to run, the window opens then immediately closes. I am starting to get concerned. Can anyone help me?

    Tuesday, April 19, 2011 10:36 PM

Answers

  • "Belmura" wrote in message news:2951be88-8165-472c-bae7-77fe6c3c9f58...
    So you are saying it is possible that my system is a counterfeit or something to that end? Forgive me for seeming unwilling to understand, but I've had this computer since around 2008, I've had to do one total system format, but other than that I bought this laptop from HP a few years ago, and I am just now getting these problems. Does that change anything?

    NO - sorry about my confusion (trying to do too many things at once again....)
    Your OEM_SLP Key is valid for the machine it's on (even if it doesn't actually work)
     
    Here's what I should have said first time around.
     
    TTS Error: M:20110419132632191-

    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:20110419132632191- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2011     04       19            1326                 32191        -
     
     
    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 19th April 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 19th April "
     
    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 16-18 April (or around the date the issue first occurred)
     
      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
     
     
     
    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
     
    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.
     
    PC Safety:
     
     
     


     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Wednesday, April 20, 2011 11:33 PM
    Wednesday, April 20, 2011 12:32 AM
    Moderator

All replies

  • "Belmura" wrote in message news:1ff18fe4-9b3b-4b2f-a0f1-7d8d0cd1d239...

    Hey everyone, I have been looking at the questions in this forum a little bit, and I know that there are other questions about this, but this is starting to seem even worse than I had feared. This is my diagnostics:

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89583-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003



    File Scan Data-->

    Other data-->
    SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv5 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.13</Version><SMBIOSVersion major="2" minor="4"/><Date>20080923000000.000000+000</Date></BIOS


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

    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            HP            3600   
      FACP            HP            3600   
      HPET            HP            3600   
      BOOT            HP            3600   
      MCFG            HP            3600   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           PowerNow

     

    I should also mention that at this time i CANNOT open control panel. I click on it to run, the window opens then immediately closes. I am starting to get concerned. Can anyone help me?


    Your installation of Windows 7 is based on an OEM_SLP Key. Such a Key relies on two things
    1) The proper SLIC table in the BIOS
    2) The proper certificates installed in the OS.
     
    Your computer was built well before Windows 7 was released, and cannot therefore have a proper SLIC table for Windows 7 - and doesn't.
     
    If you purchased this copy of Win 7 as either a proper OEM installation, or a Retail pack, then you were sold a counterfeit.
    If you bought the computer with this OS installed, then your vendor sold you a counterfeit.
     
    For what version and edition of Windows is your computer license according to the COA sticker on the case?
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, April 19, 2011 11:00 PM
    Moderator
  • Actually this is windows vista.
    Tuesday, April 19, 2011 11:21 PM
  • For the information Noel described, it is the same for Vista and Windows 7.

    He most likely just forgot which Forum he was in, but regardless, the information he provided is still relevant.


    Darin MS
    Tuesday, April 19, 2011 11:32 PM
  • So you are saying it is possible that my system is a counterfeit or something to that end? Forgive me for seeming unwilling to understand, but I've had this computer since around 2008, I've had to do one total system format, but other than that I bought this laptop from HP a few years ago, and I am just now getting these problems. Does that change anything?
    Tuesday, April 19, 2011 11:37 PM
  • "Belmura" wrote in message news:2951be88-8165-472c-bae7-77fe6c3c9f58...
    So you are saying it is possible that my system is a counterfeit or something to that end? Forgive me for seeming unwilling to understand, but I've had this computer since around 2008, I've had to do one total system format, but other than that I bought this laptop from HP a few years ago, and I am just now getting these problems. Does that change anything?

    NO - sorry about my confusion (trying to do too many things at once again....)
    Your OEM_SLP Key is valid for the machine it's on (even if it doesn't actually work)
     
    Here's what I should have said first time around.
     
    TTS Error: M:20110419132632191-

    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:20110419132632191- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2011     04       19            1326                 32191        -
     
     
    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 19th April 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 19th April "
     
    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 16-18 April (or around the date the issue first occurred)
     
      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
     
     
     
    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
     
    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.
     
    PC Safety:
     
     
     


     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Wednesday, April 20, 2011 11:33 PM
    Wednesday, April 20, 2011 12:32 AM
    Moderator
  • Hey everyone, I have been looking at the questions in this forum a little bit, and I know that there are other questions about this, but this is starting to seem even worse than I had feared. This is my diagnostics:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89583-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {8F1C3287-C001-44F6-BF0D-ED902767900B}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.101014-0432
    TTS Error: M:20110419132632191-
    Validation Diagnostic:
    Resolution Status: N/A

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

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Home and Student 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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-8009_E2AD56EA-766-2ee7_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\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>{8F1C3287-C001-44F6-BF0D-ED902767900B}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89583-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-1502892438-1668698235-3231128645</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv5 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.13</Version><SMBIOSVersion major="2" minor="4"/><Date>20080923000000.000000+000</Date></BIOS><HWID>5C303507018400F6</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>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>8D624513106EDB2</Val><Hash>kw82hwiZ6NmryM6u86sS4HzLeFk=</Hash><Pid>81602-OEM-6872946-85992</Pid><PidType>4</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAJoIAAAAAAAAYWECAAAAAADcO46eP+rLARhy9171jCizkdIEkQaJZ678tJ4Ny3HOp9S4syJX0WpJhIsxtetu1e4OPzZ5tsjTLCd7IPmIgITKmLNv1wD2WLZyRNYm//fHipHGX7yIbsQPqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOntaE+R2pndVdwiQf9u1zaeZn0+XwJIK7QecSF/kJ+BROU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuMgpiwIcH5H15HpTc49O3gy9Qi9/rc2mEe/h6Qu1xp6cneyD5iICEypizb9cA9li2zHXbw0XAe4OdD/6i9p6lVamjnBHePB2LDp7apxATyFCKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDp7WhPkdqZ3VXcIkH/btc2nmZ9Pl8CSCu0HnEhf5CfgUTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrss/vbgim5d3ULOYXFG1yFj9VgDud4dL5HiwHuXOXh9cJ3sg+YiAhMqYs2/XAPZYtnE2dFsZAq+7WB/DvBdM7hapo5wR3jwdiw6e2qcQE8hQipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6e1oT5Hamd1V3CJB/27XNp5mfT5fAkgrtB5xIX+Qn4FE5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ654ro7QVp/qbVgTCOzFJ2v+Rr9fdp2ppuax3g4deFswjid7IPmIgITKmLNv1wD2WLZtwgElwMh/tT50FmgBOqMGqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOntaE+R2pndVdwiQf9u1zaeZn0+XwJIK7QecSF/kJ+BROU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuF0nxoCRfq2jM9+sFBDV5MDN5sOg4LDDQLPVYfBQFNnEneyD5iICEypizb9cA9li2QWC06Ojaf838VqfEZICMwqmjnBHePB2LDp7apxATyFCKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDp7WhPkdqZ3VXcIkH/btc2nmZ9Pl8CSCu0HnEhf5CfgUTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrhObhSg04w852igEwyUDb4JLP6Msj5E1huF8bNnr/FKtJ3sg+YiAhMqYs2/XAPZYtvRLpsM/bh25LVPxqmKlZ0Wpo5wR3jwdiw6e2qcQE8hQipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6e1oT5Hamd1V3CJB/27XNp5mfT5fAkgrtB5xIX+Qn4FE5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ67kybb9hO7yITXkdtudnWMY+h0FNMCPWIiKLA0lqn/wXCd7IPmIgITKmLNv1wD2WLaoUjX4dMgQ0CWvgumSU9FrqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOntaE+R2pndVdwiQf9u1zaeZn0+XwJIK7QecSF/kJ+BROU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

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

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: OAAAAAEAAgABAAEAAwACAAAAAwABAAEA6GFE5VKiPq0QMyyD+OHCoPL04I8a7LywmgvKP6xWfig=

    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            HP            3600   
      FACP            HP            3600   
      HPET            HP            3600   
      BOOT            HP            3600   
      MCFG            HP            3600   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           PowerNow

    I should also mention that at this time i CANNOT open control panel. I click on it to run, the window opens then immediately closes. I am starting to get concerned. Can anyone help me?

    Can anyone help me. I unistalled windows vista home edition and then reinstalled and now I come up with a product key error 0xC004D401, T. Anyone had this problem
    Friday, March 23, 2012 2:33 PM
  • Start a NEW thread of your own - tell what Anti-virus you are using, and post an MGADiag report

    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
     Once saved, run the tool.
    Click on the Continue button, which will produce the report.
     To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
      - **in your own thread**, please

    Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine, but do NOT quote the Key on the sticker!
     http://www.microsoft.com/howtotell/content.aspx?pg=coa


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, March 23, 2012 2:44 PM
    Moderator