Hello, I think it could be the non-legacy GlassWire driver. Indeed the common causes of that error are mostly related to drivers Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE - Windows drivers | Microsoft Learn Moreover another user had the same issue some months ago KERNEL SECURITY CHECK FAILURE 0x139 That user was using 32-bit GlassWire as the post is dated back to March but I guess that since your OS is 64-bit you were using 64-bit GlassWire before reverting to a older version. If this is the case the same error can occur both on 64-bit GlassWire than on 32-bit GlassWire. Maybe both versions use the same non-legacy driver, I would not know.
The “Use Legacy Driver” installation option has been removed in 64-bit GlassWire and some other users had to revert to 32-bit version to use Legacy driver because they had different issues so I wonder why 64-bit GlassWire was released as official version and not as beta version.