Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Crazy Lines On Screen Leads To BSOD.

18 Jul 2013   #31
Britton30
Microsoft MVP

Windows 7 Ultimate X64 SP1
 
 

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



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


My System SpecsSystem Spec
.
18 Jul 2013   #32
ayoitzyu

Windows 7 Ultimate x64
 
 

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.
My System SpecsSystem Spec
18 Jul 2013   #33
Britton30
Microsoft MVP

Windows 7 Ultimate X64 SP1
 
 

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

18 Jul 2013   #34
ayoitzyu

Windows 7 Ultimate x64
 
 

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.
My System SpecsSystem Spec
19 Jul 2013   #35
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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.
My System SpecsSystem Spec
19 Jul 2013   #36
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

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
My System SpecsSystem Spec
19 Jul 2013   #37
ayoitzyu

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by essenbe View Post
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!!
My System SpecsSystem Spec
19 Jul 2013   #38
ayoitzyu

Windows 7 Ultimate x64
 
 

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.
My System SpecsSystem Spec
19 Jul 2013   #39
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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

Quote   Quote: Originally Posted by Hairbear View Post
Quote   Quote: Originally Posted by essenbe View Post
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!!
My System SpecsSystem Spec
19 Jul 2013   #40
ayoitzyu

Windows 7 Ultimate x64
 
 

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?
My System SpecsSystem Spec
Reply

 Crazy Lines On Screen Leads To BSOD.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Screen freezes with red/blue/yellow horizontal lines then BSOD
This normally happens when I first start using the computer for the day. Sometimes when it happens there is a sound to it when it freezes but not always. Once the computer is going good for around 15-20mins then it no longer happens until the next reboot.
BSOD Help and Support
Horizontal White Lines on Screen, Some times bsod when I try log in.
Hello everyone my computer that I built two years ago seems to be having some trouble that started over night. The Problem: When I start up the computer, white horizontal (almost bar code like) lines cover the screen. (Image uploaded). Some times it will bsod when i try log in some times it...
BSOD Help and Support
Wierd lines and colors on my screen and BSOD : 0x00000116
My computer was working normaly 2 days ago, i was just playing some counterstrike and teamfortress, and suddenly i got a blue screen. So i tried to plug out all the cables of the gpu and unplug it from the mobo. Did that like 3 times but it didnt help. Another day passed, and now i got all these...
BSOD Help and Support
screen gets fuzzy lines then freezes and/or bsod
had the same issue awhile back so I did a fresh install of windows 7 ultimate and still getting the random fuzzy screen and bsod without having really installed anything It is really random. I can just surf the net and it happens. I don't have to do anything that stresses the computer. It's late so...
BSOD Help and Support
Help - W7 Install leads to BSOD or WHITE screen.
Man, I'm going nuts! :) I'm trying to install W7x64 onto a custom rig. Parts are a few years old but they're still good, however I'm running into a host of problems. I need some advice as to how to proceed. Here are the relevant specs of my system.... -MoBo: Gigabyte GA-MA69GM-S2H (also...
Hardware & Devices
Restart leads to black screen before windows 7 splash screen
I am not sure what's wrong, but I have uninstall nvidia drivers that gave me problems ie. 257.21, 196.21....etc. I am currently using 195.62. I am certain that it was a VGA driver problem, because it never happened again, till I decided to remove windows internet explorer and it did the black...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:10.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App