Check your motherboard's manual for how to enter BIOS.

@LittleHelper Where can I find the name of my motherboard?

On the motherboard itself.

@LittleHelper Nevermind, found it here: superuser.com/questions/175213/… :)

Also, check your hard drive. I think that's the reason for corrupted files. Try using. CrystalDiskInfo, it's free.

@LittleHelper I figured out the model of my motherboard (MSI G31TM-P35). The manual says that I need to press the <Del> key when the message "Press DEL to enter SETUP" appears on screen. However, I never see this message, and just mashing the DEL-key does nothing (Windows just boots up). Also, what does CrystalDiskInfo do?

It monitors your disk drives. It tells you how healthy is your drive so it's kind-of the first tool to use if you suspect your drive for failing.

Which parameters did you use to run chkdsk? Also, here's a related question: How to Repair Corrupt System Files from a Installation Disc

@and31415 I believe I provided no extra parameters to chkdsk.

@JSQuareD Then run it again like this for a more thorough test: chkdsk %systemdrive% /r

So you two are afraid of loosing Windows file integrity after the crash?

@LittleHelper Well, I figured something's gotta be wrong. And since SFC reported corrupt files... Anyway, if this CHKDSK ever finishes (it seems to be stuck at 11%), I'll try installing CrystalDiskInfo.

@and31415 CHCKDSK has been stuck at 11% for the past hour.. Any thoughts on that?

@and31415 The CHKDSK required locking the drive, which required executing the program on startup. All I see is the Windows 8 icon, the text "Scanning and reparing drive (C:): 11% complete", and the spinning-dots-busy-icon.

@JSQuareD Okay, disregard my previous comment. I forgot that in Windows 8 the technical details are stripped out when chkdsk is run during the startup phase. How big is the disk? Keep in mind that using the /r parameter will make the disk checking utility perform extra tests, including the available free space. The whole process might therefore take a while; leave it running and report back.

@and31415 about 700 Gigs, about 500 of which is in use.

@and31415 Alright, checking finally finished (I think it just jumped from 11 to a 100 at some point). You can see the log here: pastebin.com/1Kcyu21i

possible duplicate of Windows cant repair even with sfc /scannow

@JSQuareD The chkdsk utility found some minor issues, and it was able to repair everything successfully. What's the exact disk model? As for the corrupted file, it's called CNBJ2530.DPB and it's part of the Canon printer drivers bundled with Windows. Follow the step outlined in the question magicandre1981 linked, then run sfc again to check whether the file got fixed.