IMHO there are two important things to know when analyzing a blue screen.
a) As you found out: the PROCESS_NAME: fsgk32.exe
If it cannot directly be associated with a product, a Google search will usually give some hints. You found out F-Secure, which Google also indicates.
b) The type of the problem, which is KMODE_EXCEPTION_NOT_HANDLED
in this case.
This becomes a bit tricky, since there are problems which immediately lead to a blue screen, such as an exception in kernel mode (this one) but there are also other problems, e.g. memory leaks, which can go undetected for a while and then crash later.
In your case, it is an immediate blue screen, so the process name is typically correct. You verified this by uninstalling in safe mode, I assume.
In that latter case (memory leak), the listed process name is not correct and other measures need to be taken. There might be different approaches for delayed crashes. I use driver verifier, which comes with Windows (Win+R, verifier.exe
). You may want to read about it before using it, since it can be cumbersome to turn it off if results in crashes during boot time.