BSOD upon skype call dxgkrnl

Ok Sam have got behind in answering mate and am trying to catch up will go back over the sruff again - so I am guessing you have BSOD's? If so mate post them on to us.
John

No mate I was just wondering if there have been more dumps since the last ones you sent .

I am still seeing a graphics driver fault and I am now wondering if the Furmark test should be run at least it will not do any harm.
http://www.carrona.org/furmark.html just reseat the card before you do it.

Hmm sorry for late reply myself Sam been on crappy shifts and these are the dumps from 27th Sept I was just wondering if you had any further blueys.
So if I am reading it right the card is working ok?

You still have some problem devices in msinfo32 though and I think they are just the drivers for the USB ports see pic which I think I may have sent earlier - just have got a lot on at the moment.

Ok Sam no need for apologies mate have been crook with my back and haven't had much to do on the forum until today.

What I might suggest is that you reinstall Skype and before you do after unistalling run these again

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

https://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2 (insafe mode is a wise way to go)



then these

http://www.superantispyware.com/

https://www.malwarebytes.org/lp/sem/5/?gclid=CJTmq6iGpscCFYqCvQodbfMN1A(free version and untick the trial option when it comesup

http://www.bleepingcomputer.com/download/adwcleaner/

ADW download from bleeping computerdelete any rubbish found with the malware scans

(Anyone running Kasperskyinternet security will find it rants about ADW - ignore it or disable Kasperskywhile running ADW)
just as a precautionary move.

Ok Sam same old same old it seems

Code:

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
FAULTING_MODULE: fffff80002c51000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:  55c01884
FAULTING_IP: 
atikmpag+ccac
fffff880`03c3fcac 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
STACK_TEXT:  
fffff880`04bf2818 fffff880`03d38134 : 00000000`00000116 fffffa80`08ff9010 fffff880`03c3fcac 00000000`00000000 : nt+0x74200
fffff880`04bf2820 00000000`00000116 : fffffa80`08ff9010 fffff880`03c3fcac 00000000`00000000 00000000`00000002 : dxgkrnl+0x5d134
fffff880`04bf2828 fffffa80`08ff9010 : fffff880`03c3fcac 00000000`00000000 00000000`00000002 00000000`00000018 : 0x116
fffff880`04bf2830 fffff880`03c3fcac : 00000000`00000000 00000000`00000002 00000000`00000018 00000000`00000000 : 0xfffffa80`08ff9010
fffff880`04bf2838 00000000`00000000 : 00000000`00000002 00000000`00000018 00000000`00000000 fffff880`03d37e3e : atikmpag+0xccac
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
atikmpag+ccac
fffff880`03c3fcac 4883ec28        sub     rsp,28h
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  atikmpag+ccac
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
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
---------

suggested fix uninstall CCC and use only the graphics device driver and this one which again is I am guessing tied in with the previous dump - it does come up with being linked to an update too

Code:

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: dxgkrnl
FAULTING_MODULE: fffff80002c02000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c
FAULTING_THREAD:  fffffa8008f83760
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0xEA
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff88003ccbf63 to fffff80002c76200
STACK_TEXT:  
fffff880`020ccf48 fffff880`03ccbf63 : 00000000`000000ea fffffa80`08f83760 00000000`00000000 00000000`00000000 : nt+0x74200
fffff880`020ccf50 00000000`000000ea : fffffa80`08f83760 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl+0x6f63
fffff880`020ccf58 fffffa80`08f83760 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`03ccbe28 : 0xea
fffff880`020ccf60 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`03ccbe28 fffff800`031f0028 : 0xfffffa80`08f83760
 
STACK_COMMAND:  .thread 0xfffffa8008f83760 ; kb
FOLLOWUP_IP: 
dxgkrnl+6f63
fffff880`03ccbf63 ??              ???
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  dxgkrnl+6f63
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  dxgkrnl.sys
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

NB I think we tried this one before with not much of a result?

Personally I am not a fan of AMD stuff switched to NVidia a long time ago because of this going on and have had no problems since but it is your budget and choice of course