locked
WGA Validation Error RRS feed

  • Question

  • Per instructions in a prior post, I installed and ran Microsoft Genuine Advantage Diagnostic Tool. Below is the pasted information from that run.

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-4B3DJ-F7DPG-CYV39
    Windows Product Key Hash: 3fhL0FArg5/c4WJFbITUrhxBASs=
    Windows Product ID: 89578-015-6603983-71870
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {317E75CB-1A4F-4F72-A610-0DF65AB15305}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.59.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071023-1545
    TTS Error: M:20080309120537882-
    Validation Diagnostic:
    Resolution Status: N/A

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

    Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    Version: 1.5.540.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: FCEE394C-2920-80070002_025D1FF3-282-80041013_025D1FF3-170-80041013_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>{317E75CB-1A4F-4F72-A610-0DF65AB15305}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-CYV39</PKey><PID>89578-015-6603983-71870</PID><PIDType>5</PIDType><SID>S-1-5-21-3545880760-1345030549-1857541669</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>Pavilion dv8000 (EP404UA#ABA)     </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.31</Version><SMBIOSVersion major="2" minor="31"/><Date>20060104000000.000000+000</Date></BIOS><HWID>B0503A07018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>2</stat><msppid></msppid><name>HP</name><model></model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91E30409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>355BF729E03ADA4</Val><Hash>8wWkDkgtk2LX1zlAuVMWy3Y/7dw=</Hash><Pid>73931-722-2951855-57092</Pid><PidType>1</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAOcOAAAAAAAAWmICANOQm5q/CCg5fHLIARhDs/4hWdo7Xkl9D+HKpnikiLQAjR8dkytq0qd8SWxn5Yt/yXoNb4mmV7R8uIPfu+fDvX0zCybmDilyQLttVIw/32F4tri9rPRo6LpgIqXbsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4jQOVKtwLXJWxHL1Lye6k5JEUGxkr9r/KBwAYveBBHPHnw719Mwsm5g4pckC7bVSMbpJjca16flXj4u6ivCXpT7BBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwgzyrUGUBSEHA1yAMBRpeg/UvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeKkjhIt622SNn5DpEXxxG5mACW9i2Lmykf/Y4Fe8WaXh58O9fTMLJuYOKXJAu21UjAhVQ7nxm72XgeN8JWdJSYGwQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMIM8q1BlAUhBwNcgDAUaXoP1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

     

    Sunday, March 9, 2008 4:29 PM

Answers

  • Hello Kevin,

     

      The TTS is pulled directly from your system clock. 

     

      It may be that Vista was reporting what was going to happen as noted in your horoscope or maybe using a crystal ball, Or a more likely reason for the TTS to show a Timestamp 1 hour ahead could be that as of Sunday 03/09 the US, switch over to Daylight Saving Time and since your Diagnostic Report shows that your Vista is set to the Pacific Time Zone (which is a Time Zone that follows Daylight Savings Time), Vista would automaticly set it's system clock ahead 1 hour.

     

      Now as to the issue that brought you to this forum, your Vista is suffering from a In Memory Mod-Auth tamper. Since it appears that you have aready read other forum threads regarding this type of issue, you know that a In Memory Mod-Auth is caused by an Incompatible Program attempting to Hook or Shim (think modify) a critical system file running in system memory.

     

      The tips I have provided in other threads on how to identify the incompatible program by looking in the Reliability Monitor is only one method I suggested. I also explain that an incompatible program can be install for a long time and as long as the program was not launched, Vista would not go into a Mod-Auth Tamper. Vista will only go into a Mod-Auth tamper when that incompatible program was Actually Running. So that fact that your Vista experianced a Mod-Auth Tamper on 03/09/2008 does not nessacaraly mean the program was installed around that time, it only means that the incompatible program was Actually Running at the time the Mod-Auth occured.

     

      Therefore, I suggest identifying the programs that were running at the time of the Mod-Auth and

     

     a) Go to the website of the Maker of each program and confirm you have the most up-to-date version and confirm that the most up-to-date version is, in fact, compatible with Vista. If the website has a forum, browse it and see if anyone else is having this problem in Vista.

     

    and/or

     

    b) Close all the programs that were running at the time of the Mod-Auth and then run each one (by itself) for a time and see if the Mod-Auth occures, if not, try the next program and so on. Once you have identified the offending program, uninstall it or update it to compatible version.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

     

    Tuesday, March 11, 2008 11:08 PM

All replies

  • Additional info: TTS (tamper time stamp according to another article) was over an hour in the future at the time I made the original post. Perhaps Windows was reacting to something was was going to happen as noted in my horoscope? Crystal Ball maybe? I also considered that the timestamp was in GMT, but I was still in bed and the computer was not turned on at 12:53 GMT. Also, according to the Reliability screen, nothing was installed or uninstalled today.

     

    Sunday, March 9, 2008 5:32 PM
  • Hello Kevin,

     

      The TTS is pulled directly from your system clock. 

     

      It may be that Vista was reporting what was going to happen as noted in your horoscope or maybe using a crystal ball, Or a more likely reason for the TTS to show a Timestamp 1 hour ahead could be that as of Sunday 03/09 the US, switch over to Daylight Saving Time and since your Diagnostic Report shows that your Vista is set to the Pacific Time Zone (which is a Time Zone that follows Daylight Savings Time), Vista would automaticly set it's system clock ahead 1 hour.

     

      Now as to the issue that brought you to this forum, your Vista is suffering from a In Memory Mod-Auth tamper. Since it appears that you have aready read other forum threads regarding this type of issue, you know that a In Memory Mod-Auth is caused by an Incompatible Program attempting to Hook or Shim (think modify) a critical system file running in system memory.

     

      The tips I have provided in other threads on how to identify the incompatible program by looking in the Reliability Monitor is only one method I suggested. I also explain that an incompatible program can be install for a long time and as long as the program was not launched, Vista would not go into a Mod-Auth Tamper. Vista will only go into a Mod-Auth tamper when that incompatible program was Actually Running. So that fact that your Vista experianced a Mod-Auth Tamper on 03/09/2008 does not nessacaraly mean the program was installed around that time, it only means that the incompatible program was Actually Running at the time the Mod-Auth occured.

     

      Therefore, I suggest identifying the programs that were running at the time of the Mod-Auth and

     

     a) Go to the website of the Maker of each program and confirm you have the most up-to-date version and confirm that the most up-to-date version is, in fact, compatible with Vista. If the website has a forum, browse it and see if anyone else is having this problem in Vista.

     

    and/or

     

    b) Close all the programs that were running at the time of the Mod-Auth and then run each one (by itself) for a time and see if the Mod-Auth occures, if not, try the next program and so on. Once you have identified the offending program, uninstall it or update it to compatible version.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

     

    Tuesday, March 11, 2008 11:08 PM