Crazy Lines On Screen Leads To BSOD.

You can try going over the steps we did before swapping monitors disabling the GPU, etc.

Graphics card test:
Video Card Stress Test with Furmark

If your temp goes above 90C, stop the test.

Do you have a GPU you can beg, borrow to try out? IT appears your may be bad, I'll have some people look.

Hairbear, do you have or do you have a friend that has a spare card? I would not want you to spend money on a new card if that isn't the problem. If you could try another card and it works OK, that may answer your question. That would be the best test.

Another thing you may try. Download GPUz if you don't have it. Create a folder on your desktop and name it whatever you want. open GPUz and click on the sensor tab. At the bottom of that screen is a check box labeled, log to file, check that. As soon as you check that a navigation box will appear. It wants to know where to put the logs. Navigate to the folder you just created on your desktop and select it. Now, go do whatever you do that makes the computer BSOD or the monitor mess up. As soon as that happens go back to GPUz and uncheck the log to file box. The folder you created will contain almost every measurement possible about your card. If you will go back to just before the BSOD and look, you will see exactly what was going on with your card at that exact moment.

Also, can you tell me what brand and size PSU you have. I would like to know the brand, Wattage and how many Amps on the +12V rail. All of that will be on a tag on the side of the PSU.

Yes it seems to be the Video BSOD again.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\minidump\071813-31824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e44e70
Debug session time: Fri Jul 19 08:04:49.890 2013 (UTC + 6:00)
System Uptime: 0 days 0:09:15.920
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e579010, fffff88004bd0e30, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+13be30 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e579010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004bd0e30, 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: 
nvlddmkm+13be30
fffff880`04bd0e30 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06cc19c8 fffff880`058b1000 : 00000000`00000116 fffffa80`0e579010 fffff880`04bd0e30 00000000`00000000 : nt!KeBugCheckEx
fffff880`06cc19d0 fffff880`058b0d87 : fffff880`04bd0e30 fffffa80`0e579010 fffffa80`0d7bfbc0 fffffa80`0d06a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06cc1a10 fffff880`05957f07 : fffffa80`0e579010 00000000`00000000 fffffa80`0d7bfbc0 fffffa80`0d06a410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`06cc1a40 fffff880`05981b75 : 00000000`ffffffff 00000000`00008a35 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06cc1b20 fffff880`059802bb : 00000000`00000102 00000000`00000000 00000000`00008a35 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06cc1b50 fffff880`059532c6 : ffffffff`ff676980 fffffa80`0d06a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06cc1bf0 fffff880`0597fe7a : 00000000`00000000 fffffa80`0d7bfbc0 00000000`00000080 fffffa80`0d06a410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06cc1d00 fffff800`02f1647a : 00000000`fffffc32 fffffa80`0cc86a10 fffffa80`09d41040 fffffa80`0cc86a10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06cc1d40 fffff800`02c55da6 : fffff800`02df1e80 fffffa80`0cc86a10 fffff800`02dffc40 fffff880`01458ef0 : nt!PspSystemThreadStartup+0x5a
fffff880`06cc1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13be30
fffff880`04bd0e30 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+13be30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

6: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04a95000 fffff880`0557a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 15:06:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

No problem. There will be, usually a tag on the PSU with all the numbers on it. I just need to know the Wattage, Amps on the 12V rail or all the r 12V rails is it has more, and brand. Here is a picture of someone elses rig. You will notice in the bottom left of the computer a box that says Corsair TX850. That means it is a Corsair PSU and the max wattage is 850W. There should be a tag on it that will answer the other question.

Attachment 277168

The tag should look something like this

Attachment 277170

Hairbear said:

essenbe said:

Hairbear, do you have or do you have a friend that has a spare card? I would not want you to spend money on a new card if that isn't the problem. If you could try another card and it works OK, that may answer your question. That would be the best test.

Another thing you may try. Download GPUz if you don't have it. Create a folder on your desktop and name it whatever you want. open GPUz and click on the sensor tab. At the bottom of that screen is a check box labeled, log to file, check that. As soon as you check that a navigation box will appear. It wants to know where to put the logs. Navigate to the folder you just created on your desktop and select it. Now, go do whatever you do that makes the computer BSOD or the monitor mess up. As soon as that happens go back to GPUz and uncheck the log to file box. The folder you created will contain almost every measurement possible about your card. If you will go back to just before the BSOD and look, you will see exactly what was going on with your card at that exact moment.


Also, can you tell me what brand and size PSU you have. I would like to know the brand, Wattage and how many Amps on the +12V rail. All of that will be on a tag on the side of the PSU.

I think I can borrow a friends in the morning. I'll try the GPUz method before I swap as well.

As for the PSU, sorry how exactly do I check that? Like what does it look like. Like I said on the first page, I'm not too familiar with computer stuff! Sorry about that!!