locked
Windows Vista 64 System Builder's Edition. An Unauthorized Change was Made to Windows Black Screen of Death Popup RRS feed

  • Question

  • Excuse the wordy title - wanted to make sure other users found this with a search should they need to.

    I have the following system:

    ASUS P6T6 Motherboard
    Intel Core i7 920 (stock speeds - no overclocking)
    12Gb Corsair Dominator Ram - fan cooled
    2 x 1Tb WD Black Hard drives
    GEForce 285 GTX
    running Windows Vista 64Bit System Builder Edition.

    Machine has been running FLAWLESSLY for nearly two years until a few weeks ago when I purchased AVAST AntiVirus Pro. Installed it onto Windows 7 laptop and this machine. Windows 7 laptop runs it fine. This machine runs it fine too, but I suspect it might be tampering with my system files as every now and then on boot I will get the black screen of death with the popup:

    An Unauthorized Change was made to Windows.

    With two selections:

    More information online
    Close

    No other way to authorize my copy of Windows at all. Sometimes shutting down and rebooting into safe mode and then restarting will cure it, other times I have to restart from last known good configuration (I get my desktop and full functionality, but I still get that popup box on boot).

    I suspected my hard drive was dying, so bought another one and did a clean boot. Again, ran fine for a few weeks until my AVAST free license ran out. Upgraded to my paid PRO license and a couple of days later, did the same thing.

    Ran SFC /SCANNOW from CMD ran as administrator and it found no tampered or corrupt files.

    When I run the MS Genuine Advantage Tool, I get the popup again when I click Continue, and again when I get the results.

    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: *****-*****-MCY4H-K6Q8P-7M4BM
    Windows Product Key Hash: lyziJUCiopWGYmwhnSufZuvQnPM=
    Windows Product ID: 89587-OEM-7347734-15543
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {D9D34389-5C92-4649-8138-E3AB34629D6F}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.100608-0458
    TTS Error: M:20100827045327143-
    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: 109 N/A
    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:\Users\Railz\AppData\Local\Google\Chrome\Application\chrome.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>{D9D34389-5C92-4649-8138-E3AB34629D6F}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7M4BM</PKey><PID>89587-OEM-7347734-15543</PID><PIDType>3</PIDType><SID>S-1-5-21-2730694898-972339016-2559196455</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0311   </Version><SMBIOSVersion major="2" minor="5"/><Date>20081219000000.000000+000</Date></BIOS><HWID>CA303507018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAFQOAAAAAAAAYWECAAD4//8GSWo13T7LARhy9171jCizkdIEkQaJZ65QQeXkq84dUqXCfjoYaeAz0Gm7IodNukL57qaPIkzyEid7IPmIgITKmLNv1wD2WLYTt1145ufL4Oav4p+GsRtG4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuV43Mc/IjXoekx/zRuYREv4gNPyP3lhy04Ob2+EDQgFgneyD5iICEypizb9cA9li28xbMDq78QwzJfwEzG9nb5eA5JAndldPsNKjMPTVtZSSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrpnTzeJGTEtlh6nN/1YOZKTk8LDKWcA7XFF0bTdpFWpAJ3sg+YiAhMqYs2/XAPZYtkvVEf3rCLUpw/0B++CTHSzgOSQJ3ZXT7DSozD01bWUkipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6AF7jARVFhwdbNq3ozTurzwbEGminRbCK4Fdrkde7OzU5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ67ciFoUyUig8JhOTy7NjOgz82jGNVocg/yhPpi1s2phFid7IPmIgITKmLNv1wD2WLai667S3kAzH7oP3l31IRZH4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuhhsvKpqTz27vQ0+SNX/Og/X48pMflEgxesJSljw7sR8neyD5iICEypizb9cA9li2vuUa71UWnzQqyLU9j36xbuA5JAndldPsNKjMPTVtZSSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrr3l+WEMYeIG/3ai/i210XDnaeliW2bJHFIGGM8qvRVHJ3sg+YiAhMqYs2/XAPZYtsNcNNurR21v7p72Agzhd3PgOSQJ3ZXT7DSozD01bWUkipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6AF7jARVFhwdbNq3ozTurzwbEGminRbCK4Fdrkde7OzU5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ65kxh9RhmqxEGwR67KRo1AgS6tFK8CKM6LAwPBl8bxGJCd7IPmIgITKmLNv1wD2WLbGqTcFk+avWqxxLCDf7KmS4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

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

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: PAAAAAEABAABAAEAAwACAAAAAwABAAEACrYsmM5tjCZoZUa8hDTymcRgXBpcH/L04EWxbDhPrjmsVuqC

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            121908        APIC1622
      FACP            121908        FACP1622
      HPET            121908        OEMHPET
      MCFG            121908        OEMMCFG
      OEMB            121908        OEMB1622
      OSFR            121908        OEMOSFR
      SSDT            DpgPmm        CpuPm


    Going to try to activate this again.
    Friday, August 27, 2010 10:12 AM

Answers

  • Hi Maria,

      You are correct, your issue is related to a file being actively modified in memory.  I have provided the normal information given for this type of issue below.  However, since you believe Avast is the cause (and you uninstalled it) I recommend that you first reboot windows.   If the issue doesn't come back, you know it was caused by Avast. But if the issue returns, even after a reboot (and Avast is no longer installed on the computer) then you know it is something else that is causing the problem.

    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:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010      08       27        0453                27143-

    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 08/27

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

    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 08/26/2010, 08/25/2010 and 08/24/2010  (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:

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

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

     Thank you,


    Darin MS
    Friday, August 27, 2010 6:55 PM

All replies

  • Tired going to microsoft.com/genuine and it would not validate - completely skipped the process and said my copy was invalid. Tried to uninstall AVAST but control panel would not open, so had to uninstall it from Explorer. Rebooted fine, no black screen of death (yet). Went to /genuine and revalidated my copy of Visa okay.

    Ran Diagnostic tool. Got a "Geniune" result.

    Can anyone shed any light as to why this might be happening? Am I correct that it's AVAST doing this? This is a brand-new install of Vista after I thought my HD was causing the previous popup issue. The install is less than a month old and it's on a brand-new hard drive. SFC /SCANNOW reports no bad files again.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-MCY4H-K6Q8P-7M4BM
    Windows Product Key Hash: lyziJUCiopWGYmwhnSufZuvQnPM=
    Windows Product ID: 89587-OEM-7347734-15543
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {D9D34389-5C92-4649-8138-E3AB34629D6F}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.100608-0458
    TTS Error: M:20100827045327143-
    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: 109 N/A
    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:\Users\Railz\AppData\Local\Google\Chrome\Application\chrome.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>{D9D34389-5C92-4649-8138-E3AB34629D6F}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7M4BM</PKey><PID>89587-OEM-7347734-15543</PID><PIDType>3</PIDType><SID>S-1-5-21-2730694898-972339016-2559196455</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0311   </Version><SMBIOSVersion major="2" minor="5"/><Date>20081219000000.000000+000</Date></BIOS><HWID>CA303507018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAFQOAAAAAAAAYWECAAD4//8GSWo13T7LARhy9171jCizkdIEkQaJZ65QQeXkq84dUqXCfjoYaeAz0Gm7IodNukL57qaPIkzyEid7IPmIgITKmLNv1wD2WLYTt1145ufL4Oav4p+GsRtG4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuV43Mc/IjXoekx/zRuYREv4gNPyP3lhy04Ob2+EDQgFgneyD5iICEypizb9cA9li28xbMDq78QwzJfwEzG9nb5eA5JAndldPsNKjMPTVtZSSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrpnTzeJGTEtlh6nN/1YOZKTk8LDKWcA7XFF0bTdpFWpAJ3sg+YiAhMqYs2/XAPZYtkvVEf3rCLUpw/0B++CTHSzgOSQJ3ZXT7DSozD01bWUkipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6AF7jARVFhwdbNq3ozTurzwbEGminRbCK4Fdrkde7OzU5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ67ciFoUyUig8JhOTy7NjOgz82jGNVocg/yhPpi1s2phFid7IPmIgITKmLNv1wD2WLai667S3kAzH7oP3l31IRZH4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuhhsvKpqTz27vQ0+SNX/Og/X48pMflEgxesJSljw7sR8neyD5iICEypizb9cA9li2vuUa71UWnzQqyLU9j36xbuA5JAndldPsNKjMPTVtZSSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrr3l+WEMYeIG/3ai/i210XDnaeliW2bJHFIGGM8qvRVHJ3sg+YiAhMqYs2/XAPZYtsNcNNurR21v7p72Agzhd3PgOSQJ3ZXT7DSozD01bWUkipoxVLnTGwaFOK7a/cdOMuXOxq7DWs3pg+2++GWCaw6AF7jARVFhwdbNq3ozTurzwbEGminRbCK4Fdrkde7OzU5TmSkjgqbzdwdkyfkGZjYd0o8Py01iTA/fgr0SSJ/6M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ65kxh9RhmqxEGwR67KRo1AgS6tFK8CKM6LAwPBl8bxGJCd7IPmIgITKmLNv1wD2WLbGqTcFk+avWqxxLCDf7KmS4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

    Licensing Data-->
    Software licensing service version: 6.0.6001.18000
    Name: Windows(TM) Vista, Ultimate edition
    Description: Windows Operating System - Vista, OEM_COA_NSLP channel
    Activation ID: 33a7e8d3-e2ab-413b-96a6-27c83b21c695
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89587-00146-477-315543-02-1033-6001.0000-1972010
    Installation ID: 016760390022388776927696978281233453255831037466642312
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: 7M4BM
    License Status: Licensed

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: PAAAAAEABAABAAEAAwACAAAAAwABAAEACrYsmM5tjCZoZUa8hDTymcRgXBpcH/L04EWxbDhPrjmsVuqC

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            121908        APIC1622
      FACP            121908        FACP1622
      HPET            121908        OEMHPET
      MCFG            121908        OEMMCFG
      OEMB            121908        OEMB1622
      OSFR            121908        OEMOSFR
      SSDT            DpgPmm        CpuPm


    Friday, August 27, 2010 10:24 AM
  • Hello Maria Camsell,

    So what did Avast's tech support people have to say when you called them for help?


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97
    Friday, August 27, 2010 12:31 PM
  • Their Tech support is next to useless. It's basically user-oritented and any type of problem like this is automatically regarded as a pirate trying to get their bad copy of Windows working.

    Some of the threads I found there:

     

    http://forum.avast.com/index.php?topic=54538.0

    http://forum.avast.com/index.php?topic=56932.0

     

    I haven't rebooted since it came back up as I need to work. I've wiped Avast off my machine completely and installed MS Security Essentials instead.

     

    From my research on this forum it seems a file was modified in memory in my case, which more often than not can be caused by malware, but I think in this case it was Avast. I have scanned my machine with four different AV kits (MS-SE, AVAST, SP S&D and Malware Bytes) and nothing. The second link above shows the same behavior I was experiencing (popup on desktop, could not open control panel etc) so maybe someone from Microsoft can talk to their devs?

    Friday, August 27, 2010 2:59 PM
  • Hi Maria,

      You are correct, your issue is related to a file being actively modified in memory.  I have provided the normal information given for this type of issue below.  However, since you believe Avast is the cause (and you uninstalled it) I recommend that you first reboot windows.   If the issue doesn't come back, you know it was caused by Avast. But if the issue returns, even after a reboot (and Avast is no longer installed on the computer) then you know it is something else that is causing the problem.

    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:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010      08       27        0453                27143-

    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 08/27

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

    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 08/26/2010, 08/25/2010 and 08/24/2010  (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:

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

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

     Thank you,


    Darin MS
    Friday, August 27, 2010 6:55 PM