Intermittent BSoDs after a power outage, what is going on?

Alright, I am now disregarding any further advice you are giving me. You are flat out WRONG, and I can no longer trust your advice.
WimFSF.sys errors can be caused by a myriad of things, with the most common being an installation problem with windows. NOT only caused by hardware errors. And, the most common cause of "sporadic" problems in electronics is not hardware errors. 90% of the time it is out of date software, or other minor issues. And yes, I think my hardware is all nice and dandy because windows has booted properly multiple times, and all the errors I am getting are pointing to corrupted files.
I am not ruling out the possibility of hardware errors though. Sure, it could be there, but the chance of it being a hardware error is extremely low, especially after I ran commands in cmd that told me I had corrupted system files. So I am doing everything else I can before moving towards hardware errors.

You are also being extremely aggressive for no good reason, you're assuming things about me that are incorrect (i.e. "... you think that Ceramic Capacitors look any different after they've been destroyed by a power overload.") and making accusations when all I am doing is asking for help about my sister's PC.

You want me to ***what?***Paste dump files here?
You know how massive those are, right? If you think my link is malicious, then please provide me with your email, so I can email you the .dmp files.
If you think that .dmp files can be malicious, then I don't know what to tell you.

You're really going to use a quote? On a tech support forum?
If we're going to do that, then I too will use one.

“who wishes to fight must first count the cost”
― Sun Tzu, The Art of War

Next time, please consider your dignity before trying to start an argument online with someone who is seeking help and advice.

I highly recommend rereading my post, as well as taking a look at the dump files, as I think you may have missed some details.

I don't follow links to other websites. If you want me to read your dump reports, post the text they contain instead of acting like you don't know malware, phishing, and other bad behaviors are ridiculously common on webforums and especially on big forums like Microsoft's.

You think that Windows managed to boot one out of several times is proof that all the hardware and specifically the electrical components are just fine and dandy, so you don't have any clue that damaged transistors are the most common cause of "sporadic" problems in electronic devices, and you think all capacitors are the same so you think that Ceramic Capacitors look any different after they've been destroyed by a power overload. You also don't know that WimFSF.sys errors can only be caused by defective hardware, but you're an old hand at the lowest-level of electronics componentry.

I'm going to quote the river guide from, "Without A Paddle," when I say: "Go ahead. Lie to me. I'm not the one who's going to DROWN!"

Andrew,

I know nothing is fried because, like I stated here, "There I tried to repair windows, but it failed to do so. I restarted again, and windows somehow successfully booted up??," windows successfully booted up.

Yes, I do know what it sounds like when a transistor overheats. Yes, I know what blown capacitors look like. My father does own a multimeter, we do not own an oscilloscope though. There is no need to thoroughly test anything though, as there is no visible, audible, or... "smellable" damage, along with a successful boot.

Thank you for reminding me about sfc and chkdsk, I completely forgot those were a thing. They did show some corrupted files, so I will immediately get to work on that, and add to my post if anything changes.

I highly recommend rereading my post, as well as taking a look at the dump files, as I think you may have missed some details.

I don't know how you can be sure "nothing is fried." Do you know what a blown catalytic, wound-film, or ceramic capacitor look like? Do you know what it sounds like when a transistor overheats enough to burn out? Do you own a digital multimeter and oscilloscope, and have you thoroughly tested every circuit and component on the mainboard? Are you aware that EMP can be caused both by "power outage" and also by "power restoration" in everything from the massive transformers in power stations to the tiny transformers in wall-wort blocks, as well as in speakers and microphones and anything with a digital display screen, and that even a small EMP can induce a power surge in a capacitor or transistor several feet away?

If you can get to the Recovery Console, you should run sfc and chkdsk and don't worry about how long it takes. If you can't get to a Recovery Console during regular boot-failure, then you can if you boot from a viable Windows Installation Media whether it is USB or DVD or whatever. If you can't boot from a CD/DVD or a USB, then something very certainly IS fried.

If you can boot and successfully fix any filesystem errors, and the system still won't boot, then you need to disable or remove your installed drivers using the external boot media which worked to run sfc and chkdsk.