locked
An unauthorized change was made to Windows [0xC004D401] RRS feed

  • Question

  • Prologue - What I have done thus far

    I have suddenly started to get a message pop up saying "An unauthorized change was made to Windows". With error code 0xC004D401.

    I did some research and found MGADiag.exe. I ran it and found it produced an invalid license error. I proceeded to reboot, and ran the MGADiag.exe again. This time the license was correct. Whereupon the 0xC004D401 message appeared again. MGADiag.exe again finds that my license is incorrect.

    Upon further research I tried using legitcheck.hta. The validation in progress window pops up, but then complains that my browser is not configured to run the component. And follows up with a Javascript error.

    I have taken screencrops of each window from this process.

    http://www.portalorigin.com/problemdiagram.jpg

    I then came to this forum to post my problem.

     

    Last Thing I Installed

    Avast! Pro Antivirus (latest version)

     

    What I was doing at the time

    Just surfing the internet

     

    Event Viewer

    Warnings (many of them):

    The system has been tampered. hr=0xC004D401

     

    System
    - Provider
    [ Name ] Microsoft-Windows-Security-Licensing-SLC
    [ Guid ] {1FD7C1D2-D037-4620-8D29-B2C7E5FCC13A}
    [ EventSourceName ] Software Licensing Service
    - EventID 1022
    [ Qualifiers ] 32768
    Version 0
    Level 3
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime ] 2010-12-22T07:53:48.000Z
    EventRecordID 5200
    Correlation
    - Execution
    [ ProcessID ] 0
    [ ThreadID ] 0
    Channel Application
    Computer SakuraPC
    Security
    - EventData
    hr=0xC004D401

    Errors (many of them):

    License Activation Scheduler (SLUINotify.dll) failed with the following error code:
    0xC004D401

    - System
    - Provider
    [ Name ] Microsoft-Windows-Security-Licensing-SLC
    [ Guid ] {1FD7C1D2-D037-4620-8D29-B2C7E5FCC13A}
    [ EventSourceName ] Software Licensing Service
    - EventID 8193
    [ Qualifiers ] 49152
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime ] 2010-12-22T07:53:48.000Z
    EventRecordID 5201
    Correlation
    - Execution
    [ ProcessID ] 0
    [ ThreadID ] 0
    Channel Application
    Computer SakuraPC
    Security
    - EventData
    0xC004D401

     

    MGADiag.exe

    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: *****-*****-224FV-YKRR3-HXKX4
    Windows Product Key Hash: QYhIX5DBSL/go4xg/6az4SKl/Zo=
    Windows Product ID: 89587-OEM-7347761-94130
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {53CABEF4-E82C-425A-B036-C93E8F0DB317}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.100218-0019
    TTS Error: K:20101222081544832-M:20101222083528252-
    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 8.0; Win32)
    Default Browser: C:\Users\SakuraKitty\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>{53CABEF4-E82C-425A-B036-C93E8F0DB317}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HXKX4</PKey><PID>89587-OEM-7347761-94130</PID><PIDType>3</PIDType><SID>S-1-5-21-3784282506-3605517420-450863972</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0504   </Version><SMBIOSVersion major="2" minor="5"/><Date>20090714000000.000000+000</Date></BIOS><HWID>4B323507018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0407</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01: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: U1BMRwEAAAAAAQAACAAAAIDl1wEAAAAAYWECAAAAAADgqirYWKHLARhy9171jCizkdIEkQaJZ65ott0HhPRQpUZBHy6PW5ZUHRrqiJNHhE19+Y2/8BEzLid7IPmIgITKmLNv1wD2WLbPvM725bPz4hofj4LRfhvm4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOgBe4wEVRYcHWzat6M07q88GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeug+N9RQbVk7087cAL1kGswJoDx3UvS2bqQZf29WPIyyQneyD5iICEypizb9cA9li2V1xx4Sjbz0/Q228ZaU+oQ+A5JAndldPsNKjMPTVtZSSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDoAXuMBFUWHB1s2rejNO6vPBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

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

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: PAAAAAIABAABAAEAAwACAAAAAgABAAEAona+5jJ/t4OMJmhlRryENJTFQs6N7wqA8vR+uovIHuqsVuqC

    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            071409        APIC1603
      FACP            071409        FACP1603
      HPET            071409        OEMHPET
      MCFG            071409        OEMMCFG
      OEMB            071409        OEMB1603
      OSFR            071409        OEMOSFR
      SSDT            DpgPmm        CpuPm


     

     

    Wednesday, December 22, 2010 8:18 AM

Answers

  • "Knossos" wrote in message news:0a5ea2f7-4021-4d61-b484-153035328d99...

    Prologue - What I have done thus far

    I have suddenly started to get a message pop up saying "An unauthorized change was made to Windows". With error code 0xC004D401.

    I did some research and found MGADiag.exe. I ran it and found it produced an invalid license error. I proceeded to reboot, and ran the MGADiag.exe again. This time the license was correct. Whereupon the 0xC004D401 message appeared again. MGADiag.exe again finds that my license is incorrect.

    Upon further research I tried using legitcheck.hta. The validation in progress window pops up, but then complains that my browser is not configured to run the component. And follows up with a Javascript error.

    I have taken screencrops of each window from this process.

    http://www.portalorigin.com/problemdiagram.jpg

    I then came to this forum to post my problem.

     

     

    MGADiag.exe

    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: *****-*****-224FV-YKRR3-HXKX4
    Windows Product Key Hash: QYhIX5DBSL/go4xg/6az4SKl/Zo=
    Windows Product ID: 89587-OEM-7347761-94130
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {53CABEF4-E82C-425A-B036-C93E8F0DB317}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.100218-0019
    TTS Error: K:20101222081544832-M:20101222083528252-
    Validation Diagnostic:
    Resolution Status: N/A

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

    The highlighted areas indicate the source of your problems
    .

    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:20101222083528252- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010       12      22         0835                  28252 -
     
     
     
    Note: I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Kernel Mode tamper may be resolved as well. But a Kernel Mode Tamper can sometime indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm)
     
     

    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 Dec 22 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for Dec 22
     
    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 Dec 19-21  (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:
     
     
     
     
    Note that Avast has occasionally been known to cause a similar issue - it's not a common one - so uninstalling Avast, and rebooting may solve it. (Run MGADiag afterwards and see if the Tampers have gone or changed). You could then reinstall Avast with a fresh download, or use an alternative AV solution.
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Wednesday, December 22, 2010 6:58 PM
    Wednesday, December 22, 2010 8:55 AM
    Moderator

All replies

  • "Knossos" wrote in message news:0a5ea2f7-4021-4d61-b484-153035328d99...

    Prologue - What I have done thus far

    I have suddenly started to get a message pop up saying "An unauthorized change was made to Windows". With error code 0xC004D401.

    I did some research and found MGADiag.exe. I ran it and found it produced an invalid license error. I proceeded to reboot, and ran the MGADiag.exe again. This time the license was correct. Whereupon the 0xC004D401 message appeared again. MGADiag.exe again finds that my license is incorrect.

    Upon further research I tried using legitcheck.hta. The validation in progress window pops up, but then complains that my browser is not configured to run the component. And follows up with a Javascript error.

    I have taken screencrops of each window from this process.

    http://www.portalorigin.com/problemdiagram.jpg

    I then came to this forum to post my problem.

     

     

    MGADiag.exe

    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: *****-*****-224FV-YKRR3-HXKX4
    Windows Product Key Hash: QYhIX5DBSL/go4xg/6az4SKl/Zo=
    Windows Product ID: 89587-OEM-7347761-94130
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    ID: {53CABEF4-E82C-425A-B036-C93E8F0DB317}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.100218-0019
    TTS Error: K:20101222081544832-M:20101222083528252-
    Validation Diagnostic:
    Resolution Status: N/A

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

    The highlighted areas indicate the source of your problems
    .

    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:20101222083528252- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010       12      22         0835                  28252 -
     
     
     
    Note: I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Kernel Mode tamper may be resolved as well. But a Kernel Mode Tamper can sometime indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm)
     
     

    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 Dec 22 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for Dec 22
     
    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 Dec 19-21  (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:
     
     
     
     
    Note that Avast has occasionally been known to cause a similar issue - it's not a common one - so uninstalling Avast, and rebooting may solve it. (Run MGADiag afterwards and see if the Tampers have gone or changed). You could then reinstall Avast with a fresh download, or use an alternative AV solution.
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Wednesday, December 22, 2010 6:58 PM
    Wednesday, December 22, 2010 8:55 AM
    Moderator
  • I am responding to this thread because I am having the exact same issue AGAIN!

    The interesting part is that it is happening after I reinstalled.

    After a format of C, reinstalling Vista x64 Ultimate:

    Installed:

    1. ASUS Motherboard drivers for Sound, Networking. (never had issues with before).
    2. Installed Nvidia graphics drivers (original drivers from DVD which I know are fine).
    3. English language pack (Vista version is German because I live in Germany).
    4. Ultramon (multiple monitor).
    5. Google Chrome (no problems with before).
    6. ICQ (horrible IM, but relatives use it).
    7. Xfire (an IM for contact with gaming friends).
    8. Dolby Axon (VOIP client, hasn't caused issues before).
    9. Steam (a game downloader client, very popular).
    10. Skype
    11. Winamp
    12. VLC (a popular media player)
    13. AVAST Antivirus (a pretty major firm, really should be compatible with Vista?).
    14. Alcohol 360 (fairly popular, should also be compatible?).
    15. Reboot.
    16. Upgraded Avast to full version.
    17. Error occurred.

    It shouldn't be a virus, with a completely fresh install. That would make no sense.

    Is it possible the error could be caused by hardware faults?

    Wednesday, February 2, 2011 12:16 PM
  • "Knossos" wrote in message news:e5f13dcf-1a0d-4a1a-b177-26a0cc41b79d...

    I am responding to this thread because I am having the exact same issue AGAIN!

    The interesting part is that it is happening after I reinstalled.

    After a format of C, reinstalling Vista x64 Ultimate:

    Installed:

    1. ASUS Motherboard drivers for Sound, Networking. (never had issues with before).
    2. Installed Nvidia graphics drivers (original drivers from DVD which I know are fine).
    3. English language pack (Vista version is German because I live in Germany).
    4. Ultramon (multiple monitor).
    5. Google Chrome (no problems with before).
    6. ICQ (horrible IM, but relatives use it).
    7. Xfire (an IM for contact with gaming friends).
    8. Dolby Axon (VOIP client, hasn't caused issues before).
    9. Steam (a game downloader client, very popular).
    10. Skype
    11. Winamp
    12. VLC (a popular media player)
    13. AVAST Antivirus (a pretty major firm, really should be compatible with Vista?).
    14. Alcohol 360 (fairly popular, should also be compatible?).
    15. Reboot.
    16. Upgraded Avast to full version.
    17. Error occurred.

    It shouldn't be a virus, with a completely fresh install. That would make no sense.

    Is it possible the error could be caused by hardware faults?

    Your earlier post showed a Mod-Auth and a Kernel Mode tamper
    Some versions of Alcohol are known to cause problems with parts of windows - perhaps it also induces a tamper?
    http://support.microsoft..com/kb/931699/ shows the known tamper-inducing apps.
    Note that it can take up to 3 days before the liceninsing system traps a tamper - so anything installed in the three days before notification is suspect.
    I use VLC and Chrome myself - so we can eliminate that :)
     
    Please post a new MGADiag report
     
    I would tend to go for Avast as being the culprit - they've had problems before.
    Uninstall it, run their cleanup tool, and reboot twice (for safety)
    then run MGADiag again
     
    If it's clear, then see what happens if you install the 'upgraded' version cleanly, rather than first going through the free version.
    (post another MGADiag at each stage, so that we can check)
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, February 2, 2011 1:32 PM
    Moderator
  • I ran a system restore point, before AVAST, so both AVAST and Alcohol are now off. We shall see if I have any more issues.
    Wednesday, February 2, 2011 1:46 PM
  • I recently received the same exact error code 0xC004D401. I also ran MGADiag which shows that my license is valid and my copy of Vista is genuine. However; I did observe that we are both using google Chrome. This is the suspect in my humble opinion.
    Wednesday, May 25, 2011 1:47 AM
  • "Curious2k3" wrote in message news:ef6316ce-0ac1-4a00-bee8-c48fa86ed630...
    I recently received the same exact error code 0xC004D401. I also ran MGADiag which shows that my license is valid and my copy of Vista is genuine. However; I did observe that we are both using google Chrome. This is the suspect in my humble opinion.

    Please read the not to users of Avast at the head of the forum index page - it may help...
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, May 25, 2011 8:40 AM
    Moderator