Author Topic: New Error  (Read 3784 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
New Error
« on: October 09, 2014, 04:01:30 AM »
I checked the error log when I reinstalled Avast and I saw this error: Log Name:      Application
Source:        Application Error
Date:          10/8/2014 9:40:11 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Applejack
Description:
Faulting application name: mftutil.exe, version: 0.0.0.0, time stamp: 0x542aa1ea
Faulting module name: mftutil.exe, version: 0.0.0.0, time stamp: 0x542aa1ea
Exception code: 0xc0000005
Fault offset: 0x00000000000109f3
Faulting process id: 0x12dc
Faulting application start time: 0x01cfe361f6b28802
Faulting application path: C:\Program Files\AVAST Software\Avast\ng\mftutil.exe
Faulting module path: C:\Program Files\AVAST Software\Avast\ng\mftutil.exe
Report Id: 3489fe1c-4f55-11e4-82f0-40a8f04a4165
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-09T01:40:11.000000000Z" />
    <EventRecordID>17848</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Applejack</Computer>
    <Security />
  </System>
  <EventData>
    <Data>mftutil.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>542aa1ea</Data>
    <Data>mftutil.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>542aa1ea</Data>
    <Data>c0000005</Data>
    <Data>00000000000109f3</Data>
    <Data>12dc</Data>
    <Data>01cfe361f6b28802</Data>
    <Data>C:\Program Files\AVAST Software\Avast\ng\mftutil.exe</Data>
    <Data>C:\Program Files\AVAST Software\Avast\ng\mftutil.exe</Data>
    <Data>3489fe1c-4f55-11e4-82f0-40a8f04a4165</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
I'm on Windows 8.1 64-bit. Could the Data Execution Prevention Always on be causing this problem? Just wondering.
« Last Edit: October 09, 2014, 05:29:25 AM by Prince Winter Flurry »