Share via

Dell Latitude E6400 with Windows 8.1 randomly freezing constantly....

Anonymous
2013-12-21T13:56:59+00:00

Hello my name is Chris and I have a Dell Latitude E6400 with a 250GB HD and 4GB of RAM with a Intel Core 2 Duo CPU (p8700 @ 2.53GHz 2.54 GHz)  that is running Windows 8.1 Pro for a 64-bit Operating System. I just recently moved to Brazil and generally my computer has been running fine without problems however over the past month since about the middle of November my computer has been randomly freezing... I've tried rolling back device drivers, looking at error checking and defragmenting, I tried the Windows memory error checker and nothing came up as well... I also tried removing programs that may have caused the problem around the time it started such as Google Hangouts and AVG... While after removing Hangouts I did notice that the computer ran cooler I still have the random freeze ups to where I have to force shut down the computer and do a hard reset. I have been looking in the event viewer and today I found these messages which never showed up before with any of the previous shut downs...

Log Name:      Application

Source:        ESENT

Date:          21-Dec-13 11:30:54 AM

Event ID:      507

Task Category: Performance

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      cdouble

Description:

LiveComm (3920) C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: A request to read from the file "C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb" at offset 3178496 (0x0000000000308000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (56 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">507</EventID>

    <Level>3</Level>

    <Task>7</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-12-21T13:30:54.000000000Z" />

    <EventRecordID>48584</EventRecordID>

    <Channel>Application</Channel>

    <Computer>cdouble</Computer>

    <Security />

  </System>

  <EventData>

    <Data>LiveComm</Data>

    <Data>3920</Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: </Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb</Data>

    <Data>3178496 (0x0000000000308000)</Data>

    <Data>8192 (0x00002000)</Data>

    <Data>56</Data>

  </EventData>

</Event>

I actually have about 52 of these types of messages all very similar with numbers slightly similar within a minute and I am noticing that at other times when the computer freezes I am recieving similar messages... For example this one from earlier in the morning:

Log Name:      Application

Source:        ESENT

Date:          21-Dec-13 9:19:01 AM

Event ID:      507

Task Category: Performance

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      cdouble

Description:

LiveComm (3120) C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: A request to read from the file "C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb" at offset 1941504 (0x00000000001da000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (19 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">507</EventID>

    <Level>3</Level>

    <Task>7</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-12-21T11:19:01.000000000Z" />

    <EventRecordID>48448</EventRecordID>

    <Channel>Application</Channel>

    <Computer>cdouble</Computer>

    <Security />

  </System>

  <EventData>

    <Data>LiveComm</Data>

    <Data>3120</Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: </Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb</Data>

    <Data>1941504 (0x00000000001da000)</Data>

    <Data>8192 (0x00002000)</Data>

    <Data>19</Data>

  </EventData>

</Event>

and this one from the night before:

Log Name:      Application

Source:        ESENT

Date:          21-Dec-13 2:43:14 AM

Event ID:      507

Task Category: Performance

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      cdouble

Description:

LiveComm (8688) C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: A request to read from the file "C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb" at offset 1941504 (0x00000000001da000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (15 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">507</EventID>

    <Level>3</Level>

    <Task>7</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-12-21T04:43:14.000000000Z" />

    <EventRecordID>48409</EventRecordID>

    <Channel>Application</Channel>

    <Computer>cdouble</Computer>

    <Security />

  </System>

  <EventData>

    <Data>LiveComm</Data>

    <Data>8688</Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: </Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb</Data>

    <Data>1941504 (0x00000000001da000)</Data>

    <Data>8192 (0x00002000)</Data>

    <Data>15</Data>

  </EventData>

</Event>

Can anyone give me some advice as to what I need to do or how I can fix this problem? This is my work computer and I need this computer so that I can work from day to day... Please let me know what I can do. Thank you in advance for any and all help that can be rendered in this regard.

Chris J

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

8 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-01-07T20:10:03+00:00

    I apologize for not getting back to you sooner. I tried all three tasks. Also I noticed that I did have Windows Live Mail on the computer and Windows Live Messenger on the computer so I uninstalled them both. Here are the results from three methods you recommended:

    I will let you know if something else happens since I uninstalled Windows Live. I'm also considering wiping my computer clean and starting over by reinstalling Windows. I will keep you posted as to what happens at the end of this week. Thank you very much for your help Anannya!

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2014-01-29T16:45:10+00:00

    Hi,

    As per the Event viewer log, it took a long time for the Operating system to read the file livecomm. This could be a result of faulty or corrupted hardware. Before we can troubleshoot further, I would suggest you to get back to us with the results of the Check disk scan, so that we can help you accordingly.

    If you face any issues with running the check disk, you can try booting the computer in Safe mode and check.

    Please refer to the section "To repair a drive to perform check disk".

    Improve performance by optimizing your hard drive

    http://windows.microsoft.com/en-US/windows-8/improve-performance-optimizing-hard-drive

    Important Note: While performing chkdsk on the hard drive if any bad sectors are found on the hard drive when chkdsk tries to repair that sector if any data available on that might be lost.

    0 comments
  3. Anonymous
    2014-01-25T17:26:25+00:00

    Sorry for the long wait on an update as to how things are going. I just went on a trip to the south of Brazil. I just got back.. (I actually live there now but in my regular city). However before I left things were running perfectly! However when I returned things started to take a turn for the worse again and the freeze ups came back with a vengeance. I am also still receiving these errors in my event viewer:

    Log Name:      Application

    Source:        ESENT

    Date:          25-Jan-14 1:41:03 PM

    Event ID:      507

    Task Category: Performance

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      cdouble

    Description:

    LiveComm (2220) C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: A request to read from the file "C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb" at offset 4456448 (0x0000000000440000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (22 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">507</EventID>

    <Level>3</Level>

    <Task>7</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-01-25T15:41:03.000000000Z" />

    <EventRecordID>51797</EventRecordID>

    <Channel>Application</Channel>

    <Computer>cdouble</Computer>

    <Security />

    </System>

    <EventData>

    <Data>LiveComm</Data>

    <Data>2220</Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049: </Data>

    <Data>C:\Users\Chris\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9af79c0de926efb7\120712-0049\DBStore\livecomm.edb</Data>

    <Data>4456448 (0x0000000000440000)</Data>

    <Data>8192 (0x00002000)</Data>

    <Data>22</Data>

    </EventData>

    </Event>

    I was doing some reading and found that it may have somethings to do with the livecom.ebd file or something like that. But I'm not sure exactly what to do. Can someone give me some tips as to what to do ASAP? Thank you so much to whoever can promptly reply with a solution!

    0 comments
  4. Anonymous
    2014-01-08T08:48:26+00:00

    Hi,

    Thank you for the update. We will look forward for a reply with the issue status.

    0 comments
  5. Anonymous
    2013-12-22T06:49:57+00:00

    Hi Chris,

    This error warnings in the event viewer are related to Mail app crashing.

    Do you have Windows Live Mail installed on the computer?

    Method 1:

    I would suggest you to run the **app troubleshooter** and restart the computer. Check if you are still facing the issues.

    Method 2:

    Run SFC scan on the computer to make sure system files are intact:

    If a Windows Resource Protection (WRP) file is missing or is corrupted, Windows may not behave as expected. For example, some Windows functions may not work, or Windows may crash. The System File Checker tool (SFC.exe) scans for missing or corrupted system files and repairs them.

    **http://support.microsoft.com/kb/929833**

    Method 3:

    Run the DISM tool:

    a. Swipe in from the right edge of the screen, and then tap Search.

    (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.)

    b. Enter command prompt in the search box.

    c. In the list of results, swipe down on or right-click Command prompt, and then tap or click Run as administrator.

    d. In the Administrator: Command Prompt window, type the following commands. Press the Enter key after each command:

    DISM.exe /Online /Cleanup-image /Scan health

    DISM.exe /Online /Cleanup-image /Restore health

    e. To close the Administrator: Command prompt window, type Exit, and then press Enter.

    If the issue still persists, please feel free to get back to us.

    0 comments