BSOD 0x0000003b after upgrade

so a little while ago i bought a new cpu and mobo (see specs) and got everything working but after a while i started getting blue screens so i started doing some tests but never realy got an error so i searched for a solution on the interwebs and found out it could be that the memory is not getting enough voltage so i raised it to 1.6 and i didnt get a bsod for 4-ish days but today i got some wierd issues with my gpu it would stutter in every game but the wierd thing was the fps was fine so i wanted to restart my pc but just when i clicked the shotdown button it gave a bsod the same one i got a few of a couple of days ago but after it gave an bsod i restarted it did the same stuttering thingy again so i installed a gt520 and guess what issue stoped and then i reinstalled my 560ti and stuttering was gone so... i have no idea
oh and i already reinstalled win becaus of a personal fck up
and temps are definetly not a problem
specs:
intel xeon 1230v3
gigabyte ga-z87-d3hp bios version:f6
asus 560 ti cu1
2x crusial balistix sport 2gb 1333mhz 2x kingston 2gb 1333mhz
samsung 840 serie
wd 1tb blue
ocz fatality 550w (painted white)

https://www.wetransfer.com/downloads...7184650/ed5144
this is the file from that programm that i had to use to get info

Arc said:

Dont host files externally. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

but i cant opload the file its 80mb's big or something

Arc said:

A minidump will be needed.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, post it following the Blue Screen of Death (BSOD) Posting Instructions.

i did do the analyze thingy and got this out of it

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: win32k

FAULTING_MODULE: fffff80002c06000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.

FAULTING_IP:
win32k!BRUSHOBJ_hGetColorTransform+3ac16
fffff960`002bc9e2 488b4808 mov rcx,qword ptr [rax+8]

CONTEXT: fffff88006612100 -- (.cxr 0xfffff88006612100;r)
rax=000000080000004d rbx=fffff900c338cad0 rcx=fffff900c23f88b8
rdx=0000000080002300 rsi=fffff900c23f88b8 rdi=fffff900c338cb68
rip=fffff960002bc9e2 rsp=fffff88006612ae0 rbp=0000000003121c93
r8=0000000003121c93 r9=0000000800000055 r10=0000000000000000
r11=fffff88006612b08 r12=fffff900c0131010 r13=0000000080002300
r14=0000000009693540 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!BRUSHOBJ_hGetColorTransform+0x3ac16:
fffff960`002bc9e2 488b4808 mov rcx,qword ptr [rax+8] ds:002b:00000008`00000055=????????????????
Last set context:
rax=000000080000004d rbx=fffff900c338cad0 rcx=fffff900c23f88b8
rdx=0000000080002300 rsi=fffff900c23f88b8 rdi=fffff900c338cb68
rip=fffff960002bc9e2 rsp=fffff88006612ae0 rbp=0000000003121c93
r8=0000000003121c93 r9=0000000800000055 r10=0000000000000000
r11=fffff88006612b08 r12=fffff900c0131010 r13=0000000080002300
r14=0000000009693540 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!BRUSHOBJ_hGetColorTransform+0x3ac16:
fffff960`002bc9e2 488b4808 mov rcx,qword ptr [rax+8] ds:002b:00000008`00000055=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff960002677bd to fffff960002bc9e2

STACK_TEXT:
fffff880`06612ae0 fffff960`002677bd : 00000000`00000000 00000000`03121c93 00000000`038df7f0 fffff900`c0131010 : win32k!BRUSHOBJ_hGetColorTransform+0x3ac16
fffff880`06612b10 fffff960`0028a969 : 00000000`00000001 fffff880`06612c60 00000000`038df7f0 00000000`000066b7 : win32k!EngSetPointerShape+0x21c5
fffff880`06612b60 fffff800`02c77153 : fffffa80`0935ca00 fffff880`06612c60 00000000`0043e000 fffffa80`093cd0b0 : win32k!BRUSHOBJ_hGetColorTransform+0x8b9d
fffff880`06612be0 000007fe`ff9c4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x3a43
00000000`038df728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`ff9c4efa


FOLLOWUP_IP:
win32k!BRUSHOBJ_hGetColorTransform+3ac16
fffff960`002bc9e2 488b4808 mov rcx,qword ptr [rax+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!BRUSHOBJ_hGetColorTransform+3ac16

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

IMAGE_VERSION: 6.1.7600.16385

STACK_COMMAND: .cxr 0xfffff88006612100 ; kb

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

Arc said:

legopc said:

Arc said:

A minidump will be needed.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, post it following the Blue Screen of Death (BSOD) Posting Instructions.

i did do the analyze thingy and got this out of it

Well done.

When you can follow the post #4, we can proceed further.

heres the dmp file

Arc said:

legopc said:

Arc said:

Well done.

When you can follow the post #4, we can proceed further.

heres the dmp file

Saying it again, Post it following the Blue Screen of Death (BSOD) Posting Instructions. We dont want a stray crash dump only.

done