BSOD - Possible GFX card VRAM?

jaloko

Honorable
Mar 26, 2012
39
0
10,540
SO i have been Experiencing strange issues with my new build.

Some notes - I have ran MemTest and passed with no errors, i will try again.

I have a GTX 980 SC 2.0 , I have been experiencing artifacts, but not in game artifacts, this happens after closing a game, and even sometimes in the bios(Strange thing is i switched from windows 8 to windows 7 and have not gotten the BIOS artifacts), Just like the BSOD im about to post.

I have had 2 BSOD so far, Last BSOD was caused by DWM.exe. This one was caused by CDD.dll and happened after closing Natural Selection 2.

DWM.exe happened randomly. I do not have the DMP for that one though.

Also since going to windows 7 the artifacts have gone from a crazy full screen artifact to lines that can be removed by unplugging the display port and putting it back in.

On windows 8 when i got the artifacts it would sit there for 1 min then restart my whole system, I looked in event viewer and it said my driver had crashed, but i do think the OS was corrupt on my SSD... but why would changing the OS change the artifacts and stop the BIOS artifacts, it makes no sense...?

At this point im wondering if it is my MB or my GFX.

Also i have changed out my PSU, so it cant be that.

Debugged Memory:

Code:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c29f07a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960006ddc51, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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

Page 3ecbfb not present in the dump file. Type ".hh dbgerr004" for details
Page 3ecbfb not present in the dump file. Type ".hh dbgerr004" for details
Page 3ecbfb not present in the dump file. Type ".hh dbgerr004" for details

READ_ADDRESS:  fffff900c29f07a0 Paged session pool

FAULTING_IP: 
cdd!CddBitmapHw::Release+31
fffff960`006ddc51 483b9080070000  cmp     rdx,qword ptr [rax+780h]

MM_INTERNAL_CODE:  0

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94

MODULE_NAME: cdd

FAULTING_MODULE: fffff960006d0000 cdd

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  NS2.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  fffff88009446660 -- (.trap 0xfffff88009446660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c29f0020 rbx=0000000000000000 rcx=fffff900c3621030
rdx=fffffa80126bd060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960006ddc51 rsp=fffff880094467f0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=000000000000a617
r11=fffff88009446810 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cdd!CddBitmapHw::Release+0x31:
fffff960`006ddc51 483b9080070000  cmp     rdx,qword ptr [rax+780h] ds:fffff900`c29f07a0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d0d1e4 to fffff80002c8df00

STACK_TEXT:  
fffff880`094464f8 fffff800`02d0d1e4 : 00000000`00000050 fffff900`c29f07a0 00000000`00000000 fffff880`09446660 : nt!KeBugCheckEx
fffff880`09446500 fffff800`02c8bfee : 00000000`00000000 fffff900`c00bf010 fffffa80`126bd000 fffff800`02e06e80 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`09446660 fffff960`006ddc51 : 00000000`00000000 00001b2c`00000000 0000375d`09446898 fffff900`c311acd0 : nt!KiPageFault+0x16e
fffff880`094467f0 fffff960`000f5080 : 00000000`00000001 fffff900`c00bf010 00000000`00000001 fffff900`c2237cd0 : cdd!CddBitmapHw::Release+0x31
fffff880`09446830 fffff960`000fd4a9 : 00000000`00000000 00000000`00000001 fffff900`c2237cd0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x358
fffff880`09446980 fffff960`000f4920 : 00000000`00001b2c 00000000`00000000 fffff900`c35f6010 fffff960`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`094469e0 fffff960`000f4063 : fffffa80`115c8600 00000000`00000001 fffffa80`126bd060 fffffa80`130dd060 : win32k!GdiProcessCallout+0x200
fffff880`09446a60 fffff800`02f705e1 : fffffa80`115c8660 00000000`00000000 00000000`00000000 fffffa80`126bd060 : win32k!W32pProcessCallout+0x6b
fffff880`09446a90 fffff800`02f49cb8 : 00000000`00000000 00000000`00000001 fffffa80`130dd000 00000000`00000000 : nt!PspExitThread+0x2b1
fffff880`09446b60 fffff800`02c8d153 : fffffa80`130dd060 00000000`00000000 fffffa80`126bd060 fffffa80`0d5e1160 : nt!NtTerminateProcess+0x138
fffff880`09446be0 00000000`77c8017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c8017a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!CddBitmapHw::Release+31
fffff960`006ddc51 483b9080070000  cmp     rdx,qword ptr [rax+780h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cdd!CddBitmapHw::Release+31

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x50_cdd!CddBitmapHw::Release+31

BUCKET_ID:  X64_0x50_cdd!CddBitmapHw::Release+31

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_cdd!cddbitmaphw::release+31

FAILURE_ID_HASH:  {132d52a7-f1ec-2256-9c87-ec1710272818}

Followup: MachineOwner

If anyone can tell me whats going on I would be happy!
 
Solution
You should really update it to 8.1 update 1 if you havent yet. If this is the only time it crashes / with that card I would remove it and use onboard if this has onboard video