Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Windows 8.1 on a Dell Latitude E6400 randomly freezing

Dec 20, 2013 10:08PM PST

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 (868Cool 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

Discussion is locked

- Collapse -
Answer
I have a question for you.
Dec 21, 2013 1:49AM PST

Will you "do the work?"

Given the machine details I would prescribe starting with the usual deep cleaning and fresh heat sink compounds to remove what is a typical cause for this troubles. Why I ask is that many seem to want to reload drivers, change settings and reload the OS and may come back with driver version 1.0 is fine but can't seem to do the work we need to on older gear.
Bob

- Collapse -
Thanks!
Dec 21, 2013 6:50AM PST

Oh I'm ready to do the work. At this point I don't have a choice. I found out the fan wasn't running anymore so I'm going to have to buy a new fan and replace it however thank you for the reminder about the heat sink compounds. As respects deep cleaning what specifically should I clean out on the computer aside from blowing out the dust from all the crevices? Your suggestions are much appreciated.

- Collapse -
For me it's as simple as canned air.
Dec 21, 2013 9:43AM PST

I take it to the bench or even outside and give the open machine a good cleaning. Remember to get into the power supply too.

With that done I can see about fresh heatsink compound on all heatsinks that come off.

Failed, vibrating fans are replaced at this time as well. Usually a lot of the issues vanish.
Bob

- Collapse -
Thank you so much
Dec 21, 2013 10:27AM PST

Thank you so much for the quick reply and the tips on what to do. I just need to learn how to say these things (heatsink, heatsink compound, etc.) in Portuguese so I can buy them... LOL... But I deeply appreciate your help!
Chris