Answered by:
Mod Auth Tamper
Question
-
Diagnostic Report (1.9.0006.1):
-----------------------------------------
WGA Data-->
Validation Status: Invalid License
Validation Code: 50
Online Validation Code: 0xc004c4a8
Cached Validation Code: N/A, hr = 0xc004d401
Windows Product Key: *****-*****-4RKRB-3BJ6B-76HCQ
Windows Product Key Hash: bRTvvV4hb8cUkHo8/deZDzRfARk=
Windows Product ID: 89578-OEM-7249445-07265
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.0.6000.2.00010300.0.0.003
ID: {2F437365-914C-4863-BF84-6BB783D9A1AE}(1)
Is Admin: Yes
TestCab: 0x0
WGA Version: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows Vista (TM) Home Premium
Architecture: 0x00000000
Build lab: 6000.vista_gdr.090302-1506
TTS Error: M:20090618014810642-
Validation Diagnostic:
Resolution Status: N/A
WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
WGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
WGATray.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 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:\Program Files\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>{2F437365-914C-4863-BF84-6BB783D9A1AE}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-76HCQ</PKey><PID>89578-OEM-7249445-07265</PID><PIDType>8</PIDType><SID>S-1-5-21-404450456-874688150-3661572422</SID><SYSTEM><Manufacturer>Dell Inc. </Manufacturer><Model>Dell DM051 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc. </Manufacturer><Version>A02</Version><SMBIOSVersion major="2" minor="3"/><Date>20051013000000.000000+000</Date></BIOS><HWID>A6333507018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08: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: U1BMRwEAAAAAAQAABAAAABYJAAAAAAAAYWECADAgAAD2Je5dB+3JARhDs/4hWdo7Xkl9D+HKpnjVd4VgmgHeiB6VYmGA/JlhtfYbAKi9qvB5hr3QnHg0YufDvX0zCybmDilyQLttVIyGGtR6Vhxbggb97CsbKkulsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTBgAm18BkdJTE0EGACwl7dV9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4fv8UnvACI1Zow6Ye7o9r2nS9ujW1lchWFVC84j+Ol2vnw719Mwsm5g4pckC7bVSMBFslqV/xPukwIXp+izApgLBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwYAJtfAZHSUxNBBgAsJe3VfUvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeGFj6NVso5NXSmStOo+aYqmxAfbpcLZUENCAwhuXiumt58O9fTMLJuYOKXJAu21UjMSpDV7bTE8E3ohFAjZh6oawQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMGACbXwGR0lMTQQYALCXt1X1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhDs/4hWdo7Xkl9D+HKpng2yc4VLIU7XRIRYSiXb8F+7kEvBDD+1Bemn6qYJ+i2rwQokzn13D2vIQWJj+yy8ZmdWRt1VLWjl6jOqjPgKAQoBtU6zyz3v9Z2MrIHa9x3W3cNP6YJJRzZ3sGPZMdauCpWgA9xqCKT2pyzU4ikmVXcUHxhcf38akJWjrTFmdio3G4MbsZdJFBl6ID8Z6PgzOFiAgd8gXL9twaWlpHw8NMJ801+h+MsTFkRlJ2ZAjRAiDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4UeDjmUkzKixI8d1d9d7kcjT8FN0V7NyW9OBQ2Pr/VWznw719Mwsm5g4pckC7bVSMBFslqV/xPukwIXp+izApgLBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwYAJtfAZHSUxNBBgAsJe3VfUvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeOpazqw25qWVnePT8dkpm5pBS0HtSBGxh/2zsn4cstrp58O9fTMLJuYOKXJAu21UjMHm4ql6K5aoiiGNp7twv+2wQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMGACbXwGR0lMTQQYALCXt1X1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==
Licensing Data-->
C:\Windows\system32\slmgr.vbs(291, 5) (null): 0xC004D401
HWID Data-->
HWID Hash Current: OgAAAAIABAABAAIAAQABAAAAAwABAAEA+l5IopCuM/Da+ypnqnZI5G4oxBh4rPL0oL2Gu/pDrFbsOw==
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 DELL DM051
FACP DELL DM051
HPET DELL DM051
BOOT DELL DM051
MCFG DELL DM051
SSDT DELL st_ex
ASF! DELL DM051
SSDT DELL st_ex
SSDT DELL st_ex
SSDT DELL st_ex
- Split by Stephen Holm Thursday, June 18, 2009 5:33 PM Splitting your thread....Stephen
Thursday, June 18, 2009 5:53 AM
Answers
-
Hello Ace High
Thank you for visiting our forum today :-). Vista is in, what we call a 'Mod-Auth' Tamper state. There are 2 types of Mod-Auth tampers.1) A critical system file was modified On Disk - What this means is that the file, located on the hard drive, and was modified in some way. This can be caused by a malicious program (spyware, malware, and 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:2009 06 18 0148 10642-
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 06/18
6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 06/18/2009 "
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 06/17/2009, 06/16/2009 and 06/15/2009 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 these 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,
Stephen
Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own which will help minimize confusion. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers. Thank you, Stephen Holm- Proposed as answer by Stephen Holm Thursday, June 18, 2009 11:22 PM
- Marked as answer by Darin Smith MS Monday, June 22, 2009 8:23 PM
Thursday, June 18, 2009 11:22 PM
