Secdrv causes BSOD?

Indeed, I don't see any dmp-files either. I tried running V2 again, but still no dmp-files. I wasn't familiar with the V2-tool before going to this forum, but I'm not doing anything differently from the first time (link in the first post), when dmp-files were created.

It was most definitely a BSOD and Windows event logger also has a report of it (attached screenshot). I know it's in Swedish again, but it says "The service SecDrv could not be started because of the following error: The file can't be located.".


Sorry about the language. I also noticed that all the logs were in my local language. I don't see any way to change the settings in V2 though, so not sure how to fix that? I was of the understanding that V2 was the preferred method in this forum, but is there a different tool I could try instead?

The Event means, blocked by Windows 10, which I said post #2.

Attachment 388676

Right. Do you agree that it's this call that crashes the computer? And if it were possible to figure out which app it is that tries to call SecDrv, I could just try to uninstall it? That's where I'm a bit stuck, since I'm not sure how to find what that is.