Crazy Lines On Screen Leads To BSOD.

[koolkat77]

should I try switching to VGA? Would that possibly stop the BSODs?

Go ahead..

 

[ayoitzyu]

should I try switching to VGA? Would that possibly stop the BSODs?

Go ahead..

Okay that ended up being a terrible idea. Not only was my resolution stuck at minimum, the problem still persisted.

Any other suggestions?

 

[koolkat77]

I think you should try this now:

should I try switching to VGA?

 

[ayoitzyu]

We have scared the PC gremlins away.

They're back ):

It was a good 3-4 weeks before this problem started again. The lines even appear in Safe Mode. I'm not that tech-savvy, but in Safe Mode, I'm not using my video card right? So that eliminates the possibility that my card is dead. (Right? RIGHT? ): I don't want to get a new card).

Same problem each time though STOPx116. Maybe it's a good time to mention that my dad and I share the computer. But in the sense that we have two "hard drives" in the computer. It's kind of hard to explain but to switch back and forth we have to turn it off, hit a switch and turn it back on. I've noticed that the lines/BSODs happen whenever theres a Windows Update. Would that have to do with anything?

I'd upload more dumps but honestly, they're all the same. If you guys want however, I could upload them.

Thanks!!

Also run all tests you didn't have time for four weeks ago. Check all the DVI/VGA cables and sockets on monitor and PC for looseness or breaks.

Hopefully you can borrow a monitor to test and try yours on another PC. That's the only way to be certain the monitor is/is not at fault.
Make sure your time/date is correct too.

I've changed the monitor, but I'm still getting the same problem. Can I run these tests in Safe Mode? I can't seem to last longer than 5-10minutes anymore.

I'm currently using DVI cables, should I try switching to VGA? Would that possibly stop the BSODs?

Date and Time are fine.

My problem is a result of windows 7 not being able to resolve the driver problem right? Hence the "drivers have stopped working" bubble I see every so often before I BSOD. Is there a way to disable windows 7 from trying to resolve and recover the driver?

VGA doesnt work, I can't run tests in Safe Mode since they only use core drivers. Although the lines/tears do appear sometimes on Safe Mode. However they are not severe enough to send my computer into BSOD.

Help please!

 

[Britton30]

Some hardware seems to be at fault here since the lines appear in Safe Mode and with another monitor. The would seem to rule out drivers and software.
Try pulling the GPU and reseating it and cables if any. Sorry if you've done this I didn't take the time to re-re-read the whole thread.
Leave the GPU card out and try onboard graphics if you have it.

 

[ayoitzyu]

Some hardware seems to be at fault here since the lines appear in Safe Mode and with another monitor. The would seem to rule out drivers and software.
Try pulling the GPU and reseating it and cables if any. Sorry if you've done this I didn't take the time to re-re-read the whole thread.
Leave the GPU card out and try onboard graphics if you have it.

No problem, I'm grateful as it is to have you guys here anyways.

I just went to Best Buy to have them diagnose my problem, they tld me it was the cause of a virus and that they'd get rid of it for me for $189. I told them I'd handle the problem myself. My question is: Is a virus powerful enough to cause lines/tearing AND bsod?

Also, does disabling the card via Device Manager work the same way as taking out my card? If it's not I'll try taking out the actual card.

 

[Britton30]

The Geek squad isn't geeky at all. For their fix you'd have lost your data and had a clean install, it's the only thing they know.

I don't think a virus would do this, but I could be wrong. You can try disabling the card in DV then attach the monitor to the board video.

you could try running this, it's fairly good.
http://www.eset.com/me/home/products/online-scanner/

 

[ayoitzyu]

The Geek squad isn't geeky at all. For their fix you'd have lost your data and had a clean install, it's the only thing they know.

I don't think a virus would do this, but I could be wrong. You can try disabling the card in DV then attach the monitor to the board video.

you could try running this, it's fairly good.
Free ESET Online Antivirus Scanner | Online Virus Scan | Virus Scanner

I just reformatted my computer, everything's fine for now. Maybe it really was just a virus. I'll update if anything goes wrong, but for now everything's pretty smooth.

Thanks for the help!

 

[Britton30]

Good news! Anything new just post back to this thread, if it's the same problem.

 

[ayoitzyu]

Hello!

It's been about 7-8 months since this topic, and unfortunately the problem has arisen again. I tried reformatting my computer since it worked last time. It however, has not worked this time around. I'm still getting the same STOPx116 bsod as before.

My specs have not changed. I'm still using Speccy to check temps: They usually hover around 50 degrees celsius on idle and rise to 60-ish under load. I installed Riva Tuner to increase my fan speeds(I have them at 60%-75%). It doesnt seem like my gpu is overheating. I could upload the minidumps again but they're the same as before.

Has my card died?

 

[Britton30]

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.

 

[ayoitzyu]

I've tried it ):

Its pretty much the exact same as before minus the fact that reformatting it does not solve the problem. However I noticed that this time it would never lead to an actual bsod. It only happened once; now its kinda like it hiccups and tears but only momentarily. Ctrl+Alt+Dlt would temporarily fix the problem for maybe 5-10 minutes. Then in would start all over again. Not sure what this means but I thought I'd tell you anyway.

Thanks for the reply!

Edit: Just noticed the link to a test, i thought it was apart of your sig haha.. I'll try it right now!

Edit 2: Nevermind, it results in BSOD. I cant even get to the download. My temps were around 40-something at the time of the tearing. Here's the dump for the latest bsod. It'll probably tell you the same information though. Is it possible for a windows update to cause this? I noticed it only started since the update that came out like a day or two ago. I would rollback, but I reformatted my PC so it'd be back to factory defaults again.

 

[Britton30]

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

 

[ayoitzyu]

Damn... I'll try to look around. If anything I'll take apart a really old computer I own.

Thanks though!

Edit: Yep I'm almost 100% positive its a broken card. I reformatted it and it BSOD'd on me almost instantaneously.

 

[essenbe]

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.

 

[koolkat77]

Yes it seems to be the Video BSOD again.

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

 

[ayoitzyu]

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!!

 

[ayoitzyu]

Sorry for the double post.

Here's my sensor log, I didn't even do anything to cause the BSOD, I was trying to download the video card tester to try and re-create it but before I even finished downloading it happened. However this time it recovered itself so I was able to save the log. Unfortunately I BSOD-ed about 30 seconds after.

I'm guessing the problem occurs at the fourth-last line? When my load goes to 59% which doesn't even make any sense because I had only a browser running.

I'll try borrowing my friends card later in the day.

 

[essenbe]

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.

View attachment 277168

The tag should look something like this

View attachment 277170

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!!

 

[ayoitzyu]

I understand what to look for from your example but I have no idea what I'm looking for here. Help please!

Edit: Nevermind! I found it. I'll upload specs in a bit

Not sure what I'm looking for so heres a picture! Also do the sensor logs give any information regarding the situation?