As Terry Suggests, we would need more information like the bugcheck code or a
memory dump to confirm if win32k.sys. If you are doing a dump analysis and
seeing win32k.sys in the stack, you need to remember that it is a critical
kernel mode component and is commonly seen on the stack. Based on windows
internals Win32k.sys is responsible for many things like
The window manager, which controls window displays; manages screen output;
collects input from keyboard, mouse, and other devices; and passes user
messages
to applications.
The Graphics Device Interface (GDI), which is a library of functions for
graphics
output devices. It includes functions for line, text, and figure drawing and
for
graphics manipulation.
However if you are a100% sure that win32k.sys or a gdi call is behind the
bugcheck you need to have a look at
http://support.microsoft.com/kb/959252
Even if the symptoms don't match there would be no harm installing that
update.
