Comment 15 for bug 990364

Hard to say at the moment.
In both cases the crash stack looks absolutely the same:

nt!KiDeliverApc+0x66
hal!HalpApcInterrupt+0xc5
hal!HalRequestSoftwareInterrupt+0x3b
win32k!RawInputThread+0x625
win32k!xxxCreateSystemThreads+0x60
win32k!NtUserCallOneParam+0x23
nt!KiFastCallEntry+0xf8

Try reproducing the problem with Kernel
memory dump option turned on instead of
minidump. In this case it will be possible
to extract more useful information.

Vadim.