First Custom Build....BSOD errors and flickering screen

Hi,
Well this one also will go up to 4 monitors and only requires a 350watt power supply
It does need a direct 6 pin power cable though
EVGA - Products - EVGA GeForce GTX 950 SSC GAMING ACX 2.0 - 02G-P4-2957-KR

EVGA - Product Specs - EVGA GeForce GTX 950 SSC GAMING ACX 2.0

fwiw evga does not charge sells tax :)
These are new cards so if you search ebay or even amazon... you might get lucky and of course black Friday is just around the corner too

Hi,
Well you have been trying to use 3 monitors with a card only supporting 2 and errors following so I'm not a BSOD dude though
I'll post that new log and ask for insight :)

I don't know if others have this to, but I can't trust the dumps

Code:

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`032a0730
Debug session time: Mon Nov 16 22:20:27.657 2015 (UTC + 1:00)
System Uptime: 0 days 0:52:54.233
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols

For me, this started to happen from the dumps of 13th this month.
There are some things that could cause this.

• symbol problems, I doubt this is causing it.
• hardware problem,
• counterfeit installation, I can't say for 100% but I don't think this a cause.
• malware
• Microsoft server down for downloading the symbols, rare but happens, definitely not the cause as this wouldn't explain why I can load from others their dumps from the same period
• other un-explained behavior.

Is there anything you have done, installing, downloading or something between the 10th and 13th?

Diagnostics Test

 Malware scan

Please run a threat scan with Malwarebytes*, a full scan with your AV, scan your system with Adwcleaner, Kaspersky TTDSKiller, ESET Online Scanner and SuperAntiSpyware

   Note

*(Uncheck trial version in the installation process)

Working fine for me most recent two are here

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {fffffa8007042870, fffffa800b0bbe90, 1, 1}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+28750 )

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

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

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: fffffa8007042870, Object type of the object whose reference count is being lowered
Arg2: fffffa800b0bbe90, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0000000000000001, Reserved
	The reference count of an object is illegal for the current state of the object.
	Each time a driver uses a pointer to an object the driver calls a kernel routine
	to increment the reference count of the object. When the driver is done with the
	pointer the driver calls another kernel routine to decrement the reference count.
	Drivers must match calls to the increment and decrement routines. This bugcheck
	can occur because an object's reference count goes to zero while there are still
	open handles to the object, in which case the fourth parameter indicates the number
	of opened handles. It may also occur when the object’s reference count drops below zero
	whether or not there are open handles to the object, and in that case the fourth parameter
	contains the actual value of the pointer references count.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000314e2ad to fffff800030ccc40

STACK_TEXT:  
fffff880`02fff7d8 fffff800`0314e2ad : 00000000`00000018 fffffa80`07042870 fffffa80`0b0bbe90 00000000`00000001 : nt!KeBugCheckEx
fffff880`02fff7e0 fffff880`1103a750 : 00000000`00000020 fffff880`05d410e8 fffffa80`0b0bbe90 00000000`00006700 : nt! ?? ::FNODOBFM::`string'+0x4884a
fffff880`02fff840 00000000`00000020 : fffff880`05d410e8 fffffa80`0b0bbe90 00000000`00006700 fffff880`02fdbf40 : atikmdag+0x28750
fffff880`02fff848 fffff880`05d410e8 : fffffa80`0b0bbe90 00000000`00006700 fffff880`02fdbf40 00000000`00000022 : 0x20
fffff880`02fff850 fffffa80`0b0bbe90 : 00000000`00006700 fffff880`02fdbf40 00000000`00000022 00000000`00000000 : 0xfffff880`05d410e8
fffff880`02fff858 00000000`00006700 : fffff880`02fdbf40 00000000`00000022 00000000`00000000 fffff880`1103c7d4 : 0xfffffa80`0b0bbe90
fffff880`02fff860 fffff880`02fdbf40 : 00000000`00000022 00000000`00000000 fffff880`1103c7d4 fffffa80`09d91000 : 0x6700
fffff880`02fff868 00000000`00000022 : 00000000`00000000 fffff880`1103c7d4 fffffa80`09d91000 fffff880`02fe1fc0 : 0xfffff880`02fdbf40
fffff880`02fff870 00000000`00000000 : fffff880`1103c7d4 fffffa80`09d91000 fffff880`02fe1fc0 fffff880`02fff980 : 0x22


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+28750
fffff880`1103a750 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  atikmdag+28750

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55c03174

FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_atikmdag+28750

BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_atikmdag+28750

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x18_corrupt_ref_count_atikmdag+28750

FAILURE_ID_HASH:  {0b404279-c6ae-3f2f-61e6-49b0a5023fb5}

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff88008a35c78, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8000302c7f8, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000001, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b1100
GetUlongFromAddress: unable to read from fffff800032b11c0
 fffff88008a35c78 Nonpaged pool

FAULTING_IP: 
nt!KeEnumerateKernelStackSegments+28
fffff800`0302c7f8 48894508        mov     qword ptr [rbp+8],rax

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff8800331d850 -- (.trap 0xfffff8800331d850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88008a30000 rbx=0000000000000000 rcx=fffffa800ab49060
rdx=fffff8000302c190 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000302c7f8 rsp=fffff8800331d9e0 rbp=fffff88008a35c70
 r8=fffff8800331da90  r9=fffff800031f8300 r10=fffff8800331db90
r11=fffff880033169f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeEnumerateKernelStackSegments+0x28:
fffff800`0302c7f8 48894508        mov     qword ptr [rbp+8],rax ss:0018:fffff880`08a35c78=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000300e260 to fffff80003073c40

STACK_TEXT:  
fffff880`0331d6e8 fffff800`0300e260 : 00000000`00000050 fffff880`08a35c78 00000000`00000001 fffff880`0331d850 : nt!KeBugCheckEx
fffff880`0331d6f0 fffff800`03071d6e : 00000000`00000001 fffff880`08a35c78 fffff880`0331d800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x418a2
fffff880`0331d850 fffff800`0302c7f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0331d9e0 fffff800`0302c794 : 00000000`00000000 00000000`00000003 fffff880`0331db88 fffffa80`0ab49060 : nt!KeEnumerateKernelStackSegments+0x28
fffff880`0331da70 fffff800`0302c738 : 00000000`00000000 00000000`00000088 00000000`00000000 fffff800`0301c303 : nt!MmOutPageKernelStack+0x34
fffff880`0331db50 fffff800`030a7f7c : 00000000`00000000 00000000`00000080 fffffa80`06fb0870 fffffa80`06fb0800 : nt!KiOutSwapKernelStacks+0x11c
fffff880`0331dbc0 fffff800`0330db86 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x48
fffff880`0331dc00 fffff800`030650e6 : fffff880`009ee180 fffffa80`06ff9040 fffff880`009f8fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0331dc40 00000000`00000000 : fffff880`0331e000 fffff880`03318000 fffff880`0331d910 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeEnumerateKernelStackSegments+28
fffff800`0302c7f8 48894508        mov     qword ptr [rbp+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeEnumerateKernelStackSegments+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5625815c

IMAGE_VERSION:  6.1.7601.19045

FAILURE_BUCKET_ID:  X64_0x50_nt!KeEnumerateKernelStackSegments+28

BUCKET_ID:  X64_0x50_nt!KeEnumerateKernelStackSegments+28

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_nt!keenumeratekernelstacksegments+28

FAILURE_ID_HASH:  {6375bfa6-b596-224c-12df-242afe189b3e}

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

Note the temps of the GPU when idle and under load and let us know what they are.

Diagnostic test

 GPU TEST

Run Furmark to test your GPU. Furmark tutorial

   Note

Run Furmark for around 30 minutes

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

Looks like I had corrupted symbols. Emptied my symbol folder, loaded the dump and the dump was loaded correctly.
My doubt was incorrect