I did a bit of research into this KB article. Looks like it also affects people with MSE and McAfee and other flavours of Norton, not just SEP.
The update replaces the win32k.sys so clearly its either corrupted or some other. SEP does not interfere with win32k.sys at all.
There's been historic issues with some Kernal level drivers released from MS:
http://support.microsoft.com/kb/2567053
http://blogs.technet.com/b/dip/archive/2011/10/12/win2003sp2-stop-0x8e-in-win32k-xxxredrawwindow-0x4c.aspx
http://www.symantec.com/docs/TECH181336
My opinion is that it's not SEP causing the issue.