Comment 9 for bug 1575467

I did wonder if it was a driver issue related to my processor, so that or a kernel issue makes sense. Not sure how to confirm that though. In the additional drivers thingy it says it is using a backport driver for something that i assume is processor related. My understanding was that backport drivers are unstable and should not be used unless absolutely necessary. There was also a processor microcode firmware proprietary driver that was not being used, so i tried it to see if that would fix the problem, it did not.

I will try to do the apport log thing that the automatic script suggested. Hopefully you guy's can figure this out as this is a pretty serious issue. Let me know if you need any more logs. It sounds like the other guy with the same processor as my laptop does also has the same problem.