not in ohio
More likely the BSOD caused them, by abruptly halting the system without a proper file system dismount.
In particular, the bitmap error is likely due to that. Disk I/O is expensive, so the file system keeps some free space in its back pocket for immediate use. That is, a certain amount gets marked as used, but is not immediately added to any file, it's just remembered as available in working memory. The file system can use it as needed. If the system shuts down cleanly, any allocated but unused space gets put back as free. If the system crashes, there's an accounting discrepancy which needs to get cleaned up. Note that 'marked as in use but not actually in any file' is benign; 'not marked as in use but actually in some file' is potentially catastrophic.
They're not serious problems if they got fixed and don't immediately show up again.