BSOD upon skype call dxgkrnl

MrParchy said:

Ok now windows is constantly sending me messages that my windows is not legit so I'll have to buy and install a new copy.

Ok mate now do you know where you can get copies of 7 from now ? because there are some sources available in Oz but they are getting scarce and more expensive. I stocked up some time ago on a few copies and even made some ISO copies from the download site when it was available too. That was before Microsoft in their cynical wisdom took that source away

Just some sites I use are these Microsoft GFC-02733 Windows 7 | Shopping Express Australia Online and Microsoft Windows 7 Home Premium 64bit with SP1 OEM [GFC-02733] - $149.00 : PC Case Gear and Windows 7 Professional OEM 64BIT Service Pack 1 | Centre Com : Best PC Hardware Prices! but you can see the Sydney site is the cheapest.
Whatever you do don't do it online unless you can guarantee the source ie EBay big no no

Ok mate and let us know how it all goes:)

OK Sam have got that mate the problem is another common one that can beanything - have marked it in red in the bug analyse. It does come up asgraphics fault though the .sys marked is a DirectX issue but like I said it canbe anything from an update to a hardware fault.

Code:

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

Code:

MODULE_NAME: dxgkrnl

FAULTING_MODULE: fffff80002863000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAULTING_THREAD:  fffffa800892a210

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 fffff800028e3640

STACK_TEXT:  
fffff880`03662d38 fffff880`03ccbf63 : 00000000`000000ea fffffa80`0892a21000000000`00000000 00000000`00000000 : nt+0x80640
fffff880`03662d40 00000000`000000ea : fffffa80`0892a210 00000000`0000000000000000`00000000 00000000`00000000 : dxgkrnl+0x6f63
fffff880`03662d48 fffffa80`0892a210 : 00000000`00000000 00000000`0000000000000000`00000000 fffff880`03ccbe28 : 0xea
fffff880`03662d50 00000000`00000000 : 00000000`00000000 00000000`00000000fffff880`03ccbe28 fffff800`02820028 : 0xfffffa80`0892a210


STACK_COMMAND:  .thread 0xfffffa800892a210 ; 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

I think we might go with the fix mentioned in a previous post to start withand that is to uninstall the CCC and use just to driver for that card. Problem is I cannot find a driver just for that card it only comes with the CCC SAPPHIRE Technology

Hi, I'm back from my holiday. I don't fully understand what you're asking me to do. I've followed your link and I've uninstalled my driver and I'm installing the one I found through your link now.
My motherboard has on-board graphics, can that be used to narrow down the problem at all?

Sorry late reply well alls well that ends that way eh? I think the reinstall of the driver has done it - typically when you plug in a GPU the onboard graphics is cut out or disconnected for want of a better term.

Anyway it is going that is the main thing as that dxgkrnl.sys is one of a number of dump files that has to be chased down it can be anything from an update (usually listed as that) to any component especially if the component is one dealing either graphics in that case it is the DirectX system.