virtualbox.org

Ok well at least that clears that up. Virtualbox is installed to D since my C drive doesn't have a lot of room (SSD).

I'll do a chkdsk d: /f just to be sure there's no file system corruption.

If you are short of space on the C drive then the typical procedure is to install the software there, since that takes very little space - but locate the VMs on the secondary drive. The drive (and folder) for new VMs is configured in File|Preferences|General|Default Machine Folder. Installing the software on a secondary drive does not cause the VMs to be located there.

BuckoA51 wrote:I do chop and change things around a lot (that's what VMs are for, testing right?) At this very moment the DVD drive (on the guest) is on E.

So why don't you just remove the disk or perhaps better the drive to see if something changes?

If you are short of space on the C drive then the typical procedure is to install the software there, since that takes very little space - but locate the VMs on the secondary drive. The drive (and folder) for new VMs is configured in File|Preferences|General|Default Machine Folder. Installing the software on a secondary drive does not cause the VMs to be located there.

Yes that's true, I made sure the VM created its storage on the D drive when setting it up.

Ran Checkdisk on the D drive on the host, it says "Windows has scanned the file system and found no problems. No further action is required.". I started the guest and did a "sfc /scannow" (in the guest) just to be thorough and it did find some damage, that I repaired with dism /online /cleanup-image /restorehealth. After I got a clean bill of health I tried Evernote again but still the blue screen.

So why don't you just remove the disk or perhaps better the drive to see if something changes?

Which disk do you want me to try removing exactly?

BuckoA51 wrote:Ran Checkdisk on the D drive on the host, it says "Windows has scanned the file system and found no problems.

The filesystem only occupies a few MB on the drive, so a filesystem consistency check really doesn't tell you much about the health of the drive. You need to do a thorough scan, and you'll probably have to leave it running all night.

BuckoA51 wrote:Which disk do you want me to try removing exactly?

I wouldn't bother pursuing that avenue. Removing the CD drive from the VM recipe will certainly prevent virtual CD drive errors, but that hardly seems like a long time solution. We need to address the disease, not just the symptoms.

The "disease" is sector errors on the host D drive.

I can run a surface scan in HD Tune if it helps?

I've never used it, so I'm not in a position to say.

What tool would you recommend then?

I used HDDScan and did a full surface read test overnight, 0 bad blocks were found.

Well, the only remaining thing I can suggest is to reinstall VirtualBox, which should repair the VBoxGuestAdditions.iso file, if it has become corrupted - which is the only remaining explanation for virtual CD read errors that I can think of.