Error 0xc004d401

Answers

• 

  

  0

  Sign in to vote

   Hello Mikex163,

  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 usually caused by a running program that is incompatible with Vista.

   Since there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a 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.
  
    I do not believe that GTA IV has anything to do with the issue.  To my knowledge, GTA IV is compatible with Vista so installing it (or uninstalling it) would not have caused this issue. I believe it is some other program that you either a) recently installed or b) installed some time in the past but only recently ran for the first time.

    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 TMod-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        01         20             1943                  27506-

    Note, I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. This is a minor tamper and is most likey directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well .

  
  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 01/20 
  6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/20/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 01/19/2009, 01/18/2009 and 01/17/2009 

    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 some time in the past (say, a few weeks ago), but you didn't run it till today (and, hence, prompted the tamper state), 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
  
  Thank you,
  Darin MS

  ---

  Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.

  • Proposed as answer by Darin Smith MS Wednesday, January 21, 2009 12:36 AM
  • Marked as answer by Carl-S Monday, January 26, 2009 4:21 PM
  • Unmarked as answer by Carl-S Monday, January 26, 2009 4:21 PM
  • Marked as answer by Darin Smith MS Tuesday, February 3, 2009 7:50 PM

  Wednesday, January 21, 2009 12:17 AM