Has anyone ran into an issue where Intel Turbo Memory causes an issue with EEPC? I have a Lenovo X61 Tablet that is running Windows 7 64Bit SP1 and has Intel Turbo Memory installed in it. I am getting a Windows Application errors after installing EEPC 6.2.0.296:
Log Name: Application
Source: Application Error
Date: 4/4/2013 2:32:44 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MyComputer.MyDomain.com
Description:
Faulting application name: MfeEpeHost.exe, version: 1.2.0.296, time stamp: 0x4f91db1d
Faulting module name: EpeOpalATASec4Sata.dll, version: 0.0.0.0, time stamp: 0x4f91e579
Exception code: 0xc0000005
Fault offset: 0x000069d8
Faulting process id: 0x764
Faulting application start time: 0x01ce316b27545b0d
Faulting application path: C:\Program Files\McAfee\Endpoint Encryption Agent\MfeEpeHost.exe
Faulting module path: C:\Program Files\McAfee\Endpoint Encryption for PC v6\EpeOpalATASec4Sata.dll
Report Id: 6c01ab26-9d5e-11e2-ac68-001d728c5e05
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="2013-04-04T19:32:44.000000000Z" />
<EventRecordID>2680</EventRecordID>
<Channel>Application</Channel>
<Computer>MyComputer.MyDomain.com</Computer>
<Security />
</System>
<EventData>
<Data>MfeEpeHost.exe</Data>
<Data>1.2.0.296</Data>
<Data>4f91db1d</Data>
<Data>EpeOpalATASec4Sata.dll</Data>
<Data>0.0.0.0</Data>
<Data>4f91e579</Data>
<Data>c0000005</Data>
<Data>000069d8</Data>
<Data>764</Data>
<Data>01ce316b27545b0d</Data>
<Data>C:\Program Files\McAfee\Endpoint Encryption Agent\MfeEpeHost.exe</Data>
<Data>C:\Program Files\McAfee\Endpoint Encryption for PC v6\EpeOpalATASec4Sata.dll</Data>
<Data>6c01ab26-9d5e-11e2-ac68-001d728c5e05</Data>
</EventData>
</Event>
When i did a search for this error I came up with this KB article https://kc.mcafee.com/corporate/index?page=content&id=KB77035&cat=ENDPOINT_ENCRYPTION_FOR_PC_6.2&act... This article mentions a different model of Lenovo and my X61 Tablet is not running a SED (Self encrypting drive) as the article states. But when I changed the name of the file as contained in the kb
"NOTE: Renaming the file EPEOPALATASEC4SATA.dll allows the users to successfully log in." I was able to login to the machine and EEPC activated and started encrypting. My only guess is that when I looked in the Device manager under disk management I found 2 disks. I only expected one disk. I see Disk0 513MB and Disk1 93.6GB. I have attached a screenshot. Would this be caused by turbo memory and is this the cause of the EEPC errors I was seeing prior to changing the name of the .dll file? Thanks in advance.
Message was edited by: kink80 on 4/5/13 10:55:56 AM GMT-06:00Solved! Go to Solution.
It was the Intel Turbo Memory causing the issue. I went into the Intel Turbo Memory Console and disabled both the ReadyBoost and the ReadyDrive and then restarted the system. The 513MB partition was gone from disk management. I then renamed the EPEOPALATASEC4SATA.dll back to the original name and restarted again. This time the machine would let me login and seemed normal although a little slower.
It was the Intel Turbo Memory causing the issue. I went into the Intel Turbo Memory Console and disabled both the ReadyBoost and the ReadyDrive and then restarted the system. The 513MB partition was gone from disk management. I then renamed the EPEOPALATASEC4SATA.dll back to the original name and restarted again. This time the machine would let me login and seemed normal although a little slower.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: