locked
windows server / wga / ati catalyst install RRS feed

  • Question

  • I attempted to install video adapter drivers and wga says invalid licencense key now (following blue screen crash on ws2008 rc0) despite numerous previous validations.  The catalyst drivers were an xp version but I had also installed some software that I could use as source for some streaming video, i.e., was going to stream activity on a game server so it could have been the game server that  was causing the problem using dx9.dll and the intel ipl library.  Plz pass that onto windows server techs for their comments.

     

    I'm getting pretty frustrated with all this since this must be about the third time that I've had this problem with ws2008 on different issues before I tried this gameserver thing, however, it is the first time that I got this far.  The last couple of times I had to reinstall and I'm getting pretty tired of that.

     

    I saw the piece about uninstalling software or drivers but I am in a loop and can't get anywhere near the operating system (desktop even!) to uninstall or investigate the problem [edit] I've now used the windir method to get into file explorer but I don't really want to get privelidged mode going[/edit].

     

    Ive now uninstalled the two items that I referred to above but I still get the messages.  I'll try the disk cleanup if I can find it anywhere... 

     

    It seems a pretty sick joke if the looping behaviour is by design - I really feel for the other ppl that might be going through this.  If ever there was a customer losing mistake this is probably it since my intial reaction in the loop tended towards a total loss of goodwill.  Sort it out plz folks..!

     

    oops - you may want this too...  I also ran silent runners and tutt, tutt guys...! 

     

    Diagnostic Report (1.7.0066.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-G8G7X-CXYY2-GPGW2
    Windows Product Key Hash: 1i/m59svExmYmslpyGrWraY4j30=
    Windows Product ID: 78440-047-2686913-70701
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00030112.1.0.004
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {055E65EC-1F0C-4E42-8D69-7051D6866DB8}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.59.1
    Signed By: Microsoft
    Product Name: Windows Server (R) 2008 Enterprise
    Architecture: 0x00000000
    Build lab: 6001.longhorn_rc0.070916-1443
    TTS Error: M:20071231094746375-
    Validation Diagnostic:
    Resolution Status: N/A

    Notifications Data-->
    Cached Result: N/A
    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 Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: FCEE394C-2989-80070002_77F760FE-152-80070002_7E90FEE8-175-80070002_77F760FE-152-80070002_7E90FEE8-175-80070002

    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>{055E65EC-1F0C-4E42-8D69-7051D6866DB8}</UGUID><Version>1.7.0066.0</Version><OS>6.0.6001.2.00030112.1.0.004</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-GPGW2</PKey><PID>78440-047-2686913-70701</PID><PIDType>5</PIDType><SID>S-1-5-21-3634677664-774456297-475611809</SID><SYSTEM><Manufacturer>VIA Technologies, Inc.</Manufacturer><Model>Aspire T120     </Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>R01-A1</Version><SMBIOSVersion major="2" minor="3"/><Date>20031202000000.000000+000</Date></BIOS><HWID>7A323507018400EE</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/><BRT/></MachineData><Software><Office><Result>109</Result><Products/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAGkVAAAAAAAAWmICAAQQBoSKMRfVZUvIAVMWKYGB4wMcsbz+lAen7WdudN1NBbMfRCG5Kgjt/0a8UkZUtR7H0OhJXFAwNWLHWWhLdCjuMrRBscVWF/p57JhDjR7LSwnuDX3rIY6QU2umPyjYe80K0dmlX46++IBZyHDgC1Uu2zsjQk6kqoqqV+iqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcWzOCJ+3uiMS1tVIm8AwATA0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjf2jNy1NFPH2GNrYOwOgEkbzYtbeXe5c1ABmToSvLpEM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nQdogf5unZrMbLSnhToFOE8CZtYCDCmZdlfHUDtrr+dzEoUm6crfBA0h1BOGybyUZykdAh/ueuP7XCgqiWrnale77b48zxh1wHBEBt9dDs2HtZlwrZV+9aSVmAyCRY8ZIsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ0HaIH+bp2azGy0p4U6BThPAmbWAgwpmXZXx1A7a6/ncxKFJunK3wQNIdQThsm8lGXH6ooli5q7J3NhHIbsG2NDu+2+PM8YdcBwRAbfXQ7Nh7WZcK2VfvWklZgMgkWPGSLBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwgzyrUGUBSEHA1yAMBRpeg/UvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7WdA/HEb6bVUGpZkBg+CdUY1SnALDtq3XMkLN5je4BqZdGhLdCjuMrRBscVWF/p57JjozqirCZw+cnCgeBMEF3DhPyjYe80K0dmlX46++IBZyHDgC1Uu2zsjQk6kqoqqV+iqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcWzOCJ+3uiMS1tVIm8AwATA0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjf2jNy1NFPH2GNrYOwOgEkbzYtbeXe5c1ABmToSvLpEM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nQPxxG+m1VBqWZAYPgnVGNT1hSMRGge1b5PKviGkuEZ/EoUm6crfBA0h1BOGybyUZi4iyQ7ZUCwaFOERmZv1vHu77b48zxh1wHBEBt9dDs2HtZlwrZV+9aSVmAyCRY8ZIsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ0D8cRvptVQalmQGD4J1RjU9YUjERoHtW+Tyr4hpLhGfxKFJunK3wQNIdQThsm8lGdL0YHEpSBFQqF1yqz5zENvu+2+PM8YdcBwRAbfXQ7Nh7WZcK2VfvWklZgMgkWPGSLBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwgzyrUGUBSEHA1yAMBRpeg/UvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7WfZxtdUA7BtL+6vDsOyY/wOJqcVM+5Yrp7q1ghqBF8ow2hLdCjuMrRBscVWF/p57JjozqirCZw+cnCgeBMEF3DhPyjYe80K0dmlX46++IBZyHDgC1Uu2zsjQk6kqoqqV+iqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcWzOCJ+3uiMS1tVIm8AwATA0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjf2jNy1NFPH2GNrYOwOgEkbzYtbeXe5c1ABmToSvLpEM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1n2cbXVAOwbS/urw7DsmP8Dt/k7IAY/RJJPwhvAdPw+QbEoUm6crfBA0h1BOGybyUZykdAh/ueuP7XCgqiWrnale77b48zxh1wHBEBt9dDs2HtZlwrZV+9aSVmAyCRY8ZIsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ9nG11QDsG0v7q8Ow7Jj/A4mpxUz7liunurWCGoEXyjDaEt0KO4ytEGxxVYX+nnsmDVxJAO4aVGy7i+N8zWlpAo/KNh7zQrR2aVfjr74gFnIcOALVS7bOyNCTqSqiqpX6KostOvttek9/t2KR7P+ImfkvDxiVcwE2xHkprZh79txbM4In7e6IxLW1UibwDABMDSkqs5hKGcTzKr4HYhiEDk/b40i1fXcxf/8eDMx4xEWN/aM3LU0U8fYY2tg7A6ASRvNi1t5d7lzUAGZOhK8ukQzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7WcGIwKohR0xsxO687jGZDkzCRFn7OdTRTEmPfjm/L11fmhLdCjuMrRBscVWF/p57JhDjR7LSwnuDX3rIY6QU2umPyjYe80K0dmlX46++IBZyHDgC1Uu2zsjQk6kqoqqV+iqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcWzOCJ+3uiMS1tVIm8AwATA0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjf2jNy1NFPH2GNrYOwOgEkbzYtbeXe5c1ABmToSvLpEM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nBiMCqIUdMbMTuvO4xmQ5M3xGEomCAQEMWD6zVn/3GVzEoUm6crfBA0h1BOGybyUZ0vRgcSlIEVCoXXKrPnMQ2+77b48zxh1wHBEBt9dDs2HtZlwrZV+9aSVmAyCRY8ZIsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

     

     

     

     

     

    Monday, December 31, 2007 6:48 AM

Answers

  • Hello antointhe,

     

      First off I want to tell you that I have no training on Windows Server 2008 and will probably not be trained on it as when it is released, the support would, most likely, be handled by Windows Server Support. Any troubleshooting I do will be baised on what I know of Vista, so it may not be applicable to WS 2008.

     

      That being said, since your Diagnostic Report is displaying intelligible data, so it appears that Windows Server 2008 isn't that much different to Vista, when it comes to Tamper states. Therefore I will troubleshoot on the assumption that the cause of your issue is the same as it would be for a Vista machine with the same Diagnostic Report.

     

     Your Diagnostic Report is showing 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 occure.

     

    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 Vista.

     

    Because there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, I beleive your issue is a In Memory Mod-Auth tamper. Basically, there is a program that is Running, that is trying to hook/shim into a critical system file running in memeory.


    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. (NOTE: this list is specific to Vista. I do not have any information as to known incompatible program for Windows Server 2008)
      
      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: 2007     12       31             0947              46375-


    Now that you know the time of the tamper, you can now try to connect that time with a program. (Note: the below steps are specific to Vista. I am unsure if the steps would be that same for Windows Server 2008)

     

    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 12/31

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

    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 12/30/2007, 12/29/2007 and 12/28/2007

      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 12/31/2007, 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 as well since it may fall outside of the 3 day time frame described above.

     

    If my help did not resolve your issue, I would strongly suggest reposting your issue in one of the Windows Server 2008 forums http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID=161&SiteID=17 for additional assistance.

     

    Thank you,

    Darin Smith

    WGA Forum Manager 

    Monday, December 31, 2007 7:45 PM
  •  

    Thanks David

     

    Unfortunately I had reinstalled before I got your message.  I have deduced that the cause of the blue screen crash was the atigag.exe program that is used for radeon 9250.  It seems that i needed the original via motherboard drivers so that the card could be installed properly as well.

     

    Yes, ws2k8 is similar to vista in that the client is vista itself although the server core is something different which is why I posted here since I couldn't really go anywhere else with it Wink

     

    I also had another program (empirical deduction over 3 OS's now), i.e., a piece of malware that was installing winsxs components in the system that was attempting to alter the system as well so it seems that a reinstall was the best option after all.

     

    Anyways, I still get the blue screens when shutting down but I've decided to download the .net 1.1 redistributable since I remember that atigag needs that to run.  If that does the trick without destroying my iis7 implementation, i.e., interfering with my priary framework of .net 3.0, I reckon I will have solved a problem that keeps many people away from vista (but saying that I have this creeping feeling of dread that your guys have already been through all that!)

     

    Anyways Happy New Year to all you folks at Microsoft, I hope it is really sucessful in terms of projects, earnings and customer relations Big Smile

    Tuesday, January 1, 2008 9:01 AM

All replies

  • Hello antointhe,

     

      First off I want to tell you that I have no training on Windows Server 2008 and will probably not be trained on it as when it is released, the support would, most likely, be handled by Windows Server Support. Any troubleshooting I do will be baised on what I know of Vista, so it may not be applicable to WS 2008.

     

      That being said, since your Diagnostic Report is displaying intelligible data, so it appears that Windows Server 2008 isn't that much different to Vista, when it comes to Tamper states. Therefore I will troubleshoot on the assumption that the cause of your issue is the same as it would be for a Vista machine with the same Diagnostic Report.

     

     Your Diagnostic Report is showing 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 occure.

     

    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 Vista.

     

    Because there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, I beleive your issue is a In Memory Mod-Auth tamper. Basically, there is a program that is Running, that is trying to hook/shim into a critical system file running in memeory.


    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. (NOTE: this list is specific to Vista. I do not have any information as to known incompatible program for Windows Server 2008)
      
      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: 2007     12       31             0947              46375-


    Now that you know the time of the tamper, you can now try to connect that time with a program. (Note: the below steps are specific to Vista. I am unsure if the steps would be that same for Windows Server 2008)

     

    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 12/31

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

    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 12/30/2007, 12/29/2007 and 12/28/2007

      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 12/31/2007, 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 as well since it may fall outside of the 3 day time frame described above.

     

    If my help did not resolve your issue, I would strongly suggest reposting your issue in one of the Windows Server 2008 forums http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID=161&SiteID=17 for additional assistance.

     

    Thank you,

    Darin Smith

    WGA Forum Manager 

    Monday, December 31, 2007 7:45 PM
  •  

    Thanks David

     

    Unfortunately I had reinstalled before I got your message.  I have deduced that the cause of the blue screen crash was the atigag.exe program that is used for radeon 9250.  It seems that i needed the original via motherboard drivers so that the card could be installed properly as well.

     

    Yes, ws2k8 is similar to vista in that the client is vista itself although the server core is something different which is why I posted here since I couldn't really go anywhere else with it Wink

     

    I also had another program (empirical deduction over 3 OS's now), i.e., a piece of malware that was installing winsxs components in the system that was attempting to alter the system as well so it seems that a reinstall was the best option after all.

     

    Anyways, I still get the blue screens when shutting down but I've decided to download the .net 1.1 redistributable since I remember that atigag needs that to run.  If that does the trick without destroying my iis7 implementation, i.e., interfering with my priary framework of .net 3.0, I reckon I will have solved a problem that keeps many people away from vista (but saying that I have this creeping feeling of dread that your guys have already been through all that!)

     

    Anyways Happy New Year to all you folks at Microsoft, I hope it is really sucessful in terms of projects, earnings and customer relations Big Smile

    Tuesday, January 1, 2008 9:01 AM