Since newyear I can't take snapshots anymore without it crashing my whole computer with BSOD and the text: thread stuck in device driver

Ok I started to dig into that and found out that many people suffer from this from various reasons, so I had to dig deeper into the dmp-file to see what driver that caused the error. I do find the reason to be atikmdag.sys and dxgkrnl.sys where the atik-file is an AMD systemfile and the dxg-file is a microsoft kernel file.
Ok so far so good. Got a little wiser then.
Many people have problems with that atik-file, so there is a solution to expand the atik-file which should solve all problems according to the "experts", but its a process where I havent got a clue about the consequenses and I dont know either if it will work at all on my problem.
Now, I do only get this crash-error in firestorm and in Kitely. I dont get it in other worlds and I dont get it in the singularity viewer, neither in other applications on my computer.
I have my graphic settings on low and draw-distance very low too on firestorm, I have no shadows or any light settings to ruin it. I have not updated firestorm since the last update last year, so I am on 4.7.4 I think its called. I have not changed a thing since last year.
I have taken snapshots with firestorm in SL, GCG and in Inworldz this year, and no crash.
My drivers are up to date, and the atik-file is not a part of the driver so thats probably not the reason.
My computer is a A10-7800 Radeon R7 - 12 compute cores, 3.50 Ghz - 64-bit and 8 GB ram
I am on win 8.1
So something tells me its a firestorm problem plus a Kitely problem - in combination with my computer.
I have to ask this before I do something drastic like twist some vital files and fiffle around in the operating system...
Has anything been updated in Kitely around newyear that could cause this?
Has anyone encountered this error other than me or maybe something similar?
