Lockup & Horizontal Lines on Dell E6410 Screen

Almost every entry in your event log seems to be this:

Event[775]:
Log Name: System
Source: SMSvcHost 4.0.0.0
Date: 2012-11-17T17:46:49.000
Event ID: 8
Task: Sharing Service
Level: Error
Opcode: N/A
Keyword: Classic
User: S-1-5-19
User Name: NT AUTHORITY\LOCAL SERVICE
Computer: Arun-Dell
Description:
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
ID: 2168
Source: System.ServiceModel.Activation.TcpWorkerProcess/56716384
Exception: System.ServiceModel.FaultException: The client was unable to process the callback request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from CallbackBehaviorAttribute or from the <clientDebug> configuration behavior) on the client in order to send the exception information back to the server, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the client trace logs.

Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
Process Name: SMSvcHost
Process ID: 1508

Try it: FIX: Smsvchost.exe for the WCF service stops responding when you run a .NET Framework 4-based WCF service

In the mean time I am asking for some more help.

I have requested Saurabh A to have a look at your thread. Hopefully he will guide you in the proper way. He is offline now, but shortly he will be here .... so dont worry. OK? :)

Hi crisscross,

Since the display and motherboard have been replaced already, it does not appears to be a 'hardware issue'. Would like to know if the back cover was also replaced along with the LCD screen. The back cover kit comprises of various cables that connect the screen to the motherboard. Though a remote possibility, I am suspecting one of the cables as the point of failure, rather than the display or the motherboard itself.

Refer to the 'back cover image' to see if you can recollect this part being replaced when the repair took place:



E6410 is built with both variants of motherboard (Integrated or Discrete); please share details of the system that you have.

To isolate 'hardware' as the possible cause of failure, would request you to perform the following steps and capture the findings:
- Try using the notebook with an external display (monitor) and see if the issue persists.
- Allow the system to stay in 'BIOS environment' for some time to check if the 'display problem' is observed there also. To enter BIOS, restart the system and repeatedly tap 'F2 key' at the 'Dell splash screen'; let the notebook stay there to check results.
- Also use the system in 'Safe mode' to see if the issue duplicates itself.

Based on these observations, we are likely to eliminate 'hardware' as the possible cause of failure.

Also confirm if Windows is configured to record the 'crash dump data'. You may want to re-check with the instructions in this tutorial: Dump Files - Configure Windows to Create on BSOD

Also refer to this tutorial if required: Blue Screen of Death (BSOD) Posting Instructions

As 'Arc' stated, please don't worry at all. We will investigate the matter on priority and hopefully, should be able to find the root cause.

Do reply with the findings; will take it forward from there.

Hi Arun,

Thank you for the reply.

If the back panel/LCD were replaced recently, there is a strong likelihood of either a loose physical connection between the cable(s) and the board; or a damaged cable/connector. The fact becomes even more probable as you began facing the 'display issues' only after the parts were replaced.

Do reply if you need any further assistance; would be glad to assist.