Repeated BSOD; ntoskrnl.exe and others; power outage induced?

I have (over the last week or two) been getting frequent and random blue screen crashes. There does not appear to be a specific trigger for these, and the frequency can vary from three in less than an hour to one in a several day period. I have also been experiencing random application crashes (specifically, Java-related applications such as Firefox and Eclipse Java IDE). I have included both the data package requested in the posting instructions and a log from one of the Java crashes in case it is informative.

I suspect that the cause is related to power outages. I initially started observing infrequent (perhaps once every few months) crashes after a maintenance worker hit all the breakers in the house and killed the power to my machine. This has recently gotten much worse after a series of thunderstorms caused around five power losses, three of which were in very rapid succession.

Because of this, I suspect that there may be harddrive corruption somewhere. Note that I have a surge protected that is supposed to protect specifically against lightning-related electrical surges, but I can not verify for certain that it actually worked.

According to BlueScreenView, essentially all of the crashes have included some issue with the "ntoskrnl.exe" file, though the exact error code varies. Additionally, sometimes this file is reported as the sole cause, whilst other times it is reported in conjunction with others. The most common (but by no means only) bug check codes are: 0x0000000a, 0x0000001a, and 0x0000001e.

Please let me know if there is any additional information I can provide, and thank you for your time and assistance.

[Edit] - I ran "sfc /scannow" since this was mentioned in a few other threads. It reports:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Looking at this log file, it appears that the problems were centered in "utc.app.json" and "telemetry.ASM-WindowsDefault.json". There do not appear to be any other files listed as not being repairable. Judging by an internet search, this is a common issue and does not seem to be related to blue screens. I have attached the CBS.log file in case it is of use.