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: Blank screen after windows screen symbol


15 Sep 2010   #1

Windows 7 Ultimate x64
 
 
Blank screen after windows screen symbol

windows 7 ultimate x64
OEM version (cyberpowerpc)
PC built ~June 2010
returned to OEM for repair to cooling system June July 2010
PC has never booted cleanly
numerous efforts to fix this on my own (clean windows installs, removed OC, latest video drivers, latest bios) nothing has worked so far.
TTT22

My System SpecsSystem Spec
.

16 Sep 2010   #2
Microsoft MVP

 
 

There are at least 45 to 50 updates available for Windows 7. Please update Windows from Windows Update and see if that fixes your issues.

Once that's done, please resubmit the reports and we'll see what we can extract from them then.
My System SpecsSystem Spec
18 Sep 2010   #3

Windows 7 Ultimate x64
 
 

I had installed windows updates ~ 6 or 7 windows installs ago. They seemed to cause even more trouble so I had not been doing windows updates with each subsequent installation. However, I installed them and this time they didn't cause any noticeable problems. Further, the system booted up cleanly once or twice!! Unfortunately it didn't last and the system has gone back to booting to a blank screen. I have attached new reports (from 9 18).
Thanks,
TTT22
My System SpecsSystem Spec
.


18 Sep 2010   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by TTT22 View Post
I had installed windows updates ~ 6 or 7 windows installs ago. They seemed to cause even more trouble so I had not been doing windows updates with each subsequent installation. However, I installed them and this time they didn't cause any noticeable problems. Further, the system booted up cleanly once or twice!! Unfortunately it didn't last and the system has gone back to booting to a blank screen. I have attached new reports (from 9 18).
Thanks,
TTT22

This crash was caused by the systems attempt to reset the video driver. Could be just the driver, or the card itself.

When re-installing the driver you need to completely remove the current one (using the mfr tool if possible) before downloading and installing the new one



Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\091510-12838-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0341a000 PsLoadedModuleList = 0xfffff800`03657e50
Debug session time: Wed Sep 15 21:21:12.576 2010 (GMT-4)
System Uptime: 0 days 0:01:38.684
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800bb2b4e0, fffff8800ffa1cf8, ffffffffc00000b5, a}

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+119cf8 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+119cf8
fffff880`0ffa1cf8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04eee498 fffff880`044e5cbc : 00000000`00000116 fffffa80`0bb2b4e0 fffff880`0ffa1cf8 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`04eee4a0 fffff880`044e5a97 : fffff880`0ffa1cf8 fffffa80`0bb2b4e0 fffffa80`0b734d50 fffffa80`0b71d010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04eee4e0 fffff880`0458cf07 : fffffa80`0bb2b4e0 00000000`c00000b5 fffffa80`0b734d50 fffffa80`0b71d010 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`04eee510 fffff880`045bad7e : fffffa80`ffffffff 00000000`000016dc fffff880`04eee650 fffffa80`0b74d640 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`04eee5f0 fffff880`045a6bf4 : 00000000`00000000 ffffffff`feced300 00000000`00000001 fffff880`045b6e65 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`04eee630 fffff880`045a5bc5 : fffffa80`0b74d540 00000000`00000000 00000000`80000011 fffffa80`0b71d010 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0xcc
fffff880`04eee700 fffff880`045a0827 : 00000000`ffffda2f 00000000`00000113 fffffa80`0b73d230 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x2a1
fffff880`04eee750 fffff880`045a3375 : fffff8a0`00000000 fffff880`0459eb71 00000000`00000000 fffff8a0`01fe6101 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x4c3
fffff880`04eee8a0 fffff880`0459b79d : 00000000`00000000 fffffa80`0c2b8000 00000000`0000000e fffffa80`0b115790 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x14d
fffff880`04eee910 fffff880`045b565d : 00000000`00000000 fffff8a0`01dd1500 fffffa80`00000000 fffffa80`0b11e1f0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd09
fffff880`04eeeae0 fffff880`045b5398 : fffff880`03336140 fffff880`045b4d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04eeecd0 fffff880`045b4e96 : 00000000`00000000 fffffa80`0b0d2570 00000000`00000080 fffffa80`0b71d010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04eeed00 fffff800`0372f166 : 00000000`01e5dd23 fffffa80`0b73cb60 fffffa80`09d4d040 fffffa80`0b73cb60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04eeed40 fffff800`0346a486 : fffff880`03331180 fffffa80`0b73cb60 fffff880`0333c1c0 fffff880`0121b534 : nt!PspSystemThreadStartup+0x5a
fffff880`04eeed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+119cf8
fffff880`0ffa1cf8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+119cf8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c37918e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 Blank screen after windows screen symbol




Thread Tools




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 01:38 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33