Graphics/Display issues after waking from sleep.

Mischief_Managed

Reputable
Dec 18, 2014
7
0
4,510
Hello all, I'm new to the forums and to custom building PC's. This is my first personal project and I knew going in that I might run into some issues due to my inexperience.

To start off, the good thing about my PC is 95% of the time, it functions great. If I can get to the Desktop without any issues I can play games like Far Cry 4, run Pro Tools and other intense software, for hours and hours without any problems BSODing, overheating, or crashing. (some GPU coil whine when playing games, but no louder than the fans!)

I've run Memtest86, EVGA OC Scanner, and other Performance Benchmarks, sometimes for hours and hours, and have never had a hardware failure, Temps are always around 35C or lower when idle and they never go above their respective thresholds. The parts used are listed in the following link...

https://pcpartpicker.com/user/musicman86/saved/WhDQzy

The bad is I've been dealing with multiple issues since I first booted up the computer and installed Windows 8.1. Two of which I haven't been able to resolve.

Initially, upon booting up Windows from Sleep-Mode or from Powered-Off, several problems were typical.

The biggest problem was the display would checkerboard at the Login Screen, and I would have to reset the PC where it would sometimes fix itself. I'll provide a picture for reference. I think this was due to a conflicting BIOS settings in regards to the "initial GPU" source where the Native Intel Graphics and the Dedicated 970 GPU were both active. I have since changed that setting and haven't seen the checkerboard artifacts since.

So that, i think, is resolved thankfully.

The issues I am dealing with at the moment still revolve around the Sleep Mode. Upon waking, sometimes the computer will BSOD, restart, and a dumpfile is created (which I'll post below). This will happen occasionally, and occurs whether I put the PC to sleep while Logged Out or Signed In.

The dumpfile says it has something to do with "nvlddmkm.sys", which is an EVGA 970 Driver, and it might also have something to do with how long the computer has been asleep. Though I'm not entirely sure about that last part.

The second part of this issue is, if I put the computer to sleep while Signed-In and then wake the computer, if it doesn't happen to BSOD, the desktop will show up, icons will be there, but opening any kind of folder or right-clicking anything on the task bar, if I highlight anything at all, it all shows up as black.

This never happens if I Log-Out before putting the PC to sleep.

I have searched online for others with similar problems but couldn't find anything anywhere.

Right-Clicking on the Desktop will show the pop-up options for half a second, but will then black-out.

I can still click on things within the blackness, the mouse will "finger" over a link, but it's just a guess as to what it is...

On the taskbar, it says my Ethernet is Disconnected, but Chrome [eventually] un-blacks itself and I can still browse the internet.

I have a picture for reference.

I have updated windows, my GPU drivers, my Intel Drivers, as well as my BIOS, and am still dealing with these issues.

Anyone else think the blackness and the BSOD's are related, in that they both have something to do with the "nvlddmkm.sys" error? Curious as to what you guys have to say about that...

I've also run maintenance and used WindowsDiagnostics in an attempt to resolve the sleep-mode issue. Didn't work.

I have run clean re-installs of my GPU drivers. I've Changed PCI slots from x16 to x8. So far, none of this has worked for me, I'm not sure exactly what I'm supposed to do and would appreciate some help.

I have linked the two pictures of the Checkerboarding, as well as the Black-outs, and will make a second post for the dump-file reports.

Lastly, would calling EVGA Tech Support be worth trying? I'm starting to wonder if my 970 is messing up, or perhaps they might know what's going on.

Thanks in advance, and sorry for the long post...

Checkerboard:

Black-Out:

As you can see, the Action Center is opened and blacked out. The taskbar pop-up is blacked out. And the start button blacks out when I hover over it with the mouse.
 

Mischief_Managed

Reputable
Dec 18, 2014
7
0
4,510
DUMP FILE REPORT

----------------------------------------------------


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


Loading Dump File [C:\Windows\Minidump\122614-5875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff803`8f018000 PsLoadedModuleList = 0xfffff803`8f2ee370
Debug session time: Fri Dec 26 00:16:21.092 2014 (UTC - 7:00)
System Uptime: 1 days 13:25:07.726
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800b5635294, ffffd00027e60940, 0}

*** 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+77a294 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800b5635294, Address of the instruction which caused the bugcheck
Arg3: ffffd00027e60940, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nvlddmkm+77a294
fffff800`b5635294 488b11 mov rdx,qword ptr [rcx]

CONTEXT: ffffd00027e60940 -- (.cxr 0xffffd00027e60940;r)
rax=0000000000000000 rbx=ffffe00159a00000 rcx=0000000000000000
rdx=0000000000000017 rsi=0000000000000000 rdi=ffffc00101f80eb8
rip=fffff800b5635294 rsp=ffffd00027e61370 rbp=ffffd00027e61470
r8=0000000000000017 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=ffffc0011c9e1500 r13=ffffe001594f4da8
r14=ffffe001594f4da8 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0x77a294:
fffff800`b5635294 488b11 mov rdx,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Last set context:
rax=0000000000000000 rbx=ffffe00159a00000 rcx=0000000000000000
rdx=0000000000000017 rsi=0000000000000000 rdi=ffffc00101f80eb8
rip=fffff800b5635294 rsp=ffffd00027e61370 rbp=ffffd00027e61470
r8=0000000000000017 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=ffffc0011c9e1500 r13=ffffe001594f4da8
r14=ffffe001594f4da8 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0x77a294:
fffff800`b5635294 488b11 mov rdx,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from ffffc0010221a000 to fffff800b5635294

STACK_TEXT:
ffffd000`27e61370 ffffc001`0221a000 : fffff800`b4f8ef5e 00000000`00000074 00000000`00000000 00000000`00000000 : nvlddmkm+0x77a294
ffffd000`27e61378 fffff800`b4f8ef5e : 00000000`00000074 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffc001`0221a000
ffffd000`27e61380 00000000`00000074 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc001`1c9e1500 : nvlddmkm+0xd3f5e
ffffd000`27e61388 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffc001`1c9e1500 ffffd000`27e615a8 : 0x74


FOLLOWUP_IP:
nvlddmkm+77a294
fffff800`b5635294 488b11 mov rdx,qword ptr [rcx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nvlddmkm+77a294

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 548be25d

STACK_COMMAND: .cxr 0xffffd00027e60940 ; kb

FAILURE_BUCKET_ID: 0x3B_nvlddmkm+77a294

BUCKET_ID: 0x3B_nvlddmkm+77a294

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_nvlddmkm+77a294

FAILURE_ID_HASH: {aefee083-2182-cad1-14b8-4d9dc4b00457}

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

0: kd> lmvm nvlddmkm
start end module name
fffff800`b4ebb000 fffff800`b58db000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Fri Dec 12 23:53:17 2014 (548BE25D)
CheckSum: 009E7B4F
ImageSize: 00A20000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4