Display/Video Card problems

I'm not sure if my display is ruined or if I'm having video card problems. My display on my laptop stopped working recently, and I've used an external monitor as a workaround. I've tried everything to get the laptop monitor working. It does give a brief flicker when first powered on. I've tried reseating the RAM, holding a flashlight to the display, reinstalling coin cell battery, etc. My problems may have been caused by some extreme power surges my house had a while back. Whenever the external monitor gets unpluuged accidentally in certain programs I end up with the blue screen of death. These are the error codes I get. Can anyone make any sense of this and diagnose my problem?

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 3d
BCP1: FFFFF88002FF3CB0
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: FFFFF88003E4035B
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020711-26785-01.dmp
C:\Users\User\AppData\Local\Temp\WER-86549-0.sysdata.xml

Thanks...

 

Hey Fortozs,can you zip the dump file and upload it as an attachment with your next post or you can debug it yourself,if there are more than one upload the latest two and post your OS.

http://forums.majorgeeks.com/showthread.php?p=1418737#post1418737

 

Thanks. Here is the dump file. I have Windows 7 pro.

 

Ok, certainly looks like a display driver or hardware issue.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\RoLY\Desktop\020711-20888-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a12000 PsLoadedModuleList = 0xfffff800`02c4fe50
Debug session time: Tue Feb  8 00:13:17.316 2011 (UTC + 0:00)
System Uptime: 0 days 0:06:41.688
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8003eea4e0, fffff88003c1c7f0, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
[B]Probably caused by : igdkmd64.sys[/B] ( igdkmd64+177f0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[B]VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.[/B]
Arguments:
Arg1: fffffa8003eea4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c1c7f0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
igdkmd64+177f0
fffff880`03c1c7f0 4889542410      mov     qword ptr [rsp+10h],rdx

DEFAULT_BUCKET_ID:  [B]GRAPHICS_DRIVER_TDR_FAULT[/B]

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02e429c8 fffff880`042e5ef8 : 00000000`00000116 fffffa80`03eea4e0 fffff880`03c1c7f0 00000000`00000000 : nt!KeBugCheckEx
fffff880`02e429d0 fffff880`042e5c7f : fffff880`03c1c7f0 fffffa80`03eea4e0 fffffa80`03c36d50 fffffa80`051f3010 : [B]dxgkrnl!TdrBugcheckOnTimeout+0xec[/B]
fffff880`02e42a10 fffff880`0438cf07 : fffffa80`03eea4e0 00000000`00000000 fffffa80`03c36d50 fffffa80`051f3010 : [B]dxgkrnl!TdrIsRecoveryRequired+0x21f[/B]
fffff880`02e42a40 fffff880`043b6b75 : 00000000`ffffffff 00000000`000063e7 00000000`00000000 00000000`00000002 : [B]dxgmms1!VidSchiReportHwHang+0x40b[/B]
fffff880`02e42b20 fffff880`043b52bb : 00000000`00000102 00000000`00000000 00000000`000063e7 00000000`00000000 : [B]dxgmms1!VidSchiCheckHwProgress+0x71[/B]
fffff880`02e42b50 fffff880`043882c6 : ffffffff`ff676980 fffffa80`051f3010 00000000`00000000 00000000`00000000 : [B]dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb[/B]
fffff880`02e42bf0 fffff880`043b4e7a : 00000000`00000000 fffffa80`051d64f0 00000000`00000080 fffffa80`051f3010 : [B]dxgmms1!VidSchiScheduleCommandToRun+0x1da[/B]
fffff880`02e42d00 fffff800`02d26c06 : 00000000`fffffc32 fffffa80`051d5a10 fffffa80`036cb040 fffffa80`051d5a10 : [B]dxgmms1!VidSchiWorkerThread+0xba[/B]
fffff880`02e42d40 fffff800`02a60c26 : fffff880`009e7180 fffffa80`051d5a10 fffff880`009f1f40 fffff880`01251534 : nt!PspSystemThreadStartup+0x5a
fffff880`02e42d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
igdkmd64+177f0
fffff880`03c1c7f0 4889542410      mov     qword ptr [rsp+10h],rdx

SYMBOL_NAME:  igdkmd64+177f0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

[B]IMAGE_NAME:  igdkmd64.sys
[/B]
DEBUG_FLR_IMAGE_TIMESTAMP:  4aba7591

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

Followup: MachineOwner
---------

I'd head off to the Intel support site and download and install the latest 64-bit drivers for your graphics chip.

Give it a thorough workout then report back, please.

 

The debug points to a a Graphics driver TDR fault "Timeout detection and recovery" this can be caused by anything from software to hardware and a failed module called Igdkm63.sys which is the Intel graphics driver, obviously confirming either there's a problem with the video card or the driver and this is as far as the diagnostic goes.

Since the video card is integrated into the motherboard you can't remove it to try in another computer,you could try another video card driver from intel so go to the manufacturer of your laptop and download the latest integrated video card driver.

Other than that you may have to replace the whole motherboard if it is indeed damaged by a power surge as you say.

EDIT looks like Satrow got there before meBut exactly the same solution really.

 

Thanks guys. I just tried the latest intel 64-bit driver, but still no luck. It looks like something is indeed fried.

 

If you don't see anything but a brief flicker while booting, then it's most likely not driver related. You should at least see bios/post information prior to loading windows. I would say it's a hardware problem.